http://microformats.org/wiki/hproduct-issues#HP2_-_FN_should_be_used_instead_of_N_for_product_title
Why does hProduct use N instead of FN for the title of a product? I
thought that the term that this community has settled on, after an
excruciating amount of debate, was FN?
-- manu
--
Manu
http://microformats.org/wiki/hproduct-issues#HP3_-_BUY_duplicates_functionality_of_PAYMENT_from_hAudio
hProduct seems to create a new term called BUY instead of re-using
PAYMENT. What's the reasoning behind creating the new term vs. using the
one that has already been invented?
-- manu
--
Manu
http://microformats.org/wiki/hproduct-issues#HP7_-_Lots_of_vocabulary_terms.2C_does_the_data_really_back_this_up.3F
There are currently 15 vocabulary terms in hProduct, but some of the
terms don't seem to be backed up in the hProduct analysis[1].
For example, MODEL shows up in 15% of the
http://microformats.org/wiki/hproduct-issues#HP6_-_P-V_seems_like_a_catch-all_for_hProduct
hProduct currently allows the author to use the P-V pattern for anything
that doesn't fit neatly into hProduct. While it is true that this is a
nice way to expand hProduct and see where future versions of
http://microformats.org/wiki/hproduct-issues#HP4_-_Are_all_of_the_formats_for_PRICE_in_hProduct_allowed
The hProduct specification lists the following formats as allowable for
PRICE:
price. optional. floating point number. can be further refined by type
(msrp, regular, sale, clearance),
http://microformats.org/wiki/hproduct-issues#HP5_-_The_format_for_the_contents_of_SHIPPING_are_vague
The definition of shipping is:
shipping:: the class name shipping MAY define the method, timeframe,
and cost associated with shipping the product. MUST be
singular.
I
