Microformats Wiki - User contributions [en]

hlisting-brainstorming

2009-06-29T16:09:56Z

JayMyers: submitting another revised version of hlisting schema changes before posting them to main hlisting page

<h1>listing microformat brainstorming </h1>
This is brainstorming for a [[hlisting]] microformat per the [[process]].

{{TOC-right}}

=== Revised Base Schema Elements (proposed, revised by [[User:JayMyers|Jay Myers]] 16:55, 29 Jun 2009 (UTC)) ===

*hListing (hlisting)
** listing action. optional. one or more tags, suggested set: sell | rent | trade | meet | announce | offer | wanted | event | service
** '''lister.''' required. hCard | (fn || email || url || tel).
** dtlisted. optional. ISO8601 absolute date time.
** dtexpired. optional. ISO8601 absolute date time.
** price. optional. text. [should include a floating-point number with optional ISO currency codes] - see the currency proposal
** item info. optional. (fn || url || photo || geo || adr) | hCard (for person or business).
** summary. optional. text.
** '''description.''' required. text with optional valid XHTML markup.
** item tags. optional. keywords or phrases describing the item being offered, using rel-tag
** permalink. optional.
** availability. optional. text.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** shipping. optional. text. text describing shipping and fulfillment

==== Notes ====

Please see [[hlisting-examples|hListing examples page]] for analysis of 80/20 use case for new attributes availability, condition and shipping. I believe condition should still be considered even though it misses the 80/20 use case mark (71.2% based on current analysis) as it is included in most product-specific data submission services (e.g., Yahoo Product Submit, Google Base).

----

=== Revised Base Schema Elements (proposed) ===

*hListing (hlisting)
** listing action. optional. one or more tags, suggested set: sell | rent | trade | meet | announce | offer | wanted | event | service
** lister. optional. hCard | (fn || email || url || tel).
** dtlisted. optional. ISO8601 absolute date time.
** dtexpired. optional. ISO8601 absolute date time.
** price. optional. text. [should include a floating-point number with optional ISO currency codes] - see the currency proposal
** item info. optional. (fn || url || photo || [[geo]] || [[adr]]) | [[hcard|hCard]] (for person or business).
** summary. optional. text.
** '''description'''. required. text with optional valid XHTML markup.
** item tags. optional. keywords or phrases describing the item being offered, using rel-tag
** permalink. optional.
** availability. optional. text.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** shipping. optional. text. text describing shipping and fulfillment

==== Items removed ====
* version. optional. text.

<div class=discussion>
* +1 I'm tending to agree with the removal of version, as in practice it has not been necessary for either [[hReview]] or [[hListing]].[[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
</div>

* item info. optional. (fn || url || photo || geo || adr) | hCard (for person or business).

<div class=discussion>
* Removal of <code>item</code> seems to be a mistake, as that is used to indicate the item itself being listed. E.g., a nested <code>hProduct</code> would be <code><p class='item hproduct'></p></code>. Removal appears to leave no way to include ''what'' is being listed. --[[User:BenWard|BenWard]] 17:38, 16 April 2009 (UTC)
** +1 completely agreed with Ben Ward's point. Wide use of [[hReview]] in the [[hreview-examples-in-wild|wild]] has shown that having an explicit "item" is both necessary and works in practice. [[User:Tantek|Tantek]] 17:40, 16 April 2009 (UTC)
* Indeed it was a mistake... left it out of my edits. Replaced. [[User:JayMyers|JayMyers]] 21:04, 22 April 2009 (UTC)
</div>

==== Items added ====
<div class=discussion>
* Each of the following should cite the analysis made of real world examples that demonstrates the 80%+ use case need, otherwise, they should not be added. [[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
</div>

* availability. optional. text.
* condition. optional. text. examples: 'new', 'used', 'refurbished'.
* shipping. optional. text. text describing shipping and fulfillment

==== Items changed: ====
* listing action => optional. if omitted, action assumed to be sell
* lister => optional. if omitted, the buyer/seller is assumed to be the site where the microformat exists
<div class=discussion>
* In that case, an algorithm should be provided for how to determine the hCard for the lister, if no explicit lister is given. [[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
</div>

hlisting-examples

2009-06-22T16:33:47Z

JayMyers: math mistake

<h1>Listing Examples </h1>
{{TOC-right}}

This page is '''informative'''.

The purpose of the content on this page is to serve as background for the improvement of the transactional/listing (hListing) microformat. There are examples in the wild, and this page can serve as a supplement for those examples and for experimentation and implementation.

== Editors/Authors ==
(alphabetical)
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

== New Examples ==
If you have implemented hListing on your own page, feel free to add it to the '''top''' of this list. Please be sure to include at least one URL to a page on your site that includes actual [[hlisting|hListing]] markup.

=== Live Product Examples ===

* [http://ottawa.en.craigslist.ca/sys/1135033483.html craiglist]
** Properties: item info, condition, description, price, lister, list date, availability, shipping

* [http://www.cowboom.com/index.cfm cow boom]
** Properties: item info, condition, price, what's included, shipping

* [http://auctions.overstock.com/Sony-HF-10-Pack-60-Minute-HiFi-Audio-Cassette-Tape/Computers-Networking/item/44773540 Overstock auctions]
** Properties: item info, list date, expiriry date, shipping, condition, description

* [http://cgi.ebay.com/4-OCTAVE-WOODEN-MARIMBA-DIRECT-FROM-ARTIST_W0QQitemZ25035963638*6QQcmdZViewItemQQptZLH_DefaultDomain_0?hash=item250359636386&_trksid=p3286.c0.m14&_trkparms=72%3A1205|66%3A2|65%3A12|39%3A1|240%3A1318|301%3A1|293%3A1|294%3A50 ebay]
** Properties: price, shipping, payment options, item info, quantity, condition, origin, product type, description, return policy, payment details

* [http://www.ubid.com/DAVIDOFF+COOL+WATER+for+men+New+in+box+Popular+5+ML+.17+FL.+OZ./a802600100-c0-s9.html ubid]
** Properties: photo, quantity, item info, condition, quantity, shipping

* [http://www.bidz.com/bzJApp/ProductDisplay.action?sid=100&tid=100&auctionId=34170660 bidz.com]
** Properties: price, item info, availability, condition, country of origin, description, shipping

* [http://www.dellauction.com/cgi-bin/ncommerce3/ProductDisplay?prrfnbr=104283039&prmenbr=75267554&aunbr=104629749 dell auctions]
** item info, price, list date, expiriry date, shipping, condition

* [http://astore.amazon.com/httpwwwsusaco-20/detail/B001KW0A3E amazon marketplace]
** Properties: availability, name, manufacturer, price, shipping, shopping cart link

* [http://shopping.msn.com/prices/best-of-esteban/itemid598175900/?itemtext=itemname:best-of-esteban&stext=esteban msn shopping]
** Properties: title, artist, photo, description, condition, price, buy, shipping, seller

* [http://www.shopping.com/xPO-Keurig-Keurig-Special-Edition-B60-Brewer-Coffee-Machine shopping.com]
** Properties: photo, title, rating (aggregate), details, manufacturer, description, seller, shipping, price, condition, availability

* [http://www4.dealtime.com/xPO-DRY_PAK_Dry_Pak_Roll_Top_Dry_Gear_Bags dealtime.com]
** Properties: photo, price range, link, seller, specs, title, shipping, description, availability

* [http://www.pronto.com/GUESS-Kids-Girls-Shoes-Tyler-p_1164738515-PP pronto.com]
** Properties: photo, price, availability, rating, shipping, link,

* [http://musical-instruments.pricegrabber.com/dj-turntables/Pioneer-CDJ-1000MK3-Digital-Vinyl-Turntable/m18215594.html/st=product/sv=title pricegrabber.com]
** Properties: photo, price, rating, description, shipping, tax, seller, condition, availability

* [http://shopper.cnet.com/smartphones/rim-blackberry-curve-8900/4014-6452_9-33485567.html?tag=contentMain;contentBody shopper.com]
** Properties: title, price range, ratings, description, seller(s), seller rating, dtstart, shipping, availability

* [http://www.mysimon.com/9015-11034_8-30883813.html my simon]
** Properties: price range, seller, store rating, availability, price, link, shipping

* [http://www.compuplus.com/i-BellO-AVSC-2123-Contemporary-Tall-Design-Audio-Video-System-BlackCherry-AVSC2123-1034723~.html?sid=5b5f55n09w5lssu compu plus]
** Properties: condition, availability, shipping, price, description

* [http://www.smarter.com/tv-stands/bello-avsc-2123-42-in-glass-tv-stand-brown/pd--ch-3--pi-361211.html smarter.com]
** Properties: seller, price, reviews, availability, condition

* [http://www.nextag.com/The-Tin-Drum-934321/prices-html nextag.com]
** Properties: format, seller(s), seller reviews, condition, availability, price, link, name/title, shipping

* [http://www.epier.com/BiddingForm.asp?1921228 epier.com]
** Properties: bid, reserve, num bids, dtstart, dtend, quantity, shipping, condition, fulfillment details, seller, title

* [http://us.nine.ebid.net/perl/auction.cgi?auction=16097877&mo=auction ebid.net]
** Properties: photo, seller, price, title, quantity, condition, views, location, dtstart, dtend, shipping, payment methods

* [http://www.etsy.com/view_listing.php?listing_id=19974630&ref=fp_feat_2 etsy.com]
** Properties: title, photo, description, shipping, payment methods, price, quantity

* [http://dealspl.us/product/sony-bravia-kdl-46s4100-46-inch-1080p-lcd-tv dealsplus]
** Properties: price, shipping, dtend, description, seller(s), title, availability

* [http://www.petco.com/product/14363/Totally-Ferret-Premium-Food-for-Active-Show-and-Pet-Ferrets.aspx petco.com]
** Properties: price, seller, reviews, shipping, dtends, availability, description

* [http://www.allposters.com/gallery.asp?startat=/getposter.asp&APNum=290796&CID=AC3917B0E4E4452CBC36B60F9B66A923&PPID=1&search=matisse&f=c&FindID=26501&P=1&PP=13&sortby=PD&cname=Henri+Matisse&SearchID allposters.com]
** Properties: price, shipping, related, availability, description

* [http://www.target.com/Britax-Decathlon-Sahara-Convertible-Seat/dp/B000JIWU4W/sr=1-1/qid=1230579365/ref=sr_1_1/179-9254632-8007737?ie=UTF8&rh=k%3Atoddler%20car%20seats%20britax&page=1 target.com]
** Properties: price, quantity, reviews, shipping, availability, shipping info, description

* [http://www.fastforklifts.com/electric-forklift-trucks-electric-forklift-walkie-forklift-xp1229-12.html fastforklifts.com]
** Properties: description, quantity, price, shipping, availability

* [http://www.leotardworld.com/Wiggles-Sparkle-Butterfly-Back-Leotard-p/mw1425-356h.htm leotardworld.com]
** Properties: price, description, availability, shipping, quantity

* [http://www.amazon.com/Nikon-Coolpix-Digital-Camera-Optical/dp/B0011MVWZ8/ref=pd_bbs_sr_1?ie=UTF8&s=electronics&qid=1231272206&sr=8-1 amazon.com]
** Properties: price, availability, shipping, description, ratings, quantity, condition

* [http://www1.macys.com/catalog/product/index.ognc?ID=290741&CategoryID=42212 macys.com]
** Properties: description, rating, shipping, returns, availability, price

* [http://www.lowes.com/lowes/lkn?action=productDetail&productId=132135-444-C14024A&lpage=none lowes.com]
** Properties: price, availability, shipping

* [http://www.homedepot.com/webapp/wcs/stores/servlet/ProductDisplay?storeId=10051&langId=-1&catalogId=10053&productId=100189145 homedepot.com]
** Properties: price, shipping, quantity, availability, ratings

* [http://www.acehardware.com/product/index.jsp?productId=1290429&cp=&sr=1&kw=lathes&origkw=lathes&parentPage=search&searchId=34784674863 acehardware.com]
** Properties: related, price, size, quantity, shipping, availability

* [http://www.walgreens.com/store/product.jsp?CATID=100218&navAction=jump&navCount=0&nug=VPD&skuid=sku359744&id=prod359743 walgreens.com]
** Properties: price, quantity, shipping, availability

* [http://www.appliancewarehousedirect.com/counterdepth-sidebyside-refrigerator-with-glass-shelves-humidity-controls-transition-lighting-external-button-icewater-dispenser-p-18476.html?cPath=3 appliancewarehousedirect.com]
** Properties: price, shipping, warranty, condition, packaging, description

* [http://www.birdbaths.com/bird-baths/resin-bird-baths/portsmouthsolarbirdbathfountain.cfm birdbaths.com]
** Properties: price, savings, rating, shipping, quantity, availability, description

* [http://www.circuitcity.com/applications/SearchTools/item-details.asp?EdpNo=3574573&CatId=1902 circuitcity.com]
** Properties: condition, price, availability, quantity, shipping, description

* [http://www.magersandquinn.com/index.php?main_page=product_info&products_id=1905787&isbn_id=4027890 magersandquinn.com]
** Properties: price, condition, availability, description,

* [http://www.bestbuy.com/site/olspage.jsp?skuId=9015638&type=product&id=1852883 bestbuy.com]
** Properties: shipping, price, description, availability

* [http://www.cduniverse.com/productinfo.asp?pid=1109198&cart=827546365 cduniverse.com]
** Properties: price, availability, shipping, description, format

* [http://www.autozone.com/autozone/catalog/accessories/accProductDetails.jsp?displayName=AirFreshener&itemId=prod63065&navValue=100507&parentId=cat30093&productId=574949&fromString=&itemIdentifier=574949_0_0_&filterByKeyWord=&categoryNValue=&subSubPartId=&subPartId=prod63065&store=3076&skuDisplayName=2pk.StrawberryExtraStrengthHangingAirFreshener&categoryDisplayName=CarCare&_requestid=742334 autozone.com]
** Properties: availability, shipping, quantity

* [http://www.napaonline.com/MasterPages/NOLMaster.aspx?PageId=470&LineCode=BSH&PartNumber=N69487&Description=Fuel+Pump+-+Electric+In-Tank+Type+-+OEM+Equivalent napaonline.com]
** Properties: description, availability, price, shipping, condition

* [http://www.toysrus.com/product/index.jsp?productId=2332387 toysrus.com]
** Properties: description, price, availability, shipping

* [http://www.usedsports.com/category/289/Drivers/listings/437/New-Extreme-Distance-Driver.html usedsports.com]
** Properties: condition, price, quantity, location, shipping, dtends, description, terms

* [http://www.biblio.com/details.php?dcx=166670305&aid=frg biblio.org]
** Properties: price, seller, date published, condition, shipping

* [http://kidzugoodbuy.ecrater.com/product.php?pid=3888669 kugby]
** Properties: price, shipping, availability, condition, payment options, description

* [http://microcenter.com/single_product_results.phtml?product_id=0310220 microcenter.com]
** Properties: condition, price, availability, quantity

* [http://www.amazon.com/Factory-Reconditioned-Bostitch-RN46-1-4-Inch-Roofing/dp/B000F10HWU/ref=sr_1_2?ie=UTF8&s=hi&qid=1243453632&sr=1-2 amazon outlet]
** Properties: price, condition, availability, shipping, quantity

* [http://www.amazon.com/Factory-Reconditioned-Bostitch-RN46-1-4-Inch-Roofing/dp/B000F10HWU/ref=sr_1_2?ie=UTF8&s=hi&qid=1243453632&sr=1-2 louisiana machinery]
** Properties: price, condition, rating, shipping

* [http://product.half.ebay.com/Too-Fat-to-Fish_W0QQtgZinfoQQprZ69582903 half.com]
** Properties: description, condition, price, format, shipping

* [http://www.tradeups.com/ tradeups.com]
** Properties: price, condition, quantity, shipping

* [http://www.itxchange.com i.t. xchange]
** Properties: description, condition, quantity, price, availability, shipping

* [http://discountechnology.com/Dell-E176FP-17-LCD-Flat-Panel-Analog-Monitor?sc=2&category=265 discount technology]
** Properties: description, condition, quantity, shipping, availability

* [http://www.microreplay.com/index.php?main_page=index&cPath=16_27 micro replay]
** Properties: condition, description, warranty, availability

* [http://www.clive.nl/audio-tv/p60-active-filter-unit-project-z60 clive.nl retro computer collections]
** Properties: title, price, condition, availability, shipping

* [http://shopping.lycos.com/product/view/m/88973303 lycos shopping]
** Properties: seller, condition, price, availability

* [http://www.abt.com/product/37181/Apple-MB528LLA.html?utm_source=scpgrabber&utm_medium=sc&utm_campaign=pricegrabber&mr:referralID=67af328a-546b-11de-8327-000423bb4e79 abt.com]
** Properties: availability, description, shipping, price

* [http://store.apple.com/us/product/FB528LL/A?afid=p210|pgbr apple store]
** Properties: title, description, price, shipping, availability, condition

* [http://lycos.pgpartner.com/user_sales_getprod.php?masterid=88973303&lot_id=9449215 the source storefront]
** Properties: price, availability, payment options, shipping, condition, buy

* [http://www.buy.com/prod/schwinn-windwood-26-men-s-cruiser-bicycle/q/loc/17250/206649684.html?dcaid=15890 buy.com]
** Properties: price, shipping, availability, quantity,

* [http://www.prosportsmemorabilia.com/Carolina-Hurricanes---Rod-BrindAmour---2006-Stanley-Cup-Jr-Ticket-Frame-_860780691_PD.html?pgrabber=35-84999 pro sports memorabilia]
** Properties: price, quantity, availability, shipping

* [http://www.techexcess.net/011656-001-proliant-dl380-motherboard-system-board-w-cmos-batt-289554-001.aspx Tech Excess]
** Properties: price, description, condition, quantity,

* [http://www.kitchengourmet.com.au/ kitchen gourmet]
** Properties: title, condition, price, quantity, shipping, description

* [http://stores.channeladvisor.com/thephotospot/Items/ko_1434273_NW_4X?&caSKU=ko_1434273_NW_4X&caTitle=Kodak%20Greeting%20Cards%20%26%20Invitations%20Printing%20Kit%20NEW%204%20PACK the photo spot/channel advisor]
** Properties: title, price, quantity, condition, shipping

* [http://www.pixmania.co.uk/uk/uk/757607/hoover/all_merchant/tc1206001-steam-cleaner.html?state=USE pixmania.co.uk]
** Properties: seller, price, condition, shipping, availability

* [http://www.samedaymusic.com/product--ALEDM5PROKIT same day music]
** Properties: condition, availability, shipping, price, description

* [http://www.onlinesurplus.com/products/prod_details.asp?Tg=1308&Sc=0 online surplus]
** Properties: condition, shipping, quantity, availability, price, description

* [http://www.secondspin.com/music/product-detail.jsp?id=2706699 second spin]
** Properties: availability, quantity, price, condition (implied)

* [http://www.wherehouse.com/music/product-detail.jsp?id=2691046 wherehouse.com]
** Properties: availability, price, condition, description

* [http://www.gamestop.com/Catalog/ProductDetails.aspx?Product_ID=71813 gamestop]
** Properties: shipping, price, condition, availability

* [http://www.bigwords.com/details/book/The_5000_Year_Leap_A_Miracle_That_Changed_the_World/9780880801485/0880801484 big words]
** Properties: condition, seller, description, price, shipping, availability

* [http://www.alibris.com/musicsearch?qwork=400860855&cm_sp=rec-_-mnhome-_-youMightLike&matches=0 alibris]
** Properties: title, condition, format, shipping, availability, price

* [http://www.mastermagnets.com/content/view/22/122/lang,en/ master magnets]
** Properties: title, availability, quantity, description, condition

* [http://yhst-31241655524746.stores.yahoo.net/quicklok-t20-single-x-keyboard-stand--us20.html soundtree audio and music technology solutions]
** Properties: price, description, condition, availability

* [http://ezcafe.com/index.php?main_page=product_info&cPath=4&products_id=7&zenid=1d586a3c214b9f0f354d508ebc178e2e ezcafe]
** Properties: title, price, description, condition, availability, dtstart

* [http://www.holtcat.com/app_used.asp holt cat]
** Properties: manufacturer, price, availability, condition

* [http://www.amhboston.com/index.cfm?event=ProductDetails&CategoryID=48&ProductID=159 american material handling group]
** Properties: condition, size, price, quantity, shipping/delivery, availability

* [http://store.academyofscuba.com/suvydswrcowu.html academy of scuba]
** Properties: price, condition, availability, description,

* [http://www.horseclicks.com/products/lp0mry/ horse clicks]
** Properties: availability, condition, price

* [http://www.siliconsolar.com/used-genlight-fixture-p-17995.html silicon solar]
** Properties: condition, price, quantity, availability

* [http://www.joessports.com/product/index.jsp?productId=3071464&CAWELAID=155516067 joe's sports]
** Properties: price, description, quantity, availability, shipping

* [http://www.amazon.com/gp/product/B000O7I6VE amazon.com]
** Properties: title, price, condition, availability, shipping

* [http://www1.tradetang.com/for-sale/Free_shipping_10pics_Brand_New_2_8_Touch_Screen_8GB_MP3_MP4_Player_2_0M_Video_Camera/110562-1239396.html tradetang.com]
** Properties: price, title, condition, shipping, availability

* [http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=4355391&CatId=2628 tiger direct]
** Properties: price, quantity, condition, availability, shipping

* [http://www.sonystyle.com/webapp/wcs/stores/servlet/ProductDisplay?catalogId=10551&storeId=10151&langId=-1&productId=8198552921665401960 sony/ sonystyle]
** Properties: condition, price, rating, description, availability, shipping

* [http://www.shopping.hp.com/webapp/shopping/product_detail.do?product_code=CC436AR%23ABA&aoid=14655&srccode=cii_10043468&cpncode=22-18868711-2 hewlett packard]
** Properties: price, condition, availability, shipping, quantity

* [http://estore.usa.canon.com/webapp/wcs/stores/servlet/ProductDisplay?catalogId=10051&storeId=10051&productId=156469&langId=-1&parent_category_rn=12056&top_category=12252 canon estore]
** Properties: condition, price, availability

=== Analysis of hListing Research ===

To date, analysis on 87 commerce or product listing sites was performed to represent a wide array of offers. The new hListing proposal adds three elements -- availability, condition, and shipping. The findings up to this point indicate many commerce and product related sites utilizing the proposed hlisting attributes of availability, condition and shipping. The research produced these results for the proposed new attributes:

* Availability (79.1%)
* Condition (71.2%)
* Shipping (82%)

hlisting-examples

2009-06-22T16:26:37Z

JayMyers: adding specific percentages from research

hlisting-examples

2009-06-08T20:54:00Z

JayMyers: updating to 87

hlisting-examples

2009-06-08T20:53:15Z

JayMyers: adding additional product/ transactional samples

<h1>Listing Examples </h1>
{{TOC-right}}

This page is '''informative'''.

The purpose of the content on this page is to serve as background for the improvement of the transactional/listing (hListing) microformat. There are examples in the wild, and this page can serve as a supplement for those examples and for experimentation and implementation.

== Editors/Authors ==
(alphabetical)
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

== New Examples ==
If you have implemented hListing on your own page, feel free to add it to the '''top''' of this list. Please be sure to include at least one URL to a page on your site that includes actual [[hlisting|hListing]] markup.

=== Live Product Examples ===

* [http://ottawa.en.craigslist.ca/sys/1135033483.html craiglist]
** Properties: item info, condition, description, price, lister, list date, availability, shipping

* [http://www.cowboom.com/index.cfm cow boom]
** Properties: item info, condition, price, what's included, shipping

* [http://auctions.overstock.com/Sony-HF-10-Pack-60-Minute-HiFi-Audio-Cassette-Tape/Computers-Networking/item/44773540 Overstock auctions]
** Properties: item info, list date, expiriry date, shipping, condition, description

* [http://cgi.ebay.com/4-OCTAVE-WOODEN-MARIMBA-DIRECT-FROM-ARTIST_W0QQitemZ25035963638*6QQcmdZViewItemQQptZLH_DefaultDomain_0?hash=item250359636386&_trksid=p3286.c0.m14&_trkparms=72%3A1205|66%3A2|65%3A12|39%3A1|240%3A1318|301%3A1|293%3A1|294%3A50 ebay]
** Properties: price, shipping, payment options, item info, quantity, condition, origin, product type, description, return policy, payment details

* [http://www.ubid.com/DAVIDOFF+COOL+WATER+for+men+New+in+box+Popular+5+ML+.17+FL.+OZ./a802600100-c0-s9.html ubid]
** Properties: photo, quantity, item info, condition, quantity, shipping

* [http://www.bidz.com/bzJApp/ProductDisplay.action?sid=100&tid=100&auctionId=34170660 bidz.com]
** Properties: price, item info, availability, condition, country of origin, description, shipping

* [http://www.dellauction.com/cgi-bin/ncommerce3/ProductDisplay?prrfnbr=104283039&prmenbr=75267554&aunbr=104629749 dell auctions]
** item info, price, list date, expiriry date, shipping, condition

* [http://astore.amazon.com/httpwwwsusaco-20/detail/B001KW0A3E amazon marketplace]
** Properties: availability, name, manufacturer, price, shipping, shopping cart link

* [http://shopping.msn.com/prices/best-of-esteban/itemid598175900/?itemtext=itemname:best-of-esteban&stext=esteban msn shopping]
** Properties: title, artist, photo, description, condition, price, buy, shipping, seller

* [http://www.shopping.com/xPO-Keurig-Keurig-Special-Edition-B60-Brewer-Coffee-Machine shopping.com]
** Properties: photo, title, rating (aggregate), details, manufacturer, description, seller, shipping, price, condition, availability

* [http://www4.dealtime.com/xPO-DRY_PAK_Dry_Pak_Roll_Top_Dry_Gear_Bags dealtime.com]
** Properties: photo, price range, link, seller, specs, title, shipping, description, availability

* [http://www.pronto.com/GUESS-Kids-Girls-Shoes-Tyler-p_1164738515-PP pronto.com]
** Properties: photo, price, availability, rating, shipping, link,

* [http://musical-instruments.pricegrabber.com/dj-turntables/Pioneer-CDJ-1000MK3-Digital-Vinyl-Turntable/m18215594.html/st=product/sv=title pricegrabber.com]
** Properties: photo, price, rating, description, shipping, tax, seller, condition, availability

* [http://shopper.cnet.com/smartphones/rim-blackberry-curve-8900/4014-6452_9-33485567.html?tag=contentMain;contentBody shopper.com]
** Properties: title, price range, ratings, description, seller(s), seller rating, dtstart, shipping, availability

* [http://www.mysimon.com/9015-11034_8-30883813.html my simon]
** Properties: price range, seller, store rating, availability, price, link, shipping

* [http://www.compuplus.com/i-BellO-AVSC-2123-Contemporary-Tall-Design-Audio-Video-System-BlackCherry-AVSC2123-1034723~.html?sid=5b5f55n09w5lssu compu plus]
** Properties: condition, availability, shipping, price, description

* [http://www.smarter.com/tv-stands/bello-avsc-2123-42-in-glass-tv-stand-brown/pd--ch-3--pi-361211.html smarter.com]
** Properties: seller, price, reviews, availability, condition

* [http://www.nextag.com/The-Tin-Drum-934321/prices-html nextag.com]
** Properties: format, seller(s), seller reviews, condition, availability, price, link, name/title, shipping

* [http://www.epier.com/BiddingForm.asp?1921228 epier.com]
** Properties: bid, reserve, num bids, dtstart, dtend, quantity, shipping, condition, fulfillment details, seller, title

* [http://us.nine.ebid.net/perl/auction.cgi?auction=16097877&mo=auction ebid.net]
** Properties: photo, seller, price, title, quantity, condition, views, location, dtstart, dtend, shipping, payment methods

* [http://www.etsy.com/view_listing.php?listing_id=19974630&ref=fp_feat_2 etsy.com]
** Properties: title, photo, description, shipping, payment methods, price, quantity

* [http://dealspl.us/product/sony-bravia-kdl-46s4100-46-inch-1080p-lcd-tv dealsplus]
** Properties: price, shipping, dtend, description, seller(s), title, availability

* [http://www.petco.com/product/14363/Totally-Ferret-Premium-Food-for-Active-Show-and-Pet-Ferrets.aspx petco.com]
** Properties: price, seller, reviews, shipping, dtends, availability, description

* [http://www.allposters.com/gallery.asp?startat=/getposter.asp&APNum=290796&CID=AC3917B0E4E4452CBC36B60F9B66A923&PPID=1&search=matisse&f=c&FindID=26501&P=1&PP=13&sortby=PD&cname=Henri+Matisse&SearchID allposters.com]
** Properties: price, shipping, related, availability, description

* [http://www.target.com/Britax-Decathlon-Sahara-Convertible-Seat/dp/B000JIWU4W/sr=1-1/qid=1230579365/ref=sr_1_1/179-9254632-8007737?ie=UTF8&rh=k%3Atoddler%20car%20seats%20britax&page=1 target.com]
** Properties: price, quantity, reviews, shipping, availability, shipping info, description

* [http://www.fastforklifts.com/electric-forklift-trucks-electric-forklift-walkie-forklift-xp1229-12.html fastforklifts.com]
** Properties: description, quantity, price, shipping, availability

* [http://www.leotardworld.com/Wiggles-Sparkle-Butterfly-Back-Leotard-p/mw1425-356h.htm leotardworld.com]
** Properties: price, description, availability, shipping, quantity

* [http://www.amazon.com/Nikon-Coolpix-Digital-Camera-Optical/dp/B0011MVWZ8/ref=pd_bbs_sr_1?ie=UTF8&s=electronics&qid=1231272206&sr=8-1 amazon.com]
** Properties: price, availability, shipping, description, ratings, quantity, condition

* [http://www1.macys.com/catalog/product/index.ognc?ID=290741&CategoryID=42212 macys.com]
** Properties: description, rating, shipping, returns, availability, price

* [http://www.lowes.com/lowes/lkn?action=productDetail&productId=132135-444-C14024A&lpage=none lowes.com]
** Properties: price, availability, shipping

* [http://www.homedepot.com/webapp/wcs/stores/servlet/ProductDisplay?storeId=10051&langId=-1&catalogId=10053&productId=100189145 homedepot.com]
** Properties: price, shipping, quantity, availability, ratings

* [http://www.acehardware.com/product/index.jsp?productId=1290429&cp=&sr=1&kw=lathes&origkw=lathes&parentPage=search&searchId=34784674863 acehardware.com]
** Properties: related, price, size, quantity, shipping, availability

* [http://www.walgreens.com/store/product.jsp?CATID=100218&navAction=jump&navCount=0&nug=VPD&skuid=sku359744&id=prod359743 walgreens.com]
** Properties: price, quantity, shipping, availability

* [http://www.appliancewarehousedirect.com/counterdepth-sidebyside-refrigerator-with-glass-shelves-humidity-controls-transition-lighting-external-button-icewater-dispenser-p-18476.html?cPath=3 appliancewarehousedirect.com]
** Properties: price, shipping, warranty, condition, packaging, description

* [http://www.birdbaths.com/bird-baths/resin-bird-baths/portsmouthsolarbirdbathfountain.cfm birdbaths.com]
** Properties: price, savings, rating, shipping, quantity, availability, description

* [http://www.circuitcity.com/applications/SearchTools/item-details.asp?EdpNo=3574573&CatId=1902 circuitcity.com]
** Properties: condition, price, availability, quantity, shipping, description

* [http://www.magersandquinn.com/index.php?main_page=product_info&products_id=1905787&isbn_id=4027890 magersandquinn.com]
** Properties: price, condition, availability, description,

* [http://www.bestbuy.com/site/olspage.jsp?skuId=9015638&type=product&id=1852883 bestbuy.com]
** Properties: shipping, price, description, availability

* [http://www.cduniverse.com/productinfo.asp?pid=1109198&cart=827546365 cduniverse.com]
** Properties: price, availability, shipping, description, format

* [http://www.autozone.com/autozone/catalog/accessories/accProductDetails.jsp?displayName=AirFreshener&itemId=prod63065&navValue=100507&parentId=cat30093&productId=574949&fromString=&itemIdentifier=574949_0_0_&filterByKeyWord=&categoryNValue=&subSubPartId=&subPartId=prod63065&store=3076&skuDisplayName=2pk.StrawberryExtraStrengthHangingAirFreshener&categoryDisplayName=CarCare&_requestid=742334 autozone.com]
** Properties: availability, shipping, quantity

* [http://www.napaonline.com/MasterPages/NOLMaster.aspx?PageId=470&LineCode=BSH&PartNumber=N69487&Description=Fuel+Pump+-+Electric+In-Tank+Type+-+OEM+Equivalent napaonline.com]
** Properties: description, availability, price, shipping, condition

* [http://www.toysrus.com/product/index.jsp?productId=2332387 toysrus.com]
** Properties: description, price, availability, shipping

* [http://www.usedsports.com/category/289/Drivers/listings/437/New-Extreme-Distance-Driver.html usedsports.com]
** Properties: condition, price, quantity, location, shipping, dtends, description, terms

* [http://www.biblio.com/details.php?dcx=166670305&aid=frg biblio.org]
** Properties: price, seller, date published, condition, shipping

* [http://kidzugoodbuy.ecrater.com/product.php?pid=3888669 kugby]
** Properties: price, shipping, availability, condition, payment options, description

* [http://microcenter.com/single_product_results.phtml?product_id=0310220 microcenter.com]
** Properties: condition, price, availability, quantity

* [http://www.amazon.com/Factory-Reconditioned-Bostitch-RN46-1-4-Inch-Roofing/dp/B000F10HWU/ref=sr_1_2?ie=UTF8&s=hi&qid=1243453632&sr=1-2 amazon outlet]
** Properties: price, condition, availability, shipping, quantity

* [http://www.amazon.com/Factory-Reconditioned-Bostitch-RN46-1-4-Inch-Roofing/dp/B000F10HWU/ref=sr_1_2?ie=UTF8&s=hi&qid=1243453632&sr=1-2 louisiana machinery]
** Properties: price, condition, rating, shipping

* [http://product.half.ebay.com/Too-Fat-to-Fish_W0QQtgZinfoQQprZ69582903 half.com]
** Properties: description, condition, price, format, shipping

* [http://www.tradeups.com/ tradeups.com]
** Properties: price, condition, quantity, shipping

* [http://www.itxchange.com i.t. xchange]
** Properties: description, condition, quantity, price, availability, shipping

* [http://discountechnology.com/Dell-E176FP-17-LCD-Flat-Panel-Analog-Monitor?sc=2&category=265 discount technology]
** Properties: description, condition, quantity, shipping, availability

* [http://www.microreplay.com/index.php?main_page=index&cPath=16_27 micro replay]
** Properties: condition, description, warranty, availability

* [http://www.clive.nl/audio-tv/p60-active-filter-unit-project-z60 clive.nl retro computer collections]
** Properties: title, price, condition, availability, shipping

* [http://shopping.lycos.com/product/view/m/88973303 lycos shopping]
** Properties: seller, condition, price, availability

* [http://www.abt.com/product/37181/Apple-MB528LLA.html?utm_source=scpgrabber&utm_medium=sc&utm_campaign=pricegrabber&mr:referralID=67af328a-546b-11de-8327-000423bb4e79 abt.com]
** Properties: availability, description, shipping, price

* [http://store.apple.com/us/product/FB528LL/A?afid=p210|pgbr apple store]
** Properties: title, description, price, shipping, availability, condition

* [http://lycos.pgpartner.com/user_sales_getprod.php?masterid=88973303&lot_id=9449215 the source storefront]
** Properties: price, availability, payment options, shipping, condition, buy

* [http://www.buy.com/prod/schwinn-windwood-26-men-s-cruiser-bicycle/q/loc/17250/206649684.html?dcaid=15890 buy.com]
** Properties: price, shipping, availability, quantity,

* [http://www.prosportsmemorabilia.com/Carolina-Hurricanes---Rod-BrindAmour---2006-Stanley-Cup-Jr-Ticket-Frame-_860780691_PD.html?pgrabber=35-84999 pro sports memorabilia]
** Properties: price, quantity, availability, shipping

* [http://www.techexcess.net/011656-001-proliant-dl380-motherboard-system-board-w-cmos-batt-289554-001.aspx Tech Excess]
** Properties: price, description, condition, quantity,

* [http://www.kitchengourmet.com.au/ kitchen gourmet]
** Properties: title, condition, price, quantity, shipping, description

* [http://stores.channeladvisor.com/thephotospot/Items/ko_1434273_NW_4X?&caSKU=ko_1434273_NW_4X&caTitle=Kodak%20Greeting%20Cards%20%26%20Invitations%20Printing%20Kit%20NEW%204%20PACK the photo spot/channel advisor]
** Properties: title, price, quantity, condition, shipping

* [http://www.pixmania.co.uk/uk/uk/757607/hoover/all_merchant/tc1206001-steam-cleaner.html?state=USE pixmania.co.uk]
** Properties: seller, price, condition, shipping, availability

* [http://www.samedaymusic.com/product--ALEDM5PROKIT same day music]
** Properties: condition, availability, shipping, price, description

* [http://www.onlinesurplus.com/products/prod_details.asp?Tg=1308&Sc=0 online surplus]
** Properties: condition, shipping, quantity, availability, price, description

* [http://www.secondspin.com/music/product-detail.jsp?id=2706699 second spin]
** Properties: availability, quantity, price, condition (implied)

* [http://www.wherehouse.com/music/product-detail.jsp?id=2691046 wherehouse.com]
** Properties: availability, price, condition, description

* [http://www.gamestop.com/Catalog/ProductDetails.aspx?Product_ID=71813 gamestop]
** Properties: shipping, price, condition, availability

* [http://www.bigwords.com/details/book/The_5000_Year_Leap_A_Miracle_That_Changed_the_World/9780880801485/0880801484 big words]
** Properties: condition, seller, description, price, shipping, availability

* [http://www.alibris.com/musicsearch?qwork=400860855&cm_sp=rec-_-mnhome-_-youMightLike&matches=0 alibris]
** Properties: title, condition, format, shipping, availability, price

* [http://www.mastermagnets.com/content/view/22/122/lang,en/ master magnets]
** Properties: title, availability, quantity, description, condition

* [http://yhst-31241655524746.stores.yahoo.net/quicklok-t20-single-x-keyboard-stand--us20.html soundtree audio and music technology solutions]
** Properties: price, description, condition, availability

* [http://ezcafe.com/index.php?main_page=product_info&cPath=4&products_id=7&zenid=1d586a3c214b9f0f354d508ebc178e2e ezcafe]
** Properties: title, price, description, condition, availability, dtstart

* [http://www.holtcat.com/app_used.asp holt cat]
** Properties: manufacturer, price, availability, condition

* [http://www.amhboston.com/index.cfm?event=ProductDetails&CategoryID=48&ProductID=159 american material handling group]
** Properties: condition, size, price, quantity, shipping/delivery, availability

* [http://store.academyofscuba.com/suvydswrcowu.html academy of scuba]
** Properties: price, condition, availability, description,

* [http://www.horseclicks.com/products/lp0mry/ horse clicks]
** Properties: availability, condition, price

* [http://www.siliconsolar.com/used-genlight-fixture-p-17995.html silicon solar]
** Properties: condition, price, quantity, availability

* [http://www.joessports.com/product/index.jsp?productId=3071464&CAWELAID=155516067 joe's sports]
** Properties: price, description, quantity, availability, shipping

* [http://www.amazon.com/gp/product/B000O7I6VE amazon.com]
** Properties: title, price, condition, availability, shipping

* [http://www1.tradetang.com/for-sale/Free_shipping_10pics_Brand_New_2_8_Touch_Screen_8GB_MP3_MP4_Player_2_0M_Video_Camera/110562-1239396.html tradetang.com]
** Properties: price, title, condition, shipping, availability

* [http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=4355391&CatId=2628 tiger direct]
** Properties: price, quantity, condition, availability, shipping

* [http://www.sonystyle.com/webapp/wcs/stores/servlet/ProductDisplay?catalogId=10551&storeId=10151&langId=-1&productId=8198552921665401960 sony/ sonystyle]
** Properties: condition, price, rating, description, availability, shipping

* [http://www.shopping.hp.com/webapp/shopping/product_detail.do?product_code=CC436AR%23ABA&aoid=14655&srccode=cii_10043468&cpncode=22-18868711-2 hewlett packard]
** Properties: price, condition, availability, shipping, quantity

* [http://estore.usa.canon.com/webapp/wcs/stores/servlet/ProductDisplay?catalogId=10051&storeId=10051&productId=156469&langId=-1&parent_category_rn=12056&top_category=12252 canon estore]
** Properties: condition, price, availability

=== Analysis of hListing Research ===

To date, analysis on 65 commerce or product listing sites was performed to represent a wide array of offers. The new hListing proposal adds three elements -- availability, condition, and shipping. The findings up to this point indicate many commerce and product related sites utilizing the proposed hlisting attributes of availability, condition and shipping.

hlisting-examples

2009-05-27T20:51:26Z

JayMyers: additional comments on hlisting research

<h1>Listing Examples </h1>
{{TOC-right}}

This page is '''informative'''.

The purpose of the content on this page is to serve as background for the improvement of the transactional/listing (hListing) microformat. There are examples in the wild, and this page can serve as a supplement for those examples and for experimentation and implementation.

== Editors/Authors ==
(alphabetical)
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

== New Examples ==
If you have implemented hListing on your own page, feel free to add it to the '''top''' of this list. Please be sure to include at least one URL to a page on your site that includes actual [[hlisting|hListing]] markup.

=== Live Product Examples ===

* [http://ottawa.en.craigslist.ca/sys/1135033483.html craiglist]
** Properties: item info, condition, description, price, lister, list date

* [http://tinyurl.com/7p6h4l BlueNile]
** Properties: item info, shipping, price, description, price

* [http://www.cowboom.com/index.cfm cow boom]
** Properties: item info, condition, price, what's included, shipping

* [http://auctions.overstock.com/Sony-HF-10-Pack-60-Minute-HiFi-Audio-Cassette-Tape/Computers-Networking/item/44773540 Overstock auctions]
** Properties: item info, list date, expiriry date, shipping, condition, description

* [http://cgi.ebay.com/4-OCTAVE-WOODEN-MARIMBA-DIRECT-FROM-ARTIST_W0QQitemZ25035963638*6QQcmdZViewItemQQptZLH_DefaultDomain_0?hash=item250359636386&_trksid=p3286.c0.m14&_trkparms=72%3A1205|66%3A2|65%3A12|39%3A1|240%3A1318|301%3A1|293%3A1|294%3A50 ebay]
** Properties: price, shipping, payment options, item info, quantity, condition, origin, product type, description, return policy, payment details

* [http://shopping.yahoo.com/p:Hitachi%20DZMV750MA%20DV%20Camcorder:1991860021;_ylt=ArAy9aGn3IsvqWGO7PBb_dlWnMUu?clink=dmss//ctx=sc:gtvvideo,c:cvideo_camera_dv,mid:59,pid:1991860021,pdid:59,pos:0 yahoo shopping/amazon marktplace]
** Properties: price (aggregate w/ min - max), item info, rating, price, condition, description

* [http://www.ubid.com/DAVIDOFF+COOL+WATER+for+men+New+in+box+Popular+5+ML+.17+FL.+OZ./a802600100-c0-s9.html ubid]
** Properties: photo, quantity, item info, condition, quantity, shipping

* [http://www.bidz.com/bzJApp/ProductDisplay.action?sid=100&tid=100&auctionId=34170660 bidz.com]
** Properties: price, item info, availability, condition, country of origin, description

* [http://www.dellauction.com/cgi-bin/ncommerce3/ProductDisplay?prrfnbr=104283039&prmenbr=75267554&aunbr=104629749 dell auctions]
** item info, price, list date, expiriry date, shipping, condition

* [http://astore.amazon.com/httpwwwsusaco-20/detail/B001KW0A3E amazon marketplace]
** Properties: availability, name, manufacturer, price, shipping, availability, shopping cart link

* [http://www.cars.com/go/search/detail.jsp;?tracktype=usedcc&searchType=21&pageNumber=0&numResultsPerPage=50&largeNumResultsPerPage=0&sortorder=descending&sortfield=PRICE+descending&certifiedOnly=false&criteria=K-|E-|M-_48_|D-_107_|N-N|R-10000|I-1%2c7|P-PRICE+descending|Q-descending|Z-55428&aff=national&paId=310971634&recnum=0&leadExists=false cars.com]
** Properties: mileage, values, photos, listing source (lister), price, phone (vcard), related, condition, description, print, name

* [http://shopping.msn.com/prices/best-of-esteban/itemid598175900/?itemtext=itemname:best-of-esteban&stext=esteban msn shopping]
** Properties: title, artist, photo, description, condition, price, buy, shipping, seller

* [http://www.thefind.com/qq-jovani-prom-dresses thefind.com]
** Properties: price, link, photo, title, seller, shipping

* [http://www.shopping.com/xPO-Keurig-Keurig-Special-Edition-B60-Brewer-Coffee-Machine shopping.com]
** Properties: photo, title, rating (aggregate), details, manufacturer, description, seller, shipping, price,

* [http://www4.dealtime.com/xPO-DRY_PAK_Dry_Pak_Roll_Top_Dry_Gear_Bags dealtime.com]
** Properties: photo, price range, link, seller, specs, title, shipping, description, availability

* [http://browsegoods.com/ http://browsegoods.com/]
** Properties: photo, availability, buy, title, date started, price range, manufacturer

* [http://www.pronto.com/GUESS-Kids-Girls-Shoes-Tyler-p_1164738515-PP pronto.com]
** Properties: photo, price, availabilty, rating, shipping, link,

* [http://ask.pronto.com/Books/The-Story-of-the-Orchestra-Listen-While-You-Learn-About-the-Instruments-the-Music-and-the-Composers-10201546205-CG.nto?SEM=true&parentId=-1a9d22bd-121551e8a0a--4a66 ask shopping]
** Properties: title, price range, sellers, description, rating, availability

* [http://musical-instruments.pricegrabber.com/dj-turntables/Pioneer-CDJ-1000MK3-Digital-Vinyl-Turntable/m18215594.html/st=product/sv=title pricegrabber.com]
** Properties: photo, price, rating, description, shipping, tax, seller, condition, availability

* [http://shopper.cnet.com/smartphones/rim-blackberry-curve-8900/4014-6452_9-33485567.html?tag=contentMain;contentBody shopper.com]
** Properties: title, price range, ratings, description, seller(s), seller rating, dtstart, shipping, availability

* [http://www.mysimon.com/9015-11034_8-30883813.html my simon]
** Properties: price range, seller, store rating, availability, price, link, shipping

* [http://www.smarter.com/tv-stands/bello-avsc-2123-42-in-glass-tv-stand-brown/pd--ch-3--pi-361211.html smarter.com]
** Properties: seller, price, reviews, availability, condition

* [http://www.like.com/menswatches-search--99e925db352e5ed2a6268c85564a4c4d34aa68f8-883f182aa5836357--price130-350-0 ilike.com]
** Properties: photo, shipping, link, price

* [http://www.nextag.com/The-Tin-Drum-934321/prices-html nextag.com]
** Properties: format, seller(s), seller reviews, condition, availability, price, link, name/title

* [http://www.epier.com/BiddingForm.asp?1921228 epier.com]
** Properties: bid, reserve, num bids, dtstart, dtend, quantity, shipping, fulfillment details, seller, title

* [http://us.nine.ebid.net/perl/auction.cgi?auction=16097877&mo=auction ebid.net]
** Properties: photo, seller, price, title, quantity, condition, views, location, dtstart, dtend, shipping, payment methods

* [http://www.google.com/products/catalog?q=headphones&cid=3095271091202633155&sa=title#ps-sellers google base]
** Properties: photo, price range, reviews (aggregate), description, shipping, title,

* [http://www.etsy.com/view_listing.php?listing_id=19974630&ref=fp_feat_2 etsy.com]
** Properties: title, photo, description, shipping, payment methods, price, quantity

* [http://dealspl.us/product/sony-bravia-kdl-46s4100-46-inch-1080p-lcd-tv dealsplus]
** Properties: price, shipping, dtend, description, seller(s), title, availability

* [http://www.petco.com/product/14363/Totally-Ferret-Premium-Food-for-Active-Show-and-Pet-Ferrets.aspx petco.com]
** Properties: price, seller, reviews, shipping, dtends, availability, description

* [http://www.allposters.com/gallery.asp?startat=/getposter.asp&APNum=290796&CID=AC3917B0E4E4452CBC36B60F9B66A923&PPID=1&search=matisse&f=c&FindID=26501&P=1&PP=13&sortby=PD&cname=Henri+Matisse&SearchID allposters.com]
** Properties: price, shipping, related, availability, description

* [http://www.target.com/Britax-Decathlon-Sahara-Convertible-Seat/dp/B000JIWU4W/sr=1-1/qid=1230579365/ref=sr_1_1/179-9254632-8007737?ie=UTF8&rh=k%3Atoddler%20car%20seats%20britax&page=1 target.com]
** Properties: price, quantity, reviews, shipping, availability, shipping info, description

* [http://www.uniformadvantage.com/pages/prod/0445.asp?frmcolor=NAVY uniformadvantage.com]
** Properties: description, price, availability, quantity

* [http://freewheelbike.com/itemdetails.cfm?LibId=45397 freewheelbike.com]
** Properties: description, price, reviews, quantity, availability,

* [http://www.fastforklifts.com/electric-forklift-trucks-electric-forklift-walkie-forklift-xp1229-12.html fastforklifts.com]
** Properties: description, quantity, price, shipping, availability

* [http://www.leotardworld.com/Wiggles-Sparkle-Butterfly-Back-Leotard-p/mw1425-356h.htm leotardworld.com]
** Properties: price, description, availability, quantity

* [http://www.gap.com/browse/product.do?cid=40772&vid=1&pid=624603&scid=624603002 gap.com]
** Properties: description, price, size, quantity

* [http://www.amazon.com/Nikon-Coolpix-Digital-Camera-Optical/dp/B0011MVWZ8/ref=pd_bbs_sr_1?ie=UTF8&s=electronics&qid=1231272206&sr=8-1 amazon.com]
** Properties: price, availability, shipping, description, ratings, quantity, condition

* [http://shop.lundsandbyerlys.com/shopping.aspx?location=E&sublocation=LP&shoplistid=336 lundsandbyerlys.com]
** Properties: price, quantity, description,

* [http://www1.macys.com/catalog/product/index.ognc?ID=290741&CategoryID=42212 macys.com]
** Properties: description, rating, shipping, returns, availability, price

* [http://www.lowes.com/lowes/lkn?action=productDetail&productId=132135-444-C14024A&lpage=none lowes.com]
** Properties: price, availability, shipping

* [http://www.homedepot.com/webapp/wcs/stores/servlet/ProductDisplay?storeId=10051&langId=-1&catalogId=10053&productId=100189145 homedepot.com]
** Properties: price, shipping, quantity, availability, ratings

* [http://www.acehardware.com/product/index.jsp?productId=1290429&cp=&sr=1&kw=lathes&origkw=lathes&parentPage=search&searchId=34784674863 acehardware.com]
** Properties: related, price, size, quantity, shipping, availability

* [http://www.walgreens.com/store/product.jsp?CATID=100218&navAction=jump&navCount=0&nug=VPD&skuid=sku359744&id=prod359743 walgreens.com]
** Properties: price, quantity, shipping, availability

* [http://www.appliancewarehousedirect.com/counterdepth-sidebyside-refrigerator-with-glass-shelves-humidity-controls-transition-lighting-external-button-icewater-dispenser-p-18476.html?cPath=3 appliancewarehousedirect.com]
** Properties: price, shipping, warranty, condition, packaging, description

* [http://www.birdbaths.com/bird-baths/resin-bird-baths/portsmouthsolarbirdbathfountain.cfm birdbaths.com]
** Properties: price, savings, rating, shipping, quantity, availability, description

* [http://www.circuitcity.com/applications/SearchTools/item-details.asp?EdpNo=3574573&CatId=1902 circuitcity.com]
** Properties: condition, price, availability, quantity, shipping, description

* [http://www.bagking.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=FN1200N&Category_Code=womens-fannypacks&Product_Count bagking.com]
** Properties: price, shipping, quantity, description

* [http://www.magersandquinn.com/index.php?main_page=product_info&products_id=1905787&isbn_id=4027890 magersandquinn.com]
** Properties: price, condition, availability, description,

* [http://www.bestbuy.com/site/olspage.jsp?skuId=9015638&type=product&id=1852883 bestbuy.com]
** Properties: shipping, price, description, availability

* [http://www.cduniverse.com/productinfo.asp?pid=1109198&cart=827546365 cduniverse.com]
** Properties: price, availability, shipping, description, format

* [http://www.cars.com/go/search/detail.jsp;?tracktype=usedcc&searchType=21&pageNumber=0&numResultsPerPage=50&largeNumResultsPerPage=0&sortorder=descending&sortfield=PRICE+descending&certifiedOnly=false&criteria=K-|E-|M-_5_|D-_34_|N-N|R-30|I-1%2c7|P-PRICE+descending|Q-descending|Z-55428&aff=national&paId=307114842&recnum=1&leadExists=true cars.com]
** Properties: description, price, condition

* [http://www.autozone.com/autozone/catalog/accessories/accProductDetails.jsp?displayName=AirFreshener&itemId=prod63065&navValue=100507&parentId=cat30093&productId=574949&fromString=&itemIdentifier=574949_0_0_&filterByKeyWord=&categoryNValue=&subSubPartId=&subPartId=prod63065&store=3076&skuDisplayName=2pk.StrawberryExtraStrengthHangingAirFreshener&categoryDisplayName=CarCare&_requestid=742334 autozone.com]
** Properties: availability, shipping, quantity

* [http://www.napaonline.com/MasterPages/NOLMaster.aspx?PageId=470&LineCode=BSH&PartNumber=N69487&Description=Fuel+Pump+-+Electric+In-Tank+Type+-+OEM+Equivalent napaonline.com]
** Properties: description, availability, price, shipping, condition

* [http://www.foosballstore.com/products/description/672.cfm fooseballstore.com]
** Properties: description, shipping, quantity, price

* [http://www.toysrus.com/product/index.jsp?productId=2332387 toysrus.com]
** Properties: description, price, availability, shipping

* [http://www.playitagainsports.com/hotproduct.aspx?id=98412b79-c781-41d7-8c9f-38fe9231be2b&tag=hockey&index=0 playitagainsports.com]
** Properties: specs, condition, availability

* [http://www.usedsports.com/category/289/Drivers/listings/437/New-Extreme-Distance-Driver.html usedsports.com]
** Properties: condition, price, quantity, location, shipping, dtends, description, terms

* [http://www.biblio.com/details.php?dcx=166670305&aid=frg biblio.org]
** Properties: price, seller, date published, condition,

* [http://kidzugoodbuy.ecrater.com/product.php?pid=3888669 kugby]
** Properties: price, shipping, availability, condition, payment options, description

* [http://microcenter.com/single_product_results.phtml?product_id=0310220 microcenter.com]
** Properties: condition, price, availability, quantity,

* [http://www.amazon.com/Factory-Reconditioned-Bostitch-RN46-1-4-Inch-Roofing/dp/B000F10HWU/ref=sr_1_2?ie=UTF8&s=hi&qid=1243453632&sr=1-2 amazon outlet]
** Properties: price, condition, availability, shipping, quantity

* [http://www.amazon.com/Factory-Reconditioned-Bostitch-RN46-1-4-Inch-Roofing/dp/B000F10HWU/ref=sr_1_2?ie=UTF8&s=hi&qid=1243453632&sr=1-2 louisiana machinery]
** Properties: price, condition, rating, shipping

* [http://myfox9.carsoup.com/used/detail.asp?usedvehicleid=5595659&xdealerid=2844&makeid=10&minyear=2005&maxyear=2007&searchid=J4944&vehicletypeid=1&uvviewid=4&page=1&certified=0 carsoup.com]
** Properties: price, color, condition, financing

* [http://product.half.ebay.com/Too-Fat-to-Fish_W0QQtgZinfoQQprZ69582903 half.com]
** Properties: description, condition, price, format, shipping

=== Analysis of hListing Research ===

To date, analysis on 65 commerce or product listing sites was performed to represent a wide array of offers. The new hListing proposal adds three elements -- availability, condition, and shipping. The findings up to this point indicate many commerce and product related sites utilizing the proposed hlisting attributes of availability, condition and shipping.

hlisting-examples

2009-05-27T20:48:24Z

JayMyers: adding several examples

<h1>Listing Examples </h1>
{{TOC-right}}

This page is '''informative'''.

The purpose of the content on this page is to serve as background for the improvement of the transactional/listing (hListing) microformat. There are examples in the wild, and this page can serve as a supplement for those examples and for experimentation and implementation.

== Editors/Authors ==
(alphabetical)
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

== New Examples ==
If you have implemented hListing on your own page, feel free to add it to the '''top''' of this list. Please be sure to include at least one URL to a page on your site that includes actual [[hlisting|hListing]] markup.

=== Live Product Examples ===

* [http://ottawa.en.craigslist.ca/sys/1135033483.html craiglist]
** Properties: item info, condition, description, price, lister, list date

* [http://tinyurl.com/7p6h4l BlueNile]
** Properties: item info, shipping, price, description, price

* [http://www.cowboom.com/index.cfm cow boom]
** Properties: item info, condition, price, what's included, shipping

* [http://auctions.overstock.com/Sony-HF-10-Pack-60-Minute-HiFi-Audio-Cassette-Tape/Computers-Networking/item/44773540 Overstock auctions]
** Properties: item info, list date, expiriry date, shipping, condition, description

* [http://cgi.ebay.com/4-OCTAVE-WOODEN-MARIMBA-DIRECT-FROM-ARTIST_W0QQitemZ25035963638*6QQcmdZViewItemQQptZLH_DefaultDomain_0?hash=item250359636386&_trksid=p3286.c0.m14&_trkparms=72%3A1205|66%3A2|65%3A12|39%3A1|240%3A1318|301%3A1|293%3A1|294%3A50 ebay]
** Properties: price, shipping, payment options, item info, quantity, condition, origin, product type, description, return policy, payment details

* [http://shopping.yahoo.com/p:Hitachi%20DZMV750MA%20DV%20Camcorder:1991860021;_ylt=ArAy9aGn3IsvqWGO7PBb_dlWnMUu?clink=dmss//ctx=sc:gtvvideo,c:cvideo_camera_dv,mid:59,pid:1991860021,pdid:59,pos:0 yahoo shopping/amazon marktplace]
** Properties: price (aggregate w/ min - max), item info, rating, price, condition, description

* [http://www.ubid.com/DAVIDOFF+COOL+WATER+for+men+New+in+box+Popular+5+ML+.17+FL.+OZ./a802600100-c0-s9.html ubid]
** Properties: photo, quantity, item info, condition, quantity, shipping

* [http://www.bidz.com/bzJApp/ProductDisplay.action?sid=100&tid=100&auctionId=34170660 bidz.com]
** Properties: price, item info, availability, condition, country of origin, description

* [http://www.dellauction.com/cgi-bin/ncommerce3/ProductDisplay?prrfnbr=104283039&prmenbr=75267554&aunbr=104629749 dell auctions]
** item info, price, list date, expiriry date, shipping, condition

* [http://astore.amazon.com/httpwwwsusaco-20/detail/B001KW0A3E amazon marketplace]
** Properties: availability, name, manufacturer, price, shipping, availability, shopping cart link

* [http://www.cars.com/go/search/detail.jsp;?tracktype=usedcc&searchType=21&pageNumber=0&numResultsPerPage=50&largeNumResultsPerPage=0&sortorder=descending&sortfield=PRICE+descending&certifiedOnly=false&criteria=K-|E-|M-_48_|D-_107_|N-N|R-10000|I-1%2c7|P-PRICE+descending|Q-descending|Z-55428&aff=national&paId=310971634&recnum=0&leadExists=false cars.com]
** Properties: mileage, values, photos, listing source (lister), price, phone (vcard), related, condition, description, print, name

* [http://shopping.msn.com/prices/best-of-esteban/itemid598175900/?itemtext=itemname:best-of-esteban&stext=esteban msn shopping]
** Properties: title, artist, photo, description, condition, price, buy, shipping, seller

* [http://www.thefind.com/qq-jovani-prom-dresses thefind.com]
** Properties: price, link, photo, title, seller, shipping

* [http://www.shopping.com/xPO-Keurig-Keurig-Special-Edition-B60-Brewer-Coffee-Machine shopping.com]
** Properties: photo, title, rating (aggregate), details, manufacturer, description, seller, shipping, price,

* [http://www4.dealtime.com/xPO-DRY_PAK_Dry_Pak_Roll_Top_Dry_Gear_Bags dealtime.com]
** Properties: photo, price range, link, seller, specs, title, shipping, description, availability

* [http://browsegoods.com/ http://browsegoods.com/]
** Properties: photo, availability, buy, title, date started, price range, manufacturer

* [http://www.pronto.com/GUESS-Kids-Girls-Shoes-Tyler-p_1164738515-PP pronto.com]
** Properties: photo, price, availabilty, rating, shipping, link,

* [http://ask.pronto.com/Books/The-Story-of-the-Orchestra-Listen-While-You-Learn-About-the-Instruments-the-Music-and-the-Composers-10201546205-CG.nto?SEM=true&parentId=-1a9d22bd-121551e8a0a--4a66 ask shopping]
** Properties: title, price range, sellers, description, rating, availability

* [http://musical-instruments.pricegrabber.com/dj-turntables/Pioneer-CDJ-1000MK3-Digital-Vinyl-Turntable/m18215594.html/st=product/sv=title pricegrabber.com]
** Properties: photo, price, rating, description, shipping, tax, seller, condition, availability

* [http://shopper.cnet.com/smartphones/rim-blackberry-curve-8900/4014-6452_9-33485567.html?tag=contentMain;contentBody shopper.com]
** Properties: title, price range, ratings, description, seller(s), seller rating, dtstart, shipping, availability

* [http://www.mysimon.com/9015-11034_8-30883813.html my simon]
** Properties: price range, seller, store rating, availability, price, link, shipping

* [http://www.smarter.com/tv-stands/bello-avsc-2123-42-in-glass-tv-stand-brown/pd--ch-3--pi-361211.html smarter.com]
** Properties: seller, price, reviews, availability, condition

* [http://www.like.com/menswatches-search--99e925db352e5ed2a6268c85564a4c4d34aa68f8-883f182aa5836357--price130-350-0 ilike.com]
** Properties: photo, shipping, link, price

* [http://www.nextag.com/The-Tin-Drum-934321/prices-html nextag.com]
** Properties: format, seller(s), seller reviews, condition, availability, price, link, name/title

* [http://www.epier.com/BiddingForm.asp?1921228 epier.com]
** Properties: bid, reserve, num bids, dtstart, dtend, quantity, shipping, fulfillment details, seller, title

* [http://us.nine.ebid.net/perl/auction.cgi?auction=16097877&mo=auction ebid.net]
** Properties: photo, seller, price, title, quantity, condition, views, location, dtstart, dtend, shipping, payment methods

* [http://www.google.com/products/catalog?q=headphones&cid=3095271091202633155&sa=title#ps-sellers google base]
** Properties: photo, price range, reviews (aggregate), description, shipping, title,

* [http://www.etsy.com/view_listing.php?listing_id=19974630&ref=fp_feat_2 etsy.com]
** Properties: title, photo, description, shipping, payment methods, price, quantity

* [http://dealspl.us/product/sony-bravia-kdl-46s4100-46-inch-1080p-lcd-tv dealsplus]
** Properties: price, shipping, dtend, description, seller(s), title, availability

* [http://www.petco.com/product/14363/Totally-Ferret-Premium-Food-for-Active-Show-and-Pet-Ferrets.aspx petco.com]
** Properties: price, seller, reviews, shipping, dtends, availability, description

* [http://www.allposters.com/gallery.asp?startat=/getposter.asp&APNum=290796&CID=AC3917B0E4E4452CBC36B60F9B66A923&PPID=1&search=matisse&f=c&FindID=26501&P=1&PP=13&sortby=PD&cname=Henri+Matisse&SearchID allposters.com]
** Properties: price, shipping, related, availability, description

* [http://www.target.com/Britax-Decathlon-Sahara-Convertible-Seat/dp/B000JIWU4W/sr=1-1/qid=1230579365/ref=sr_1_1/179-9254632-8007737?ie=UTF8&rh=k%3Atoddler%20car%20seats%20britax&page=1 target.com]
** Properties: price, quantity, reviews, shipping, availability, shipping info, description

* [http://www.uniformadvantage.com/pages/prod/0445.asp?frmcolor=NAVY uniformadvantage.com]
** Properties: description, price, availability, quantity

* [http://freewheelbike.com/itemdetails.cfm?LibId=45397 freewheelbike.com]
** Properties: description, price, reviews, quantity, availability,

* [http://www.fastforklifts.com/electric-forklift-trucks-electric-forklift-walkie-forklift-xp1229-12.html fastforklifts.com]
** Properties: description, quantity, price, shipping, availability

* [http://www.leotardworld.com/Wiggles-Sparkle-Butterfly-Back-Leotard-p/mw1425-356h.htm leotardworld.com]
** Properties: price, description, availability, quantity

* [http://www.gap.com/browse/product.do?cid=40772&vid=1&pid=624603&scid=624603002 gap.com]
** Properties: description, price, size, quantity

* [http://www.amazon.com/Nikon-Coolpix-Digital-Camera-Optical/dp/B0011MVWZ8/ref=pd_bbs_sr_1?ie=UTF8&s=electronics&qid=1231272206&sr=8-1 amazon.com]
** Properties: price, availability, shipping, description, ratings, quantity, condition

* [http://shop.lundsandbyerlys.com/shopping.aspx?location=E&sublocation=LP&shoplistid=336 lundsandbyerlys.com]
** Properties: price, quantity, description,

* [http://www1.macys.com/catalog/product/index.ognc?ID=290741&CategoryID=42212 macys.com]
** Properties: description, rating, shipping, returns, availability, price

* [http://www.lowes.com/lowes/lkn?action=productDetail&productId=132135-444-C14024A&lpage=none lowes.com]
** Properties: price, availability, shipping

* [http://www.homedepot.com/webapp/wcs/stores/servlet/ProductDisplay?storeId=10051&langId=-1&catalogId=10053&productId=100189145 homedepot.com]
** Properties: price, shipping, quantity, availability, ratings

* [http://www.acehardware.com/product/index.jsp?productId=1290429&cp=&sr=1&kw=lathes&origkw=lathes&parentPage=search&searchId=34784674863 acehardware.com]
** Properties: related, price, size, quantity, shipping, availability

* [http://www.walgreens.com/store/product.jsp?CATID=100218&navAction=jump&navCount=0&nug=VPD&skuid=sku359744&id=prod359743 walgreens.com]
** Properties: price, quantity, shipping, availability

* [http://www.appliancewarehousedirect.com/counterdepth-sidebyside-refrigerator-with-glass-shelves-humidity-controls-transition-lighting-external-button-icewater-dispenser-p-18476.html?cPath=3 appliancewarehousedirect.com]
** Properties: price, shipping, warranty, condition, packaging, description

* [http://www.birdbaths.com/bird-baths/resin-bird-baths/portsmouthsolarbirdbathfountain.cfm birdbaths.com]
** Properties: price, savings, rating, shipping, quantity, availability, description

* [http://www.circuitcity.com/applications/SearchTools/item-details.asp?EdpNo=3574573&CatId=1902 circuitcity.com]
** Properties: condition, price, availability, quantity, shipping, description

* [http://www.bagking.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=FN1200N&Category_Code=womens-fannypacks&Product_Count bagking.com]
** Properties: price, shipping, quantity, description

* [http://www.magersandquinn.com/index.php?main_page=product_info&products_id=1905787&isbn_id=4027890 magersandquinn.com]
** Properties: price, condition, availability, description,

* [http://www.bestbuy.com/site/olspage.jsp?skuId=9015638&type=product&id=1852883 bestbuy.com]
** Properties: shipping, price, description, availability

* [http://www.cduniverse.com/productinfo.asp?pid=1109198&cart=827546365 cduniverse.com]
** Properties: price, availability, shipping, description, format

* [http://www.cars.com/go/search/detail.jsp;?tracktype=usedcc&searchType=21&pageNumber=0&numResultsPerPage=50&largeNumResultsPerPage=0&sortorder=descending&sortfield=PRICE+descending&certifiedOnly=false&criteria=K-|E-|M-_5_|D-_34_|N-N|R-30|I-1%2c7|P-PRICE+descending|Q-descending|Z-55428&aff=national&paId=307114842&recnum=1&leadExists=true cars.com]
** Properties: description, price, condition

* [http://www.autozone.com/autozone/catalog/accessories/accProductDetails.jsp?displayName=AirFreshener&itemId=prod63065&navValue=100507&parentId=cat30093&productId=574949&fromString=&itemIdentifier=574949_0_0_&filterByKeyWord=&categoryNValue=&subSubPartId=&subPartId=prod63065&store=3076&skuDisplayName=2pk.StrawberryExtraStrengthHangingAirFreshener&categoryDisplayName=CarCare&_requestid=742334 autozone.com]
** Properties: availability, shipping, quantity

* [http://www.napaonline.com/MasterPages/NOLMaster.aspx?PageId=470&LineCode=BSH&PartNumber=N69487&Description=Fuel+Pump+-+Electric+In-Tank+Type+-+OEM+Equivalent napaonline.com]
** Properties: description, availability, price, shipping, condition

* [http://www.foosballstore.com/products/description/672.cfm fooseballstore.com]
** Properties: description, shipping, quantity, price

* [http://www.toysrus.com/product/index.jsp?productId=2332387 toysrus.com]
** Properties: description, price, availability, shipping

* [http://www.playitagainsports.com/hotproduct.aspx?id=98412b79-c781-41d7-8c9f-38fe9231be2b&tag=hockey&index=0 playitagainsports.com]
** Properties: specs, condition, availability

* [http://www.usedsports.com/category/289/Drivers/listings/437/New-Extreme-Distance-Driver.html usedsports.com]
** Properties: condition, price, quantity, location, shipping, dtends, description, terms

* [http://www.biblio.com/details.php?dcx=166670305&aid=frg biblio.org]
** Properties: price, seller, date published, condition,

* [http://kidzugoodbuy.ecrater.com/product.php?pid=3888669 kugby]
** Properties: price, shipping, availability, condition, payment options, description

* [http://microcenter.com/single_product_results.phtml?product_id=0310220 microcenter.com]
** Properties: condition, price, availability, quantity,

* [http://www.amazon.com/Factory-Reconditioned-Bostitch-RN46-1-4-Inch-Roofing/dp/B000F10HWU/ref=sr_1_2?ie=UTF8&s=hi&qid=1243453632&sr=1-2 amazon outlet]
** Properties: price, condition, availability, shipping, quantity

* [http://www.amazon.com/Factory-Reconditioned-Bostitch-RN46-1-4-Inch-Roofing/dp/B000F10HWU/ref=sr_1_2?ie=UTF8&s=hi&qid=1243453632&sr=1-2 louisiana machinery]
** Properties: price, condition, rating, shipping

* [http://myfox9.carsoup.com/used/detail.asp?usedvehicleid=5595659&xdealerid=2844&makeid=10&minyear=2005&maxyear=2007&searchid=J4944&vehicletypeid=1&uvviewid=4&page=1&certified=0 carsoup.com]
** Properties: price, color, condition, financing

* [http://product.half.ebay.com/Too-Fat-to-Fish_W0QQtgZinfoQQprZ69582903 half.com]
** Properties: description, condition, price, format, shipping

=== Analysis of hListing Research ===

To date, analysis on 30 commerce or product listing sites was performed to represent a wide array of offers. The new hListing proposal adds three elements -- availability, condition, and shipping. The findings up to this point as a percentage:

* shipping: 66%
* condition: 46%
* availability: 40%

hlisting-examples

2009-05-18T21:27:03Z

JayMyers: changing order

hlisting-examples

2009-05-18T21:26:30Z

JayMyers: adding analysis

hlisting-examples

2009-05-18T21:15:05Z

JayMyers: adding four more examples

hlisting-examples

2009-05-18T21:06:18Z

JayMyers: corecting shopper.com example link

hlisting-examples

2009-05-18T21:05:04Z

JayMyers: editing spacing

hlisting-examples

2009-05-18T21:04:42Z

JayMyers: adding more examples

hlisting-examples

2009-05-18T19:35:52Z

JayMyers: initial load of new page

hproduct-recipes

2009-05-13T20:50:21Z

JayMyers: loading ramsay example

== Coded Recipe Examples ==

This page is to provide coded examples showing the interplay between hListing, hProduct and other formats (hAggregateReview, xoxo, to name a few) that could be used to create better semantic page markup.

=== hlisting, hproduct example ===
<div class="vevent">
posted: <span class="summary vcard"><span class="dtstart">2009-05-13</span> by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
</div>
[http://jay.beweep.com/wp-content/uploads/2009/05/ramsay.png Example mock]

<pre><nowiki>
<div class="hlisting">
<div class="item hproduct">
<ol>
<li class="lister vcard"><a class="url fn" href="http://storename.com">Magers and Quinn</a></li>
<li class="category"><a href="http://storename.com/categories/books">Books</a></li>
<li class="category"><a href="http://storename.com/categories/cooking">Cooking</a></li>
<li class="category"><a href="http://storename.com/categories/quick-easy-cooking">Quick and Easy Cooking</a></li>
<li>Gordon Ramsay's Fast Food</li>
</ol>
<div class="leftcol">
<img src="http://images.storename.com/products/ramsay-fast-food.jpg" class="photo" alt="gordan ramsay fast food book" />
<p><span class="condition">New:</span> <span class="price">$27.99</span></p>
<p>Pub price: $35.00</p>
<p>Hardcover</p>
<p class="availability">Out of stock</p>
</div>
<div class="rightcol">
<h1 class="fn">Gordon Ramsay's Fast Food Recipes from the F Word</h1>
<p>By Ramsay, Gordon</p>
<dl class="identifier">
<dt>ISBN:</dt>
<dd>1554700647</dd>
</dl>
<dl>
<dt>Contributors:</dt>
<dd>Sargeant, Mark (Contributor); Quah, Emily (Contributor); Mead, Jill (Photographer)</dd>
<dt>Publisher:</dt>
<dd>Amer Youth Hostels</dd>
<dt>Published:</dt>
<dd>2008</dd>
<dt>Pages:</dt>
<dd>255</dd>
<dt>Weight:</dt>
<dd>2.70lbs.</dd>
<dt>Height:</dt>
<dd>10.25"</dd>
<dt>Width:</dt>
<dd>8.00"</dd>
<dt>Depth:</dt>
<dd>1.50"</dd>
<dt>Language:</dt>
<dd>English </dd>
</dl>
<h4>Publishers Comments</h4>
<p class="description">A celebrity host of Hell's Kitchen features more than one hundred accessible recipes that are organized in accordance with everyday needs and special occasions, in a volume that places an emphasis on fast preparation and features complementary tips on stocking a pantry.</p>
</div>
</div>
</div>
</nowiki></pre>

=== hreview, hproduct, hlisting product example ===

<div class="vevent">
posted: <span class="summary vcard"><span class="dtstart">2009-05-07</span> by <span class="fn">[[User:JayMyers|JayMyers]]</span></span><br/>
Source URL: http://reviews.cnet.com/car-gps-navigation/tomtom-go-930-gps/4505-3430_7-33003945.html
</div>

<pre><nowiki>
<div class="hReview">
<div class="item hProduct">
<span class="fn">TomTom GO 930 GPS</span>
<span class="rating">3.5</span>
<div class="listing hListing-aggregate">
<div class="price">
<span class="min">$352.35</span> - <span class="max">$588.99</span>
</div>
</div>
</div>
<div class="reviewer vcard"><span class="fn">Bonnie Cha</span></div>
<span class="dtreviewed">05/28/2008</span>
</div>
</nowiki></pre>

=== combining hreview-aggregate (new proposal), hlisting, hproduct, xoxo ===

<div class="vevent">
posted: <span class="summary vcard"><span class="dtstart">2009-05-07</span> by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">A more production-grade example of combining microformats, while mixing in other class attributes for the purpose of presentation.</div>
</div>

<pre><nowiki>
<div class="hreview-aggregate">
<div class="item hproduct">
<h1 class="fn"><span class="brand">Sony</span> - BRAVIA / 46" Class / 1080p / 120Hz / LCD HDTV</h1>
<ul>
<li class="identifier"><span class="type">Model</span>: <span class="value">LN40A550</span></li>
<li class="identifier"><span class="type">SKU</span>: <span class="value">8749465</span></li>
</ul>
<div class="listing hListing">
<div class="leftcol"><img src="/images/product.jpg" alt="Sony - BRAVIA 46 Class 1080p 120Hz LCD HDTV" class="photo"/></div>
<div class="rightcol">
<div class="rating"><img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" class="average" /></div>
<div>(<span class="count">187</span> Reviews)</div>
<div class="grey">was $1,099.99</div>
<div class="price">$999.99</div>
</div>
<div class="shipping">Shipping: Usually leaves our warehouse in 1 business day.</div>
</div>
<div id="product-overview" class="product-overview" onclick="toggleBox('product-overview-open','product-overview-closed');changeClass('overview-head','down','right');">
<h3><a href="#" class="right" id="overview-head">Overview</a></h3>
<div id="product-overview-closed">
<p class="padtop">This flat-panel LCD HDTV features a 16:9 widescreen aspect ratio and a 50,000:1 dynamic contrast ratio, so you can enjoy your favorite movies in true 1080p high-definition.</p>
<a href="#" class="readmore mini-right">Show Full Overview</a>
</div>
<div id="product-overview-open">
<p class="description">This flat-panel LCD HDTV features a 16:9 widescreen aspect ratio and a 50,000:1 dynamic contrast ratio, so you can enjoy your favorite movies in true 1080p high-definition.</p>
<ul class="xoxo">
<li><h3 class="bottom-line">What's Included</h3>
<ol>
<li>Sony BRAVIA / 46" Class / 1080p / 120Hz / LCD HDTV</li>
<li>Tabletop stand, 4 screws</li>
<li>Remote RM-YD028</li>
<li>AC power cord, 2 AA batteries</li>
<li>Owner's manual</li>
</ol>
</li>
</ul>
<ul class="xoxo">
<li><h3 class="bottom-line">Product Features</h3>
<dl>
<dt>Built-in HDTV tuner</dt>
<dd>Add HD-capable antenna to receive over-the-air high-definition broadcasts, where available. Optional set-top box required for high-definition cable or satellite programming.</dd>
<dt>46" screen measured diagonally from corner to corner</dt>
<dd>Everyone will have a great view of the show or game.</dd>
<dt>1080p display</dt>
<dd>Provides the highest quality progressive-scan picture possible for a high-definition source.</dd>
<dt>16:9 widescreen aspect ratio</dt>
<dd>With CineMotion reverse 3.2 pulldown technology and 24p True Cinema mode delivers accurate reproduction of film-based sources for a cinema-style entertainment experience.</dd>
<dt>BRAVIA Engine 2 full digital video processor</dt>
<dd>Reduces video noise, improves color and sharpens the overall image detail.</dd>
<dt>Advanced Contrast Enhancer (ACE)</dt>
<dd>Uses real-time image processing to adjust the contrast ratio.</dd>
<dt>Motionflow 120Hz technology</dt>
<dd>Reduces jitter and sharpens fast-moving images for a crisp picture.</dd>
<dt>LightSensor technology</dt>
<dd>Monitors ambient room lighting conditions and adjusts the backlit intensity accordingly.</dd>
<dt>50,000:1 dynamic contrast ratio</dt>
<dd>For an arresting viewing experience.</dd>
<dt>3D digital comb filter</dt>
<dd>Brings out fine picture detail and enhances color purity.</dd>
<dt>SRS TruSurround XT</dt>
<dd>With Dolby Digital and SteadySound automatic volume control delivers a lush soundscape.</dd>
<dt>Ultraslim (3-4/5" deep) design and VESA compatible</dt>
<dd>Ideal for wall mounting (with optional mounting kit, not included).</dd>
</dl>
</li>
</ul>
</div>
<div id="customer-overview" class="customer-overview">
<div onclick="toggleBox('customer-open','customer-closed');changeClass('review-head','down','right');">
<h3><span class="right" id="review-head" >Customer Reviews (34)</span></h3>
<p class="padtop">Average: <img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" /></p>
<p>50% of customers would recommend this product to a friend (2 of 4).</p>
</div>
<div id="customer-closed">
<a href="#" class="readmore mini-right" onclick="toggleBox('customer-open','customer-closed');changeClass('review-head','down','right');" >Show Reviews</a>
</div>
<div id="customer-open">
<div id="sort-reviews">
<span class="big-grey">Sort by:</span>
<select>
<option value="newest">Date: Newest</option>
<option value="oldest">Date: Oldest</option>
</select>
<input type="submit" value="Go" />
</div>
<div id="review-list">
<div class="number-of-reviews grey">1 - 10 of 34 Reviews</div>
<div class="hreview">
<span id="review-one" class="summary">TV may be better than you think.</span>
<span class="reviewer vcard">by <span class="fn nickname">bezb18</span> from Maryland on <span class="dtreviewed">04/07/2009</span></span>
<span class="rating"><img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" /></span>
<div id="hidden-one">
<div class="review-box">
<table class="review-summary">
<tr><td>Picture Quality:</td><td><img alt="50% Rating" src="images/bar-50.gif" /></td></tr>
<tr><td>Sound Quality:</td><td><img alt="100% Rating" src="images/bar-100.gif" /></td></tr>
<tr><td>Features:</td><td><img alt="75% Rating" src="images/bar-75.gif" /></td></tr>
</table>
<span class="review-great"><b>What's great about it:</b> Vivid picture.</span>
<span class="review-not"><b>What's not so great:</b> Backlight, fades picture to black.</span>
<p class="description">"I purchased this TV about a week ago and
after putting a DVD on and noticed the scene fading to almost
completely black at several times in the movie, I thought I
might have a problem. Then noticed that it also happens when
watching regular movies on the cable. Screen gets too dark and
then returns to the regular picture. It is very upsetting and you
want to throw something. You think you have bought a really good
TV, paid a good price for it and then you get this. I purchased
a Sony KDL46z4100 Out of Box before this one and had Audio
problems. I took it back and got this one. I really wish
Sony could get it right on something. Will also return this one."</p>
<span class="review-recommend"><b>Would you recommend this product to a friend?:</b> Yes</span>
<span class="review-business"><b>Is this product used primarily for business?:</b> No</span>
</div>
</div>
</div>
</div>
</div>
</div>
<div id="specs-overview" class="specs-overview" onclick="toggleBox('specs-open','specs-closed');changeClass('specs-head','down','right');" >
<h3><a href="#" class="right" id="specs-head">Specifications</a></h3>
<div id="specs-closed"> </div>
<div id="specs-open">
<ul class="xoxo">
<li><h3><a href="#" class="right" id="specs-head">Specifications</a></h3>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year limited</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year limited</dd>
<dt>Product Height</dt>
<dd>30-1/3" with stand (28-5/8" without</dd>
<dt>Product Width</dt>
<dd>44-1/5"</dd>
</dl>
</li>
</ul>
</div>
</div>
</div>
</div>
</div>

</nowiki></pre>

=== hlisting, hproduct, haggregatereview/hreview, xoxo ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/tv-and-video">TV & Video</a></li>
<li class="category"><a href="http://storename.com/televisions">Televisions</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/samsung-ln40a550.jpg" class="photo" alt="picture of samsung ln40a550" />
<div class="fn"><span class="brand">Samsung</span> - 40" 1080p Flat-Panel LCD HDTV</div>
<dl class="identifier">
<dt>Model</dt>
<dd>LN40A550</dd>
<dt>SKU</dt>
<dd>8749465</dd>
</dl>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_3_5.gif" alt="3.5 out of 5 stars"/></a></span><span class="rating">4.7</span> / <span class="best">5</span> (<span class="num">13</span> reviews)</div>
</div>
</div>
<div class="price">$1,099.99</div>
<ol class="xoxo">
<li><h2>Specifications</h2>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year</dd>
<dt>Product Height</dt>
<dd>27" with stand (24-7/10" without)</dd>
<dt>Product Width</dt>
<dd>39-1/5"</dd>
<dt>Product Weight</dt>
<dd>61.5 lbs. with stand (54.5 lbs. without)</dd>
<dt>Product Depth</dt>
<dd>11-4/5" with stand (3-3/5" without)</dd>
<dt>TV Type</dt>
<dd>LCD Flat-Panel</dd>
</dl>
</li>
</div>
</div>
</nowiki></pre>

=== hlisting, hproduct, haudio, haggregatereview/hreview ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct haudio">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/gangsta">Gangsta/Hardcore</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/50cent-curtis.jpg" class="photo" alt="picture of 50 cent" />
<div class="album">Curtis</div>
<div class="contributor"><span class="vcard"><span class=n nickname">50 Cent</span></span></div>
<p>Release date:<abbr class="published" title="2007-09-11">September 11, 2007</abbr></p>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_4_0.gif" alt="4 out of 5 stars"/></a></span><span class="rating">4.0</span> / <span class="best">5</span> Number of reviews:(<span class="num">4</span> reviews)</div>
</div>
<div class="price">$9.99</div>
<a href="add-to-cart-url" rel="payment"><img src="http://storename.com/images/global/add-to-cart.gif" alt="add to cart" /></a>
<h2>Tracks</h2>
<ol>
<li class="item"><span class="position">1</span>.<span class="fn">Intro</span><a href="http://images.storename.com/media/sample/50cent-intro.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">2</span>.<span class="fn">My Gun Go Off</span><a href="http://images.storename.com/media/sample/50cent-gun-go-off.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">3</span>.<span class="fn">Man Down - (censored)</span><a href="http://images.storename.com/media/sample/50cent-man-down.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">4</span>.<span class="fn">I'll Still Kill - (with Akon)</span><a href="http://images.storename.com/media/sample/50cent-ill-still-kill.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">5</span>.<span class="fn">I Get Money</span><a href="http://images.storename.com/media/sample/50cent-i-get-money.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">6</span>.<span class="fn">Come & Go - (with Dr. Dre)</span><a href="http://images.storename.com/media/sample/50cent-come-go.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">7</span>.<span class="fn">Ayo Technology - (with Timbaland/Justin Timberlake)</span><a href="http://images.storename.com/media/sample/50cent-ayo-technology.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">8</span>.<span class="fn">Follow My Lead - (with Robin Thicke)</span><a href="http://images.storename.com/media/sample/50cent-follow-my-lead.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">9</span>.<span class="fn">Movin' on Up</span><a href="http://images.storename.com/media/sample/50cent-movin-on-up.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">10</span>.<span class="fn">Straight to the Bank</span><a href="http://images.storename.com/media/sample/50cent-straight-to-bank.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">11</span>.<span class="fn">Amusement Park</span><a href="http://images.storename.com/media/sample/50cent-amusement-park.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">12</span>.<span class="fn">Fully Loaded Clip</span><a href="http://images.storename.com/media/sample/50cent-fully-loaded-clip.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">13</span>.<span class="fn">Peep Show - (with Eminem)</span><a href="http://images.storename.com/media/sample/50cent-peep-show.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">14</span>.<span class="fn">Fire - (with Young Buck/Nicole Scherzinger)</span><a href="http://images.storename.com/media/sample/50cent-fire.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">15</span>.<span class="fn">All of Me - (with Mary J. Blige)</span><a href="http://images.storename.com/media/sample/50cent-all-of-me.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">16</span>.<span class="fn">Curtis 187</span><a href="http://images.storename.com/media/sample/50cent-curtis-187.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">17</span>.<span class="fn">Touch the Sky - (with Tony Yayo)</span><a href="http://images.storename.com/media/sample/50cent-touch-the-sky.mp3" rel="sample">Listen</a></li>
</ol>
</div>
</div>
</nowiki></pre>

hproduct-recipes

2009-05-13T20:42:17Z

JayMyers: adding gordon ramsay book example

== Coded Recipe Examples ==

This page is to provide coded examples showing the interplay between hListing, hProduct and other formats (hAggregateReview, xoxo, to name a few) that could be used to create better semantic page markup.

=== hlisting, hproduct example ===
<div class="vevent">
posted: <span class="summary vcard"><span class="dtstart">2009-05-13</span> by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
</div>

<pre><nowiki>

</nowiki></pre>

=== hreview, hproduct, hlisting product example ===

<div class="vevent">
posted: <span class="summary vcard"><span class="dtstart">2009-05-07</span> by <span class="fn">[[User:JayMyers|JayMyers]]</span></span><br/>
Source URL: http://reviews.cnet.com/car-gps-navigation/tomtom-go-930-gps/4505-3430_7-33003945.html
</div>

<pre><nowiki>
<div class="hReview">
<div class="item hProduct">
<span class="fn">TomTom GO 930 GPS</span>
<span class="rating">3.5</span>
<div class="listing hListing-aggregate">
<div class="price">
<span class="min">$352.35</span> - <span class="max">$588.99</span>
</div>
</div>
</div>
<div class="reviewer vcard"><span class="fn">Bonnie Cha</span></div>
<span class="dtreviewed">05/28/2008</span>
</div>
</nowiki></pre>

=== combining hreview-aggregate (new proposal), hlisting, hproduct, xoxo ===

<div class="vevent">
posted: <span class="summary vcard"><span class="dtstart">2009-05-07</span> by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">A more production-grade example of combining microformats, while mixing in other class attributes for the purpose of presentation.</div>
</div>

<pre><nowiki>
<div class="hreview-aggregate">
<div class="item hproduct">
<h1 class="fn"><span class="brand">Sony</span> - BRAVIA / 46" Class / 1080p / 120Hz / LCD HDTV</h1>
<ul>
<li class="identifier"><span class="type">Model</span>: <span class="value">LN40A550</span></li>
<li class="identifier"><span class="type">SKU</span>: <span class="value">8749465</span></li>
</ul>
<div class="listing hListing">
<div class="leftcol"><img src="/images/product.jpg" alt="Sony - BRAVIA 46 Class 1080p 120Hz LCD HDTV" class="photo"/></div>
<div class="rightcol">
<div class="rating"><img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" class="average" /></div>
<div>(<span class="count">187</span> Reviews)</div>
<div class="grey">was $1,099.99</div>
<div class="price">$999.99</div>
</div>
<div class="shipping">Shipping: Usually leaves our warehouse in 1 business day.</div>
</div>
<div id="product-overview" class="product-overview" onclick="toggleBox('product-overview-open','product-overview-closed');changeClass('overview-head','down','right');">
<h3><a href="#" class="right" id="overview-head">Overview</a></h3>
<div id="product-overview-closed">
<p class="padtop">This flat-panel LCD HDTV features a 16:9 widescreen aspect ratio and a 50,000:1 dynamic contrast ratio, so you can enjoy your favorite movies in true 1080p high-definition.</p>
<a href="#" class="readmore mini-right">Show Full Overview</a>
</div>
<div id="product-overview-open">
<p class="description">This flat-panel LCD HDTV features a 16:9 widescreen aspect ratio and a 50,000:1 dynamic contrast ratio, so you can enjoy your favorite movies in true 1080p high-definition.</p>
<ul class="xoxo">
<li><h3 class="bottom-line">What's Included</h3>
<ol>
<li>Sony BRAVIA / 46" Class / 1080p / 120Hz / LCD HDTV</li>
<li>Tabletop stand, 4 screws</li>
<li>Remote RM-YD028</li>
<li>AC power cord, 2 AA batteries</li>
<li>Owner's manual</li>
</ol>
</li>
</ul>
<ul class="xoxo">
<li><h3 class="bottom-line">Product Features</h3>
<dl>
<dt>Built-in HDTV tuner</dt>
<dd>Add HD-capable antenna to receive over-the-air high-definition broadcasts, where available. Optional set-top box required for high-definition cable or satellite programming.</dd>
<dt>46" screen measured diagonally from corner to corner</dt>
<dd>Everyone will have a great view of the show or game.</dd>
<dt>1080p display</dt>
<dd>Provides the highest quality progressive-scan picture possible for a high-definition source.</dd>
<dt>16:9 widescreen aspect ratio</dt>
<dd>With CineMotion reverse 3.2 pulldown technology and 24p True Cinema mode delivers accurate reproduction of film-based sources for a cinema-style entertainment experience.</dd>
<dt>BRAVIA Engine 2 full digital video processor</dt>
<dd>Reduces video noise, improves color and sharpens the overall image detail.</dd>
<dt>Advanced Contrast Enhancer (ACE)</dt>
<dd>Uses real-time image processing to adjust the contrast ratio.</dd>
<dt>Motionflow 120Hz technology</dt>
<dd>Reduces jitter and sharpens fast-moving images for a crisp picture.</dd>
<dt>LightSensor technology</dt>
<dd>Monitors ambient room lighting conditions and adjusts the backlit intensity accordingly.</dd>
<dt>50,000:1 dynamic contrast ratio</dt>
<dd>For an arresting viewing experience.</dd>
<dt>3D digital comb filter</dt>
<dd>Brings out fine picture detail and enhances color purity.</dd>
<dt>SRS TruSurround XT</dt>
<dd>With Dolby Digital and SteadySound automatic volume control delivers a lush soundscape.</dd>
<dt>Ultraslim (3-4/5" deep) design and VESA compatible</dt>
<dd>Ideal for wall mounting (with optional mounting kit, not included).</dd>
</dl>
</li>
</ul>
</div>
<div id="customer-overview" class="customer-overview">
<div onclick="toggleBox('customer-open','customer-closed');changeClass('review-head','down','right');">
<h3><span class="right" id="review-head" >Customer Reviews (34)</span></h3>
<p class="padtop">Average: <img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" /></p>
<p>50% of customers would recommend this product to a friend (2 of 4).</p>
</div>
<div id="customer-closed">
<a href="#" class="readmore mini-right" onclick="toggleBox('customer-open','customer-closed');changeClass('review-head','down','right');" >Show Reviews</a>
</div>
<div id="customer-open">
<div id="sort-reviews">
<span class="big-grey">Sort by:</span>
<select>
<option value="newest">Date: Newest</option>
<option value="oldest">Date: Oldest</option>
</select>
<input type="submit" value="Go" />
</div>
<div id="review-list">
<div class="number-of-reviews grey">1 - 10 of 34 Reviews</div>
<div class="hreview">
<span id="review-one" class="summary">TV may be better than you think.</span>
<span class="reviewer vcard">by <span class="fn nickname">bezb18</span> from Maryland on <span class="dtreviewed">04/07/2009</span></span>
<span class="rating"><img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" /></span>
<div id="hidden-one">
<div class="review-box">
<table class="review-summary">
<tr><td>Picture Quality:</td><td><img alt="50% Rating" src="images/bar-50.gif" /></td></tr>
<tr><td>Sound Quality:</td><td><img alt="100% Rating" src="images/bar-100.gif" /></td></tr>
<tr><td>Features:</td><td><img alt="75% Rating" src="images/bar-75.gif" /></td></tr>
</table>
<span class="review-great"><b>What's great about it:</b> Vivid picture.</span>
<span class="review-not"><b>What's not so great:</b> Backlight, fades picture to black.</span>
<p class="description">"I purchased this TV about a week ago and
after putting a DVD on and noticed the scene fading to almost
completely black at several times in the movie, I thought I
might have a problem. Then noticed that it also happens when
watching regular movies on the cable. Screen gets too dark and
then returns to the regular picture. It is very upsetting and you
want to throw something. You think you have bought a really good
TV, paid a good price for it and then you get this. I purchased
a Sony KDL46z4100 Out of Box before this one and had Audio
problems. I took it back and got this one. I really wish
Sony could get it right on something. Will also return this one."</p>
<span class="review-recommend"><b>Would you recommend this product to a friend?:</b> Yes</span>
<span class="review-business"><b>Is this product used primarily for business?:</b> No</span>
</div>
</div>
</div>
</div>
</div>
</div>
<div id="specs-overview" class="specs-overview" onclick="toggleBox('specs-open','specs-closed');changeClass('specs-head','down','right');" >
<h3><a href="#" class="right" id="specs-head">Specifications</a></h3>
<div id="specs-closed"> </div>
<div id="specs-open">
<ul class="xoxo">
<li><h3><a href="#" class="right" id="specs-head">Specifications</a></h3>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year limited</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year limited</dd>
<dt>Product Height</dt>
<dd>30-1/3" with stand (28-5/8" without</dd>
<dt>Product Width</dt>
<dd>44-1/5"</dd>
</dl>
</li>
</ul>
</div>
</div>
</div>
</div>
</div>

</nowiki></pre>

=== hlisting, hproduct, haggregatereview/hreview, xoxo ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/tv-and-video">TV & Video</a></li>
<li class="category"><a href="http://storename.com/televisions">Televisions</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/samsung-ln40a550.jpg" class="photo" alt="picture of samsung ln40a550" />
<div class="fn"><span class="brand">Samsung</span> - 40" 1080p Flat-Panel LCD HDTV</div>
<dl class="identifier">
<dt>Model</dt>
<dd>LN40A550</dd>
<dt>SKU</dt>
<dd>8749465</dd>
</dl>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_3_5.gif" alt="3.5 out of 5 stars"/></a></span><span class="rating">4.7</span> / <span class="best">5</span> (<span class="num">13</span> reviews)</div>
</div>
</div>
<div class="price">$1,099.99</div>
<ol class="xoxo">
<li><h2>Specifications</h2>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year</dd>
<dt>Product Height</dt>
<dd>27" with stand (24-7/10" without)</dd>
<dt>Product Width</dt>
<dd>39-1/5"</dd>
<dt>Product Weight</dt>
<dd>61.5 lbs. with stand (54.5 lbs. without)</dd>
<dt>Product Depth</dt>
<dd>11-4/5" with stand (3-3/5" without)</dd>
<dt>TV Type</dt>
<dd>LCD Flat-Panel</dd>
</dl>
</li>
</div>
</div>
</nowiki></pre>

=== hlisting, hproduct, haudio, haggregatereview/hreview ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct haudio">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/gangsta">Gangsta/Hardcore</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/50cent-curtis.jpg" class="photo" alt="picture of 50 cent" />
<div class="album">Curtis</div>
<div class="contributor"><span class="vcard"><span class=n nickname">50 Cent</span></span></div>
<p>Release date:<abbr class="published" title="2007-09-11">September 11, 2007</abbr></p>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_4_0.gif" alt="4 out of 5 stars"/></a></span><span class="rating">4.0</span> / <span class="best">5</span> Number of reviews:(<span class="num">4</span> reviews)</div>
</div>
<div class="price">$9.99</div>
<a href="add-to-cart-url" rel="payment"><img src="http://storename.com/images/global/add-to-cart.gif" alt="add to cart" /></a>
<h2>Tracks</h2>
<ol>
<li class="item"><span class="position">1</span>.<span class="fn">Intro</span><a href="http://images.storename.com/media/sample/50cent-intro.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">2</span>.<span class="fn">My Gun Go Off</span><a href="http://images.storename.com/media/sample/50cent-gun-go-off.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">3</span>.<span class="fn">Man Down - (censored)</span><a href="http://images.storename.com/media/sample/50cent-man-down.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">4</span>.<span class="fn">I'll Still Kill - (with Akon)</span><a href="http://images.storename.com/media/sample/50cent-ill-still-kill.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">5</span>.<span class="fn">I Get Money</span><a href="http://images.storename.com/media/sample/50cent-i-get-money.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">6</span>.<span class="fn">Come & Go - (with Dr. Dre)</span><a href="http://images.storename.com/media/sample/50cent-come-go.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">7</span>.<span class="fn">Ayo Technology - (with Timbaland/Justin Timberlake)</span><a href="http://images.storename.com/media/sample/50cent-ayo-technology.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">8</span>.<span class="fn">Follow My Lead - (with Robin Thicke)</span><a href="http://images.storename.com/media/sample/50cent-follow-my-lead.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">9</span>.<span class="fn">Movin' on Up</span><a href="http://images.storename.com/media/sample/50cent-movin-on-up.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">10</span>.<span class="fn">Straight to the Bank</span><a href="http://images.storename.com/media/sample/50cent-straight-to-bank.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">11</span>.<span class="fn">Amusement Park</span><a href="http://images.storename.com/media/sample/50cent-amusement-park.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">12</span>.<span class="fn">Fully Loaded Clip</span><a href="http://images.storename.com/media/sample/50cent-fully-loaded-clip.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">13</span>.<span class="fn">Peep Show - (with Eminem)</span><a href="http://images.storename.com/media/sample/50cent-peep-show.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">14</span>.<span class="fn">Fire - (with Young Buck/Nicole Scherzinger)</span><a href="http://images.storename.com/media/sample/50cent-fire.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">15</span>.<span class="fn">All of Me - (with Mary J. Blige)</span><a href="http://images.storename.com/media/sample/50cent-all-of-me.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">16</span>.<span class="fn">Curtis 187</span><a href="http://images.storename.com/media/sample/50cent-curtis-187.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">17</span>.<span class="fn">Touch the Sky - (with Tony Yayo)</span><a href="http://images.storename.com/media/sample/50cent-touch-the-sky.mp3" rel="sample">Listen</a></li>
</ol>
</div>
</div>
</nowiki></pre>

hproduct-recipes

2009-05-07T21:32:23Z

JayMyers: adding description to vevent

== Coded Recipe Examples ==

This page is to provide coded examples showing the interplay between hListing, hProduct and other formats (hAggregateReview, xoxo, to name a few) that could be used to create better semantic page markup.

=== hreview, hproduct, hlisting product example ===

<div class="vevent">
posted: <span class="summary vcard"><span class="dtstart">2009-05-07</span> by <span class="fn">[[User:JayMyers|JayMyers]]</span></span><br/>
Source URL: http://reviews.cnet.com/car-gps-navigation/tomtom-go-930-gps/4505-3430_7-33003945.html
</div>

<pre><nowiki>
<div class="hReview">
<div class="item hProduct">
<span class="fn">TomTom GO 930 GPS</span>
<span class="rating">3.5</span>
<div class="listing hListing-aggregate">
<div class="price">
<span class="min">$352.35</span> - <span class="max">$588.99</span>
</div>
</div>
</div>
<div class="reviewer vcard"><span class="fn">Bonnie Cha</span></div>
<span class="dtreviewed">05/28/2008</span>
</div>
</nowiki></pre>

=== combining hreview-aggregate (new proposal), hlisting, hproduct, xoxo ===

<div class="vevent">
posted: <span class="summary vcard"><span class="dtstart">2009-05-07</span> by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">A more production-grade example of combining microformats, while mixing in other class attributes for the purpose of presentation.</div>
</div>

<pre><nowiki>
<div class="hreview-aggregate">
<div class="item hproduct">
<h1 class="fn"><span class="brand">Sony</span> - BRAVIA / 46" Class / 1080p / 120Hz / LCD HDTV</h1>
<ul>
<li class="identifier"><span class="type">Model</span>: <span class="value">LN40A550</span></li>
<li class="identifier"><span class="type">SKU</span>: <span class="value">8749465</span></li>
</ul>
<div class="listing hListing">
<div class="leftcol"><img src="/images/product.jpg" alt="Sony - BRAVIA 46 Class 1080p 120Hz LCD HDTV" class="photo"/></div>
<div class="rightcol">
<div class="rating"><img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" class="average" /></div>
<div>(<span class="count">187</span> Reviews)</div>
<div class="grey">was $1,099.99</div>
<div class="price">$999.99</div>
</div>
<div class="shipping">Shipping: Usually leaves our warehouse in 1 business day.</div>
</div>
<div id="product-overview" class="product-overview" onclick="toggleBox('product-overview-open','product-overview-closed');changeClass('overview-head','down','right');">
<h3><a href="#" class="right" id="overview-head">Overview</a></h3>
<div id="product-overview-closed">
<p class="padtop">This flat-panel LCD HDTV features a 16:9 widescreen aspect ratio and a 50,000:1 dynamic contrast ratio, so you can enjoy your favorite movies in true 1080p high-definition.</p>
<a href="#" class="readmore mini-right">Show Full Overview</a>
</div>
<div id="product-overview-open">
<p class="description">This flat-panel LCD HDTV features a 16:9 widescreen aspect ratio and a 50,000:1 dynamic contrast ratio, so you can enjoy your favorite movies in true 1080p high-definition.</p>
<ul class="xoxo">
<li><h3 class="bottom-line">What's Included</h3>
<ol>
<li>Sony BRAVIA / 46" Class / 1080p / 120Hz / LCD HDTV</li>
<li>Tabletop stand, 4 screws</li>
<li>Remote RM-YD028</li>
<li>AC power cord, 2 AA batteries</li>
<li>Owner's manual</li>
</ol>
</li>
</ul>
<ul class="xoxo">
<li><h3 class="bottom-line">Product Features</h3>
<dl>
<dt>Built-in HDTV tuner</dt>
<dd>Add HD-capable antenna to receive over-the-air high-definition broadcasts, where available. Optional set-top box required for high-definition cable or satellite programming.</dd>
<dt>46" screen measured diagonally from corner to corner</dt>
<dd>Everyone will have a great view of the show or game.</dd>
<dt>1080p display</dt>
<dd>Provides the highest quality progressive-scan picture possible for a high-definition source.</dd>
<dt>16:9 widescreen aspect ratio</dt>
<dd>With CineMotion reverse 3.2 pulldown technology and 24p True Cinema mode delivers accurate reproduction of film-based sources for a cinema-style entertainment experience.</dd>
<dt>BRAVIA Engine 2 full digital video processor</dt>
<dd>Reduces video noise, improves color and sharpens the overall image detail.</dd>
<dt>Advanced Contrast Enhancer (ACE)</dt>
<dd>Uses real-time image processing to adjust the contrast ratio.</dd>
<dt>Motionflow 120Hz technology</dt>
<dd>Reduces jitter and sharpens fast-moving images for a crisp picture.</dd>
<dt>LightSensor technology</dt>
<dd>Monitors ambient room lighting conditions and adjusts the backlit intensity accordingly.</dd>
<dt>50,000:1 dynamic contrast ratio</dt>
<dd>For an arresting viewing experience.</dd>
<dt>3D digital comb filter</dt>
<dd>Brings out fine picture detail and enhances color purity.</dd>
<dt>SRS TruSurround XT</dt>
<dd>With Dolby Digital and SteadySound automatic volume control delivers a lush soundscape.</dd>
<dt>Ultraslim (3-4/5" deep) design and VESA compatible</dt>
<dd>Ideal for wall mounting (with optional mounting kit, not included).</dd>
</dl>
</li>
</ul>
</div>
<div id="customer-overview" class="customer-overview">
<div onclick="toggleBox('customer-open','customer-closed');changeClass('review-head','down','right');">
<h3><span class="right" id="review-head" >Customer Reviews (34)</span></h3>
<p class="padtop">Average: <img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" /></p>
<p>50% of customers would recommend this product to a friend (2 of 4).</p>
</div>
<div id="customer-closed">
<a href="#" class="readmore mini-right" onclick="toggleBox('customer-open','customer-closed');changeClass('review-head','down','right');" >Show Reviews</a>
</div>
<div id="customer-open">
<div id="sort-reviews">
<span class="big-grey">Sort by:</span>
<select>
<option value="newest">Date: Newest</option>
<option value="oldest">Date: Oldest</option>
</select>
<input type="submit" value="Go" />
</div>
<div id="review-list">
<div class="number-of-reviews grey">1 - 10 of 34 Reviews</div>
<div class="hreview">
<span id="review-one" class="summary">TV may be better than you think.</span>
<span class="reviewer vcard">by <span class="fn nickname">bezb18</span> from Maryland on <span class="dtreviewed">04/07/2009</span></span>
<span class="rating"><img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" /></span>
<div id="hidden-one">
<div class="review-box">
<table class="review-summary">
<tr><td>Picture Quality:</td><td><img alt="50% Rating" src="images/bar-50.gif" /></td></tr>
<tr><td>Sound Quality:</td><td><img alt="100% Rating" src="images/bar-100.gif" /></td></tr>
<tr><td>Features:</td><td><img alt="75% Rating" src="images/bar-75.gif" /></td></tr>
</table>
<span class="review-great"><b>What's great about it:</b> Vivid picture.</span>
<span class="review-not"><b>What's not so great:</b> Backlight, fades picture to black.</span>
<p class="description">"I purchased this TV about a week ago and
after putting a DVD on and noticed the scene fading to almost
completely black at several times in the movie, I thought I
might have a problem. Then noticed that it also happens when
watching regular movies on the cable. Screen gets too dark and
then returns to the regular picture. It is very upsetting and you
want to throw something. You think you have bought a really good
TV, paid a good price for it and then you get this. I purchased
a Sony KDL46z4100 Out of Box before this one and had Audio
problems. I took it back and got this one. I really wish
Sony could get it right on something. Will also return this one."</p>
<span class="review-recommend"><b>Would you recommend this product to a friend?:</b> Yes</span>
<span class="review-business"><b>Is this product used primarily for business?:</b> No</span>
</div>
</div>
</div>
</div>
</div>
</div>
<div id="specs-overview" class="specs-overview" onclick="toggleBox('specs-open','specs-closed');changeClass('specs-head','down','right');" >
<h3><a href="#" class="right" id="specs-head">Specifications</a></h3>
<div id="specs-closed"> </div>
<div id="specs-open">
<ul class="xoxo">
<li><h3><a href="#" class="right" id="specs-head">Specifications</a></h3>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year limited</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year limited</dd>
<dt>Product Height</dt>
<dd>30-1/3" with stand (28-5/8" without</dd>
<dt>Product Width</dt>
<dd>44-1/5"</dd>
</dl>
</li>
</ul>
</div>
</div>
</div>
</div>
</div>

</nowiki></pre>

=== hlisting, hproduct, haggregatereview/hreview, xoxo ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/tv-and-video">TV & Video</a></li>
<li class="category"><a href="http://storename.com/televisions">Televisions</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/samsung-ln40a550.jpg" class="photo" alt="picture of samsung ln40a550" />
<div class="fn"><span class="brand">Samsung</span> - 40" 1080p Flat-Panel LCD HDTV</div>
<dl class="identifier">
<dt>Model</dt>
<dd>LN40A550</dd>
<dt>SKU</dt>
<dd>8749465</dd>
</dl>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_3_5.gif" alt="3.5 out of 5 stars"/></a></span><span class="rating">4.7</span> / <span class="best">5</span> (<span class="num">13</span> reviews)</div>
</div>
</div>
<div class="price">$1,099.99</div>
<ol class="xoxo">
<li><h2>Specifications</h2>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year</dd>
<dt>Product Height</dt>
<dd>27" with stand (24-7/10" without)</dd>
<dt>Product Width</dt>
<dd>39-1/5"</dd>
<dt>Product Weight</dt>
<dd>61.5 lbs. with stand (54.5 lbs. without)</dd>
<dt>Product Depth</dt>
<dd>11-4/5" with stand (3-3/5" without)</dd>
<dt>TV Type</dt>
<dd>LCD Flat-Panel</dd>
</dl>
</li>
</div>
</div>
</nowiki></pre>

=== hlisting, hproduct, haudio, haggregatereview/hreview ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct haudio">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/gangsta">Gangsta/Hardcore</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/50cent-curtis.jpg" class="photo" alt="picture of 50 cent" />
<div class="album">Curtis</div>
<div class="contributor"><span class="vcard"><span class=n nickname">50 Cent</span></span></div>
<p>Release date:<abbr class="published" title="2007-09-11">September 11, 2007</abbr></p>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_4_0.gif" alt="4 out of 5 stars"/></a></span><span class="rating">4.0</span> / <span class="best">5</span> Number of reviews:(<span class="num">4</span> reviews)</div>
</div>
<div class="price">$9.99</div>
<a href="add-to-cart-url" rel="payment"><img src="http://storename.com/images/global/add-to-cart.gif" alt="add to cart" /></a>
<h2>Tracks</h2>
<ol>
<li class="item"><span class="position">1</span>.<span class="fn">Intro</span><a href="http://images.storename.com/media/sample/50cent-intro.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">2</span>.<span class="fn">My Gun Go Off</span><a href="http://images.storename.com/media/sample/50cent-gun-go-off.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">3</span>.<span class="fn">Man Down - (censored)</span><a href="http://images.storename.com/media/sample/50cent-man-down.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">4</span>.<span class="fn">I'll Still Kill - (with Akon)</span><a href="http://images.storename.com/media/sample/50cent-ill-still-kill.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">5</span>.<span class="fn">I Get Money</span><a href="http://images.storename.com/media/sample/50cent-i-get-money.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">6</span>.<span class="fn">Come & Go - (with Dr. Dre)</span><a href="http://images.storename.com/media/sample/50cent-come-go.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">7</span>.<span class="fn">Ayo Technology - (with Timbaland/Justin Timberlake)</span><a href="http://images.storename.com/media/sample/50cent-ayo-technology.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">8</span>.<span class="fn">Follow My Lead - (with Robin Thicke)</span><a href="http://images.storename.com/media/sample/50cent-follow-my-lead.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">9</span>.<span class="fn">Movin' on Up</span><a href="http://images.storename.com/media/sample/50cent-movin-on-up.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">10</span>.<span class="fn">Straight to the Bank</span><a href="http://images.storename.com/media/sample/50cent-straight-to-bank.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">11</span>.<span class="fn">Amusement Park</span><a href="http://images.storename.com/media/sample/50cent-amusement-park.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">12</span>.<span class="fn">Fully Loaded Clip</span><a href="http://images.storename.com/media/sample/50cent-fully-loaded-clip.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">13</span>.<span class="fn">Peep Show - (with Eminem)</span><a href="http://images.storename.com/media/sample/50cent-peep-show.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">14</span>.<span class="fn">Fire - (with Young Buck/Nicole Scherzinger)</span><a href="http://images.storename.com/media/sample/50cent-fire.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">15</span>.<span class="fn">All of Me - (with Mary J. Blige)</span><a href="http://images.storename.com/media/sample/50cent-all-of-me.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">16</span>.<span class="fn">Curtis 187</span><a href="http://images.storename.com/media/sample/50cent-curtis-187.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">17</span>.<span class="fn">Touch the Sky - (with Tony Yayo)</span><a href="http://images.storename.com/media/sample/50cent-touch-the-sky.mp3" rel="sample">Listen</a></li>
</ol>
</div>
</div>
</nowiki></pre>

hproduct-recipes

2009-05-07T21:30:10Z

JayMyers: /* hreview, hproduct, hlisting single product example */

== Coded Recipe Examples ==

This page is to provide coded examples showing the interplay between hListing, hProduct and other formats (hAggregateReview, xoxo, to name a few) that could be used to create better semantic page markup.

=== hreview, hproduct, hlisting product example ===

<div class="vevent">
posted: <span class="summary vcard"><span class="dtstart">2009-05-07</span> by <span class="fn">[[User:JayMyers|JayMyers]]</span></span><br/>
Source URL: http://reviews.cnet.com/car-gps-navigation/tomtom-go-930-gps/4505-3430_7-33003945.html
</div>

<pre><nowiki>
<div class="hReview">
<div class="item hProduct">
<span class="fn">TomTom GO 930 GPS</span>
<span class="rating">3.5</span>
<div class="listing hListing-aggregate">
<div class="price">
<span class="min">$352.35</span> - <span class="max">$588.99</span>
</div>
</div>
</div>
<div class="reviewer vcard"><span class="fn">Bonnie Cha</span></div>
<span class="dtreviewed">05/28/2008</span>
</div>
</nowiki></pre>

=== combining hreview-aggregate (new proposal), hlisting, hproduct, xoxo ===

<div class="vevent">
posted: <span class="summary vcard"><span class="dtstart">2009-05-07</span> by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
</div>

<pre><nowiki>
<div class="hreview-aggregate">
<div class="item hproduct">
<h1 class="fn"><span class="brand">Sony</span> - BRAVIA / 46" Class / 1080p / 120Hz / LCD HDTV</h1>
<ul>
<li class="identifier"><span class="type">Model</span>: <span class="value">LN40A550</span></li>
<li class="identifier"><span class="type">SKU</span>: <span class="value">8749465</span></li>
</ul>
<div class="listing hListing">
<div class="leftcol"><img src="/images/product.jpg" alt="Sony - BRAVIA 46 Class 1080p 120Hz LCD HDTV" class="photo"/></div>
<div class="rightcol">
<div class="rating"><img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" class="average" /></div>
<div>(<span class="count">187</span> Reviews)</div>
<div class="grey">was $1,099.99</div>
<div class="price">$999.99</div>
</div>
<div class="shipping">Shipping: Usually leaves our warehouse in 1 business day.</div>
</div>
<div id="product-overview" class="product-overview" onclick="toggleBox('product-overview-open','product-overview-closed');changeClass('overview-head','down','right');">
<h3><a href="#" class="right" id="overview-head">Overview</a></h3>
<div id="product-overview-closed">
<p class="padtop">This flat-panel LCD HDTV features a 16:9 widescreen aspect ratio and a 50,000:1 dynamic contrast ratio, so you can enjoy your favorite movies in true 1080p high-definition.</p>
<a href="#" class="readmore mini-right">Show Full Overview</a>
</div>
<div id="product-overview-open">
<p class="description">This flat-panel LCD HDTV features a 16:9 widescreen aspect ratio and a 50,000:1 dynamic contrast ratio, so you can enjoy your favorite movies in true 1080p high-definition.</p>
<ul class="xoxo">
<li><h3 class="bottom-line">What's Included</h3>
<ol>
<li>Sony BRAVIA / 46" Class / 1080p / 120Hz / LCD HDTV</li>
<li>Tabletop stand, 4 screws</li>
<li>Remote RM-YD028</li>
<li>AC power cord, 2 AA batteries</li>
<li>Owner's manual</li>
</ol>
</li>
</ul>
<ul class="xoxo">
<li><h3 class="bottom-line">Product Features</h3>
<dl>
<dt>Built-in HDTV tuner</dt>
<dd>Add HD-capable antenna to receive over-the-air high-definition broadcasts, where available. Optional set-top box required for high-definition cable or satellite programming.</dd>
<dt>46" screen measured diagonally from corner to corner</dt>
<dd>Everyone will have a great view of the show or game.</dd>
<dt>1080p display</dt>
<dd>Provides the highest quality progressive-scan picture possible for a high-definition source.</dd>
<dt>16:9 widescreen aspect ratio</dt>
<dd>With CineMotion reverse 3.2 pulldown technology and 24p True Cinema mode delivers accurate reproduction of film-based sources for a cinema-style entertainment experience.</dd>
<dt>BRAVIA Engine 2 full digital video processor</dt>
<dd>Reduces video noise, improves color and sharpens the overall image detail.</dd>
<dt>Advanced Contrast Enhancer (ACE)</dt>
<dd>Uses real-time image processing to adjust the contrast ratio.</dd>
<dt>Motionflow 120Hz technology</dt>
<dd>Reduces jitter and sharpens fast-moving images for a crisp picture.</dd>
<dt>LightSensor technology</dt>
<dd>Monitors ambient room lighting conditions and adjusts the backlit intensity accordingly.</dd>
<dt>50,000:1 dynamic contrast ratio</dt>
<dd>For an arresting viewing experience.</dd>
<dt>3D digital comb filter</dt>
<dd>Brings out fine picture detail and enhances color purity.</dd>
<dt>SRS TruSurround XT</dt>
<dd>With Dolby Digital and SteadySound automatic volume control delivers a lush soundscape.</dd>
<dt>Ultraslim (3-4/5" deep) design and VESA compatible</dt>
<dd>Ideal for wall mounting (with optional mounting kit, not included).</dd>
</dl>
</li>
</ul>
</div>
<div id="customer-overview" class="customer-overview">
<div onclick="toggleBox('customer-open','customer-closed');changeClass('review-head','down','right');">
<h3><span class="right" id="review-head" >Customer Reviews (34)</span></h3>
<p class="padtop">Average: <img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" /></p>
<p>50% of customers would recommend this product to a friend (2 of 4).</p>
</div>
<div id="customer-closed">
<a href="#" class="readmore mini-right" onclick="toggleBox('customer-open','customer-closed');changeClass('review-head','down','right');" >Show Reviews</a>
</div>
<div id="customer-open">
<div id="sort-reviews">
<span class="big-grey">Sort by:</span>
<select>
<option value="newest">Date: Newest</option>
<option value="oldest">Date: Oldest</option>
</select>
<input type="submit" value="Go" />
</div>
<div id="review-list">
<div class="number-of-reviews grey">1 - 10 of 34 Reviews</div>
<div class="hreview">
<span id="review-one" class="summary">TV may be better than you think.</span>
<span class="reviewer vcard">by <span class="fn nickname">bezb18</span> from Maryland on <span class="dtreviewed">04/07/2009</span></span>
<span class="rating"><img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" /></span>
<div id="hidden-one">
<div class="review-box">
<table class="review-summary">
<tr><td>Picture Quality:</td><td><img alt="50% Rating" src="images/bar-50.gif" /></td></tr>
<tr><td>Sound Quality:</td><td><img alt="100% Rating" src="images/bar-100.gif" /></td></tr>
<tr><td>Features:</td><td><img alt="75% Rating" src="images/bar-75.gif" /></td></tr>
</table>
<span class="review-great"><b>What's great about it:</b> Vivid picture.</span>
<span class="review-not"><b>What's not so great:</b> Backlight, fades picture to black.</span>
<p class="description">"I purchased this TV about a week ago and
after putting a DVD on and noticed the scene fading to almost
completely black at several times in the movie, I thought I
might have a problem. Then noticed that it also happens when
watching regular movies on the cable. Screen gets too dark and
then returns to the regular picture. It is very upsetting and you
want to throw something. You think you have bought a really good
TV, paid a good price for it and then you get this. I purchased
a Sony KDL46z4100 Out of Box before this one and had Audio
problems. I took it back and got this one. I really wish
Sony could get it right on something. Will also return this one."</p>
<span class="review-recommend"><b>Would you recommend this product to a friend?:</b> Yes</span>
<span class="review-business"><b>Is this product used primarily for business?:</b> No</span>
</div>
</div>
</div>
</div>
</div>
</div>
<div id="specs-overview" class="specs-overview" onclick="toggleBox('specs-open','specs-closed');changeClass('specs-head','down','right');" >
<h3><a href="#" class="right" id="specs-head">Specifications</a></h3>
<div id="specs-closed"> </div>
<div id="specs-open">
<ul class="xoxo">
<li><h3><a href="#" class="right" id="specs-head">Specifications</a></h3>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year limited</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year limited</dd>
<dt>Product Height</dt>
<dd>30-1/3" with stand (28-5/8" without</dd>
<dt>Product Width</dt>
<dd>44-1/5"</dd>
</dl>
</li>
</ul>
</div>
</div>
</div>
</div>
</div>

</nowiki></pre>

=== hlisting, hproduct, haggregatereview/hreview, xoxo ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/tv-and-video">TV & Video</a></li>
<li class="category"><a href="http://storename.com/televisions">Televisions</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/samsung-ln40a550.jpg" class="photo" alt="picture of samsung ln40a550" />
<div class="fn"><span class="brand">Samsung</span> - 40" 1080p Flat-Panel LCD HDTV</div>
<dl class="identifier">
<dt>Model</dt>
<dd>LN40A550</dd>
<dt>SKU</dt>
<dd>8749465</dd>
</dl>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_3_5.gif" alt="3.5 out of 5 stars"/></a></span><span class="rating">4.7</span> / <span class="best">5</span> (<span class="num">13</span> reviews)</div>
</div>
</div>
<div class="price">$1,099.99</div>
<ol class="xoxo">
<li><h2>Specifications</h2>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year</dd>
<dt>Product Height</dt>
<dd>27" with stand (24-7/10" without)</dd>
<dt>Product Width</dt>
<dd>39-1/5"</dd>
<dt>Product Weight</dt>
<dd>61.5 lbs. with stand (54.5 lbs. without)</dd>
<dt>Product Depth</dt>
<dd>11-4/5" with stand (3-3/5" without)</dd>
<dt>TV Type</dt>
<dd>LCD Flat-Panel</dd>
</dl>
</li>
</div>
</div>
</nowiki></pre>

=== hlisting, hproduct, haudio, haggregatereview/hreview ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct haudio">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/gangsta">Gangsta/Hardcore</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/50cent-curtis.jpg" class="photo" alt="picture of 50 cent" />
<div class="album">Curtis</div>
<div class="contributor"><span class="vcard"><span class=n nickname">50 Cent</span></span></div>
<p>Release date:<abbr class="published" title="2007-09-11">September 11, 2007</abbr></p>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_4_0.gif" alt="4 out of 5 stars"/></a></span><span class="rating">4.0</span> / <span class="best">5</span> Number of reviews:(<span class="num">4</span> reviews)</div>
</div>
<div class="price">$9.99</div>
<a href="add-to-cart-url" rel="payment"><img src="http://storename.com/images/global/add-to-cart.gif" alt="add to cart" /></a>
<h2>Tracks</h2>
<ol>
<li class="item"><span class="position">1</span>.<span class="fn">Intro</span><a href="http://images.storename.com/media/sample/50cent-intro.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">2</span>.<span class="fn">My Gun Go Off</span><a href="http://images.storename.com/media/sample/50cent-gun-go-off.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">3</span>.<span class="fn">Man Down - (censored)</span><a href="http://images.storename.com/media/sample/50cent-man-down.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">4</span>.<span class="fn">I'll Still Kill - (with Akon)</span><a href="http://images.storename.com/media/sample/50cent-ill-still-kill.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">5</span>.<span class="fn">I Get Money</span><a href="http://images.storename.com/media/sample/50cent-i-get-money.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">6</span>.<span class="fn">Come & Go - (with Dr. Dre)</span><a href="http://images.storename.com/media/sample/50cent-come-go.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">7</span>.<span class="fn">Ayo Technology - (with Timbaland/Justin Timberlake)</span><a href="http://images.storename.com/media/sample/50cent-ayo-technology.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">8</span>.<span class="fn">Follow My Lead - (with Robin Thicke)</span><a href="http://images.storename.com/media/sample/50cent-follow-my-lead.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">9</span>.<span class="fn">Movin' on Up</span><a href="http://images.storename.com/media/sample/50cent-movin-on-up.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">10</span>.<span class="fn">Straight to the Bank</span><a href="http://images.storename.com/media/sample/50cent-straight-to-bank.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">11</span>.<span class="fn">Amusement Park</span><a href="http://images.storename.com/media/sample/50cent-amusement-park.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">12</span>.<span class="fn">Fully Loaded Clip</span><a href="http://images.storename.com/media/sample/50cent-fully-loaded-clip.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">13</span>.<span class="fn">Peep Show - (with Eminem)</span><a href="http://images.storename.com/media/sample/50cent-peep-show.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">14</span>.<span class="fn">Fire - (with Young Buck/Nicole Scherzinger)</span><a href="http://images.storename.com/media/sample/50cent-fire.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">15</span>.<span class="fn">All of Me - (with Mary J. Blige)</span><a href="http://images.storename.com/media/sample/50cent-all-of-me.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">16</span>.<span class="fn">Curtis 187</span><a href="http://images.storename.com/media/sample/50cent-curtis-187.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">17</span>.<span class="fn">Touch the Sky - (with Tony Yayo)</span><a href="http://images.storename.com/media/sample/50cent-touch-the-sky.mp3" rel="sample">Listen</a></li>
</ol>
</div>
</div>
</nowiki></pre>

hproduct-recipes

2009-05-07T21:29:35Z

JayMyers: changing title

== Coded Recipe Examples ==

This page is to provide coded examples showing the interplay between hListing, hProduct and other formats (hAggregateReview, xoxo, to name a few) that could be used to create better semantic page markup.

=== hreview, hproduct, hlisting single product example ===

<div class="vevent">
posted: <span class="summary vcard"><span class="dtstart">2009-05-07</span> by <span class="fn">[[User:JayMyers|JayMyers]]</span></span><br/>
Source URL: http://reviews.cnet.com/car-gps-navigation/tomtom-go-930-gps/4505-3430_7-33003945.html
</div>

<pre><nowiki>
<div class="hReview">
<div class="item hProduct">
<span class="fn">TomTom GO 930 GPS</span>
<span class="rating">3.5</span>
<div class="listing hListing-aggregate">
<div class="price">
<span class="min">$352.35</span> - <span class="max">$588.99</span>
</div>
</div>
</div>
<div class="reviewer vcard"><span class="fn">Bonnie Cha</span></div>
<span class="dtreviewed">05/28/2008</span>
</div>
</nowiki></pre>

=== combining hreview-aggregate (new proposal), hlisting, hproduct, xoxo ===

<div class="vevent">
posted: <span class="summary vcard"><span class="dtstart">2009-05-07</span> by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
</div>

<pre><nowiki>
<div class="hreview-aggregate">
<div class="item hproduct">
<h1 class="fn"><span class="brand">Sony</span> - BRAVIA / 46" Class / 1080p / 120Hz / LCD HDTV</h1>
<ul>
<li class="identifier"><span class="type">Model</span>: <span class="value">LN40A550</span></li>
<li class="identifier"><span class="type">SKU</span>: <span class="value">8749465</span></li>
</ul>
<div class="listing hListing">
<div class="leftcol"><img src="/images/product.jpg" alt="Sony - BRAVIA 46 Class 1080p 120Hz LCD HDTV" class="photo"/></div>
<div class="rightcol">
<div class="rating"><img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" class="average" /></div>
<div>(<span class="count">187</span> Reviews)</div>
<div class="grey">was $1,099.99</div>
<div class="price">$999.99</div>
</div>
<div class="shipping">Shipping: Usually leaves our warehouse in 1 business day.</div>
</div>
<div id="product-overview" class="product-overview" onclick="toggleBox('product-overview-open','product-overview-closed');changeClass('overview-head','down','right');">
<h3><a href="#" class="right" id="overview-head">Overview</a></h3>
<div id="product-overview-closed">
<p class="padtop">This flat-panel LCD HDTV features a 16:9 widescreen aspect ratio and a 50,000:1 dynamic contrast ratio, so you can enjoy your favorite movies in true 1080p high-definition.</p>
<a href="#" class="readmore mini-right">Show Full Overview</a>
</div>
<div id="product-overview-open">
<p class="description">This flat-panel LCD HDTV features a 16:9 widescreen aspect ratio and a 50,000:1 dynamic contrast ratio, so you can enjoy your favorite movies in true 1080p high-definition.</p>
<ul class="xoxo">
<li><h3 class="bottom-line">What's Included</h3>
<ol>
<li>Sony BRAVIA / 46" Class / 1080p / 120Hz / LCD HDTV</li>
<li>Tabletop stand, 4 screws</li>
<li>Remote RM-YD028</li>
<li>AC power cord, 2 AA batteries</li>
<li>Owner's manual</li>
</ol>
</li>
</ul>
<ul class="xoxo">
<li><h3 class="bottom-line">Product Features</h3>
<dl>
<dt>Built-in HDTV tuner</dt>
<dd>Add HD-capable antenna to receive over-the-air high-definition broadcasts, where available. Optional set-top box required for high-definition cable or satellite programming.</dd>
<dt>46" screen measured diagonally from corner to corner</dt>
<dd>Everyone will have a great view of the show or game.</dd>
<dt>1080p display</dt>
<dd>Provides the highest quality progressive-scan picture possible for a high-definition source.</dd>
<dt>16:9 widescreen aspect ratio</dt>
<dd>With CineMotion reverse 3.2 pulldown technology and 24p True Cinema mode delivers accurate reproduction of film-based sources for a cinema-style entertainment experience.</dd>
<dt>BRAVIA Engine 2 full digital video processor</dt>
<dd>Reduces video noise, improves color and sharpens the overall image detail.</dd>
<dt>Advanced Contrast Enhancer (ACE)</dt>
<dd>Uses real-time image processing to adjust the contrast ratio.</dd>
<dt>Motionflow 120Hz technology</dt>
<dd>Reduces jitter and sharpens fast-moving images for a crisp picture.</dd>
<dt>LightSensor technology</dt>
<dd>Monitors ambient room lighting conditions and adjusts the backlit intensity accordingly.</dd>
<dt>50,000:1 dynamic contrast ratio</dt>
<dd>For an arresting viewing experience.</dd>
<dt>3D digital comb filter</dt>
<dd>Brings out fine picture detail and enhances color purity.</dd>
<dt>SRS TruSurround XT</dt>
<dd>With Dolby Digital and SteadySound automatic volume control delivers a lush soundscape.</dd>
<dt>Ultraslim (3-4/5" deep) design and VESA compatible</dt>
<dd>Ideal for wall mounting (with optional mounting kit, not included).</dd>
</dl>
</li>
</ul>
</div>
<div id="customer-overview" class="customer-overview">
<div onclick="toggleBox('customer-open','customer-closed');changeClass('review-head','down','right');">
<h3><span class="right" id="review-head" >Customer Reviews (34)</span></h3>
<p class="padtop">Average: <img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" /></p>
<p>50% of customers would recommend this product to a friend (2 of 4).</p>
</div>
<div id="customer-closed">
<a href="#" class="readmore mini-right" onclick="toggleBox('customer-open','customer-closed');changeClass('review-head','down','right');" >Show Reviews</a>
</div>
<div id="customer-open">
<div id="sort-reviews">
<span class="big-grey">Sort by:</span>
<select>
<option value="newest">Date: Newest</option>
<option value="oldest">Date: Oldest</option>
</select>
<input type="submit" value="Go" />
</div>
<div id="review-list">
<div class="number-of-reviews grey">1 - 10 of 34 Reviews</div>
<div class="hreview">
<span id="review-one" class="summary">TV may be better than you think.</span>
<span class="reviewer vcard">by <span class="fn nickname">bezb18</span> from Maryland on <span class="dtreviewed">04/07/2009</span></span>
<span class="rating"><img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" /></span>
<div id="hidden-one">
<div class="review-box">
<table class="review-summary">
<tr><td>Picture Quality:</td><td><img alt="50% Rating" src="images/bar-50.gif" /></td></tr>
<tr><td>Sound Quality:</td><td><img alt="100% Rating" src="images/bar-100.gif" /></td></tr>
<tr><td>Features:</td><td><img alt="75% Rating" src="images/bar-75.gif" /></td></tr>
</table>
<span class="review-great"><b>What's great about it:</b> Vivid picture.</span>
<span class="review-not"><b>What's not so great:</b> Backlight, fades picture to black.</span>
<p class="description">"I purchased this TV about a week ago and
after putting a DVD on and noticed the scene fading to almost
completely black at several times in the movie, I thought I
might have a problem. Then noticed that it also happens when
watching regular movies on the cable. Screen gets too dark and
then returns to the regular picture. It is very upsetting and you
want to throw something. You think you have bought a really good
TV, paid a good price for it and then you get this. I purchased
a Sony KDL46z4100 Out of Box before this one and had Audio
problems. I took it back and got this one. I really wish
Sony could get it right on something. Will also return this one."</p>
<span class="review-recommend"><b>Would you recommend this product to a friend?:</b> Yes</span>
<span class="review-business"><b>Is this product used primarily for business?:</b> No</span>
</div>
</div>
</div>
</div>
</div>
</div>
<div id="specs-overview" class="specs-overview" onclick="toggleBox('specs-open','specs-closed');changeClass('specs-head','down','right');" >
<h3><a href="#" class="right" id="specs-head">Specifications</a></h3>
<div id="specs-closed"> </div>
<div id="specs-open">
<ul class="xoxo">
<li><h3><a href="#" class="right" id="specs-head">Specifications</a></h3>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year limited</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year limited</dd>
<dt>Product Height</dt>
<dd>30-1/3" with stand (28-5/8" without</dd>
<dt>Product Width</dt>
<dd>44-1/5"</dd>
</dl>
</li>
</ul>
</div>
</div>
</div>
</div>
</div>

</nowiki></pre>

=== hlisting, hproduct, haggregatereview/hreview, xoxo ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/tv-and-video">TV & Video</a></li>
<li class="category"><a href="http://storename.com/televisions">Televisions</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/samsung-ln40a550.jpg" class="photo" alt="picture of samsung ln40a550" />
<div class="fn"><span class="brand">Samsung</span> - 40" 1080p Flat-Panel LCD HDTV</div>
<dl class="identifier">
<dt>Model</dt>
<dd>LN40A550</dd>
<dt>SKU</dt>
<dd>8749465</dd>
</dl>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_3_5.gif" alt="3.5 out of 5 stars"/></a></span><span class="rating">4.7</span> / <span class="best">5</span> (<span class="num">13</span> reviews)</div>
</div>
</div>
<div class="price">$1,099.99</div>
<ol class="xoxo">
<li><h2>Specifications</h2>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year</dd>
<dt>Product Height</dt>
<dd>27" with stand (24-7/10" without)</dd>
<dt>Product Width</dt>
<dd>39-1/5"</dd>
<dt>Product Weight</dt>
<dd>61.5 lbs. with stand (54.5 lbs. without)</dd>
<dt>Product Depth</dt>
<dd>11-4/5" with stand (3-3/5" without)</dd>
<dt>TV Type</dt>
<dd>LCD Flat-Panel</dd>
</dl>
</li>
</div>
</div>
</nowiki></pre>

=== hlisting, hproduct, haudio, haggregatereview/hreview ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct haudio">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/gangsta">Gangsta/Hardcore</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/50cent-curtis.jpg" class="photo" alt="picture of 50 cent" />
<div class="album">Curtis</div>
<div class="contributor"><span class="vcard"><span class=n nickname">50 Cent</span></span></div>
<p>Release date:<abbr class="published" title="2007-09-11">September 11, 2007</abbr></p>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_4_0.gif" alt="4 out of 5 stars"/></a></span><span class="rating">4.0</span> / <span class="best">5</span> Number of reviews:(<span class="num">4</span> reviews)</div>
</div>
<div class="price">$9.99</div>
<a href="add-to-cart-url" rel="payment"><img src="http://storename.com/images/global/add-to-cart.gif" alt="add to cart" /></a>
<h2>Tracks</h2>
<ol>
<li class="item"><span class="position">1</span>.<span class="fn">Intro</span><a href="http://images.storename.com/media/sample/50cent-intro.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">2</span>.<span class="fn">My Gun Go Off</span><a href="http://images.storename.com/media/sample/50cent-gun-go-off.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">3</span>.<span class="fn">Man Down - (censored)</span><a href="http://images.storename.com/media/sample/50cent-man-down.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">4</span>.<span class="fn">I'll Still Kill - (with Akon)</span><a href="http://images.storename.com/media/sample/50cent-ill-still-kill.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">5</span>.<span class="fn">I Get Money</span><a href="http://images.storename.com/media/sample/50cent-i-get-money.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">6</span>.<span class="fn">Come & Go - (with Dr. Dre)</span><a href="http://images.storename.com/media/sample/50cent-come-go.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">7</span>.<span class="fn">Ayo Technology - (with Timbaland/Justin Timberlake)</span><a href="http://images.storename.com/media/sample/50cent-ayo-technology.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">8</span>.<span class="fn">Follow My Lead - (with Robin Thicke)</span><a href="http://images.storename.com/media/sample/50cent-follow-my-lead.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">9</span>.<span class="fn">Movin' on Up</span><a href="http://images.storename.com/media/sample/50cent-movin-on-up.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">10</span>.<span class="fn">Straight to the Bank</span><a href="http://images.storename.com/media/sample/50cent-straight-to-bank.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">11</span>.<span class="fn">Amusement Park</span><a href="http://images.storename.com/media/sample/50cent-amusement-park.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">12</span>.<span class="fn">Fully Loaded Clip</span><a href="http://images.storename.com/media/sample/50cent-fully-loaded-clip.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">13</span>.<span class="fn">Peep Show - (with Eminem)</span><a href="http://images.storename.com/media/sample/50cent-peep-show.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">14</span>.<span class="fn">Fire - (with Young Buck/Nicole Scherzinger)</span><a href="http://images.storename.com/media/sample/50cent-fire.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">15</span>.<span class="fn">All of Me - (with Mary J. Blige)</span><a href="http://images.storename.com/media/sample/50cent-all-of-me.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">16</span>.<span class="fn">Curtis 187</span><a href="http://images.storename.com/media/sample/50cent-curtis-187.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">17</span>.<span class="fn">Touch the Sky - (with Tony Yayo)</span><a href="http://images.storename.com/media/sample/50cent-touch-the-sky.mp3" rel="sample">Listen</a></li>
</ol>
</div>
</div>
</nowiki></pre>

hproduct-recipes

2009-05-07T21:28:35Z

JayMyers: correcting User: url

== Coded Recipe Examples ==

This page is to provide coded examples showing the interplay between hListing, hProduct and other formats (hAggregateReview, xoxo, to name a few) that could be used to create better semantic page markup.

=== hreview, hproduct, hlisting short example ===

<div class="vevent">
posted: <span class="summary vcard"><span class="dtstart">2009-05-07</span> by <span class="fn">[[User:JayMyers|JayMyers]]</span></span><br/>
Source URL: http://reviews.cnet.com/car-gps-navigation/tomtom-go-930-gps/4505-3430_7-33003945.html
</div>

<pre><nowiki>
<div class="hReview">
<div class="item hProduct">
<span class="fn">TomTom GO 930 GPS</span>
<span class="rating">3.5</span>
<div class="listing hListing-aggregate">
<div class="price">
<span class="min">$352.35</span> - <span class="max">$588.99</span>
</div>
</div>
</div>
<div class="reviewer vcard"><span class="fn">Bonnie Cha</span></div>
<span class="dtreviewed">05/28/2008</span>
</div>
</nowiki></pre>

=== combining hreview-aggregate (new proposal), hlisting, hproduct, xoxo ===

<div class="vevent">
posted: <span class="summary vcard"><span class="dtstart">2009-05-07</span> by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
</div>

<pre><nowiki>
<div class="hreview-aggregate">
<div class="item hproduct">
<h1 class="fn"><span class="brand">Sony</span> - BRAVIA / 46" Class / 1080p / 120Hz / LCD HDTV</h1>
<ul>
<li class="identifier"><span class="type">Model</span>: <span class="value">LN40A550</span></li>
<li class="identifier"><span class="type">SKU</span>: <span class="value">8749465</span></li>
</ul>
<div class="listing hListing">
<div class="leftcol"><img src="/images/product.jpg" alt="Sony - BRAVIA 46 Class 1080p 120Hz LCD HDTV" class="photo"/></div>
<div class="rightcol">
<div class="rating"><img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" class="average" /></div>
<div>(<span class="count">187</span> Reviews)</div>
<div class="grey">was $1,099.99</div>
<div class="price">$999.99</div>
</div>
<div class="shipping">Shipping: Usually leaves our warehouse in 1 business day.</div>
</div>
<div id="product-overview" class="product-overview" onclick="toggleBox('product-overview-open','product-overview-closed');changeClass('overview-head','down','right');">
<h3><a href="#" class="right" id="overview-head">Overview</a></h3>
<div id="product-overview-closed">
<p class="padtop">This flat-panel LCD HDTV features a 16:9 widescreen aspect ratio and a 50,000:1 dynamic contrast ratio, so you can enjoy your favorite movies in true 1080p high-definition.</p>
<a href="#" class="readmore mini-right">Show Full Overview</a>
</div>
<div id="product-overview-open">
<p class="description">This flat-panel LCD HDTV features a 16:9 widescreen aspect ratio and a 50,000:1 dynamic contrast ratio, so you can enjoy your favorite movies in true 1080p high-definition.</p>
<ul class="xoxo">
<li><h3 class="bottom-line">What's Included</h3>
<ol>
<li>Sony BRAVIA / 46" Class / 1080p / 120Hz / LCD HDTV</li>
<li>Tabletop stand, 4 screws</li>
<li>Remote RM-YD028</li>
<li>AC power cord, 2 AA batteries</li>
<li>Owner's manual</li>
</ol>
</li>
</ul>
<ul class="xoxo">
<li><h3 class="bottom-line">Product Features</h3>
<dl>
<dt>Built-in HDTV tuner</dt>
<dd>Add HD-capable antenna to receive over-the-air high-definition broadcasts, where available. Optional set-top box required for high-definition cable or satellite programming.</dd>
<dt>46" screen measured diagonally from corner to corner</dt>
<dd>Everyone will have a great view of the show or game.</dd>
<dt>1080p display</dt>
<dd>Provides the highest quality progressive-scan picture possible for a high-definition source.</dd>
<dt>16:9 widescreen aspect ratio</dt>
<dd>With CineMotion reverse 3.2 pulldown technology and 24p True Cinema mode delivers accurate reproduction of film-based sources for a cinema-style entertainment experience.</dd>
<dt>BRAVIA Engine 2 full digital video processor</dt>
<dd>Reduces video noise, improves color and sharpens the overall image detail.</dd>
<dt>Advanced Contrast Enhancer (ACE)</dt>
<dd>Uses real-time image processing to adjust the contrast ratio.</dd>
<dt>Motionflow 120Hz technology</dt>
<dd>Reduces jitter and sharpens fast-moving images for a crisp picture.</dd>
<dt>LightSensor technology</dt>
<dd>Monitors ambient room lighting conditions and adjusts the backlit intensity accordingly.</dd>
<dt>50,000:1 dynamic contrast ratio</dt>
<dd>For an arresting viewing experience.</dd>
<dt>3D digital comb filter</dt>
<dd>Brings out fine picture detail and enhances color purity.</dd>
<dt>SRS TruSurround XT</dt>
<dd>With Dolby Digital and SteadySound automatic volume control delivers a lush soundscape.</dd>
<dt>Ultraslim (3-4/5" deep) design and VESA compatible</dt>
<dd>Ideal for wall mounting (with optional mounting kit, not included).</dd>
</dl>
</li>
</ul>
</div>
<div id="customer-overview" class="customer-overview">
<div onclick="toggleBox('customer-open','customer-closed');changeClass('review-head','down','right');">
<h3><span class="right" id="review-head" >Customer Reviews (34)</span></h3>
<p class="padtop">Average: <img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" /></p>
<p>50% of customers would recommend this product to a friend (2 of 4).</p>
</div>
<div id="customer-closed">
<a href="#" class="readmore mini-right" onclick="toggleBox('customer-open','customer-closed');changeClass('review-head','down','right');" >Show Reviews</a>
</div>
<div id="customer-open">
<div id="sort-reviews">
<span class="big-grey">Sort by:</span>
<select>
<option value="newest">Date: Newest</option>
<option value="oldest">Date: Oldest</option>
</select>
<input type="submit" value="Go" />
</div>
<div id="review-list">
<div class="number-of-reviews grey">1 - 10 of 34 Reviews</div>
<div class="hreview">
<span id="review-one" class="summary">TV may be better than you think.</span>
<span class="reviewer vcard">by <span class="fn nickname">bezb18</span> from Maryland on <span class="dtreviewed">04/07/2009</span></span>
<span class="rating"><img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" /></span>
<div id="hidden-one">
<div class="review-box">
<table class="review-summary">
<tr><td>Picture Quality:</td><td><img alt="50% Rating" src="images/bar-50.gif" /></td></tr>
<tr><td>Sound Quality:</td><td><img alt="100% Rating" src="images/bar-100.gif" /></td></tr>
<tr><td>Features:</td><td><img alt="75% Rating" src="images/bar-75.gif" /></td></tr>
</table>
<span class="review-great"><b>What's great about it:</b> Vivid picture.</span>
<span class="review-not"><b>What's not so great:</b> Backlight, fades picture to black.</span>
<p class="description">"I purchased this TV about a week ago and
after putting a DVD on and noticed the scene fading to almost
completely black at several times in the movie, I thought I
might have a problem. Then noticed that it also happens when
watching regular movies on the cable. Screen gets too dark and
then returns to the regular picture. It is very upsetting and you
want to throw something. You think you have bought a really good
TV, paid a good price for it and then you get this. I purchased
a Sony KDL46z4100 Out of Box before this one and had Audio
problems. I took it back and got this one. I really wish
Sony could get it right on something. Will also return this one."</p>
<span class="review-recommend"><b>Would you recommend this product to a friend?:</b> Yes</span>
<span class="review-business"><b>Is this product used primarily for business?:</b> No</span>
</div>
</div>
</div>
</div>
</div>
</div>
<div id="specs-overview" class="specs-overview" onclick="toggleBox('specs-open','specs-closed');changeClass('specs-head','down','right');" >
<h3><a href="#" class="right" id="specs-head">Specifications</a></h3>
<div id="specs-closed"> </div>
<div id="specs-open">
<ul class="xoxo">
<li><h3><a href="#" class="right" id="specs-head">Specifications</a></h3>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year limited</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year limited</dd>
<dt>Product Height</dt>
<dd>30-1/3" with stand (28-5/8" without</dd>
<dt>Product Width</dt>
<dd>44-1/5"</dd>
</dl>
</li>
</ul>
</div>
</div>
</div>
</div>
</div>

</nowiki></pre>

=== hlisting, hproduct, haggregatereview/hreview, xoxo ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/tv-and-video">TV & Video</a></li>
<li class="category"><a href="http://storename.com/televisions">Televisions</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/samsung-ln40a550.jpg" class="photo" alt="picture of samsung ln40a550" />
<div class="fn"><span class="brand">Samsung</span> - 40" 1080p Flat-Panel LCD HDTV</div>
<dl class="identifier">
<dt>Model</dt>
<dd>LN40A550</dd>
<dt>SKU</dt>
<dd>8749465</dd>
</dl>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_3_5.gif" alt="3.5 out of 5 stars"/></a></span><span class="rating">4.7</span> / <span class="best">5</span> (<span class="num">13</span> reviews)</div>
</div>
</div>
<div class="price">$1,099.99</div>
<ol class="xoxo">
<li><h2>Specifications</h2>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year</dd>
<dt>Product Height</dt>
<dd>27" with stand (24-7/10" without)</dd>
<dt>Product Width</dt>
<dd>39-1/5"</dd>
<dt>Product Weight</dt>
<dd>61.5 lbs. with stand (54.5 lbs. without)</dd>
<dt>Product Depth</dt>
<dd>11-4/5" with stand (3-3/5" without)</dd>
<dt>TV Type</dt>
<dd>LCD Flat-Panel</dd>
</dl>
</li>
</div>
</div>
</nowiki></pre>

=== hlisting, hproduct, haudio, haggregatereview/hreview ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct haudio">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/gangsta">Gangsta/Hardcore</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/50cent-curtis.jpg" class="photo" alt="picture of 50 cent" />
<div class="album">Curtis</div>
<div class="contributor"><span class="vcard"><span class=n nickname">50 Cent</span></span></div>
<p>Release date:<abbr class="published" title="2007-09-11">September 11, 2007</abbr></p>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_4_0.gif" alt="4 out of 5 stars"/></a></span><span class="rating">4.0</span> / <span class="best">5</span> Number of reviews:(<span class="num">4</span> reviews)</div>
</div>
<div class="price">$9.99</div>
<a href="add-to-cart-url" rel="payment"><img src="http://storename.com/images/global/add-to-cart.gif" alt="add to cart" /></a>
<h2>Tracks</h2>
<ol>
<li class="item"><span class="position">1</span>.<span class="fn">Intro</span><a href="http://images.storename.com/media/sample/50cent-intro.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">2</span>.<span class="fn">My Gun Go Off</span><a href="http://images.storename.com/media/sample/50cent-gun-go-off.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">3</span>.<span class="fn">Man Down - (censored)</span><a href="http://images.storename.com/media/sample/50cent-man-down.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">4</span>.<span class="fn">I'll Still Kill - (with Akon)</span><a href="http://images.storename.com/media/sample/50cent-ill-still-kill.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">5</span>.<span class="fn">I Get Money</span><a href="http://images.storename.com/media/sample/50cent-i-get-money.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">6</span>.<span class="fn">Come & Go - (with Dr. Dre)</span><a href="http://images.storename.com/media/sample/50cent-come-go.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">7</span>.<span class="fn">Ayo Technology - (with Timbaland/Justin Timberlake)</span><a href="http://images.storename.com/media/sample/50cent-ayo-technology.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">8</span>.<span class="fn">Follow My Lead - (with Robin Thicke)</span><a href="http://images.storename.com/media/sample/50cent-follow-my-lead.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">9</span>.<span class="fn">Movin' on Up</span><a href="http://images.storename.com/media/sample/50cent-movin-on-up.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">10</span>.<span class="fn">Straight to the Bank</span><a href="http://images.storename.com/media/sample/50cent-straight-to-bank.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">11</span>.<span class="fn">Amusement Park</span><a href="http://images.storename.com/media/sample/50cent-amusement-park.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">12</span>.<span class="fn">Fully Loaded Clip</span><a href="http://images.storename.com/media/sample/50cent-fully-loaded-clip.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">13</span>.<span class="fn">Peep Show - (with Eminem)</span><a href="http://images.storename.com/media/sample/50cent-peep-show.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">14</span>.<span class="fn">Fire - (with Young Buck/Nicole Scherzinger)</span><a href="http://images.storename.com/media/sample/50cent-fire.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">15</span>.<span class="fn">All of Me - (with Mary J. Blige)</span><a href="http://images.storename.com/media/sample/50cent-all-of-me.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">16</span>.<span class="fn">Curtis 187</span><a href="http://images.storename.com/media/sample/50cent-curtis-187.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">17</span>.<span class="fn">Touch the Sky - (with Tony Yayo)</span><a href="http://images.storename.com/media/sample/50cent-touch-the-sky.mp3" rel="sample">Listen</a></li>
</ol>
</div>
</div>
</nowiki></pre>

hproduct-recipes

2009-05-07T21:27:03Z

JayMyers: posting short example

== Coded Recipe Examples ==

This page is to provide coded examples showing the interplay between hListing, hProduct and other formats (hAggregateReview, xoxo, to name a few) that could be used to create better semantic page markup.

=== hreview, hproduct, hlisting short example ===

<div class="vevent">
posted: <span class="summary vcard"><span class="dtstart">2009-05-07</span> by <span class="fn">[[JayMyers|JayMyers]]</span></span><br/>
Source URL: http://reviews.cnet.com/car-gps-navigation/tomtom-go-930-gps/4505-3430_7-33003945.html
</div>

<pre><nowiki>
<div class="hReview">
<div class="item hProduct">
<span class="fn">TomTom GO 930 GPS</span>
<span class="rating">3.5</span>
<div class="listing hListing-aggregate">
<div class="price">
<span class="min">$352.35</span> - <span class="max">$588.99</span>
</div>
</div>
</div>
<div class="reviewer vcard"><span class="fn">Bonnie Cha</span></div>
<span class="dtreviewed">05/28/2008</span>
</div>
</nowiki></pre>

=== combining hreview-aggregate (new proposal), hlisting, hproduct, xoxo ===

<div class="vevent">
posted: <span class="summary vcard"><span class="dtstart">2009-05-07</span> by <span class="fn">[[JayMyers|JayMyers]]</span></span>
</div>

<pre><nowiki>
<div class="hreview-aggregate">
<div class="item hproduct">
<h1 class="fn"><span class="brand">Sony</span> - BRAVIA / 46" Class / 1080p / 120Hz / LCD HDTV</h1>
<ul>
<li class="identifier"><span class="type">Model</span>: <span class="value">LN40A550</span></li>
<li class="identifier"><span class="type">SKU</span>: <span class="value">8749465</span></li>
</ul>
<div class="listing hListing">
<div class="leftcol"><img src="/images/product.jpg" alt="Sony - BRAVIA 46 Class 1080p 120Hz LCD HDTV" class="photo"/></div>
<div class="rightcol">
<div class="rating"><img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" class="average" /></div>
<div>(<span class="count">187</span> Reviews)</div>
<div class="grey">was $1,099.99</div>
<div class="price">$999.99</div>
</div>
<div class="shipping">Shipping: Usually leaves our warehouse in 1 business day.</div>
</div>
<div id="product-overview" class="product-overview" onclick="toggleBox('product-overview-open','product-overview-closed');changeClass('overview-head','down','right');">
<h3><a href="#" class="right" id="overview-head">Overview</a></h3>
<div id="product-overview-closed">
<p class="padtop">This flat-panel LCD HDTV features a 16:9 widescreen aspect ratio and a 50,000:1 dynamic contrast ratio, so you can enjoy your favorite movies in true 1080p high-definition.</p>
<a href="#" class="readmore mini-right">Show Full Overview</a>
</div>
<div id="product-overview-open">
<p class="description">This flat-panel LCD HDTV features a 16:9 widescreen aspect ratio and a 50,000:1 dynamic contrast ratio, so you can enjoy your favorite movies in true 1080p high-definition.</p>
<ul class="xoxo">
<li><h3 class="bottom-line">What's Included</h3>
<ol>
<li>Sony BRAVIA / 46" Class / 1080p / 120Hz / LCD HDTV</li>
<li>Tabletop stand, 4 screws</li>
<li>Remote RM-YD028</li>
<li>AC power cord, 2 AA batteries</li>
<li>Owner's manual</li>
</ol>
</li>
</ul>
<ul class="xoxo">
<li><h3 class="bottom-line">Product Features</h3>
<dl>
<dt>Built-in HDTV tuner</dt>
<dd>Add HD-capable antenna to receive over-the-air high-definition broadcasts, where available. Optional set-top box required for high-definition cable or satellite programming.</dd>
<dt>46" screen measured diagonally from corner to corner</dt>
<dd>Everyone will have a great view of the show or game.</dd>
<dt>1080p display</dt>
<dd>Provides the highest quality progressive-scan picture possible for a high-definition source.</dd>
<dt>16:9 widescreen aspect ratio</dt>
<dd>With CineMotion reverse 3.2 pulldown technology and 24p True Cinema mode delivers accurate reproduction of film-based sources for a cinema-style entertainment experience.</dd>
<dt>BRAVIA Engine 2 full digital video processor</dt>
<dd>Reduces video noise, improves color and sharpens the overall image detail.</dd>
<dt>Advanced Contrast Enhancer (ACE)</dt>
<dd>Uses real-time image processing to adjust the contrast ratio.</dd>
<dt>Motionflow 120Hz technology</dt>
<dd>Reduces jitter and sharpens fast-moving images for a crisp picture.</dd>
<dt>LightSensor technology</dt>
<dd>Monitors ambient room lighting conditions and adjusts the backlit intensity accordingly.</dd>
<dt>50,000:1 dynamic contrast ratio</dt>
<dd>For an arresting viewing experience.</dd>
<dt>3D digital comb filter</dt>
<dd>Brings out fine picture detail and enhances color purity.</dd>
<dt>SRS TruSurround XT</dt>
<dd>With Dolby Digital and SteadySound automatic volume control delivers a lush soundscape.</dd>
<dt>Ultraslim (3-4/5" deep) design and VESA compatible</dt>
<dd>Ideal for wall mounting (with optional mounting kit, not included).</dd>
</dl>
</li>
</ul>
</div>
<div id="customer-overview" class="customer-overview">
<div onclick="toggleBox('customer-open','customer-closed');changeClass('review-head','down','right');">
<h3><span class="right" id="review-head" >Customer Reviews (34)</span></h3>
<p class="padtop">Average: <img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" /></p>
<p>50% of customers would recommend this product to a friend (2 of 4).</p>
</div>
<div id="customer-closed">
<a href="#" class="readmore mini-right" onclick="toggleBox('customer-open','customer-closed');changeClass('review-head','down','right');" >Show Reviews</a>
</div>
<div id="customer-open">
<div id="sort-reviews">
<span class="big-grey">Sort by:</span>
<select>
<option value="newest">Date: Newest</option>
<option value="oldest">Date: Oldest</option>
</select>
<input type="submit" value="Go" />
</div>
<div id="review-list">
<div class="number-of-reviews grey">1 - 10 of 34 Reviews</div>
<div class="hreview">
<span id="review-one" class="summary">TV may be better than you think.</span>
<span class="reviewer vcard">by <span class="fn nickname">bezb18</span> from Maryland on <span class="dtreviewed">04/07/2009</span></span>
<span class="rating"><img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" /></span>
<div id="hidden-one">
<div class="review-box">
<table class="review-summary">
<tr><td>Picture Quality:</td><td><img alt="50% Rating" src="images/bar-50.gif" /></td></tr>
<tr><td>Sound Quality:</td><td><img alt="100% Rating" src="images/bar-100.gif" /></td></tr>
<tr><td>Features:</td><td><img alt="75% Rating" src="images/bar-75.gif" /></td></tr>
</table>
<span class="review-great"><b>What's great about it:</b> Vivid picture.</span>
<span class="review-not"><b>What's not so great:</b> Backlight, fades picture to black.</span>
<p class="description">"I purchased this TV about a week ago and
after putting a DVD on and noticed the scene fading to almost
completely black at several times in the movie, I thought I
might have a problem. Then noticed that it also happens when
watching regular movies on the cable. Screen gets too dark and
then returns to the regular picture. It is very upsetting and you
want to throw something. You think you have bought a really good
TV, paid a good price for it and then you get this. I purchased
a Sony KDL46z4100 Out of Box before this one and had Audio
problems. I took it back and got this one. I really wish
Sony could get it right on something. Will also return this one."</p>
<span class="review-recommend"><b>Would you recommend this product to a friend?:</b> Yes</span>
<span class="review-business"><b>Is this product used primarily for business?:</b> No</span>
</div>
</div>
</div>
</div>
</div>
</div>
<div id="specs-overview" class="specs-overview" onclick="toggleBox('specs-open','specs-closed');changeClass('specs-head','down','right');" >
<h3><a href="#" class="right" id="specs-head">Specifications</a></h3>
<div id="specs-closed"> </div>
<div id="specs-open">
<ul class="xoxo">
<li><h3><a href="#" class="right" id="specs-head">Specifications</a></h3>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year limited</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year limited</dd>
<dt>Product Height</dt>
<dd>30-1/3" with stand (28-5/8" without</dd>
<dt>Product Width</dt>
<dd>44-1/5"</dd>
</dl>
</li>
</ul>
</div>
</div>
</div>
</div>
</div>

</nowiki></pre>

=== hlisting, hproduct, haggregatereview/hreview, xoxo ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/tv-and-video">TV & Video</a></li>
<li class="category"><a href="http://storename.com/televisions">Televisions</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/samsung-ln40a550.jpg" class="photo" alt="picture of samsung ln40a550" />
<div class="fn"><span class="brand">Samsung</span> - 40" 1080p Flat-Panel LCD HDTV</div>
<dl class="identifier">
<dt>Model</dt>
<dd>LN40A550</dd>
<dt>SKU</dt>
<dd>8749465</dd>
</dl>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_3_5.gif" alt="3.5 out of 5 stars"/></a></span><span class="rating">4.7</span> / <span class="best">5</span> (<span class="num">13</span> reviews)</div>
</div>
</div>
<div class="price">$1,099.99</div>
<ol class="xoxo">
<li><h2>Specifications</h2>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year</dd>
<dt>Product Height</dt>
<dd>27" with stand (24-7/10" without)</dd>
<dt>Product Width</dt>
<dd>39-1/5"</dd>
<dt>Product Weight</dt>
<dd>61.5 lbs. with stand (54.5 lbs. without)</dd>
<dt>Product Depth</dt>
<dd>11-4/5" with stand (3-3/5" without)</dd>
<dt>TV Type</dt>
<dd>LCD Flat-Panel</dd>
</dl>
</li>
</div>
</div>
</nowiki></pre>

=== hlisting, hproduct, haudio, haggregatereview/hreview ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct haudio">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/gangsta">Gangsta/Hardcore</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/50cent-curtis.jpg" class="photo" alt="picture of 50 cent" />
<div class="album">Curtis</div>
<div class="contributor"><span class="vcard"><span class=n nickname">50 Cent</span></span></div>
<p>Release date:<abbr class="published" title="2007-09-11">September 11, 2007</abbr></p>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_4_0.gif" alt="4 out of 5 stars"/></a></span><span class="rating">4.0</span> / <span class="best">5</span> Number of reviews:(<span class="num">4</span> reviews)</div>
</div>
<div class="price">$9.99</div>
<a href="add-to-cart-url" rel="payment"><img src="http://storename.com/images/global/add-to-cart.gif" alt="add to cart" /></a>
<h2>Tracks</h2>
<ol>
<li class="item"><span class="position">1</span>.<span class="fn">Intro</span><a href="http://images.storename.com/media/sample/50cent-intro.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">2</span>.<span class="fn">My Gun Go Off</span><a href="http://images.storename.com/media/sample/50cent-gun-go-off.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">3</span>.<span class="fn">Man Down - (censored)</span><a href="http://images.storename.com/media/sample/50cent-man-down.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">4</span>.<span class="fn">I'll Still Kill - (with Akon)</span><a href="http://images.storename.com/media/sample/50cent-ill-still-kill.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">5</span>.<span class="fn">I Get Money</span><a href="http://images.storename.com/media/sample/50cent-i-get-money.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">6</span>.<span class="fn">Come & Go - (with Dr. Dre)</span><a href="http://images.storename.com/media/sample/50cent-come-go.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">7</span>.<span class="fn">Ayo Technology - (with Timbaland/Justin Timberlake)</span><a href="http://images.storename.com/media/sample/50cent-ayo-technology.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">8</span>.<span class="fn">Follow My Lead - (with Robin Thicke)</span><a href="http://images.storename.com/media/sample/50cent-follow-my-lead.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">9</span>.<span class="fn">Movin' on Up</span><a href="http://images.storename.com/media/sample/50cent-movin-on-up.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">10</span>.<span class="fn">Straight to the Bank</span><a href="http://images.storename.com/media/sample/50cent-straight-to-bank.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">11</span>.<span class="fn">Amusement Park</span><a href="http://images.storename.com/media/sample/50cent-amusement-park.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">12</span>.<span class="fn">Fully Loaded Clip</span><a href="http://images.storename.com/media/sample/50cent-fully-loaded-clip.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">13</span>.<span class="fn">Peep Show - (with Eminem)</span><a href="http://images.storename.com/media/sample/50cent-peep-show.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">14</span>.<span class="fn">Fire - (with Young Buck/Nicole Scherzinger)</span><a href="http://images.storename.com/media/sample/50cent-fire.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">15</span>.<span class="fn">All of Me - (with Mary J. Blige)</span><a href="http://images.storename.com/media/sample/50cent-all-of-me.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">16</span>.<span class="fn">Curtis 187</span><a href="http://images.storename.com/media/sample/50cent-curtis-187.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">17</span>.<span class="fn">Touch the Sky - (with Tony Yayo)</span><a href="http://images.storename.com/media/sample/50cent-touch-the-sky.mp3" rel="sample">Listen</a></li>
</ol>
</div>
</div>
</nowiki></pre>

hproduct-recipes

2009-05-07T21:22:05Z

JayMyers: adding more complex example of aggregate reviews, hproduct, xoxo

== Coded Recipe Examples ==

This page is to provide coded examples showing the interplay between hListing, hProduct and other formats (hAggregateReview, xoxo, to name a few) that could be used to create better semantic page markup.

=== combining hreview-aggregate (new proposal), hlisting, hproduct, xoxo ===

<div class="vevent">
posted: <span class="summary vcard"><span class="dtstart">2009-05-07</span> by <span class="fn">[[JayMyers|JayMyers]]</span></span>
</div>

<pre><nowiki>
<div class="hreview-aggregate">
<div class="item hproduct">
<h1 class="fn"><span class="brand">Sony</span> - BRAVIA / 46" Class / 1080p / 120Hz / LCD HDTV</h1>
<ul>
<li class="identifier"><span class="type">Model</span>: <span class="value">LN40A550</span></li>
<li class="identifier"><span class="type">SKU</span>: <span class="value">8749465</span></li>
</ul>
<div class="listing hListing">
<div class="leftcol"><img src="/images/product.jpg" alt="Sony - BRAVIA 46 Class 1080p 120Hz LCD HDTV" class="photo"/></div>
<div class="rightcol">
<div class="rating"><img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" class="average" /></div>
<div>(<span class="count">187</span> Reviews)</div>
<div class="grey">was $1,099.99</div>
<div class="price">$999.99</div>
</div>
<div class="shipping">Shipping: Usually leaves our warehouse in 1 business day.</div>
</div>
<div id="product-overview" class="product-overview" onclick="toggleBox('product-overview-open','product-overview-closed');changeClass('overview-head','down','right');">
<h3><a href="#" class="right" id="overview-head">Overview</a></h3>
<div id="product-overview-closed">
<p class="padtop">This flat-panel LCD HDTV features a 16:9 widescreen aspect ratio and a 50,000:1 dynamic contrast ratio, so you can enjoy your favorite movies in true 1080p high-definition.</p>
<a href="#" class="readmore mini-right">Show Full Overview</a>
</div>
<div id="product-overview-open">
<p class="description">This flat-panel LCD HDTV features a 16:9 widescreen aspect ratio and a 50,000:1 dynamic contrast ratio, so you can enjoy your favorite movies in true 1080p high-definition.</p>
<ul class="xoxo">
<li><h3 class="bottom-line">What's Included</h3>
<ol>
<li>Sony BRAVIA / 46" Class / 1080p / 120Hz / LCD HDTV</li>
<li>Tabletop stand, 4 screws</li>
<li>Remote RM-YD028</li>
<li>AC power cord, 2 AA batteries</li>
<li>Owner's manual</li>
</ol>
</li>
</ul>
<ul class="xoxo">
<li><h3 class="bottom-line">Product Features</h3>
<dl>
<dt>Built-in HDTV tuner</dt>
<dd>Add HD-capable antenna to receive over-the-air high-definition broadcasts, where available. Optional set-top box required for high-definition cable or satellite programming.</dd>
<dt>46" screen measured diagonally from corner to corner</dt>
<dd>Everyone will have a great view of the show or game.</dd>
<dt>1080p display</dt>
<dd>Provides the highest quality progressive-scan picture possible for a high-definition source.</dd>
<dt>16:9 widescreen aspect ratio</dt>
<dd>With CineMotion reverse 3.2 pulldown technology and 24p True Cinema mode delivers accurate reproduction of film-based sources for a cinema-style entertainment experience.</dd>
<dt>BRAVIA Engine 2 full digital video processor</dt>
<dd>Reduces video noise, improves color and sharpens the overall image detail.</dd>
<dt>Advanced Contrast Enhancer (ACE)</dt>
<dd>Uses real-time image processing to adjust the contrast ratio.</dd>
<dt>Motionflow 120Hz technology</dt>
<dd>Reduces jitter and sharpens fast-moving images for a crisp picture.</dd>
<dt>LightSensor technology</dt>
<dd>Monitors ambient room lighting conditions and adjusts the backlit intensity accordingly.</dd>
<dt>50,000:1 dynamic contrast ratio</dt>
<dd>For an arresting viewing experience.</dd>
<dt>3D digital comb filter</dt>
<dd>Brings out fine picture detail and enhances color purity.</dd>
<dt>SRS TruSurround XT</dt>
<dd>With Dolby Digital and SteadySound automatic volume control delivers a lush soundscape.</dd>
<dt>Ultraslim (3-4/5" deep) design and VESA compatible</dt>
<dd>Ideal for wall mounting (with optional mounting kit, not included).</dd>
</dl>
</li>
</ul>
</div>
<div id="customer-overview" class="customer-overview">
<div onclick="toggleBox('customer-open','customer-closed');changeClass('review-head','down','right');">
<h3><span class="right" id="review-head" >Customer Reviews (34)</span></h3>
<p class="padtop">Average: <img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" /></p>
<p>50% of customers would recommend this product to a friend (2 of 4).</p>
</div>
<div id="customer-closed">
<a href="#" class="readmore mini-right" onclick="toggleBox('customer-open','customer-closed');changeClass('review-head','down','right');" >Show Reviews</a>
</div>
<div id="customer-open">
<div id="sort-reviews">
<span class="big-grey">Sort by:</span>
<select>
<option value="newest">Date: Newest</option>
<option value="oldest">Date: Oldest</option>
</select>
<input type="submit" value="Go" />
</div>
<div id="review-list">
<div class="number-of-reviews grey">1 - 10 of 34 Reviews</div>
<div class="hreview">
<span id="review-one" class="summary">TV may be better than you think.</span>
<span class="reviewer vcard">by <span class="fn nickname">bezb18</span> from Maryland on <span class="dtreviewed">04/07/2009</span></span>
<span class="rating"><img src="/images/stars-four-half.gif" alt="Four and a Half Star Rating" /></span>
<div id="hidden-one">
<div class="review-box">
<table class="review-summary">
<tr><td>Picture Quality:</td><td><img alt="50% Rating" src="images/bar-50.gif" /></td></tr>
<tr><td>Sound Quality:</td><td><img alt="100% Rating" src="images/bar-100.gif" /></td></tr>
<tr><td>Features:</td><td><img alt="75% Rating" src="images/bar-75.gif" /></td></tr>
</table>
<span class="review-great"><b>What's great about it:</b> Vivid picture.</span>
<span class="review-not"><b>What's not so great:</b> Backlight, fades picture to black.</span>
<p class="description">"I purchased this TV about a week ago and
after putting a DVD on and noticed the scene fading to almost
completely black at several times in the movie, I thought I
might have a problem. Then noticed that it also happens when
watching regular movies on the cable. Screen gets too dark and
then returns to the regular picture. It is very upsetting and you
want to throw something. You think you have bought a really good
TV, paid a good price for it and then you get this. I purchased
a Sony KDL46z4100 Out of Box before this one and had Audio
problems. I took it back and got this one. I really wish
Sony could get it right on something. Will also return this one."</p>
<span class="review-recommend"><b>Would you recommend this product to a friend?:</b> Yes</span>
<span class="review-business"><b>Is this product used primarily for business?:</b> No</span>
</div>
</div>
</div>
</div>
</div>
</div>
<div id="specs-overview" class="specs-overview" onclick="toggleBox('specs-open','specs-closed');changeClass('specs-head','down','right');" >
<h3><a href="#" class="right" id="specs-head">Specifications</a></h3>
<div id="specs-closed"> </div>
<div id="specs-open">
<ul class="xoxo">
<li><h3><a href="#" class="right" id="specs-head">Specifications</a></h3>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year limited</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year limited</dd>
<dt>Product Height</dt>
<dd>30-1/3" with stand (28-5/8" without</dd>
<dt>Product Width</dt>
<dd>44-1/5"</dd>
</dl>
</li>
</ul>
</div>
</div>
</div>
</div>
</div>

</nowiki></pre>

=== hlisting, hproduct, haggregatereview/hreview, xoxo ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/tv-and-video">TV & Video</a></li>
<li class="category"><a href="http://storename.com/televisions">Televisions</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/samsung-ln40a550.jpg" class="photo" alt="picture of samsung ln40a550" />
<div class="fn"><span class="brand">Samsung</span> - 40" 1080p Flat-Panel LCD HDTV</div>
<dl class="identifier">
<dt>Model</dt>
<dd>LN40A550</dd>
<dt>SKU</dt>
<dd>8749465</dd>
</dl>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_3_5.gif" alt="3.5 out of 5 stars"/></a></span><span class="rating">4.7</span> / <span class="best">5</span> (<span class="num">13</span> reviews)</div>
</div>
</div>
<div class="price">$1,099.99</div>
<ol class="xoxo">
<li><h2>Specifications</h2>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year</dd>
<dt>Product Height</dt>
<dd>27" with stand (24-7/10" without)</dd>
<dt>Product Width</dt>
<dd>39-1/5"</dd>
<dt>Product Weight</dt>
<dd>61.5 lbs. with stand (54.5 lbs. without)</dd>
<dt>Product Depth</dt>
<dd>11-4/5" with stand (3-3/5" without)</dd>
<dt>TV Type</dt>
<dd>LCD Flat-Panel</dd>
</dl>
</li>
</div>
</div>
</nowiki></pre>

=== hlisting, hproduct, haudio, haggregatereview/hreview ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct haudio">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/gangsta">Gangsta/Hardcore</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/50cent-curtis.jpg" class="photo" alt="picture of 50 cent" />
<div class="album">Curtis</div>
<div class="contributor"><span class="vcard"><span class=n nickname">50 Cent</span></span></div>
<p>Release date:<abbr class="published" title="2007-09-11">September 11, 2007</abbr></p>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_4_0.gif" alt="4 out of 5 stars"/></a></span><span class="rating">4.0</span> / <span class="best">5</span> Number of reviews:(<span class="num">4</span> reviews)</div>
</div>
<div class="price">$9.99</div>
<a href="add-to-cart-url" rel="payment"><img src="http://storename.com/images/global/add-to-cart.gif" alt="add to cart" /></a>
<h2>Tracks</h2>
<ol>
<li class="item"><span class="position">1</span>.<span class="fn">Intro</span><a href="http://images.storename.com/media/sample/50cent-intro.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">2</span>.<span class="fn">My Gun Go Off</span><a href="http://images.storename.com/media/sample/50cent-gun-go-off.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">3</span>.<span class="fn">Man Down - (censored)</span><a href="http://images.storename.com/media/sample/50cent-man-down.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">4</span>.<span class="fn">I'll Still Kill - (with Akon)</span><a href="http://images.storename.com/media/sample/50cent-ill-still-kill.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">5</span>.<span class="fn">I Get Money</span><a href="http://images.storename.com/media/sample/50cent-i-get-money.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">6</span>.<span class="fn">Come & Go - (with Dr. Dre)</span><a href="http://images.storename.com/media/sample/50cent-come-go.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">7</span>.<span class="fn">Ayo Technology - (with Timbaland/Justin Timberlake)</span><a href="http://images.storename.com/media/sample/50cent-ayo-technology.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">8</span>.<span class="fn">Follow My Lead - (with Robin Thicke)</span><a href="http://images.storename.com/media/sample/50cent-follow-my-lead.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">9</span>.<span class="fn">Movin' on Up</span><a href="http://images.storename.com/media/sample/50cent-movin-on-up.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">10</span>.<span class="fn">Straight to the Bank</span><a href="http://images.storename.com/media/sample/50cent-straight-to-bank.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">11</span>.<span class="fn">Amusement Park</span><a href="http://images.storename.com/media/sample/50cent-amusement-park.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">12</span>.<span class="fn">Fully Loaded Clip</span><a href="http://images.storename.com/media/sample/50cent-fully-loaded-clip.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">13</span>.<span class="fn">Peep Show - (with Eminem)</span><a href="http://images.storename.com/media/sample/50cent-peep-show.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">14</span>.<span class="fn">Fire - (with Young Buck/Nicole Scherzinger)</span><a href="http://images.storename.com/media/sample/50cent-fire.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">15</span>.<span class="fn">All of Me - (with Mary J. Blige)</span><a href="http://images.storename.com/media/sample/50cent-all-of-me.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">16</span>.<span class="fn">Curtis 187</span><a href="http://images.storename.com/media/sample/50cent-curtis-187.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">17</span>.<span class="fn">Touch the Sky - (with Tony Yayo)</span><a href="http://images.storename.com/media/sample/50cent-touch-the-sky.mp3" rel="sample">Listen</a></li>
</ol>
</div>
</div>
</nowiki></pre>

hproduct-issues

2009-04-24T17:34:50Z

JayMyers: resolutions for hp1, hp2, hp3, hp5, hp6 ,hp7

__TOC__

== HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields ==

<div class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-12-17</span> raised by <span class="fn">NicolasLeroy</span></span>
<div class="description">
*# In the "[[hproduct#Out_of_Scope|out of scope]]" section, it is explained: _"This microformat does not intend to replicate any of the content proposed within hListing and would defer all money/transactional matters to that microformat"_
*# However, in the hProduct schema, we have the following fields:
*#* "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
*#* I would say there is also ambiguity between the responsibilities of hProduct vs hListing for the following fields: quantity / shipping
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I believe everyone agrees that we would borrow price from hListing for hProduct spec. I will explain the concept further in the schema.
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I don't follow the quantity/ shipping issue. I don't see either of these on hListing, unless the concepts are somehow embedded in other attributes. Can you elaborate on what the ambiguity is? ([[User:PaulLee|Paul Lee]]: If there's no objection here, may I suggest updating the price reference and keeping quantity and shipping as is?])
*#* +1 I agree with NicholasLeroy, anything price or transaction related should be left out of hProduct 0.1, and instead develop recipes / mark-up examples showing use of hListing with hProduct. We need to strongly resist and fight the tendency to include "just one more field" to individual formats and instead push to use formats as building blocks. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: If price should be left to hListing, should hAudio be modified not to include "price"?
*#* I am going to add price back into the hProduct spec. Price is an attribute of a product. We should be able to use microformats either standalone or as building blocks in combination with other formats. On price I'm thinking specifically of product manufacturer sites who may not be commerce enabled and are listing their products for informational purposes. In this case, they would not be using hListing, as there would be no transaction taking place. Leaving the price attribute out would ignore a major product attribute (in 99% of product sites, per hproduct examples analysis).
</div>
</div>

<div class="vevent">

== <span class="summary">HP2 - FN should be used instead of N for product title</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Why is <b>n</b> used instead of <b>fn</b> for the title of the product? hCard and hAudio both use fn for the formatted name of the product. <b>n</b> is usually an optimization.
* +1 hProduct should use "fn" for the name of the product. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: "n" will be changed to "fn" in the next version of the schema
* "fn" is hardly semantic, even though commonly deployed - surely "formatted-name" is truer to the principles of "humans-first, machines second" --[[User:Wowitim|Wowitim]] 12:59, 28 March 2009 (UTC)
</div>

<div class="vevent">

== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{OpenIssue}} <span class="vcard">BUY duplicates functionality of PAYMENT from hAudio<span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>buy</b> is duplicating the functionality of <b>payment</b> from hAudio.
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: From the payment page: "RelPayment is a microformat for making exchanges of support (be it financial or otherwise) possible. By adding rel="payment" to a hyperlink a page indicates that the destination of that hyperlink provides a way to show or give support for the current page. For example to give financial support to the owner of the current page. One of the goals with this microformat is to give content aggregators such as RSS readers a way to extract these support links and give them special attention (such as displaying a standard button along with the content)." First, this seems like a simple exercise for blogs, etc.; but the transaction process for shopping sites is typically considerably more complex. Usually, the actual payment URI is toward the end of the cart checkout process, the entry to which "buy" is intended to direct to the beginning of. Second, there is the potential for confusion when using payment, since "payment" in the shopping space often refers to payment methods, e.g., credit card, check, etc.
* +1 but in a different way. BUY/PAYMENT should both be out of scope for hProduct, and only be in hListing per issue HP1 above. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should these be in scope for hAudio then?
</div>
</div>

<div class="vevent">

== <span class="summary">HP4 - Are all of the formats for PRICE in hProduct allowed</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* The way that <b>price</b> is used is iffy - do we allow anything but currency/amount in the compound statement?
* +1 PRICE should not be in hProduct per issue HP1. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should other microformats (thinking hAudio) be modified not to include "price"?
</div>
</div>

<div class="vevent">

== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Seems like <b>shipping</b> could be abused quite a bit, resulting in a term that is fairly useless as time moves on.
* +1 agreed and I think SHIPPING belongs in hListing (not in hProduct) as it applies to a particular transaction/offering, and is not intrinsic to the product itself. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>p-v</b> seems like a catch-all, shoe-horn attempt at making the microformat infinitely scalable? Is this really useful?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: IIUC, part of the reason why hproduct has been under discussion for quite awhile is b/c of the debate between p-v vs. more defined attributes. p-v is quite helpful b/c the attributes users care about change over time. Take cameras, for instance. Did anyone care about megapixels 10 years ago? etc.
* +1 I strongly oppose p-v as it is nothing more than a circumvention of the microformats [[process]] and 80/20 [[principle]] of formalizing only common properties. [[microformats]] are NOT designed to be infinitely extensible. p-v is simply another source of Tower of Babel problems. When attributes change over time, then the microformat can be iterated/extended to include them, *when* publishing behavior on the web for the *data* of such attributes exceeds the required 80/20 usage per microformats process. That being said, if you really must include arbitrary property-value data, there is already a microformat for that: [[xoxo]]. Modularly include a [[xoxo]] child and that way the extension is contained in a specific structure that can be ignored by implementations. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">

== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* There seem to be a great deal of vocab terms and the terms seem to be fairly loosely defined... are they all justified? Is there a file that we can analyze (like via microformalyze)?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>:The examples aren't necessarily an accurate reflection of how frequently attributes/data is used by retailers. In practice, model/mpn is used much more frequently than dimensions, both for retailer websites as well as retailer submissions to search and shopping engines. Defer to those with more experience/other data on version.
* +1. If you cannot justify a property, or are unsure about including it, or don't think it is necessarily an accurate reflection of how frequently the data is used, then leave it out per microformats [[principles]]. A "version" property was added to [[hReview]] for largely theoretical concerns, but has never been needed/used. So in practice (per experience), leave out "version". [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: I agree on both fronts here, I was surprised that model wasn't more prevalent in the research data, as it seems like an attribute that appears on nearly every product. Since "model" is often used as a type of identifier, it should be moved under the identifier attribute. "Version" will be taken out.
</div>
</div>

== Resolved Issues ==
<div class="vevent">
<div class="vevent">
== <span class="summary">HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* "quantity" and "shipping" have been removed from hproduct and transitioned to a new [[hlisting]] proposal. "price" has been retained, with the caveat that if hproduct is being used alone (eg., a non-commerce site who provides product information), without combining it with a microformat like [[hlisting]], it is assumed that the price attribute represents the suggested manufacturers retail price. All transactional details (including transactional price) would be deferred to [[hlisting]].
</div>
</div>

<div class="vevent">
== <span class="summary">HP2 - FN should be used instead of N for product titles</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* changed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* buy removed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* shipping removed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* p-v has been removed in draft spec 0.3 in favor of [[xoxo]]
</div>
</div>

<div class="vevent">
== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* many attributes have been removed in draft specs 0.2 and 0.3. We believe the current number of attributes accurately represents a product object while providing adequate opportunity to be combined with other microformats for better overall semantic solutions.
</div>
</div>

== Closed Issues ==

== Template ==
{{issues-format}}

hproduct-issues

2009-04-24T17:18:07Z

JayMyers: adding p-v resolution

__TOC__

== HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields ==

<div class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-12-17</span> raised by <span class="fn">NicolasLeroy</span></span>
<div class="description">
*# In the "[[hproduct#Out_of_Scope|out of scope]]" section, it is explained: _"This microformat does not intend to replicate any of the content proposed within hListing and would defer all money/transactional matters to that microformat"_
*# However, in the hProduct schema, we have the following fields:
*#* "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
*#* I would say there is also ambiguity between the responsibilities of hProduct vs hListing for the following fields: quantity / shipping
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I believe everyone agrees that we would borrow price from hListing for hProduct spec. I will explain the concept further in the schema.
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I don't follow the quantity/ shipping issue. I don't see either of these on hListing, unless the concepts are somehow embedded in other attributes. Can you elaborate on what the ambiguity is? ([[User:PaulLee|Paul Lee]]: If there's no objection here, may I suggest updating the price reference and keeping quantity and shipping as is?])
*#* +1 I agree with NicholasLeroy, anything price or transaction related should be left out of hProduct 0.1, and instead develop recipes / mark-up examples showing use of hListing with hProduct. We need to strongly resist and fight the tendency to include "just one more field" to individual formats and instead push to use formats as building blocks. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: If price should be left to hListing, should hAudio be modified not to include "price"?
*#* I am going to add price back into the hProduct spec. Price is an attribute of a product. We should be able to use microformats either standalone or as building blocks in combination with other formats. On price I'm thinking specifically of product manufacturer sites who may not be commerce enabled and are listing their products for informational purposes. In this case, they would not be using hListing, as there would be no transaction taking place. Leaving the price attribute out would ignore a major product attribute (in 99% of product sites, per hproduct examples analysis).
</div>
</div>

<div class="vevent">

== <span class="summary">HP2 - FN should be used instead of N for product title</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Why is <b>n</b> used instead of <b>fn</b> for the title of the product? hCard and hAudio both use fn for the formatted name of the product. <b>n</b> is usually an optimization.
* +1 hProduct should use "fn" for the name of the product. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: "n" will be changed to "fn" in the next version of the schema
* "fn" is hardly semantic, even though commonly deployed - surely "formatted-name" is truer to the principles of "humans-first, machines second" --[[User:Wowitim|Wowitim]] 12:59, 28 March 2009 (UTC)
</div>

<div class="vevent">

== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{OpenIssue}} <span class="vcard">BUY duplicates functionality of PAYMENT from hAudio<span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>buy</b> is duplicating the functionality of <b>payment</b> from hAudio.
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: From the payment page: "RelPayment is a microformat for making exchanges of support (be it financial or otherwise) possible. By adding rel="payment" to a hyperlink a page indicates that the destination of that hyperlink provides a way to show or give support for the current page. For example to give financial support to the owner of the current page. One of the goals with this microformat is to give content aggregators such as RSS readers a way to extract these support links and give them special attention (such as displaying a standard button along with the content)." First, this seems like a simple exercise for blogs, etc.; but the transaction process for shopping sites is typically considerably more complex. Usually, the actual payment URI is toward the end of the cart checkout process, the entry to which "buy" is intended to direct to the beginning of. Second, there is the potential for confusion when using payment, since "payment" in the shopping space often refers to payment methods, e.g., credit card, check, etc.
* +1 but in a different way. BUY/PAYMENT should both be out of scope for hProduct, and only be in hListing per issue HP1 above. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should these be in scope for hAudio then?
</div>
</div>

<div class="vevent">

== <span class="summary">HP4 - Are all of the formats for PRICE in hProduct allowed</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* The way that <b>price</b> is used is iffy - do we allow anything but currency/amount in the compound statement?
* +1 PRICE should not be in hProduct per issue HP1. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should other microformats (thinking hAudio) be modified not to include "price"?
</div>
</div>

<div class="vevent">

== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Seems like <b>shipping</b> could be abused quite a bit, resulting in a term that is fairly useless as time moves on.
* +1 agreed and I think SHIPPING belongs in hListing (not in hProduct) as it applies to a particular transaction/offering, and is not intrinsic to the product itself. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>p-v</b> seems like a catch-all, shoe-horn attempt at making the microformat infinitely scalable? Is this really useful?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: IIUC, part of the reason why hproduct has been under discussion for quite awhile is b/c of the debate between p-v vs. more defined attributes. p-v is quite helpful b/c the attributes users care about change over time. Take cameras, for instance. Did anyone care about megapixels 10 years ago? etc.
* +1 I strongly oppose p-v as it is nothing more than a circumvention of the microformats [[process]] and 80/20 [[principle]] of formalizing only common properties. [[microformats]] are NOT designed to be infinitely extensible. p-v is simply another source of Tower of Babel problems. When attributes change over time, then the microformat can be iterated/extended to include them, *when* publishing behavior on the web for the *data* of such attributes exceeds the required 80/20 usage per microformats process. That being said, if you really must include arbitrary property-value data, there is already a microformat for that: [[xoxo]]. Modularly include a [[xoxo]] child and that way the extension is contained in a specific structure that can be ignored by implementations. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">

== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* There seem to be a great deal of vocab terms and the terms seem to be fairly loosely defined... are they all justified? Is there a file that we can analyze (like via microformalyze)?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>:The examples aren't necessarily an accurate reflection of how frequently attributes/data is used by retailers. In practice, model/mpn is used much more frequently than dimensions, both for retailer websites as well as retailer submissions to search and shopping engines. Defer to those with more experience/other data on version.
* +1. If you cannot justify a property, or are unsure about including it, or don't think it is necessarily an accurate reflection of how frequently the data is used, then leave it out per microformats [[principles]]. A "version" property was added to [[hReview]] for largely theoretical concerns, but has never been needed/used. So in practice (per experience), leave out "version". [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: I agree on both fronts here, I was surprised that model wasn't more prevalent in the research data, as it seems like an attribute that appears on nearly every product. Since "model" is often used as a type of identifier, it should be moved under the identifier attribute. "Version" will be taken out.
</div>
</div>

== Resolved Issues ==
<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* p-v has been removed in draft spec 0.3 in favor of [[xoxo]]

</div>
</div>

== Closed Issues ==

== Template ==
{{issues-format}}

hproduct-issues

2009-04-24T17:11:16Z

JayMyers: changes

__TOC__

== HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields ==

<div class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-12-17</span> raised by <span class="fn">NicolasLeroy</span></span>
<div class="description">
*# In the "[[hproduct#Out_of_Scope|out of scope]]" section, it is explained: _"This microformat does not intend to replicate any of the content proposed within hListing and would defer all money/transactional matters to that microformat"_
*# However, in the hProduct schema, we have the following fields:
*#* "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
*#* I would say there is also ambiguity between the responsibilities of hProduct vs hListing for the following fields: quantity / shipping
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I believe everyone agrees that we would borrow price from hListing for hProduct spec. I will explain the concept further in the schema.
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I don't follow the quantity/ shipping issue. I don't see either of these on hListing, unless the concepts are somehow embedded in other attributes. Can you elaborate on what the ambiguity is? ([[User:PaulLee|Paul Lee]]: If there's no objection here, may I suggest updating the price reference and keeping quantity and shipping as is?])
*#* +1 I agree with NicholasLeroy, anything price or transaction related should be left out of hProduct 0.1, and instead develop recipes / mark-up examples showing use of hListing with hProduct. We need to strongly resist and fight the tendency to include "just one more field" to individual formats and instead push to use formats as building blocks. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: If price should be left to hListing, should hAudio be modified not to include "price"?
*#* I am going to add price back into the hProduct spec. Price is an attribute of a product. We should be able to use microformats either standalone or as building blocks in combination with other formats. On price I'm thinking specifically of product manufacturer sites who may not be commerce enabled and are listing their products for informational purposes. In this case, they would not be using hListing, as there would be no transaction taking place. Leaving the price attribute out would ignore a major product attribute (in 99% of product sites, per hproduct examples analysis).
</div>
</div>

<div class="vevent">

== <span class="summary">HP2 - FN should be used instead of N for product title</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Why is <b>n</b> used instead of <b>fn</b> for the title of the product? hCard and hAudio both use fn for the formatted name of the product. <b>n</b> is usually an optimization.
* +1 hProduct should use "fn" for the name of the product. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: "n" will be changed to "fn" in the next version of the schema
* "fn" is hardly semantic, even though commonly deployed - surely "formatted-name" is truer to the principles of "humans-first, machines second" --[[User:Wowitim|Wowitim]] 12:59, 28 March 2009 (UTC)
</div>

<div class="vevent">

== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{OpenIssue}} <span class="vcard">BUY duplicates functionality of PAYMENT from hAudio<span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>buy</b> is duplicating the functionality of <b>payment</b> from hAudio.
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: From the payment page: "RelPayment is a microformat for making exchanges of support (be it financial or otherwise) possible. By adding rel="payment" to a hyperlink a page indicates that the destination of that hyperlink provides a way to show or give support for the current page. For example to give financial support to the owner of the current page. One of the goals with this microformat is to give content aggregators such as RSS readers a way to extract these support links and give them special attention (such as displaying a standard button along with the content)." First, this seems like a simple exercise for blogs, etc.; but the transaction process for shopping sites is typically considerably more complex. Usually, the actual payment URI is toward the end of the cart checkout process, the entry to which "buy" is intended to direct to the beginning of. Second, there is the potential for confusion when using payment, since "payment" in the shopping space often refers to payment methods, e.g., credit card, check, etc.
* +1 but in a different way. BUY/PAYMENT should both be out of scope for hProduct, and only be in hListing per issue HP1 above. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should these be in scope for hAudio then?
</div>
</div>

<div class="vevent">

== <span class="summary">HP4 - Are all of the formats for PRICE in hProduct allowed</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* The way that <b>price</b> is used is iffy - do we allow anything but currency/amount in the compound statement?
* +1 PRICE should not be in hProduct per issue HP1. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should other microformats (thinking hAudio) be modified not to include "price"?
</div>
</div>

<div class="vevent">

== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Seems like <b>shipping</b> could be abused quite a bit, resulting in a term that is fairly useless as time moves on.
* +1 agreed and I think SHIPPING belongs in hListing (not in hProduct) as it applies to a particular transaction/offering, and is not intrinsic to the product itself. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>p-v</b> seems like a catch-all, shoe-horn attempt at making the microformat infinitely scalable? Is this really useful?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: IIUC, part of the reason why hproduct has been under discussion for quite awhile is b/c of the debate between p-v vs. more defined attributes. p-v is quite helpful b/c the attributes users care about change over time. Take cameras, for instance. Did anyone care about megapixels 10 years ago? etc.
* +1 I strongly oppose p-v as it is nothing more than a circumvention of the microformats [[process]] and 80/20 [[principle]] of formalizing only common properties. [[microformats]] are NOT designed to be infinitely extensible. p-v is simply another source of Tower of Babel problems. When attributes change over time, then the microformat can be iterated/extended to include them, *when* publishing behavior on the web for the *data* of such attributes exceeds the required 80/20 usage per microformats process. That being said, if you really must include arbitrary property-value data, there is already a microformat for that: [[xoxo]]. Modularly include a [[xoxo]] child and that way the extension is contained in a specific structure that can be ignored by implementations. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">

== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* There seem to be a great deal of vocab terms and the terms seem to be fairly loosely defined... are they all justified? Is there a file that we can analyze (like via microformalyze)?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>:The examples aren't necessarily an accurate reflection of how frequently attributes/data is used by retailers. In practice, model/mpn is used much more frequently than dimensions, both for retailer websites as well as retailer submissions to search and shopping engines. Defer to those with more experience/other data on version.
* +1. If you cannot justify a property, or are unsure about including it, or don't think it is necessarily an accurate reflection of how frequently the data is used, then leave it out per microformats [[principles]]. A "version" property was added to [[hReview]] for largely theoretical concerns, but has never been needed/used. So in practice (per experience), leave out "version". [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: I agree on both fronts here, I was surprised that model wasn't more prevalent in the research data, as it seems like an attribute that appears on nearly every product. Since "model" is often used as a type of identifier, it should be moved under the identifier attribute. "Version" will be taken out.
</div>
</div>

== Resolved Issues ==
<div class="vevent">
* {{ResolvedIssue}} <span class="summary vcard">HP6 - P-V seems like a catch-all for hProduct<span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
** p-v has been removed in draft spec 0.3 in favor of [[xoxo]]
</div>
</div>

== Closed Issues ==

== Template ==
{{issues-format}}

hproduct-issues

2009-04-24T17:10:32Z

JayMyers: /* Resolved Issues */

__TOC__

== HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields ==

<div class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-12-17</span> raised by <span class="fn">NicolasLeroy</span></span>
<div class="description">
*# In the "[[hproduct#Out_of_Scope|out of scope]]" section, it is explained: _"This microformat does not intend to replicate any of the content proposed within hListing and would defer all money/transactional matters to that microformat"_
*# However, in the hProduct schema, we have the following fields:
*#* "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
*#* I would say there is also ambiguity between the responsibilities of hProduct vs hListing for the following fields: quantity / shipping
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I believe everyone agrees that we would borrow price from hListing for hProduct spec. I will explain the concept further in the schema.
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I don't follow the quantity/ shipping issue. I don't see either of these on hListing, unless the concepts are somehow embedded in other attributes. Can you elaborate on what the ambiguity is? ([[User:PaulLee|Paul Lee]]: If there's no objection here, may I suggest updating the price reference and keeping quantity and shipping as is?])
*#* +1 I agree with NicholasLeroy, anything price or transaction related should be left out of hProduct 0.1, and instead develop recipes / mark-up examples showing use of hListing with hProduct. We need to strongly resist and fight the tendency to include "just one more field" to individual formats and instead push to use formats as building blocks. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: If price should be left to hListing, should hAudio be modified not to include "price"?
*#* I am going to add price back into the hProduct spec. Price is an attribute of a product. We should be able to use microformats either standalone or as building blocks in combination with other formats. On price I'm thinking specifically of product manufacturer sites who may not be commerce enabled and are listing their products for informational purposes. In this case, they would not be using hListing, as there would be no transaction taking place. Leaving the price attribute out would ignore a major product attribute (in 99% of product sites, per hproduct examples analysis).
</div>
</div>

<div class="vevent">

== <span class="summary">HP2 - FN should be used instead of N for product title</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Why is <b>n</b> used instead of <b>fn</b> for the title of the product? hCard and hAudio both use fn for the formatted name of the product. <b>n</b> is usually an optimization.
* +1 hProduct should use "fn" for the name of the product. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: "n" will be changed to "fn" in the next version of the schema
* "fn" is hardly semantic, even though commonly deployed - surely "formatted-name" is truer to the principles of "humans-first, machines second" --[[User:Wowitim|Wowitim]] 12:59, 28 March 2009 (UTC)
</div>

<div class="vevent">

== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{OpenIssue}} <span class="vcard">BUY duplicates functionality of PAYMENT from hAudio<span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>buy</b> is duplicating the functionality of <b>payment</b> from hAudio.
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: From the payment page: "RelPayment is a microformat for making exchanges of support (be it financial or otherwise) possible. By adding rel="payment" to a hyperlink a page indicates that the destination of that hyperlink provides a way to show or give support for the current page. For example to give financial support to the owner of the current page. One of the goals with this microformat is to give content aggregators such as RSS readers a way to extract these support links and give them special attention (such as displaying a standard button along with the content)." First, this seems like a simple exercise for blogs, etc.; but the transaction process for shopping sites is typically considerably more complex. Usually, the actual payment URI is toward the end of the cart checkout process, the entry to which "buy" is intended to direct to the beginning of. Second, there is the potential for confusion when using payment, since "payment" in the shopping space often refers to payment methods, e.g., credit card, check, etc.
* +1 but in a different way. BUY/PAYMENT should both be out of scope for hProduct, and only be in hListing per issue HP1 above. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should these be in scope for hAudio then?
</div>
</div>

<div class="vevent">

== <span class="summary">HP4 - Are all of the formats for PRICE in hProduct allowed</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* The way that <b>price</b> is used is iffy - do we allow anything but currency/amount in the compound statement?
* +1 PRICE should not be in hProduct per issue HP1. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should other microformats (thinking hAudio) be modified not to include "price"?
</div>
</div>

<div class="vevent">

== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Seems like <b>shipping</b> could be abused quite a bit, resulting in a term that is fairly useless as time moves on.
* +1 agreed and I think SHIPPING belongs in hListing (not in hProduct) as it applies to a particular transaction/offering, and is not intrinsic to the product itself. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>p-v</b> seems like a catch-all, shoe-horn attempt at making the microformat infinitely scalable? Is this really useful?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: IIUC, part of the reason why hproduct has been under discussion for quite awhile is b/c of the debate between p-v vs. more defined attributes. p-v is quite helpful b/c the attributes users care about change over time. Take cameras, for instance. Did anyone care about megapixels 10 years ago? etc.
* +1 I strongly oppose p-v as it is nothing more than a circumvention of the microformats [[process]] and 80/20 [[principle]] of formalizing only common properties. [[microformats]] are NOT designed to be infinitely extensible. p-v is simply another source of Tower of Babel problems. When attributes change over time, then the microformat can be iterated/extended to include them, *when* publishing behavior on the web for the *data* of such attributes exceeds the required 80/20 usage per microformats process. That being said, if you really must include arbitrary property-value data, there is already a microformat for that: [[xoxo]]. Modularly include a [[xoxo]] child and that way the extension is contained in a specific structure that can be ignored by implementations. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">

== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* There seem to be a great deal of vocab terms and the terms seem to be fairly loosely defined... are they all justified? Is there a file that we can analyze (like via microformalyze)?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>:The examples aren't necessarily an accurate reflection of how frequently attributes/data is used by retailers. In practice, model/mpn is used much more frequently than dimensions, both for retailer websites as well as retailer submissions to search and shopping engines. Defer to those with more experience/other data on version.
* +1. If you cannot justify a property, or are unsure about including it, or don't think it is necessarily an accurate reflection of how frequently the data is used, then leave it out per microformats [[principles]]. A "version" property was added to [[hReview]] for largely theoretical concerns, but has never been needed/used. So in practice (per experience), leave out "version". [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: I agree on both fronts here, I was surprised that model wasn't more prevalent in the research data, as it seems like an attribute that appears on nearly every product. Since "model" is often used as a type of identifier, it should be moved under the identifier attribute. "Version" will be taken out.
</div>
</div>

== Resolved Issues ==
<div class="vevent">
* {{ResolvedIssue}} <span class="summary vcard">HP6 - P-V seems like a catch-all for hProduct<span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* p-v has been removed in draft spec 0.3 in favor of [[xoxo]]
</div>
</div>

== Closed Issues ==

== Template ==
{{issues-format}}

hproduct-issues

2009-04-24T17:10:03Z

JayMyers: revising format

__TOC__

== HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields ==

<div class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-12-17</span> raised by <span class="fn">NicolasLeroy</span></span>
<div class="description">
*# In the "[[hproduct#Out_of_Scope|out of scope]]" section, it is explained: _"This microformat does not intend to replicate any of the content proposed within hListing and would defer all money/transactional matters to that microformat"_
*# However, in the hProduct schema, we have the following fields:
*#* "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
*#* I would say there is also ambiguity between the responsibilities of hProduct vs hListing for the following fields: quantity / shipping
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I believe everyone agrees that we would borrow price from hListing for hProduct spec. I will explain the concept further in the schema.
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I don't follow the quantity/ shipping issue. I don't see either of these on hListing, unless the concepts are somehow embedded in other attributes. Can you elaborate on what the ambiguity is? ([[User:PaulLee|Paul Lee]]: If there's no objection here, may I suggest updating the price reference and keeping quantity and shipping as is?])
*#* +1 I agree with NicholasLeroy, anything price or transaction related should be left out of hProduct 0.1, and instead develop recipes / mark-up examples showing use of hListing with hProduct. We need to strongly resist and fight the tendency to include "just one more field" to individual formats and instead push to use formats as building blocks. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: If price should be left to hListing, should hAudio be modified not to include "price"?
*#* I am going to add price back into the hProduct spec. Price is an attribute of a product. We should be able to use microformats either standalone or as building blocks in combination with other formats. On price I'm thinking specifically of product manufacturer sites who may not be commerce enabled and are listing their products for informational purposes. In this case, they would not be using hListing, as there would be no transaction taking place. Leaving the price attribute out would ignore a major product attribute (in 99% of product sites, per hproduct examples analysis).
</div>
</div>

<div class="vevent">

== <span class="summary">HP2 - FN should be used instead of N for product title</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Why is <b>n</b> used instead of <b>fn</b> for the title of the product? hCard and hAudio both use fn for the formatted name of the product. <b>n</b> is usually an optimization.
* +1 hProduct should use "fn" for the name of the product. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: "n" will be changed to "fn" in the next version of the schema
* "fn" is hardly semantic, even though commonly deployed - surely "formatted-name" is truer to the principles of "humans-first, machines second" --[[User:Wowitim|Wowitim]] 12:59, 28 March 2009 (UTC)
</div>

<div class="vevent">

== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{OpenIssue}} <span class="vcard">BUY duplicates functionality of PAYMENT from hAudio<span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>buy</b> is duplicating the functionality of <b>payment</b> from hAudio.
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: From the payment page: "RelPayment is a microformat for making exchanges of support (be it financial or otherwise) possible. By adding rel="payment" to a hyperlink a page indicates that the destination of that hyperlink provides a way to show or give support for the current page. For example to give financial support to the owner of the current page. One of the goals with this microformat is to give content aggregators such as RSS readers a way to extract these support links and give them special attention (such as displaying a standard button along with the content)." First, this seems like a simple exercise for blogs, etc.; but the transaction process for shopping sites is typically considerably more complex. Usually, the actual payment URI is toward the end of the cart checkout process, the entry to which "buy" is intended to direct to the beginning of. Second, there is the potential for confusion when using payment, since "payment" in the shopping space often refers to payment methods, e.g., credit card, check, etc.
* +1 but in a different way. BUY/PAYMENT should both be out of scope for hProduct, and only be in hListing per issue HP1 above. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should these be in scope for hAudio then?
</div>
</div>

<div class="vevent">

== <span class="summary">HP4 - Are all of the formats for PRICE in hProduct allowed</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* The way that <b>price</b> is used is iffy - do we allow anything but currency/amount in the compound statement?
* +1 PRICE should not be in hProduct per issue HP1. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should other microformats (thinking hAudio) be modified not to include "price"?
</div>
</div>

<div class="vevent">

== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Seems like <b>shipping</b> could be abused quite a bit, resulting in a term that is fairly useless as time moves on.
* +1 agreed and I think SHIPPING belongs in hListing (not in hProduct) as it applies to a particular transaction/offering, and is not intrinsic to the product itself. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>p-v</b> seems like a catch-all, shoe-horn attempt at making the microformat infinitely scalable? Is this really useful?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: IIUC, part of the reason why hproduct has been under discussion for quite awhile is b/c of the debate between p-v vs. more defined attributes. p-v is quite helpful b/c the attributes users care about change over time. Take cameras, for instance. Did anyone care about megapixels 10 years ago? etc.
* +1 I strongly oppose p-v as it is nothing more than a circumvention of the microformats [[process]] and 80/20 [[principle]] of formalizing only common properties. [[microformats]] are NOT designed to be infinitely extensible. p-v is simply another source of Tower of Babel problems. When attributes change over time, then the microformat can be iterated/extended to include them, *when* publishing behavior on the web for the *data* of such attributes exceeds the required 80/20 usage per microformats process. That being said, if you really must include arbitrary property-value data, there is already a microformat for that: [[xoxo]]. Modularly include a [[xoxo]] child and that way the extension is contained in a specific structure that can be ignored by implementations. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">

== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* There seem to be a great deal of vocab terms and the terms seem to be fairly loosely defined... are they all justified? Is there a file that we can analyze (like via microformalyze)?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>:The examples aren't necessarily an accurate reflection of how frequently attributes/data is used by retailers. In practice, model/mpn is used much more frequently than dimensions, both for retailer websites as well as retailer submissions to search and shopping engines. Defer to those with more experience/other data on version.
* +1. If you cannot justify a property, or are unsure about including it, or don't think it is necessarily an accurate reflection of how frequently the data is used, then leave it out per microformats [[principles]]. A "version" property was added to [[hReview]] for largely theoretical concerns, but has never been needed/used. So in practice (per experience), leave out "version". [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: I agree on both fronts here, I was surprised that model wasn't more prevalent in the research data, as it seems like an attribute that appears on nearly every product. Since "model" is often used as a type of identifier, it should be moved under the identifier attribute. "Version" will be taken out.
</div>
</div>

== Resolved Issues ==
<div class="vevent">
* {{ResolvedIssue}} <span class="summary vcard">HP6 - P-V seems like a catch-all for hProduct<span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
*# p-v has been removed in draft spec 0.3 in favor of [[xoxo]]
</div>
</div>

== Closed Issues ==

== Template ==
{{issues-format}}

hproduct-issues

2009-04-24T17:07:20Z

JayMyers: adding resolution

__TOC__

== HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields ==

<div class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-12-17</span> raised by <span class="fn">NicolasLeroy</span></span>
<div class="description">
*# In the "[[hproduct#Out_of_Scope|out of scope]]" section, it is explained: _"This microformat does not intend to replicate any of the content proposed within hListing and would defer all money/transactional matters to that microformat"_
*# However, in the hProduct schema, we have the following fields:
*#* "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
*#* I would say there is also ambiguity between the responsibilities of hProduct vs hListing for the following fields: quantity / shipping
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I believe everyone agrees that we would borrow price from hListing for hProduct spec. I will explain the concept further in the schema.
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I don't follow the quantity/ shipping issue. I don't see either of these on hListing, unless the concepts are somehow embedded in other attributes. Can you elaborate on what the ambiguity is? ([[User:PaulLee|Paul Lee]]: If there's no objection here, may I suggest updating the price reference and keeping quantity and shipping as is?])
*#* +1 I agree with NicholasLeroy, anything price or transaction related should be left out of hProduct 0.1, and instead develop recipes / mark-up examples showing use of hListing with hProduct. We need to strongly resist and fight the tendency to include "just one more field" to individual formats and instead push to use formats as building blocks. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: If price should be left to hListing, should hAudio be modified not to include "price"?
*#* I am going to add price back into the hProduct spec. Price is an attribute of a product. We should be able to use microformats either standalone or as building blocks in combination with other formats. On price I'm thinking specifically of product manufacturer sites who may not be commerce enabled and are listing their products for informational purposes. In this case, they would not be using hListing, as there would be no transaction taking place. Leaving the price attribute out would ignore a major product attribute (in 99% of product sites, per hproduct examples analysis).
</div>
</div>

<div class="vevent">

== <span class="summary">HP2 - FN should be used instead of N for product title</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Why is <b>n</b> used instead of <b>fn</b> for the title of the product? hCard and hAudio both use fn for the formatted name of the product. <b>n</b> is usually an optimization.
* +1 hProduct should use "fn" for the name of the product. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: "n" will be changed to "fn" in the next version of the schema
* "fn" is hardly semantic, even though commonly deployed - surely "formatted-name" is truer to the principles of "humans-first, machines second" --[[User:Wowitim|Wowitim]] 12:59, 28 March 2009 (UTC)
</div>

<div class="vevent">

== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{OpenIssue}} <span class="vcard">BUY duplicates functionality of PAYMENT from hAudio<span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>buy</b> is duplicating the functionality of <b>payment</b> from hAudio.
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: From the payment page: "RelPayment is a microformat for making exchanges of support (be it financial or otherwise) possible. By adding rel="payment" to a hyperlink a page indicates that the destination of that hyperlink provides a way to show or give support for the current page. For example to give financial support to the owner of the current page. One of the goals with this microformat is to give content aggregators such as RSS readers a way to extract these support links and give them special attention (such as displaying a standard button along with the content)." First, this seems like a simple exercise for blogs, etc.; but the transaction process for shopping sites is typically considerably more complex. Usually, the actual payment URI is toward the end of the cart checkout process, the entry to which "buy" is intended to direct to the beginning of. Second, there is the potential for confusion when using payment, since "payment" in the shopping space often refers to payment methods, e.g., credit card, check, etc.
* +1 but in a different way. BUY/PAYMENT should both be out of scope for hProduct, and only be in hListing per issue HP1 above. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should these be in scope for hAudio then?
</div>
</div>

<div class="vevent">

== <span class="summary">HP4 - Are all of the formats for PRICE in hProduct allowed</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* The way that <b>price</b> is used is iffy - do we allow anything but currency/amount in the compound statement?
* +1 PRICE should not be in hProduct per issue HP1. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should other microformats (thinking hAudio) be modified not to include "price"?
</div>
</div>

<div class="vevent">

== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Seems like <b>shipping</b> could be abused quite a bit, resulting in a term that is fairly useless as time moves on.
* +1 agreed and I think SHIPPING belongs in hListing (not in hProduct) as it applies to a particular transaction/offering, and is not intrinsic to the product itself. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>p-v</b> seems like a catch-all, shoe-horn attempt at making the microformat infinitely scalable? Is this really useful?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: IIUC, part of the reason why hproduct has been under discussion for quite awhile is b/c of the debate between p-v vs. more defined attributes. p-v is quite helpful b/c the attributes users care about change over time. Take cameras, for instance. Did anyone care about megapixels 10 years ago? etc.
* +1 I strongly oppose p-v as it is nothing more than a circumvention of the microformats [[process]] and 80/20 [[principle]] of formalizing only common properties. [[microformats]] are NOT designed to be infinitely extensible. p-v is simply another source of Tower of Babel problems. When attributes change over time, then the microformat can be iterated/extended to include them, *when* publishing behavior on the web for the *data* of such attributes exceeds the required 80/20 usage per microformats process. That being said, if you really must include arbitrary property-value data, there is already a microformat for that: [[xoxo]]. Modularly include a [[xoxo]] child and that way the extension is contained in a specific structure that can be ignored by implementations. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">

== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* There seem to be a great deal of vocab terms and the terms seem to be fairly loosely defined... are they all justified? Is there a file that we can analyze (like via microformalyze)?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>:The examples aren't necessarily an accurate reflection of how frequently attributes/data is used by retailers. In practice, model/mpn is used much more frequently than dimensions, both for retailer websites as well as retailer submissions to search and shopping engines. Defer to those with more experience/other data on version.
* +1. If you cannot justify a property, or are unsure about including it, or don't think it is necessarily an accurate reflection of how frequently the data is used, then leave it out per microformats [[principles]]. A "version" property was added to [[hReview]] for largely theoretical concerns, but has never been needed/used. So in practice (per experience), leave out "version". [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: I agree on both fronts here, I was surprised that model wasn't more prevalent in the research data, as it seems like an attribute that appears on nearly every product. Since "model" is often used as a type of identifier, it should be moved under the identifier attribute. "Version" will be taken out.
</div>
</div>

== Resolved Issues ==
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> response by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
*# p-v has been removed in draft spec 0.3 in favor of [[xoxo]]
</div>

== Closed Issues ==

== Template ==
{{issues-format}}

hproduct-issues

2009-04-24T17:03:41Z

JayMyers: adding

__TOC__

== HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields ==

<div class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-12-17</span> raised by <span class="fn">NicolasLeroy</span></span>
<div class="description">
*# In the "[[hproduct#Out_of_Scope|out of scope]]" section, it is explained: _"This microformat does not intend to replicate any of the content proposed within hListing and would defer all money/transactional matters to that microformat"_
*# However, in the hProduct schema, we have the following fields:
*#* "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
*#* I would say there is also ambiguity between the responsibilities of hProduct vs hListing for the following fields: quantity / shipping
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I believe everyone agrees that we would borrow price from hListing for hProduct spec. I will explain the concept further in the schema.
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I don't follow the quantity/ shipping issue. I don't see either of these on hListing, unless the concepts are somehow embedded in other attributes. Can you elaborate on what the ambiguity is? ([[User:PaulLee|Paul Lee]]: If there's no objection here, may I suggest updating the price reference and keeping quantity and shipping as is?])
*#* +1 I agree with NicholasLeroy, anything price or transaction related should be left out of hProduct 0.1, and instead develop recipes / mark-up examples showing use of hListing with hProduct. We need to strongly resist and fight the tendency to include "just one more field" to individual formats and instead push to use formats as building blocks. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: If price should be left to hListing, should hAudio be modified not to include "price"?
*#* I am going to add price back into the hProduct spec. Price is an attribute of a product. We should be able to use microformats either standalone or as building blocks in combination with other formats. On price I'm thinking specifically of product manufacturer sites who may not be commerce enabled and are listing their products for informational purposes. In this case, they would not be using hListing, as there would be no transaction taking place. Leaving the price attribute out would ignore a major product attribute (in 99% of product sites, per hproduct examples analysis).
</div>
</div>

<div class="vevent">

== <span class="summary">HP2 - FN should be used instead of N for product title</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Why is <b>n</b> used instead of <b>fn</b> for the title of the product? hCard and hAudio both use fn for the formatted name of the product. <b>n</b> is usually an optimization.
* +1 hProduct should use "fn" for the name of the product. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: "n" will be changed to "fn" in the next version of the schema
* "fn" is hardly semantic, even though commonly deployed - surely "formatted-name" is truer to the principles of "humans-first, machines second" --[[User:Wowitim|Wowitim]] 12:59, 28 March 2009 (UTC)
</div>

<div class="vevent">

== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{OpenIssue}} <span class="vcard">BUY duplicates functionality of PAYMENT from hAudio<span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>buy</b> is duplicating the functionality of <b>payment</b> from hAudio.
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: From the payment page: "RelPayment is a microformat for making exchanges of support (be it financial or otherwise) possible. By adding rel="payment" to a hyperlink a page indicates that the destination of that hyperlink provides a way to show or give support for the current page. For example to give financial support to the owner of the current page. One of the goals with this microformat is to give content aggregators such as RSS readers a way to extract these support links and give them special attention (such as displaying a standard button along with the content)." First, this seems like a simple exercise for blogs, etc.; but the transaction process for shopping sites is typically considerably more complex. Usually, the actual payment URI is toward the end of the cart checkout process, the entry to which "buy" is intended to direct to the beginning of. Second, there is the potential for confusion when using payment, since "payment" in the shopping space often refers to payment methods, e.g., credit card, check, etc.
* +1 but in a different way. BUY/PAYMENT should both be out of scope for hProduct, and only be in hListing per issue HP1 above. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should these be in scope for hAudio then?
</div>
</div>

<div class="vevent">

== <span class="summary">HP4 - Are all of the formats for PRICE in hProduct allowed</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* The way that <b>price</b> is used is iffy - do we allow anything but currency/amount in the compound statement?
* +1 PRICE should not be in hProduct per issue HP1. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should other microformats (thinking hAudio) be modified not to include "price"?
</div>
</div>

<div class="vevent">

== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Seems like <b>shipping</b> could be abused quite a bit, resulting in a term that is fairly useless as time moves on.
* +1 agreed and I think SHIPPING belongs in hListing (not in hProduct) as it applies to a particular transaction/offering, and is not intrinsic to the product itself. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>p-v</b> seems like a catch-all, shoe-horn attempt at making the microformat infinitely scalable? Is this really useful?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: IIUC, part of the reason why hproduct has been under discussion for quite awhile is b/c of the debate between p-v vs. more defined attributes. p-v is quite helpful b/c the attributes users care about change over time. Take cameras, for instance. Did anyone care about megapixels 10 years ago? etc.
* +1 I strongly oppose p-v as it is nothing more than a circumvention of the microformats [[process]] and 80/20 [[principle]] of formalizing only common properties. [[microformats]] are NOT designed to be infinitely extensible. p-v is simply another source of Tower of Babel problems. When attributes change over time, then the microformat can be iterated/extended to include them, *when* publishing behavior on the web for the *data* of such attributes exceeds the required 80/20 usage per microformats process. That being said, if you really must include arbitrary property-value data, there is already a microformat for that: [[xoxo]]. Modularly include a [[xoxo]] child and that way the extension is contained in a specific structure that can be ignored by implementations. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">

== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* There seem to be a great deal of vocab terms and the terms seem to be fairly loosely defined... are they all justified? Is there a file that we can analyze (like via microformalyze)?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>:The examples aren't necessarily an accurate reflection of how frequently attributes/data is used by retailers. In practice, model/mpn is used much more frequently than dimensions, both for retailer websites as well as retailer submissions to search and shopping engines. Defer to those with more experience/other data on version.
* +1. If you cannot justify a property, or are unsure about including it, or don't think it is necessarily an accurate reflection of how frequently the data is used, then leave it out per microformats [[principles]]. A "version" property was added to [[hReview]] for largely theoretical concerns, but has never been needed/used. So in practice (per experience), leave out "version". [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: I agree on both fronts here, I was surprised that model wasn't more prevalent in the research data, as it seems like an attribute that appears on nearly every product. Since "model" is often used as a type of identifier, it should be moved under the identifier attribute. "Version" will be taken out.
</div>
</div>

== Resolved Issues ==
* {{ResolvedIssue}}

== Closed Issues ==

== Template ==
{{issues-format}}

hproduct-issues

2009-04-24T17:02:33Z

JayMyers: editing format

__TOC__

== HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields ==

<div class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-12-17</span> raised by <span class="fn">NicolasLeroy</span></span>
<div class="description">
*# In the "[[hproduct#Out_of_Scope|out of scope]]" section, it is explained: _"This microformat does not intend to replicate any of the content proposed within hListing and would defer all money/transactional matters to that microformat"_
*# However, in the hProduct schema, we have the following fields:
*#* "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
*#* I would say there is also ambiguity between the responsibilities of hProduct vs hListing for the following fields: quantity / shipping
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I believe everyone agrees that we would borrow price from hListing for hProduct spec. I will explain the concept further in the schema.
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I don't follow the quantity/ shipping issue. I don't see either of these on hListing, unless the concepts are somehow embedded in other attributes. Can you elaborate on what the ambiguity is? ([[User:PaulLee|Paul Lee]]: If there's no objection here, may I suggest updating the price reference and keeping quantity and shipping as is?])
*#* +1 I agree with NicholasLeroy, anything price or transaction related should be left out of hProduct 0.1, and instead develop recipes / mark-up examples showing use of hListing with hProduct. We need to strongly resist and fight the tendency to include "just one more field" to individual formats and instead push to use formats as building blocks. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: If price should be left to hListing, should hAudio be modified not to include "price"?
*#* I am going to add price back into the hProduct spec. Price is an attribute of a product. We should be able to use microformats either standalone or as building blocks in combination with other formats. On price I'm thinking specifically of product manufacturer sites who may not be commerce enabled and are listing their products for informational purposes. In this case, they would not be using hListing, as there would be no transaction taking place. Leaving the price attribute out would ignore a major product attribute (in 99% of product sites, per hproduct examples analysis).
</div>
</div>

<div class="vevent">

== <span class="summary">HP2 - FN should be used instead of N for product title</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Why is <b>n</b> used instead of <b>fn</b> for the title of the product? hCard and hAudio both use fn for the formatted name of the product. <b>n</b> is usually an optimization.
* +1 hProduct should use "fn" for the name of the product. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: "n" will be changed to "fn" in the next version of the schema
* "fn" is hardly semantic, even though commonly deployed - surely "formatted-name" is truer to the principles of "humans-first, machines second" --[[User:Wowitim|Wowitim]] 12:59, 28 March 2009 (UTC)
</div>

<div class="vevent">

== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{OpenIssue}} <span class="vcard">BUY duplicates functionality of PAYMENT from hAudio<span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>buy</b> is duplicating the functionality of <b>payment</b> from hAudio.
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: From the payment page: "RelPayment is a microformat for making exchanges of support (be it financial or otherwise) possible. By adding rel="payment" to a hyperlink a page indicates that the destination of that hyperlink provides a way to show or give support for the current page. For example to give financial support to the owner of the current page. One of the goals with this microformat is to give content aggregators such as RSS readers a way to extract these support links and give them special attention (such as displaying a standard button along with the content)." First, this seems like a simple exercise for blogs, etc.; but the transaction process for shopping sites is typically considerably more complex. Usually, the actual payment URI is toward the end of the cart checkout process, the entry to which "buy" is intended to direct to the beginning of. Second, there is the potential for confusion when using payment, since "payment" in the shopping space often refers to payment methods, e.g., credit card, check, etc.
* +1 but in a different way. BUY/PAYMENT should both be out of scope for hProduct, and only be in hListing per issue HP1 above. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should these be in scope for hAudio then?
</div>
</div>

<div class="vevent">

== <span class="summary">HP4 - Are all of the formats for PRICE in hProduct allowed</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* The way that <b>price</b> is used is iffy - do we allow anything but currency/amount in the compound statement?
* +1 PRICE should not be in hProduct per issue HP1. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should other microformats (thinking hAudio) be modified not to include "price"?
</div>
</div>

<div class="vevent">

== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Seems like <b>shipping</b> could be abused quite a bit, resulting in a term that is fairly useless as time moves on.
* +1 agreed and I think SHIPPING belongs in hListing (not in hProduct) as it applies to a particular transaction/offering, and is not intrinsic to the product itself. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>p-v</b> seems like a catch-all, shoe-horn attempt at making the microformat infinitely scalable? Is this really useful?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: IIUC, part of the reason why hproduct has been under discussion for quite awhile is b/c of the debate between p-v vs. more defined attributes. p-v is quite helpful b/c the attributes users care about change over time. Take cameras, for instance. Did anyone care about megapixels 10 years ago? etc.
* +1 I strongly oppose p-v as it is nothing more than a circumvention of the microformats [[process]] and 80/20 [[principle]] of formalizing only common properties. [[microformats]] are NOT designed to be infinitely extensible. p-v is simply another source of Tower of Babel problems. When attributes change over time, then the microformat can be iterated/extended to include them, *when* publishing behavior on the web for the *data* of such attributes exceeds the required 80/20 usage per microformats process. That being said, if you really must include arbitrary property-value data, there is already a microformat for that: [[xoxo]]. Modularly include a [[xoxo]] child and that way the extension is contained in a specific structure that can be ignored by implementations. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">

== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* There seem to be a great deal of vocab terms and the terms seem to be fairly loosely defined... are they all justified? Is there a file that we can analyze (like via microformalyze)?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>:The examples aren't necessarily an accurate reflection of how frequently attributes/data is used by retailers. In practice, model/mpn is used much more frequently than dimensions, both for retailer websites as well as retailer submissions to search and shopping engines. Defer to those with more experience/other data on version.
* +1. If you cannot justify a property, or are unsure about including it, or don't think it is necessarily an accurate reflection of how frequently the data is used, then leave it out per microformats [[principles]]. A "version" property was added to [[hReview]] for largely theoretical concerns, but has never been needed/used. So in practice (per experience), leave out "version". [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: I agree on both fronts here, I was surprised that model wasn't more prevalent in the research data, as it seems like an attribute that appears on nearly every product. Since "model" is often used as a type of identifier, it should be moved under the identifier attribute. "Version" will be taken out.
</div>
</div>

== Resolved Issues ==

== Closed Issues ==

== Template ==
{{issues-format}}

hproduct-issues

2009-04-24T17:01:57Z

JayMyers: adding more site areas

__TOC__

== HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields ==

<div class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-12-17</span> raised by <span class="fn">NicolasLeroy</span></span>
<div class="description">
*# In the "[[hproduct#Out_of_Scope|out of scope]]" section, it is explained: _"This microformat does not intend to replicate any of the content proposed within hListing and would defer all money/transactional matters to that microformat"_
*# However, in the hProduct schema, we have the following fields:
*#* "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
*#* I would say there is also ambiguity between the responsibilities of hProduct vs hListing for the following fields: quantity / shipping
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I believe everyone agrees that we would borrow price from hListing for hProduct spec. I will explain the concept further in the schema.
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I don't follow the quantity/ shipping issue. I don't see either of these on hListing, unless the concepts are somehow embedded in other attributes. Can you elaborate on what the ambiguity is? ([[User:PaulLee|Paul Lee]]: If there's no objection here, may I suggest updating the price reference and keeping quantity and shipping as is?])
*#* +1 I agree with NicholasLeroy, anything price or transaction related should be left out of hProduct 0.1, and instead develop recipes / mark-up examples showing use of hListing with hProduct. We need to strongly resist and fight the tendency to include "just one more field" to individual formats and instead push to use formats as building blocks. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: If price should be left to hListing, should hAudio be modified not to include "price"?
*#* I am going to add price back into the hProduct spec. Price is an attribute of a product. We should be able to use microformats either standalone or as building blocks in combination with other formats. On price I'm thinking specifically of product manufacturer sites who may not be commerce enabled and are listing their products for informational purposes. In this case, they would not be using hListing, as there would be no transaction taking place. Leaving the price attribute out would ignore a major product attribute (in 99% of product sites, per hproduct examples analysis).
</div>
</div>

<div class="vevent">

== <span class="summary">HP2 - FN should be used instead of N for product title</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Why is <b>n</b> used instead of <b>fn</b> for the title of the product? hCard and hAudio both use fn for the formatted name of the product. <b>n</b> is usually an optimization.
* +1 hProduct should use "fn" for the name of the product. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: "n" will be changed to "fn" in the next version of the schema
* "fn" is hardly semantic, even though commonly deployed - surely "formatted-name" is truer to the principles of "humans-first, machines second" --[[User:Wowitim|Wowitim]] 12:59, 28 March 2009 (UTC)
</div>

<div class="vevent">

== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{OpenIssue}} <span class="vcard">BUY duplicates functionality of PAYMENT from hAudio<span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>buy</b> is duplicating the functionality of <b>payment</b> from hAudio.
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: From the payment page: "RelPayment is a microformat for making exchanges of support (be it financial or otherwise) possible. By adding rel="payment" to a hyperlink a page indicates that the destination of that hyperlink provides a way to show or give support for the current page. For example to give financial support to the owner of the current page. One of the goals with this microformat is to give content aggregators such as RSS readers a way to extract these support links and give them special attention (such as displaying a standard button along with the content)." First, this seems like a simple exercise for blogs, etc.; but the transaction process for shopping sites is typically considerably more complex. Usually, the actual payment URI is toward the end of the cart checkout process, the entry to which "buy" is intended to direct to the beginning of. Second, there is the potential for confusion when using payment, since "payment" in the shopping space often refers to payment methods, e.g., credit card, check, etc.
* +1 but in a different way. BUY/PAYMENT should both be out of scope for hProduct, and only be in hListing per issue HP1 above. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should these be in scope for hAudio then?
</div>
</div>

<div class="vevent">

== <span class="summary">HP4 - Are all of the formats for PRICE in hProduct allowed</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* The way that <b>price</b> is used is iffy - do we allow anything but currency/amount in the compound statement?
* +1 PRICE should not be in hProduct per issue HP1. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should other microformats (thinking hAudio) be modified not to include "price"?
</div>
</div>

<div class="vevent">

== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Seems like <b>shipping</b> could be abused quite a bit, resulting in a term that is fairly useless as time moves on.
* +1 agreed and I think SHIPPING belongs in hListing (not in hProduct) as it applies to a particular transaction/offering, and is not intrinsic to the product itself. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>p-v</b> seems like a catch-all, shoe-horn attempt at making the microformat infinitely scalable? Is this really useful?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: IIUC, part of the reason why hproduct has been under discussion for quite awhile is b/c of the debate between p-v vs. more defined attributes. p-v is quite helpful b/c the attributes users care about change over time. Take cameras, for instance. Did anyone care about megapixels 10 years ago? etc.
* +1 I strongly oppose p-v as it is nothing more than a circumvention of the microformats [[process]] and 80/20 [[principle]] of formalizing only common properties. [[microformats]] are NOT designed to be infinitely extensible. p-v is simply another source of Tower of Babel problems. When attributes change over time, then the microformat can be iterated/extended to include them, *when* publishing behavior on the web for the *data* of such attributes exceeds the required 80/20 usage per microformats process. That being said, if you really must include arbitrary property-value data, there is already a microformat for that: [[xoxo]]. Modularly include a [[xoxo]] child and that way the extension is contained in a specific structure that can be ignored by implementations. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">

== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* There seem to be a great deal of vocab terms and the terms seem to be fairly loosely defined... are they all justified? Is there a file that we can analyze (like via microformalyze)?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>:The examples aren't necessarily an accurate reflection of how frequently attributes/data is used by retailers. In practice, model/mpn is used much more frequently than dimensions, both for retailer websites as well as retailer submissions to search and shopping engines. Defer to those with more experience/other data on version.
* +1. If you cannot justify a property, or are unsure about including it, or don't think it is necessarily an accurate reflection of how frequently the data is used, then leave it out per microformats [[principles]]. A "version" property was added to [[hReview]] for largely theoretical concerns, but has never been needed/used. So in practice (per experience), leave out "version". [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: I agree on both fronts here, I was surprised that model wasn't more prevalent in the research data, as it seems like an attribute that appears on nearly every product. Since "model" is often used as a type of identifier, it should be moved under the identifier attribute. "Version" will be taken out.
</div>
</div>

== Template ==
{{issues-format}}

== Resolved Issues ==

== Closed Issues ==

hproduct-issues

2009-04-24T17:00:57Z

JayMyers: adding more templates

__TOC__

== HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields ==

<div class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-12-17</span> raised by <span class="fn">NicolasLeroy</span></span>
<div class="description">
*# In the "[[hproduct#Out_of_Scope|out of scope]]" section, it is explained: _"This microformat does not intend to replicate any of the content proposed within hListing and would defer all money/transactional matters to that microformat"_
*# However, in the hProduct schema, we have the following fields:
*#* "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
*#* I would say there is also ambiguity between the responsibilities of hProduct vs hListing for the following fields: quantity / shipping
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I believe everyone agrees that we would borrow price from hListing for hProduct spec. I will explain the concept further in the schema.
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I don't follow the quantity/ shipping issue. I don't see either of these on hListing, unless the concepts are somehow embedded in other attributes. Can you elaborate on what the ambiguity is? ([[User:PaulLee|Paul Lee]]: If there's no objection here, may I suggest updating the price reference and keeping quantity and shipping as is?])
*#* +1 I agree with NicholasLeroy, anything price or transaction related should be left out of hProduct 0.1, and instead develop recipes / mark-up examples showing use of hListing with hProduct. We need to strongly resist and fight the tendency to include "just one more field" to individual formats and instead push to use formats as building blocks. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: If price should be left to hListing, should hAudio be modified not to include "price"?
*#* I am going to add price back into the hProduct spec. Price is an attribute of a product. We should be able to use microformats either standalone or as building blocks in combination with other formats. On price I'm thinking specifically of product manufacturer sites who may not be commerce enabled and are listing their products for informational purposes. In this case, they would not be using hListing, as there would be no transaction taking place. Leaving the price attribute out would ignore a major product attribute (in 99% of product sites, per hproduct examples analysis).
</div>
</div>

<div class="vevent">

== <span class="summary">HP2 - FN should be used instead of N for product title</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Why is <b>n</b> used instead of <b>fn</b> for the title of the product? hCard and hAudio both use fn for the formatted name of the product. <b>n</b> is usually an optimization.
* +1 hProduct should use "fn" for the name of the product. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: "n" will be changed to "fn" in the next version of the schema
* "fn" is hardly semantic, even though commonly deployed - surely "formatted-name" is truer to the principles of "humans-first, machines second" --[[User:Wowitim|Wowitim]] 12:59, 28 March 2009 (UTC)
</div>

<div class="vevent">

== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{OpenIssue}} <span class="vcard">BUY duplicates functionality of PAYMENT from hAudio<span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>buy</b> is duplicating the functionality of <b>payment</b> from hAudio.
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: From the payment page: "RelPayment is a microformat for making exchanges of support (be it financial or otherwise) possible. By adding rel="payment" to a hyperlink a page indicates that the destination of that hyperlink provides a way to show or give support for the current page. For example to give financial support to the owner of the current page. One of the goals with this microformat is to give content aggregators such as RSS readers a way to extract these support links and give them special attention (such as displaying a standard button along with the content)." First, this seems like a simple exercise for blogs, etc.; but the transaction process for shopping sites is typically considerably more complex. Usually, the actual payment URI is toward the end of the cart checkout process, the entry to which "buy" is intended to direct to the beginning of. Second, there is the potential for confusion when using payment, since "payment" in the shopping space often refers to payment methods, e.g., credit card, check, etc.
* +1 but in a different way. BUY/PAYMENT should both be out of scope for hProduct, and only be in hListing per issue HP1 above. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should these be in scope for hAudio then?
</div>
</div>

<div class="vevent">

== <span class="summary">HP4 - Are all of the formats for PRICE in hProduct allowed</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* The way that <b>price</b> is used is iffy - do we allow anything but currency/amount in the compound statement?
* +1 PRICE should not be in hProduct per issue HP1. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should other microformats (thinking hAudio) be modified not to include "price"?
</div>
</div>

<div class="vevent">

== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Seems like <b>shipping</b> could be abused quite a bit, resulting in a term that is fairly useless as time moves on.
* +1 agreed and I think SHIPPING belongs in hListing (not in hProduct) as it applies to a particular transaction/offering, and is not intrinsic to the product itself. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>p-v</b> seems like a catch-all, shoe-horn attempt at making the microformat infinitely scalable? Is this really useful?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: IIUC, part of the reason why hproduct has been under discussion for quite awhile is b/c of the debate between p-v vs. more defined attributes. p-v is quite helpful b/c the attributes users care about change over time. Take cameras, for instance. Did anyone care about megapixels 10 years ago? etc.
* +1 I strongly oppose p-v as it is nothing more than a circumvention of the microformats [[process]] and 80/20 [[principle]] of formalizing only common properties. [[microformats]] are NOT designed to be infinitely extensible. p-v is simply another source of Tower of Babel problems. When attributes change over time, then the microformat can be iterated/extended to include them, *when* publishing behavior on the web for the *data* of such attributes exceeds the required 80/20 usage per microformats process. That being said, if you really must include arbitrary property-value data, there is already a microformat for that: [[xoxo]]. Modularly include a [[xoxo]] child and that way the extension is contained in a specific structure that can be ignored by implementations. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">

== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* There seem to be a great deal of vocab terms and the terms seem to be fairly loosely defined... are they all justified? Is there a file that we can analyze (like via microformalyze)?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>:The examples aren't necessarily an accurate reflection of how frequently attributes/data is used by retailers. In practice, model/mpn is used much more frequently than dimensions, both for retailer websites as well as retailer submissions to search and shopping engines. Defer to those with more experience/other data on version.
* +1. If you cannot justify a property, or are unsure about including it, or don't think it is necessarily an accurate reflection of how frequently the data is used, then leave it out per microformats [[principles]]. A "version" property was added to [[hReview]] for largely theoretical concerns, but has never been needed/used. So in practice (per experience), leave out "version". [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: I agree on both fronts here, I was surprised that model wasn't more prevalent in the research data, as it seems like an attribute that appears on nearly every product. Since "model" is often used as a type of identifier, it should be moved under the identifier attribute. "Version" will be taken out.
</div>
</div>

== Template ==
{{issues-format}}

== Resolved Issues ==

== Closed Issues ==

== Related Pages ==

hproduct

2009-04-24T16:58:22Z

JayMyers: updating to draft v 0.3

<entry-title>hProduct</entry-title>
{{DraftSpecification}}
__TOC__
hProduct is a microformat suitable for publishing and embedding product data. hProduct is one of several open microformats standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

==hProduct Microformat Draft Specification==

; Editors/Authors
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

; Contributors
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

== Status ==
Draft, version 0.3.

== Introduction ==
The web is a thriving consumer marketplace with a plethora of manufacturers and vendors scattered across the globe. Sifting through massive amounts of unstructured product data is a difficult task for both browsers and machines alike. The hProduct microformat gives structure to this metadata by providing constructs to identify universal product attributes, plus a mechanism to accomodate the wide variation in product attributes.

The hProduct microformat can assist consumers, manufacturers and retailers in a number of ways. If a browser or application understands that a specific web page contains the hProduct microformat, it can inform and help facilitate the best product choice by the consumer to fulfill their needs. An adpoted, open standard will ensure the correct product data is published between manufacturers and retailers, to the benefit of the consumer. Bringing order and structure to product data makes it easy for people and organizations to list the products and services they offer, and easy for web services to consume that product data for analysis and syndication.

=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

=== Inspiration and Acknowledgment ===
Many thanks go out to the contributors who laid the foundation for the current hProduct draft spec.

=== Scope ===
Giving details about a particular product is sometimes very complex as parameters are different for books and CDs than they are for iPods or cars. It should be very easy to mark up an item using hProduct and the syntax should be simple yet flexible enough for more advanced applications.

=== Out of Scope ===
This microformat does not intend to replicate any of the content proposed within [[hListing]] and would defer all money/transactional matters to that microformat. This microformat also does not attempt to specify a product ontology, or category-specific attributes; instead, it aims to create a framework to allow for flexible expression of both.

== Format ==
{{rfc-2119-intro}}

=== In General ===
The hProduct format is based on a set of fields common to numerous ecommerce sites and formats in use today on the web.

=== Schema ===
The hProduct schema consists of the following (see existing class names for reference):

*hproduct
** brand. optional. text. can also use [[hcard|hCard]] for manufacturer.
** category. optional. text. can also use rel-tag. re-used from [[hcard|hCard]].
** price. optional. floating point number. can use currency format.
** description. optional. text. can also include valid HTML markup. re-used from [[hreview|hReview]].
** fn. '''required.''' text. product name or title. re-used from [[hcard|hCard]].
** photo. optional. image element or link. re-used from [[hcard|hCard]].
** url. optional. href. can contain rel-tag rel='product'. re-used from [[hcard|hCard]].
** review. optional. [[hreview|hReview]], or [[aggregate-microformat-template-examples|hReview-aggregate]].
** listing. optional. [[hlisting|hListing]], or [[aggregate-microformat-template-examples|hListing-aggregate]].
** identifier. optional.
*** type. required. - examples:
**** model
**** mpn
**** upc
**** isbn
**** issn
**** ean
**** jan
**** sn
**** vin
**** sku
*** value. required. - label may be implied

=== Field details ===
Class names <code class="class-name">category</code>, <code class="class-name">fn</code>, <code class="class-name">photo</code>, <code class="class-name">url</code> are reused from [[hcard|hCard]]. <code class="class-name">description</code> is reused from [[hreview|hReview]].

The fields of the hProduct schema represent the following:

*'''<code class="class-name">hproduct::</code>''' Root class name
*'''<code class="class-name">brand::</code>''' the class name brand is used identify brand of the product. {{should}} use [[hcard|hCard]] for manufacturer name. {{must}} be singular.
*'''<code class="class-name">category::</code>''' the class name category identifies product category. {{may}} use [[rel-tag]] microformat. {{may}} be plural to represent multiple categories.
*'''<code class="class-name">price::</code>''' the class name price is used to indicate the price of the product. {{must}} be singular.
*'''<code class="class-name">description::</code>''' the class name description is used to describe the product. {{must}} be singular.
*'''<code class="class-name">fn::</code>''' product text name. {{must}} be singular.
*'''<code class="class-name">photo::</code>''' the class name photo {{may}} be applied to an <img> or <a> element. {{may}} be plural.
*'''<code class="class-name">url::</code>''' the class name url {{should}} refer to the web page associated with product details. {{may}} use [[rel-tag]], rel='product'. {{must}} be singular.
*'''<code class="class-name">review::</code>''' the class name review identifies review(s) for the product. {{should}} use [[hreview|hReview]]. {{may}} be plural.
*'''<code class="class-name">listing::</code>''' the class name listing identifies product listings. {{should}} use [[hlisting|hListing]]. {{may}} be plural.
*'''<code class="class-name">identifier::</code>''' the identifier structure is used to describe product identifiers like Model, UPC or SKU, and is designed to accommodate new or as-yet-unidentified identifiers. {{should}} be singular.
**'''<code class="class-name">type::</code>''' the class name type identifies the identifier type.
**'''<code class="class-name">value::</code>''' label {{may}} be implied

=== Additional Details ===
'''Note:''' If hProduct markup is used in a "standalone" fashion (eg. a manufacturer site that's not commerce enabled, strictly informational), it is assumed that the price attribute represents the manufacturer's suggested retail price. Any transactional (commerce) representation of price should be delegated to [[hlisting|hListing]].

''Internationalization'': Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. Note that (X)HTML LANG attribute rules still apply as usual, for multilingual aggregators of hProduct.

=== Relationships with other microformats ===
Products can be complex structures with attributes and features that may fall outside the bounds of the proposed hProduct microformat. Care has been taken to provide just enough attributes to accurately represent products while not overloading the hProduct spec. This means that complete semantic solutions would rely on using hProduct in combination with other microformats to achieve their goals. Through [[hproduct-examples#Coded_examples|examples]] (see also: [[hproduct-recipes|recipes]]) and [[hproduct-examples#Analysis_of_Product.2FCommerce_Sites|analysis]], there are some clear relationships between hProduct and these microformats:

* [[hlisting|hListing]] :: provides additional context to the transaction side of a product, including elements like the transactional price.
* [[hReview|hReview]]/hAggregate(concept) :: research shows that many commerce sites include product reviews, and they are often aggregated to provide overall ratings and reviews on the web. Utilizing these microformats can provide additional data around a product or service.
* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a product.

Of course, these are just a few of many that could be used with the hProduct microformat.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hproduct</dt>
<dd>Used to identify and describe metadata universally common to products.</dd>
<dt>brand</dt>
<dd>The brand name of the product.</dd>
<dt>category</dt>
<dd>The product category/ categories the product belongs to.</dd>
<dt>price</dt>
<dd>The price of the product.</dd>
<dt>description</dt>
<dd>The full text representing the written description of the product.</dd>
<dt>fn</dt>
<dd>The common name of the product.</dd>
<dt>photo</dt>
<dd>Accompanying image of the product.</dd>
<dt>url</dt>
<dd>A link to the product details.</dd>
<dt>review</dt>
<dd>A review of the product.</dd>
<dt>listing</dt>
<dd>Listing details of the product.</dd>
<dt>identifier</dt>
<dd>The product identifier like Model, SKU, ISBN, or EAN associated with the product</dd>
</dl>
</dd>
</dl>
</pre>

=== Notes ===
This section is informative.
*...

=== Other examples ===

Please see examples at [[hproduct-examples|hProduct examples]].

== Copyright ==
* [[User:JayMyers|JayMyers]]: I release all of my contributions to the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== Related ==
* '''hproduct'''
* [[hproduct-issues]]
* [[hproduct-faq]]
* [[hproduct-examples]]
* [[hproduct-recipes]]

* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

[[Category:Draft Specifications]]
[[Category:hProduct]]

hproduct

2009-04-24T16:57:51Z

JayMyers: deleting production examples, old

<entry-title>hProduct</entry-title>
{{DraftSpecification}}
__TOC__
hProduct is a microformat suitable for publishing and embedding product data. hProduct is one of several open microformats standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

==hProduct Microformat Draft Specification==

; Editors/Authors
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

; Contributors
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

== Status ==
Draft, version 0.2.

== Introduction ==
The web is a thriving consumer marketplace with a plethora of manufacturers and vendors scattered across the globe. Sifting through massive amounts of unstructured product data is a difficult task for both browsers and machines alike. The hProduct microformat gives structure to this metadata by providing constructs to identify universal product attributes, plus a mechanism to accomodate the wide variation in product attributes.

The hProduct microformat can assist consumers, manufacturers and retailers in a number of ways. If a browser or application understands that a specific web page contains the hProduct microformat, it can inform and help facilitate the best product choice by the consumer to fulfill their needs. An adpoted, open standard will ensure the correct product data is published between manufacturers and retailers, to the benefit of the consumer. Bringing order and structure to product data makes it easy for people and organizations to list the products and services they offer, and easy for web services to consume that product data for analysis and syndication.

=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

=== Inspiration and Acknowledgment ===
Many thanks go out to the contributors who laid the foundation for the current hProduct draft spec.

=== Scope ===
Giving details about a particular product is sometimes very complex as parameters are different for books and CDs than they are for iPods or cars. It should be very easy to mark up an item using hProduct and the syntax should be simple yet flexible enough for more advanced applications.

=== Out of Scope ===
This microformat does not intend to replicate any of the content proposed within [[hListing]] and would defer all money/transactional matters to that microformat. This microformat also does not attempt to specify a product ontology, or category-specific attributes; instead, it aims to create a framework to allow for flexible expression of both.

== Format ==
{{rfc-2119-intro}}

=== In General ===
The hProduct format is based on a set of fields common to numerous ecommerce sites and formats in use today on the web.

=== Schema ===
The hProduct schema consists of the following (see existing class names for reference):

*hproduct
** brand. optional. text. can also use [[hcard|hCard]] for manufacturer.
** category. optional. text. can also use rel-tag. re-used from [[hcard|hCard]].
** price. optional. floating point number. can use currency format.
** description. optional. text. can also include valid HTML markup. re-used from [[hreview|hReview]].
** fn. '''required.''' text. product name or title. re-used from [[hcard|hCard]].
** photo. optional. image element or link. re-used from [[hcard|hCard]].
** url. optional. href. can contain rel-tag rel='product'. re-used from [[hcard|hCard]].
** review. optional. [[hreview|hReview]], or [[aggregate-microformat-template-examples|hReview-aggregate]].
** listing. optional. [[hlisting|hListing]], or [[aggregate-microformat-template-examples|hListing-aggregate]].
** identifier. optional.
*** type. required. - examples:
**** model
**** mpn
**** upc
**** isbn
**** issn
**** ean
**** jan
**** sn
**** vin
**** sku
*** value. required. - label may be implied

=== Field details ===
Class names <code class="class-name">category</code>, <code class="class-name">fn</code>, <code class="class-name">photo</code>, <code class="class-name">url</code> are reused from [[hcard|hCard]]. <code class="class-name">description</code> is reused from [[hreview|hReview]].

The fields of the hProduct schema represent the following:

*'''<code class="class-name">hproduct::</code>''' Root class name
*'''<code class="class-name">brand::</code>''' the class name brand is used identify brand of the product. {{should}} use [[hcard|hCard]] for manufacturer name. {{must}} be singular.
*'''<code class="class-name">category::</code>''' the class name category identifies product category. {{may}} use [[rel-tag]] microformat. {{may}} be plural to represent multiple categories.
*'''<code class="class-name">price::</code>''' the class name price is used to indicate the price of the product. {{must}} be singular.
*'''<code class="class-name">description::</code>''' the class name description is used to describe the product. {{must}} be singular.
*'''<code class="class-name">fn::</code>''' product text name. {{must}} be singular.
*'''<code class="class-name">photo::</code>''' the class name photo {{may}} be applied to an <img> or <a> element. {{may}} be plural.
*'''<code class="class-name">url::</code>''' the class name url {{should}} refer to the web page associated with product details. {{may}} use [[rel-tag]], rel='product'. {{must}} be singular.
*'''<code class="class-name">review::</code>''' the class name review identifies review(s) for the product. {{should}} use [[hreview|hReview]]. {{may}} be plural.
*'''<code class="class-name">listing::</code>''' the class name listing identifies product listings. {{should}} use [[hlisting|hListing]]. {{may}} be plural.
*'''<code class="class-name">identifier::</code>''' the identifier structure is used to describe product identifiers like Model, UPC or SKU, and is designed to accommodate new or as-yet-unidentified identifiers. {{should}} be singular.
**'''<code class="class-name">type::</code>''' the class name type identifies the identifier type.
**'''<code class="class-name">value::</code>''' label {{may}} be implied

=== Additional Details ===
'''Note:''' If hProduct markup is used in a "standalone" fashion (eg. a manufacturer site that's not commerce enabled, strictly informational), it is assumed that the price attribute represents the manufacturer's suggested retail price. Any transactional (commerce) representation of price should be delegated to [[hlisting|hListing]].

''Internationalization'': Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. Note that (X)HTML LANG attribute rules still apply as usual, for multilingual aggregators of hProduct.

=== Relationships with other microformats ===
Products can be complex structures with attributes and features that may fall outside the bounds of the proposed hProduct microformat. Care has been taken to provide just enough attributes to accurately represent products while not overloading the hProduct spec. This means that complete semantic solutions would rely on using hProduct in combination with other microformats to achieve their goals. Through [[hproduct-examples#Coded_examples|examples]] (see also: [[hproduct-recipes|recipes]]) and [[hproduct-examples#Analysis_of_Product.2FCommerce_Sites|analysis]], there are some clear relationships between hProduct and these microformats:

* [[hlisting|hListing]] :: provides additional context to the transaction side of a product, including elements like the transactional price.
* [[hReview|hReview]]/hAggregate(concept) :: research shows that many commerce sites include product reviews, and they are often aggregated to provide overall ratings and reviews on the web. Utilizing these microformats can provide additional data around a product or service.
* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a product.

Of course, these are just a few of many that could be used with the hProduct microformat.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hproduct</dt>
<dd>Used to identify and describe metadata universally common to products.</dd>
<dt>brand</dt>
<dd>The brand name of the product.</dd>
<dt>category</dt>
<dd>The product category/ categories the product belongs to.</dd>
<dt>price</dt>
<dd>The price of the product.</dd>
<dt>description</dt>
<dd>The full text representing the written description of the product.</dd>
<dt>fn</dt>
<dd>The common name of the product.</dd>
<dt>photo</dt>
<dd>Accompanying image of the product.</dd>
<dt>url</dt>
<dd>A link to the product details.</dd>
<dt>review</dt>
<dd>A review of the product.</dd>
<dt>listing</dt>
<dd>Listing details of the product.</dd>
<dt>identifier</dt>
<dd>The product identifier like Model, SKU, ISBN, or EAN associated with the product</dd>
</dl>
</dd>
</dl>
</pre>

=== Notes ===
This section is informative.
*...

=== Other examples ===

Please see examples at [[hproduct-examples|hProduct examples]].

== Copyright ==
* [[User:JayMyers|JayMyers]]: I release all of my contributions to the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== Related ==
* '''hproduct'''
* [[hproduct-issues]]
* [[hproduct-faq]]
* [[hproduct-examples]]
* [[hproduct-recipes]]

* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

[[Category:Draft Specifications]]
[[Category:hProduct]]

hproduct

2009-04-24T16:57:19Z

JayMyers: adding transactional price stipulation

<entry-title>hProduct</entry-title>
{{DraftSpecification}}
__TOC__
hProduct is a microformat suitable for publishing and embedding product data. hProduct is one of several open microformats standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

==hProduct Microformat Draft Specification==

; Editors/Authors
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

; Contributors
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

== Status ==
Draft, version 0.2.

== Introduction ==
The web is a thriving consumer marketplace with a plethora of manufacturers and vendors scattered across the globe. Sifting through massive amounts of unstructured product data is a difficult task for both browsers and machines alike. The hProduct microformat gives structure to this metadata by providing constructs to identify universal product attributes, plus a mechanism to accomodate the wide variation in product attributes.

The hProduct microformat can assist consumers, manufacturers and retailers in a number of ways. If a browser or application understands that a specific web page contains the hProduct microformat, it can inform and help facilitate the best product choice by the consumer to fulfill their needs. An adpoted, open standard will ensure the correct product data is published between manufacturers and retailers, to the benefit of the consumer. Bringing order and structure to product data makes it easy for people and organizations to list the products and services they offer, and easy for web services to consume that product data for analysis and syndication.

=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

=== Inspiration and Acknowledgment ===
Many thanks go out to the contributors who laid the foundation for the current hProduct draft spec.

=== Scope ===
Giving details about a particular product is sometimes very complex as parameters are different for books and CDs than they are for iPods or cars. It should be very easy to mark up an item using hProduct and the syntax should be simple yet flexible enough for more advanced applications.

=== Out of Scope ===
This microformat does not intend to replicate any of the content proposed within [[hListing]] and would defer all money/transactional matters to that microformat. This microformat also does not attempt to specify a product ontology, or category-specific attributes; instead, it aims to create a framework to allow for flexible expression of both.

== Format ==
{{rfc-2119-intro}}

=== In General ===
The hProduct format is based on a set of fields common to numerous ecommerce sites and formats in use today on the web.

=== Schema ===
The hProduct schema consists of the following (see existing class names for reference):

*hproduct
** brand. optional. text. can also use [[hcard|hCard]] for manufacturer.
** category. optional. text. can also use rel-tag. re-used from [[hcard|hCard]].
** price. optional. floating point number. can use currency format.
** description. optional. text. can also include valid HTML markup. re-used from [[hreview|hReview]].
** fn. '''required.''' text. product name or title. re-used from [[hcard|hCard]].
** photo. optional. image element or link. re-used from [[hcard|hCard]].
** url. optional. href. can contain rel-tag rel='product'. re-used from [[hcard|hCard]].
** review. optional. [[hreview|hReview]], or [[aggregate-microformat-template-examples|hReview-aggregate]].
** listing. optional. [[hlisting|hListing]], or [[aggregate-microformat-template-examples|hListing-aggregate]].
** identifier. optional.
*** type. required. - examples:
**** model
**** mpn
**** upc
**** isbn
**** issn
**** ean
**** jan
**** sn
**** vin
**** sku
*** value. required. - label may be implied

=== Field details ===
Class names <code class="class-name">category</code>, <code class="class-name">fn</code>, <code class="class-name">photo</code>, <code class="class-name">url</code> are reused from [[hcard|hCard]]. <code class="class-name">description</code> is reused from [[hreview|hReview]].

The fields of the hProduct schema represent the following:

*'''<code class="class-name">hproduct::</code>''' Root class name
*'''<code class="class-name">brand::</code>''' the class name brand is used identify brand of the product. {{should}} use [[hcard|hCard]] for manufacturer name. {{must}} be singular.
*'''<code class="class-name">category::</code>''' the class name category identifies product category. {{may}} use [[rel-tag]] microformat. {{may}} be plural to represent multiple categories.
*'''<code class="class-name">price::</code>''' the class name price is used to indicate the price of the product. {{must}} be singular.
*'''<code class="class-name">description::</code>''' the class name description is used to describe the product. {{must}} be singular.
*'''<code class="class-name">fn::</code>''' product text name. {{must}} be singular.
*'''<code class="class-name">photo::</code>''' the class name photo {{may}} be applied to an <img> or <a> element. {{may}} be plural.
*'''<code class="class-name">url::</code>''' the class name url {{should}} refer to the web page associated with product details. {{may}} use [[rel-tag]], rel='product'. {{must}} be singular.
*'''<code class="class-name">review::</code>''' the class name review identifies review(s) for the product. {{should}} use [[hreview|hReview]]. {{may}} be plural.
*'''<code class="class-name">listing::</code>''' the class name listing identifies product listings. {{should}} use [[hlisting|hListing]]. {{may}} be plural.
*'''<code class="class-name">identifier::</code>''' the identifier structure is used to describe product identifiers like Model, UPC or SKU, and is designed to accommodate new or as-yet-unidentified identifiers. {{should}} be singular.
**'''<code class="class-name">type::</code>''' the class name type identifies the identifier type.
**'''<code class="class-name">value::</code>''' label {{may}} be implied

=== Additional Details ===
'''Note:''' If hProduct markup is used in a "standalone" fashion (eg. a manufacturer site that's not commerce enabled, strictly informational), it is assumed that the price attribute represents the manufacturer's suggested retail price. Any transactional (commerce) representation of price should be delegated to [[hlisting|hListing]].

''Internationalization'': Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. Note that (X)HTML LANG attribute rules still apply as usual, for multilingual aggregators of hProduct.

=== Relationships with other microformats ===
Products can be complex structures with attributes and features that may fall outside the bounds of the proposed hProduct microformat. Care has been taken to provide just enough attributes to accurately represent products while not overloading the hProduct spec. This means that complete semantic solutions would rely on using hProduct in combination with other microformats to achieve their goals. Through [[hproduct-examples#Coded_examples|examples]] (see also: [[hproduct-recipes|recipes]]) and [[hproduct-examples#Analysis_of_Product.2FCommerce_Sites|analysis]], there are some clear relationships between hProduct and these microformats:

* [[hlisting|hListing]] :: provides additional context to the transaction side of a product, including elements like the transactional price.
* [[hReview|hReview]]/hAggregate(concept) :: research shows that many commerce sites include product reviews, and they are often aggregated to provide overall ratings and reviews on the web. Utilizing these microformats can provide additional data around a product or service.
* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a product.

Of course, these are just a few of many that could be used with the hProduct microformat.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hproduct</dt>
<dd>Used to identify and describe metadata universally common to products.</dd>
<dt>brand</dt>
<dd>The brand name of the product.</dd>
<dt>category</dt>
<dd>The product category/ categories the product belongs to.</dd>
<dt>price</dt>
<dd>The price of the product.</dd>
<dt>description</dt>
<dd>The full text representing the written description of the product.</dd>
<dt>fn</dt>
<dd>The common name of the product.</dd>
<dt>photo</dt>
<dd>Accompanying image of the product.</dd>
<dt>url</dt>
<dd>A link to the product details.</dd>
<dt>review</dt>
<dd>A review of the product.</dd>
<dt>listing</dt>
<dd>Listing details of the product.</dd>
<dt>identifier</dt>
<dd>The product identifier like Model, SKU, ISBN, or EAN associated with the product</dd>
</dl>
</dd>
</dl>
</pre>

=== Notes ===
This section is informative.
*...

=== Examples in Production ===
* Description of [http://jay.beweep.com/index.php/2008/10/14/reviving-shop-urls-with-hproduct BestBuy.com implementation]

=== Other examples ===

Please see examples at [[hproduct-examples|hProduct examples]].

== Copyright ==
* [[User:JayMyers|JayMyers]]: I release all of my contributions to the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== Related ==
* '''hproduct'''
* [[hproduct-issues]]
* [[hproduct-faq]]
* [[hproduct-examples]]
* [[hproduct-recipes]]

* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

[[Category:Draft Specifications]]
[[Category:hProduct]]

hproduct

2009-04-24T16:53:35Z

JayMyers: adding additional data points to profile

<entry-title>hProduct</entry-title>
{{DraftSpecification}}
__TOC__
hProduct is a microformat suitable for publishing and embedding product data. hProduct is one of several open microformats standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

==hProduct Microformat Draft Specification==

; Editors/Authors
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

; Contributors
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

== Status ==
Draft, version 0.2.

== Introduction ==
The web is a thriving consumer marketplace with a plethora of manufacturers and vendors scattered across the globe. Sifting through massive amounts of unstructured product data is a difficult task for both browsers and machines alike. The hProduct microformat gives structure to this metadata by providing constructs to identify universal product attributes, plus a mechanism to accomodate the wide variation in product attributes.

The hProduct microformat can assist consumers, manufacturers and retailers in a number of ways. If a browser or application understands that a specific web page contains the hProduct microformat, it can inform and help facilitate the best product choice by the consumer to fulfill their needs. An adpoted, open standard will ensure the correct product data is published between manufacturers and retailers, to the benefit of the consumer. Bringing order and structure to product data makes it easy for people and organizations to list the products and services they offer, and easy for web services to consume that product data for analysis and syndication.

=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

=== Inspiration and Acknowledgment ===
Many thanks go out to the contributors who laid the foundation for the current hProduct draft spec.

=== Scope ===
Giving details about a particular product is sometimes very complex as parameters are different for books and CDs than they are for iPods or cars. It should be very easy to mark up an item using hProduct and the syntax should be simple yet flexible enough for more advanced applications.

=== Out of Scope ===
This microformat does not intend to replicate any of the content proposed within [[hListing]] and would defer all money/transactional matters to that microformat. This microformat also does not attempt to specify a product ontology, or category-specific attributes; instead, it aims to create a framework to allow for flexible expression of both.

== Format ==
{{rfc-2119-intro}}

=== In General ===
The hProduct format is based on a set of fields common to numerous ecommerce sites and formats in use today on the web.

=== Schema ===
The hProduct schema consists of the following (see existing class names for reference):

*hproduct
** brand. optional. text. can also use [[hcard|hCard]] for manufacturer.
** category. optional. text. can also use rel-tag. re-used from [[hcard|hCard]].
** price. optional. floating point number. can use currency format.
** description. optional. text. can also include valid HTML markup. re-used from [[hreview|hReview]].
** fn. '''required.''' text. product name or title. re-used from [[hcard|hCard]].
** photo. optional. image element or link. re-used from [[hcard|hCard]].
** url. optional. href. can contain rel-tag rel='product'. re-used from [[hcard|hCard]].
** review. optional. [[hreview|hReview]], or [[aggregate-microformat-template-examples|hReview-aggregate]].
** listing. optional. [[hlisting|hListing]], or [[aggregate-microformat-template-examples|hListing-aggregate]].
** identifier. optional.
*** type. required. - examples:
**** model
**** mpn
**** upc
**** isbn
**** issn
**** ean
**** jan
**** sn
**** vin
**** sku
*** value. required. - label may be implied

=== Field details ===
Class names <code class="class-name">category</code>, <code class="class-name">fn</code>, <code class="class-name">photo</code>, <code class="class-name">url</code> are reused from [[hcard|hCard]]. <code class="class-name">description</code> is reused from [[hreview|hReview]].

The fields of the hProduct schema represent the following:

*'''<code class="class-name">hproduct::</code>''' Root class name
*'''<code class="class-name">brand::</code>''' the class name brand is used identify brand of the product. {{should}} use [[hcard|hCard]] for manufacturer name. {{must}} be singular.
*'''<code class="class-name">category::</code>''' the class name category identifies product category. {{may}} use [[rel-tag]] microformat. {{may}} be plural to represent multiple categories.
*'''<code class="class-name">price::</code>''' the class name price is used to indicate the price of the product. {{must}} be singular.
*'''<code class="class-name">description::</code>''' the class name description is used to describe the product. {{must}} be singular.
*'''<code class="class-name">fn::</code>''' product text name. {{must}} be singular.
*'''<code class="class-name">photo::</code>''' the class name photo {{may}} be applied to an <img> or <a> element. {{may}} be plural.
*'''<code class="class-name">url::</code>''' the class name url {{should}} refer to the web page associated with product details. {{may}} use [[rel-tag]], rel='product'. {{must}} be singular.
*'''<code class="class-name">review::</code>''' the class name review identifies review(s) for the product. {{should}} use [[hreview|hReview]]. {{may}} be plural.
*'''<code class="class-name">listing::</code>''' the class name listing identifies product listings. {{should}} use [[hlisting|hListing]]. {{may}} be plural.
*'''<code class="class-name">identifier::</code>''' the identifier structure is used to describe product identifiers like Model, UPC or SKU, and is designed to accommodate new or as-yet-unidentified identifiers. {{should}} be singular.
**'''<code class="class-name">type::</code>''' the class name type identifies the identifier type.
**'''<code class="class-name">value::</code>''' label {{may}} be implied

=== Additional Details ===
'''Note:''' If hProduct markup is used in a "standalone" fashion (eg. a manufacturer site that's not commerce enabled, strictly informational), it is assumed that the price attribute represents the manufacturer's suggested retail price. Any transactional (commerce) representation of price should be delegated to [[hlisting|hListing]].

''Internationalization'': Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. Note that (X)HTML LANG attribute rules still apply as usual, for multilingual aggregators of hProduct.

=== Relationships with other microformats ===
Products can be complex structures with attributes and features that may fall outside the bounds of the proposed hProduct microformat. Care has been taken to provide just enough attributes to accurately represent products while not overloading the hProduct spec. This means that complete semantic solutions would rely on using hProduct in combination with other microformats to achieve their goals. Through [[hproduct-examples#Coded_examples|examples]] (see also: [[hproduct-recipes|recipes]]) and [[hproduct-examples#Analysis_of_Product.2FCommerce_Sites|analysis]], there are some clear relationships between hProduct and these microformats:

* [[hlisting|hListing]] :: provides additional context to the transaction side of a product, including crucial elements like "price".
* [[hReview|hReview]]/hAggregate(concept) :: research shows that many commerce sites include product reviews, and they are often aggregated to provide overall ratings and reviews on the web. Utilizing these microformats can provide additional data around a product or service.
* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a product.

Of course, these are just a few of many that could be used with the hProduct microformat.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hproduct</dt>
<dd>Used to identify and describe metadata universally common to products.</dd>
<dt>brand</dt>
<dd>The brand name of the product.</dd>
<dt>category</dt>
<dd>The product category/ categories the product belongs to.</dd>
<dt>price</dt>
<dd>The price of the product.</dd>
<dt>description</dt>
<dd>The full text representing the written description of the product.</dd>
<dt>fn</dt>
<dd>The common name of the product.</dd>
<dt>photo</dt>
<dd>Accompanying image of the product.</dd>
<dt>url</dt>
<dd>A link to the product details.</dd>
<dt>review</dt>
<dd>A review of the product.</dd>
<dt>listing</dt>
<dd>Listing details of the product.</dd>
<dt>identifier</dt>
<dd>The product identifier like Model, SKU, ISBN, or EAN associated with the product</dd>
</dl>
</dd>
</dl>
</pre>

=== Notes ===
This section is informative.
*...

=== Examples in Production ===
* Description of [http://jay.beweep.com/index.php/2008/10/14/reviving-shop-urls-with-hproduct BestBuy.com implementation]

=== Other examples ===

Please see examples at [[hproduct-examples|hProduct examples]].

== Copyright ==
* [[User:JayMyers|JayMyers]]: I release all of my contributions to the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== Related ==
* '''hproduct'''
* [[hproduct-issues]]
* [[hproduct-faq]]
* [[hproduct-examples]]
* [[hproduct-recipes]]

* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

[[Category:Draft Specifications]]
[[Category:hProduct]]

hproduct-examples-in-wild

2009-04-24T16:48:50Z

JayMyers: editing analysis results based off of new data

<h1> Product Examples </h1>
{{TOC-right}}

This page is '''informative'''.

The purpose of the studies on this page is to serve as background for the design of a simple distributed product microformat. There are limited number of examples in the wild, but this page can serve as a base for experimentation and implementation.

== Editors/Authors ==
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

== Contributors ==
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

== New Examples ==
If you have implemented hProduct on your own page, feel free to add it to the '''top''' of this list. Please be sure to include at least one URL to a page on your site that includes actual [[hproduct|hProduct]] markup.

== Examples ==

=== Experimental Live hProduct Examples ===
See bestbuy.com's experimental hProduct implementation (pre-draft) on "Shop URLs" at:
<nowiki>http://www.bestbuy.com/shop/</nowiki>''term'', or more information here: [http://jay.beweep.com/index.php/2008/10/14/reviving-shop-urls-with-hproduct/ Shop URL details]
Karniyarik.com [http://www.karniyarik.com/karniyarik-web]is a vertical search engine for online goods and experimented hProduct.

=== See Also ===
(Note: See [[hlisting-extended-examples|hlisting-extended-examples]] also for examples of products listed on classified services.--[[PaulLee|Paul Lee]] 21:24 20 Aug 2008)

=== Live Product Examples ===

* [http://tinyurl.com/7p6h4l BlueNile]
** Product type: Jewelry > Bracelets
** Properties: categories, name, description, product rating, photo, price, order info, shipping information, stock number, metal type, clasp type, width, weight, add to basket, reviews

* [http://www.petco.com/product/14363/Totally-Ferret-Premium-Food-for-Active-Show-and-Pet-Ferrets.aspx Petco]
** Product type: Ferrets > Ferret food
** Properties: photo, name, brand/ manufacturer, description, product rating, reviews, weight, sku, shipping, internet price, sale price, quantity, add to cart, category, warranty, analysis, directions

* [http://www.allposters.com/gallery.asp?startat=/getposter.asp&APNum=290796&CID=AC3917B0E4E4452CBC36B60F9B66A923&PPID=1&search=matisse&f=c&FindID=26501&P=1&PP=13&sortby=PD&cname=Henri+Matisse&SearchID allposters.com]
** Product type: Artwork > Prints
** Properties: photo, title, artist, type, size, item number, shipping, price, add to cart, custom frame, additional services, description

* [http://www.target.com/Britax-Decathlon-Sahara-Convertible-Seat/dp/B000JIWU4W/sr=1-1/qid=1230579365/ref=sr_1_1/179-9254632-8007737?ie=UTF8&rh=k%3Atoddler%20car%20seats%20britax&page=1 target.com]
** Product type: Baby & Toddler > Toddler car seat
** Properties: photo, shipping, brand, title, price, guest rating, quantity, add to cart, add to list(s), availability, features, reviews, identifiers (dpci, asin, catalog number), height, width, depth

* [http://www.uniformadvantage.com/pages/prod/0445.asp?frmcolor=NAVY uniformadvantage.com]
** Product type: Business & Industrial > Medical > Medical Scrubs
** Properties: name, style number, brand, photo, description, price, color, size, quantity, add to cart

* [http://freewheelbike.com/itemdetails.cfm?LibId=45397 freewheelbike.com]
** Product type: Sporting Goods > Bicycles
** Properties: categories, photo, brand, name, price, product rating, description, features (click-through/pop-up), color, size, add to cart, add and checkout, add to wish list

* [http://www.fastforklifts.com/electric-forklift-trucks-electric-forklift-walkie-forklift-xp1229-12.html fastforklifts.com]
** Product type: Industrial Equipment > Forklifts
** Properties: photo, name, product id, manufacturer, price, sale price, savings, quantity, add to cart, category, description

* [http://www.leotardworld.com/Wiggles-Sparkle-Butterfly-Back-Leotard-p/mw1425-356h.htm leotardworld.com]
** Product type: Clothing & Accessories > Leotards
** Properties: categories, name, brand, photo, price, sale price, you save, size, status, product code, quantity, add to cart, add to wish list, description, review

* [http://www.gap.com/browse/product.do?cid=40772&pid=405608&scid=405608002 gap.com]
** Product type: Clothing & Accessories > Men's Blazers
** Properties: photo, name, description, size, color, sku, quantity, price, sale price, add to bag, product details

* [http://www.amazon.com/Nikon-Coolpix-Digital-Camera-Optical/dp/B0011MVWZ8/ref=pd_bbs_sr_1?ie=UTF8&s=electronics&qid=1231272206&sr=8-1 amazon.com]
** Product type: Electronics > Cameras
** Properties: photo, name, brand/manufacturer, reviews, colors, price, availability, shipping, quantity, add to cart, related, product details, product dimentions, weight, asin, model number, sales rank, categories, description, tags, reviews, discussions

* [http://shop.lundsandbyerlys.com/shopping.aspx?location=E&sublocation=LP&shoplistid=336 lundsandbyerlys.com(frames, maui bento sushi chosen as example)]
** Product type: Food Items > Sushi
** Properties: on sale, photo, name, serving size, quantity, price, sale price, savings, add to basket

* [http://www1.macys.com/catalog/product/index.ognc?ID=290741&CategoryID=42212 macys.com]
** Product type: Furniture > Living Room Sets
** Properties: photo (flash), name, brand, description, details, shipping, returns, product rating, colors, related, height, width, depth, product features, warranty info, web id, price, reviews

* [http://www.lowes.com/lowes/lkn?action=productDetail&productId=132135-444-C14024A&lpage=none lowes.com]
** Product type: Household Hardware > Vanity
** Properties: photo, name, manufacturer/brand, item number, model, price, add to cart, availability, shipping, description, total width, total depth, total height, top width, top depth, color, series, assembly, number drawers, construction type, mount type, reviews

* [http://www.homedepot.com/webapp/wcs/stores/servlet/ProductDisplay?storeId=10051&langId=-1&catalogId=10053&productId=100189145 homedepot.com]
** Product type: Hardware > Sump Pump
** Properties: photo, name, model, brand, price, quantity, add to cart, add to list, add to registry, product rating, description, model number, part number, features, specifications, ada compliant, amperage, depth, height, weight, width, battery backup, cord length, energy star, horsepower, length, outlet connection, outlet dimension, switch type, voltage, reviews, warranty

* [http://www.acehardware.com/product/index.jsp?productId=1290429&cp=&sr=1&kw=lathes&origkw=lathes&parentPage=search&searchId=34784674863 acehardware.com]
** Product type: Hardware > Lath Screws
** Properties: photo, name, product rating, price, rewards points, shipping, categories, color, size, quantity, add to cart, add to wish list, related, availability, product details: head type, size, material, reviews

* [http://www.walgreens.com/store/product.jsp?CATID=100218&navAction=jump&navCount=0&nug=VPD&skuid=sku359744&id=prod359743 walgreens.com]
** Product type: Health & Beauty > Ear Wax Removal
** Properties: categories, photo, price, quantity, name, brand, size/count, add to cart, shipping, availability, product rating, description, reviews

* [http://www.appliancewarehousedirect.com/counterdepth-sidebyside-refrigerator-with-glass-shelves-humidity-controls-transition-lighting-external-button-icewater-dispenser-p-18476.html?cPath=3 appliancewarehousedirect.com]
** Product type: Home & Garden > Refrigerators
** Properties: name, width, weight, depth, height, sku, brand, model, price, add to cart, shipping, warranty, photo, description, condition, packaging, features

* [http://www.birdbaths.com/bird-baths/resin-bird-baths/portsmouthsolarbirdbathfountain.cfm birdbaths.com]
** Product type: Home & Garden > Bird Baths
** Properties: photo, categories, name, brand, item number, regular price, sale price, savings, length, width, height, warranty, product rating, shipping, related, description, material, style, water sound, light, series, assembly, warranty, exchange, reviews

* [http://www.bagking.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=FN1200N&Category_Code=womens-fannypacks&Product_Count bagking.com]
** Product type: Luggage > Fanny Packs
** Properties: name, brand, photo, product code, price, weight, shipping, color, quantity, add to cart, description, features, warranty, width, height, depth

* [http://www.magersandquinn.com/index.php?main_page=product_info&products_id=1905787&isbn_id=4027890 magersandquinn.com]
** Product type: Media > Books
** Properties: categories, photo, name, author, condition, isbn, contributor, publisher, publish date, pages, weight, height, width, depth, language, description, sale price, regular price, availability, add to cart

* [http://www.bestbuy.com/site/olspage.jsp?skuId=9015638&type=product&id=1852883 bestbuy.com]
** Product type: Media > DVD > Bluray
** Properties: categories, photo, name, sku, release date, mpaa rating, product rating, shipping, availability, offers, list price, regular price, add to cart, add to wish list, print, format, release date, length, genre, studio, other formats, description, language, subtitles, additional features, cast & crew, reviews

* [http://www.cduniverse.com/productinfo.asp?pid=1109198&cart=827546365 cduniverse.com]
** Product type: Media > CDs
** Properties: photo, name, artist, product rating, regular price, price, shipping, add to cart, description, list price, categories, label, release year, part number, catalog number, number of discs, recording length, track name(s), reviews

* [http://www.cars.com/go/search/detail.jsp;?tracktype=usedcc&searchType=21&pageNumber=0&numResultsPerPage=50&largeNumResultsPerPage=0&sortorder=descending&sortfield=PRICE+descending&certifiedOnly=false&criteria=K-|E-|M-_563_|N-N|R-10000|I-1%2c7|P-PRICE+descending|Q-descending|Z-55428&aff=national&paId=298456384&recnum=0&leadExists=true cars.com]
** Product type: Motor Vehicles > Cars
** Properties: photo, name, brand, mileage, body style, color, engine, transmission, drivetrain, doors, features, description, condition, listing source, reviews, seller, related, warranty

* [http://www.autozone.com/selectedZip,55423/initialAction,partProductDetail/initialpartType,01233/initialR,1855279/initialvehicleId,2401601/shopping/selectZip.htm autozone.com]
** Product type: Motor Vehicles > Automotive Parts > Front Break Pads
** Properties: category, name, brand, accessory for, photo, part number, weight, warranty, application, note, price, availability, shipping

* [http://www.officedepot.com/a/products/908194/Swingline-Commercial-Desk-Stapler-Black/ officedepot.com]
** Product type: Office supplies > Stapler
** Properties: categories, name, brand, item number, photo, availability, shipping, price, quantity, add to cart, add to list, compare, product rating, reviews

* [http://www.amazon.com/gp/product/3937514775?ie=UTF8&tag=ubuntusearch-20&linkCode=as2&camp=1789&creative=390957&creativeASIN=3937514775 amazon.com]
** Product type: Software > Operating Systems
** Properties: photo, name, brand, platform, product rating, price, shipping, availability, media type, quantity, related, features, width, height, length, weight, asin, model number, publish date, sales rank, categories, description, tags, reviews, discussions

* [http://www.foosballstore.com/products/description/672.cfm foosballstore.com]
** Product type: Sporting Goods > Foosball Table
** Properties: name, brand, photo, description, model, price, shipping, quantity, accessories, add to cart, product specs, optional items, parts for, reviews

* [http://www.toysrus.com/product/index.jsp?productId=2332387 toysrus.com]
** Product type: Toys & Games > Board Games
** Properties: categories, photo, name, brand, price, product rating, availability, quantity, add to cart, add to registry, add to wish list, description, features, item number, ski, upc, ean, isbn, manufacturer number

* [http://www.williams-sonoma.com/products/8232084/index.cfm?pkey=cbakeware-top-rated&cm_src=hero williams-sonoma.com]
** Product Type: Home & Garden > Kitchen & Dining > Bundt Pan
** Properties: photo, name, brand, description, product rating, reviews, price, quantity, add to basket, shipping, reviews

* [http://www.nulime.com/Hurricane-650-Fog-Machine/p201638 nulime.com]
** Product Type: Arts & Entertainment > Visual Effects > Fog Machines
** Properties: categories, item id, name, photo, list price, regular price, savings, availability, add to cart, send to friend, quantity, shipping, brand, product date, weight, height, width, depth, mode, upc, condition, return info, condition, warranty, url, description, accessories, reviews

* [http://shop.symantecstore.com/DRHM/servlet/ControllerServlet?SiteID=symnahho&Action=DisplayProductDetailsPage&productID=81884500&pgm=13665000&ThemeID=106300 symantecstore.com]
** Product Type: Software > Security Software
** Properties: photo, name, brand, description, add to cart, features, price

* [http://www.needledoctor.com/Rega-P9-Turntable?sc=2&category=353 needledoctor.com]
** Product Type: Electronics > Audio > Audio Components > Turntables
** Properties: name, description, brand, photo, price, color, quantity, add to cart

* [http://www.golfsmith.com/ppage.php?stynum=PG191091&lcode=CI&cm_mmc=froogle-_-consumer-_-1-_-r&ci_src=14110944&ci_sku=PG191091&tcode=fr_home golfsmith.com]
** Product Type: Sporting goods > Outdoor Recreation > Golf
** Properties: categories, photo, name, brand, regular price, sale price, quantity, stock number, availability, rating, reviews, description, shipping, condition

* [http://shop.lego.com/productsmall.asp?prod_id=7627 shop.lego.com]
** Product Type: Toys & Games > Toys > Building Toys
** Properties: name, photo, item number, price, availability, description, height, width, add to cart

* [https://www.nascigs.com/Our-Products/Product-Selector.aspx#a=blue_details nascigs.com]
** Product Type: Food, Beverages & Tobacco > Tobacco Products
** Properties: photo, name, description

* [http://store.mozilla.org/product.php?code=14%2013111&catid=9 store.mozilla.org]
** Product Type: Clothing & Accessories > Clothing > T-shirts
** Properties: photo, name, price, description, item number, size, quantity, add to cart

* [http://www.cvs.com/CVSApp/catalog/shop_product_detail.jsp?filterBy=default&skuId=144888&productId=144888&navAction=push&no_new_crumb=true cvs.com]
** Product Type: Health & Beauty > Health Care > Smoking Cessation
** Properties: category, photo, name, brand, sku, price, quantity, add to cart, description, ingredients, directions, warnings

* [http://shop.samsonite.com/storefront/suitcases/25-quot-spinner/prod35566XXXX-cC05-.html shop.samsonite.com]
** Product Type: Luggage > Suitcases
** Properties: category, name, brand, price, availability, color, quantity, add to cart, photo, description, height, width, depth, product code, item number

* [http://www.beanbags.com/bean-bag-chairs/extra-large/exclusivexlblackvinylbeanbag.cfm beanbags.com]
** Product Type: Furniture > Bean Bags
** Properties: category, photo, name, item number, list price, sale price, savings, features, price, availability, quantity, add to cart, rating, shipping, description, specifications, guarantee, reviews

* [http://www.amazon.com/Watching-The-Detectives/dp/B000V6THXO/ref=dm_ap_trk9 amazon.com]
** Product Type: Media > Music > Rock & Pop > MP3
** Properties: photo, name, artist, price, reviews, format, release date, label, copyright, length, genres, asin, product rating

* [http://ww22.1800flowers.com/product.do?baseCode=16156&dataset=10314&cm_sp=subproduct_Roses_Multicolored%20Roses%20-%20Buy%2012%2C%20Get%206%20Free-_-tab2_image2-_-basecode_16156_dataset_10314_01122009_0830 1800flowers.com]
** Product Type: Home & Garden > Plants > Flowers
** Properties: name, photo, description, product code, price, zip, location

* [http://www.6pm.com/n/p/p/7257462/c/6971.html 6pm.com]
** Product Type: Clothing & Accessories > Footwear > Boots
** Properties: brand, name, ski, price, savings, photo, size, width, color, add to cart, features, reviews

* [http://www.abebooks.com/servlet/SearchResults?isbn=9780495011606 abebooks.com]
** Product Type: Media > Books > Non-fiction
** Properties: categories, name, author, manufacturer, rating, photo, price, quantity, shipping, add to cart, description, isbn, publisher, condition

* [http://www.abercrombie.com/webapp/wcs/stores/servlet/product_10051_10901_482623_-1_12213_12202 abercrombe & fitch]
** Product Type: Clothing & Accessories > Clothing > Tops
** Properties: photo, name, style, price, description, color, size, add to cart

* [http://www.abt.com/product/21632.html abt.com]
** Product Type: Electronics > Audio > Audio Accessories
** Properties: categories, brand, name, photo, price, description, availability, shipping, rating, add to cart, model, features, reviews

* [http://www.ae.com/web/browse/product.jsp?catId=cat1070004&productId=0423_3693 ae.com]
** Product Type: Clothing & Accessories > Clothing Accessories > Belts
** Properties: photo, brand, name, style number, price, description, color, size, availability, quantity, add to cart, payment

* [http://www.altrec.com/the-north-face/trailhead-6-tent altrec.com]
** Product Type: Sporting goods > Outdoor recreation > Camping, Backpacking & Hiking > Tents
** Properties: categories, photo, brand, name, price regular, price sale, quantity, color, add to cart, sku, shipping, description, review

* [http://www.americanstationery.com/shopping/prod_detail/main.asp-pid-3329 americanstationery.com]
** Product Type: Office supplies > General Supplies > Paper Products > Stationery
** Properties: categories, name, photo, item number, description, size, color, style, price, description, quantity, order, review

* [http://www.anthropologie.com/anthro/catalog/productdetail.jsp?_dyncharset=ISO-8859-1&_dynSessConf=7579514410004107168&id=844658&parentid=ACC_EYE_SUN&pushId=ACC_EYE_SUN&popId=ACC_EYEWEAR&sortProperties=&navCount=1&navAction=&fromCategoryPage=true&selectedProductSize=&selectedProductSize1=&color=tur&colorName=TURQUOISE anthropologie.com]
** Product Type: Clothing & Accessories > Clothing Accessories > Eyewear
** Properties: photo, name, description, material, style number, price, color, size, quantity, add to cart

* [http://store.apple.com/us/product/FB323LL/A?mco=MjE0NDk5Mw apple.com]
** Product Type: Electronics > Computers > Desktops
** Properties: name, photo, brand, description, features, price, shipping, add to cart, product details, whats in the box

* [http://www.audible.com/adbl/site/products/ProductDetail.jsp?BV_UseBVCookie=Yes&productID=BK_SANS_000623 audible.com]
** Product Type: Media > Downloadable Audio
** Properties: photo, name, author, narrator, price regular, add to cart, price sale, program type, publisher, length, release date, audio formats, rating, description, reviews

* [http://gifts.barnesandnoble.com/search/product.asp?EAN=2000003285044 barnesandnoble.com]
** Product Type: Media > Magazines & Newspapers >
** Properties: categories, photo, brand, name, rating, reviews, ean, sales rank, price regular, price online, price sale, price member, add to cart, description, shipping, product details

* [http://www.bestkiteboarding.com/09-Waroo bestkiteboarding.com]
** Product Type: Sporting goods > Water Sports > Windsurfing
** Properties: model, name, photo, color, description, product features, performance metrics, size, price, quantity, add to cart

* [http://bodybuilding.com/store/iron/creatine.html bodybuilding.com]
** Product Type: Health & Beauty > Health Care > Fitness & Nutrition > Vitamins & Supplements
** Properties: size(s), product details, directions, brand, photo, description, price, buy/ order

* [http://www.brooksbrothers.com/IWCatProductPage.process?Merchant_Id=1&Section_Id=591&Product_Id=827242&Parent_Id=356&default_color=Navy brooksbrothers.com]
** Product Type: Clothing & Accessories > Clothing > Suits > Boy's Two-Button Prep Blazer
** Properties: photo, categories, name, brand, description, article number, price, color, size, quantity, add to cart

* [http://www.bulbs.com/eSpec.aspx?ID=14561&Ref=Category&RefId=13 bulbs.com]
** Product Type: Home & Garden > Lighting > Light Bulbs
** Properties: photo, brand, name, description, quantity, add to cart, product details, price, shipping

* [http://www.buy.com/prod/wenger-potomac-black-rolling-notebook-case-fits-up-to-17-inch-laptop/q/loc/16234/208905968.html buy.com]
** Product Type: Luggage > Laptop Bags
** Properties: name, photo, shipping, regular price, sale price, you save, quantity, availability, brand, manufacturer part number, sku, upc, features, color, package contents, manufacturer, manufacturer part number, weight, product type, reviews, categories

* [http://www.cabelas.com/cabelas/en/templates/product/standard-item.jsp?_DARGS=/cabelas/en/common/catalog/item-link.jsp_A&_DAV=MainCatcat21412-cat20145&id=0006612513096a&navCount=2&podId=0006612&parentId=cat20145&masterpathid=&navAction=push&catalogCode=XJ&rid=&parentType=index&indexId=cat20145&hasJS=true cabelas.com]
** Product Type: Motor Vehicles > Automotive Safety Equipment > Tire Chains
** Properties: categories, photo, name, item number, price, rating, description, size, add to cart, quantity, weight

* [http://www.carolsdaughter.com/product/color/lip_gloss_bubbling_brown_sugar.do carolsdaughter.com]
** Product Type: Health & Beauty > Personal Care > Hair Care > Hair Coloring
** Properties: categories, photo, name, size, description, reviews, item number, quantity, price, availability, add to list, instructions

* [http://www.coach.com/content/product.aspx?product_no=12613&category_id=53 coach.com]
** Product Type: Clothing & Accessories > Clothing Accessories > Wallets
** Properties: photo, name, product details, length, height, price, style number, quantity, colors, add to cart

* [http://www.costco.com/Browse/Product.aspx?Prodid=11295243&whse=BC&topnav=&browse=&lang=en-US costco.com]
** Product Type: Gifts & Tickets > Membership > Fitness membership
** Properties: categories, photo, name, brand, item number, rating, price, quantity, add to cart, description, product details, shipping, reviews

* [http://www.crateandbarrel.com/family.aspx?c=14210&f=11731 crateandbarrel.com]
** Product Type: Home & Garden > Kitchen & Dining > Grillware
** Properties: categories, photo, name, price, description, diameter, height, sku, shipping, quantity, add to cart, availability

* [http://www.davidsbridal.com/webapp/wcs/stores/servlet/ProductDisplayView?storeId=10052&catalogId=10051&categoryId=-49997326&currentIdx=0&subCategory=-49998493|-49997962|-49997326&catentryId=4000138 davidsbridal.com]
** Product Type: Home & Garden > Decor > Candles
** Properties: categories, photo, name, description, price, height, diameter, rating, color, shipping, quantity, availability, reviews

* [http://www.delightfuldeliveries.com/wine/8366.asp delightfuldeliveries.com]
** Product Type: Food, Beverages & Tobacco > Beverages > Wine > Gift Baskets
** Properties: name, photo, description, brand(s), price, item number, shipping, add to cart

* [http://accessories.us.dell.com/sna/products/Displays/productdetail.aspx?c=us&l=en&s=dhs&cs=19&sku=A1732949 dell.com]
** Product Type: Electronics > Electronics Accessories > Mounts
** Properties: categories, brand, name, photo, description, price, add to cart, shipping, manufacturer part number, dell part number, rating, reviews, product specs, weight

* [http://www.diapers.com/Product/ProductDetail.aspx?productId=7710 diapers.com]
** Product Type: Baby & Toddler > Baby Transport > Baby Carriers
** Properties: categories, photo, name, rating, price, shipping, description, quantity, add to cart, reviews

* [http://www.dickssportinggoods.com/product/index.jsp?productId=1373378 dickssportinggoods.com]
** Product Type: Sporting Goods > Team Sports > Cricket
** Properties: categories, photo, name, brand, item number, rating, description, shipping, price, size, quantity, add to cart, availability, shipping, product features, reviews

* [http://www.currys.co.uk/martprd/product/402032 currys.co.uk]
** Product Type: Home & Garden > Household Appliances > Vacuuming > Vacuums
** Properties: name, brand, product code, photo, availability, price sale, delivery, add to cart, product details, warranty/guarantee, description

* [http://www.johnlewis.com/230508557/Product.aspx johnlewis.com]
** Product Type: Home & Garden > Household Appliances > Vacuuming > Vacuums > Wallpaper
** Properties: name, brand, photo, product code, quantity, availability, price, terms and conditions, add to cart, shipping, colours, descriptions, dimensions (width, length)

* [http://quelle.fr/portal/portal/SiteInternet/App/Shopping-bijoux?secteur=bijoux quelle.fr]
** Product Type: Clothing & Accessories > Jewelry > Rings
** Properties: categories, photo, name, size, quantity, price regular, price sale, savings, description, weight, add to cart

* [http://www.cdiscount.com/maison/canape-canapes/banquette-sydney-convertible/f-1170103-SX19851M.html cdiscount.com]
** Product Type: Furniture > Living Room > Sofas
** Properties: categories, name, brand, photo, price sale, price regular, add to cart, description, height, width

* [http://www.tchibo.de/is-bin/INTERSHOP.enfinity/eCS/Store/de/-/EUR/TdTchDisplayProductInformation-Start?ProductSKU=0001193&produkt=Tchibo-Cafissimo-Anthrazit tchibo.de]
** Product Type: Home & Garden > Kitchen & Dining > Appliances > Coffee Makers & Espresso Machines
** Properties: photo, name, brand, price, quantity, description, test rating, demensions (height, width, depth), color, add to cart

* [http://www.karstadt.de/produktAnzeigen.do?pfad=866898+884179+881377&pid=3201158 karstadt.de]
** Product Type: Sporting Goods > Team Sports > Soccer > Accessories
** Properties: photo, name, description, availability, add to cart, product details, size (height, width)

* [http://www.exlibris.ch/papier/ChipResetter/ChipResetter_f%C3%BCr_Canon_CLI8_und_PGI5_Patronen/thl/02163.aspx?system=&haupt=&unter=&pa=&pa_bis= exlibris.ch]
** Product Type: Electronics > Print, Copy, Scan & Fax > Print, Copy, Scan & Fax Accessories > Printer Accessories > Toner & Inkjet Cartridges
** Properties: name, photo, product type, price, ean, description, add to cart, shipping

* [http://www.radioshack.com/product/index.jsp?productId=2603246 radioshack.com]
** Product Type: Electronics > Electronics Accessories > Cables & Adapters > Adapters
** Properties: categories, photo, name, price, model, catalog number, availability, shipping, add to cart, description, reviews, rating

* [http://www.drsfostersmith.com/product/prod_Display.cfm?pCatId=9722 drsfostersmith.com]
** Product Type: Animals > Pet Supplies > Dog Supplies > Dog Medication
** Properties: name, photo, brand, shipping, description, item number, add to cart, weight

* [http://www.drugstore.com/products/prod.asp?pid=205134&catid=33699&trx=GFI-0-EVGR-11690&trxp1=33699&trxp2=205134&trxp3=1&trxp4=1&btrx=BUY-GFI-0-EVGR-11690 drugstore.com]
** Product Type: Health & Beauty > Personal Care > Oral Care > Toothbrushes
** Properties: categories, name, brand, quantity, photo, shipping, rating, quantity, add to cart, description, reviews, price

* [http://www.ecampus.com/merch_detail.asp?item=31589270 ecampus.com]
** Product Type: Office Supplies > Office Instruments > Office Rulers
** Properties: name, brand, categories, photo, price sale, price regular, savings, description, length, shipping, model number, add to cart

* [http://www.fye.com/The-Beatles-1-Used_stcVVproductId1400843VVcatId473167VVviewprod.htm fye.com]
** Product Type: Media > Music > Rock & Pop > British Invasion
** Properties: categories, photo, name, artist, format, release date, record label, upc, product id, sku, amg rating, genre, condition, price regular, price used, price member, savings, availability, add to cart, tracks (hAudio?), rating, description, reviews, credits (name-value pair), related

* [http://www.foodnetworkstore.com/p-646354-Mesa-Grill-Barbeque-Sauce-97ozbr-By-Bobby-Flay.aspx foodnetworkstore.com]
** Product Type: Food, Beverages & Tobacco > Food Items > Condiments, Seasoning & Sauces > Barbecue Sauce
** Properties: photo, name, size, brand, price, rating, quantity, add to cart, availability, shipping, item number, description, origin, shelf life, reviews

* [http://www.gifttree.com/p3/2402/Chicken_Soup_for_the_Soul_Get_Well_Gift_Basket-1.html gifttree.com]
** Product Type: Food, Beverages & Tobacco > Food Items > Food Gift Baskets
** Properties: categories, photo, name, shipping, price, quantity, add to cart, description, width, height, depth

* [http://www.golfballs.com/PB1512-OWH/Titleist-Pro-V1-Golf-Balls-Logo-Overruns-2008-Model.html golfballs.com]
** Product Type: Sporting Goods > Outdoor Recreation > Golf > Golf Balls
** Properties: categories, name, rating, photo, brand, sku, condition, color, number, price, quantity, add to cart, shipping, description, reviews, faqs

* [http://shop.guess.com/ProductDetails.aspx?style=M8412200&image=M8412200-LBEI&root_category|90=Men&category|101=Denim&browse=1&rpt=Department.aspx&pt=ProductListing.aspx guess.com]
** Product Type: Clothing & Accessories > Clothing > Pants > Jeans
** Properties: photo, name, description, size, color, quantity, price, add to cart

* [http://www.harryanddavid.com/gifts/store/product____gourmet-popcorn-moose-munch-gifts_moose-munch-popcorn-gifts_5031937 harryanddavid.com]
** Product Type: Food, Beverages & Tobacco > Food Items > Candy, Sweets & Gum
** Properties: categories, photo, name, brand, description, size, availability, item number, price, add to cart

* [http://www.shopping.hp.com/product/51629A?landing=supplies&category=&family_name= hpshopping.com]
** Product Type: Electronics > Print, Copy, Scan & Fax > Print, Copy, Scan & Fax Accessories > Printer Accessories > Toner & Inkjet Cartridges
** Properties: name, model number, photo, brand, offers, price, availability, shipping, quantity, add to cart, description, features, specifications

* [http://www.klwines.com/detail.asp?sku=1041623 klwines.com]
** Product Type: Food, Beverages & Tobacco > Beverages > Wine
** Properties: photo, name, brand, year, sku, description, price, quantity, add to cart, rating, availability, reviews, varietal, country, sub-region, appellation

* [http://www.karmaloop.com/products.aspx?ProductID=53615&VendorCode=COA karmaloop.com/]
** Product Type: Clothing & Accessories > Clothing Accessories > Gloves & Mittens
** Properties: brand, photo, name, price (in us/ canadian/austrailian dollar, british pound, euro), color, size, add to cart, description, style number

* [http://www.lancome-usa.com/makeup/mascara/definicils-mascara.htm lancome-usa.com]
** Product Type: Health & Beauty > Personal Care > Cosmetics > Makeup > Eyes > Mascara
** Properties: categories, model, photo, brand, description, color, quantity, price, add to cart, benefits, technology, tips

* [http://www.levenger.com/PAGETEMPLATES/PRODUCT/Product.asp?Params=Category=13-850|Level=2-3|pageid=341 levenger.com]
** Product Type: Office Supplies > Filing & Organization > Desk Organizers
** Properties: photo, brand, name, price, item identifier, description, size (width, height, depth), color, quantity, add to cart, rating, reviews, product specifications

* [http://www.lillianvernon.com/catalog/product_display.jsp?pdId=12342&name=Deluxe+Hanging+Pants+Rack&parentCatId=3&catId=149 lillianvernon.com]
** Product Type: Home & Garden > Household Supplies > Storage & Organization > Hangers
** Properties: categories, photo, name, sku, color, size, description, price regular, price sale, savings, quantity, add to cart, rating, reviews

* [http://www.moosejaw.com/moosejaw/shop/product_Moosejaw-Barf-Bag_10085155_10208_10000001_-1_ moosejaw.com]
** Product Type: Sporting Goods > Outdoor Recreation > Camping, Backpacking & Hiking > Barf Bags
** Properties: photo, condition, name, brand, item number, price, rating, color, quantity, add to cart, description, reviews

* [http://www.mymms.com/gifts/gifts.asp?item=51 mymms.com]
** Product Type: Food, Beverages & Tobacco > Food Items > Candy, Sweets & Gum
** Properties: name, description, size, photo, price, quantity

* [http://www.netflix.com/Movie/Indiana_Jones_and_the_Last_Crusade/60010487?lnkctr=srchrd-sr&strkid=962279771_0_0 netflix.com]
** Product Type: Media > DVDs & Videos
** Properties: name, release date (year), photo, description, artist(s), genre, format, language, subtitiles, awards, movie rating,

* [http://www.netshops.com/seasonal-&-gifts/gifts-for-him/hammocks/bestsellerislandbayxlropehammock.cfm netshops.com]
** Product Type: Home & Garden > Lawn & Garden > Outdoor Living > Hammocks
** Properties: categories, photo, name, brand, item number, price regular, price sale, savings, features, rating, shipping, material, quantity, add to cart, description, warranty, weight, length, size, hardware, compatibility, style, width, min/max distance, reviews

* [http://store.nike.com/index.jsp?country=GB&lang_locale=en_GB&ref=http%3A//store.nike.com/index.jsp%3Fsitesrc%3DEMFC%26ref%3Dhttp%3A//www.nikefootball.com%26l%3Dshop%2Cpdp%2Cctr-inline/cid-300/pid-219653/pgid-183395&sitesrc=EMFC&ref=http://www.nikefootball.com&l=shop,pdp,ctr-inline/cid-300/pid-219653/pgid-183395 nike.com]
** Product Type: Sporting Goods > Team Sports > Football > Football Shoes
** Properties: brand, name, price, style number, photo, size, quantity, add to cart, description, features, reviews

* [http://www.ninewest.com/Nightlight/3506933,default,pd.html?cgid=1039 ninewest.com]
** Product Type: Clothing & Accessories > Footwear > Boots
** Properties: name, price, photo, color, width, size, description, heel, shaft size, circumference, add to cart

* [http://www.oneida.com/index.cfm/fuseaction/product.detail/_/Paul-Revere/productID/ab228c02-d447-42d0-8aac-995522504787/categoryID/7f6f89c9-5e89-4fda-ba39-a10c0588d5b6/ oneida.com]
** Product Type: Home & Garden > Kitchen & Dining > Tableware > Flatware
** Properties: categories, name, description, photo, metal type, shipping, rating, reviews, add to cart, quantity, item identifier, price regular, price sale

* [http://www.overstock.com/Home-Garden/Serta-Cool-Memory-Foam-2-inch-Mattress-Topper/3297642/product.html overstock.com]
** Product Type: Home & Garden > Bedroom > Mattress Pads
** Properties: categories, photo, brand, name, price regular, price sale, description, quantity, size, add to cart, rating, availability, shipping, reviews, size, warranty, materials, model number, height, width, length

* [http://www.chainsawsdirect.com/Husqvarna-235E/p2524.html chainsawsdirect.com]
** Product Type:Hardware > Tools > Chainsaws
** Properties: brand, name, photo, price regular, price sale, savings, model, shipping, availability, add to cart, rating, reviews, features, manufacturer, specs, weight, length, width, height

* [http://www.repairclinic.com/SSPartDetail.aspx?s=b5a4c216i1159182&PartID=1159182 repairclinic.com]
** Product Type: Home & Garden > Kitchen & Dining > Appliances > Refrigerators > parts > compressor parts
** Properties: categories, brand, part/item number, price, availability, quantity, add to cart, shipping, photo

=== Analysis of Product/Commerce Sites ===

Analysis on 100 ecommerce and manufacturing sites was performed to represent a wide array of product families. Below are the most notable '''universal''' product attributes. Analysis is ongoing and more examples may be selected as they are added to the product taxonomy.

* photo/image: 100.00%
* price: 99% price variations include:
** instant
** sale
** regular
** list
** online
** member
** used
* name/title: 98%
* brand/manufacturer: 93%
* description: 90%
* add to cart/ buy: 87%
* identifier: 79% examples include:
** stock number
** sku
** item number
** dpci
** asin
** catalog number
** style number
** product id
** product code
** web id
** series
** part number
** product code
** mpc
** isbn
** ean
** upc
** style
** article number
* product reviews: 78%
* quantity: 61%
* dimensions: 51% dimensions attributes include:
** height
** width
** depth
** weight
** length
** circumference
* category/ categories: 50%
* shipping: 50%
* product rating: 44%
* status/ availability: 36%
* color: 31%
* size: 27%
* model: 15%
* monetary savings/"you save": 14%
* warranty/guarantee: 13%
* condition: 10%
* language: 1%

=== Coded examples ===

(Note: this example contains additional markup for positioning and presentation purposes)

<pre><nowiki>
<div class="hproduct">
<ul id="breadcrumbs">
<li>Storename</li>
<li class="category">Cameras</li>
<li class="category">Video Cameras</li>
<li class="category">High-Definition Cameras</li>
</ul>
<h1 class="n">Pure Digital Flip Video MinoHD Camcorder</h1>
<div id="topbox">
<div class="rightcol">
<img src="http://images.storename.com/images/products/front.jpg" alt="Image of Pure Digital F460B" class="photo" />
</div>
<div class="leftcol">
<div class="infomain">
<ul>
<li><strong>Brand: </strong><span class="brand">Pure Digital</span></li>
<li><strong>Model: </strong><span class="model">F460B</span></li>
<li><strong>SKU: </strong><span class="sku">9077054</span></li>
</ul>
<p class="description">This camcorder offers true high-definition recording in an incredibly compact body, so you can be sure you won't miss a minute of recording time.</p>
<p>
<span class="availability online">Available online</span>. <span class="shipping">Backordered: Usually leaves our warehouse within 1-2 weeks. <span class="money">Estimated shipping cost: <abbr class="currency" title="USD" lang="en">$</abbr><span class="amount">0.0</span>.</span></span>
</p>
<p>
<span class="availability instore">Not available for purchase in store</span>.
</p>
<p>
<span class="availability specialorder">Not available for special order</span>.
</p>
</div>
<div class="infoside">
<span class="price sale"><span class="money"><strong>Sale Price: </strong><abbr class="currency" title="USD" lang="en">$</abbr><span class="amount">206.99</span></span></span>
<div class="buy">
<img src="http://images.storename.com/products/images/btn_add_to_cart.gif" alt="buy this product"></div>
</div>
<div class="clear"></div>
</div>
<div class="clear"></div>
</div>
<div id="bottombox">
<div id="tabs">
<ul>
<li><a href="#featuresbox"><span>Features</span></a></li>
<li><a href="#specsbox"><span>Specs</span></a></li>
<li><a href="#reviewsbox"><span>Reviews</span></a></li>
</ul>
</div>
<div id="specsbox">
<h3>Product Specs</h3>
<dl class="p-v">
<dt>Color</dt>
<dd>Black</dd>
<dt>Height</dt>
<dd>3.9"</dd>
<dt>Width</dt>
<dd>2"</dd>
<dt>Depth</dt>
<dd>0.6"</dd>
<dt>Weight</dt>
<dd>3.3 oz.</dd>
<dt>Warranty -- Parts</dt>
<dd>90 days</dd>
<dt>Warranty -- Labor</dt>
<dd>90 days</dd>
<dt>Format</dt>
<dd>Flash memory</dd>
<dt>Vista Compatible</dt>
<dd>Home Basic</dd>
<dt>LCD Screen Size</dt>
<dd>1.5"</dd>
<dt>Image Stabilization</dt>
<dd>No</dd>
<dt>Optical Zoom</dt>
<dd>None</dd>
<dt>Digital Zoom</dt>
<dd>2x</dd>
<dt>Night Recording</dt>
<dd>Yes</dd>
<dt>Audio Sensor</dt>
<dd>Yes</dd>
<dt>Lines of Resolution</dt>
<dd>720</dd>
<dt>Video Resolution</dt>
<dd>Up to 1280 x 720</dd>
<dt>Digital Still Resolution</dt>
<dd>Up to 1280 x 720</dd>
<dt>Auto Date/Time Stamp</dt>
<dd>Yes</dd>
<dt>Audio Recording</dt>
<dd>Yes</dd>
<dt>Color Viewfinder</dt>
<dd>Yes</dd>
<dt>Speaker</dt>
<dd>Yes</dd>
<dt>Exposure Control</dt>
<dd>Automatic</dd>
<dt>PC Software</dt>
<dd>Yes</dd>
<dt>Connectivity</dt>
<dd>USB 2.0</dd>
<dt>PC Cable</dt>
<dd>Yes</dd>
<dt>Rechargeable Battery</dt>
<dd>Yes</dd>
</dl>
<div class="clear"></div>
</div>
<div id="reviewsbox">
<h3>Product Reviews</h3>
<div class="hreview">
<h4>"<span class="summary">Amazing little camera</span>"</h4>
<p>
<strong>Reviewer: </strong><span class="reviewer vcard"><a href="http://reviews.storename.com/3545a/kevwhitesf/profile.htm" class="url fn">kevwhitesf</a></span> from <span class="adr"></span>
</p>
<p>
<strong>Date reviewed: </strong><abbr title="200502" class="dtreviewed">2008-11-24T18:53:32.000-06:00</abbr>
</p>
<p>
<strong>Rating: </strong><span class="rating">5</span> out of 5</p>
<p class="description">"It definitely exceeded my expectations. It does everything it claims to do and more at a very reasonable price. I was pretty shocked that such a small device was capable of producing such a nice picture. Limited functionality, but that's what I was expecting. It interfaces nicely with Macs. I'm having lot of fun with my MinoHD! I've been taking it everywhere."</p>
</div>
<div class="hreview">
<h4>"<span class="summary">Amazing HD Consumer Camera</span>"</h4>
<p>
<strong>Reviewer: </strong><span class="reviewer vcard"><a href="http://reviews.storename.com/3545a/sscrozz/profile.htm" class="url fn">sscrozz</a></span> from <span class="adr">Lafayette, CA</span>
</p>
<p>
<strong>Date reviewed: </strong><abbr title="200502" class="dtreviewed">2008-11-22T03:08:41.000-06:00</abbr>
</p>
<p>
<strong>Rating: </strong><span class="rating">4</span> out of 5</p>
<p class="description">"This camera is perfect for the consumer who wants a pocket camera that shoots HD. It shoots in full HD using H.264 compression (great quality video that takes up little space) It now works with Macs using Mpeg4 instead of AVI. Here is a HD test video. http://www.vimeo.com/2291493"</p>
</div>
</div>
<div class="clear"></div>
</div>
</div>
</nowiki></pre>

hproduct

2009-04-24T16:46:41Z

JayMyers: removing out of date examples

<entry-title>hProduct</entry-title>
{{DraftSpecification}}
__TOC__
hProduct is a microformat suitable for publishing and embedding product data. hProduct is one of several open microformats standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

==hProduct Microformat Draft Specification==

; Editors/Authors
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

; Contributors
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

== Status ==
Draft, version 0.2.

== Introduction ==
The web is a thriving consumer marketplace with a plethora of manufacturers and vendors scattered across the globe. Sifting through massive amounts of unstructured product data is a difficult task for both browsers and machines alike. The hProduct microformat gives structure to this metadata by providing constructs to identify universal product attributes, plus a mechanism to accomodate the wide variation in product attributes.

The hProduct microformat can assist consumers, manufacturers and retailers in a number of ways. If a browser or application understands that a specific web page contains the hProduct microformat, it can inform and help facilitate the best product choice by the consumer to fulfill their needs. An adpoted, open standard will ensure the correct product data is published between manufacturers and retailers, to the benefit of the consumer. Bringing order and structure to product data makes it easy for people and organizations to list the products and services they offer, and easy for web services to consume that product data for analysis and syndication.

=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

=== Inspiration and Acknowledgment ===
Many thanks go out to the contributors who laid the foundation for the current hProduct draft spec.

=== Scope ===
Giving details about a particular product is sometimes very complex as parameters are different for books and CDs than they are for iPods or cars. It should be very easy to mark up an item using hProduct and the syntax should be simple yet flexible enough for more advanced applications.

=== Out of Scope ===
This microformat does not intend to replicate any of the content proposed within [[hListing]] and would defer all money/transactional matters to that microformat. This microformat also does not attempt to specify a product ontology, or category-specific attributes; instead, it aims to create a framework to allow for flexible expression of both.

== Format ==
{{rfc-2119-intro}}

=== In General ===
The hProduct format is based on a set of fields common to numerous ecommerce sites and formats in use today on the web.

=== Schema ===
The hProduct schema consists of the following (see existing class names for reference):

*hproduct
** brand. optional. text. can also use [[hcard|hCard]] for manufacturer.
** category. optional. text. can also use rel-tag. re-used from [[hcard|hCard]].
** price. optional. floating point number. can use currency format.
** description. optional. text. can also include valid HTML markup. re-used from [[hreview|hReview]].
** fn. '''required.''' text. product name or title. re-used from [[hcard|hCard]].
** photo. optional. image element or link. re-used from [[hcard|hCard]].
** url. optional. href. can contain rel-tag rel='product'. re-used from [[hcard|hCard]].
** review. optional. [[hreview|hReview]], or [[aggregate-microformat-template-examples|hReview-aggregate]].
** listing. optional. [[hlisting|hListing]], or [[aggregate-microformat-template-examples|hListing-aggregate]].
** identifier. optional.
*** type. required. - examples:
**** model
**** mpn
**** upc
**** isbn
**** issn
**** ean
**** jan
**** sn
**** vin
**** sku
*** value. required. - label may be implied

=== Field details ===
Class names <code class="class-name">category</code>, <code class="class-name">fn</code>, <code class="class-name">photo</code>, <code class="class-name">url</code> are reused from [[hcard|hCard]]. <code class="class-name">description</code> is reused from [[hreview|hReview]].

The fields of the hProduct schema represent the following:

*'''<code class="class-name">hproduct::</code>''' Root class name
*'''<code class="class-name">brand::</code>''' the class name brand is used identify brand of the product. {{should}} use [[hcard|hCard]] for manufacturer name. {{must}} be singular.
*'''<code class="class-name">category::</code>''' the class name category identifies product category. {{may}} use [[rel-tag]] microformat. {{may}} be plural to represent multiple categories.
*'''<code class="class-name">price::</code>''' the class name price is used to indicate the price of the product. {{must}} be singular.
*'''<code class="class-name">description::</code>''' the class name description is used to describe the product. {{must}} be singular.
*'''<code class="class-name">fn::</code>''' product text name. {{must}} be singular.
*'''<code class="class-name">photo::</code>''' the class name photo {{may}} be applied to an <img> or <a> element. {{may}} be plural.
*'''<code class="class-name">url::</code>''' the class name url {{should}} refer to the web page associated with product details. {{may}} use [[rel-tag]], rel='product'. {{must}} be singular.
*'''<code class="class-name">review::</code>''' the class name review identifies review(s) for the product. {{should}} use [[hreview|hReview]]. {{may}} be plural.
*'''<code class="class-name">listing::</code>''' the class name listing identifies product listings. {{should}} use [[hlisting|hListing]]. {{may}} be plural.
*'''<code class="class-name">identifier::</code>''' the identifier structure is used to describe product identifiers like Model, UPC or SKU, and is designed to accommodate new or as-yet-unidentified identifiers. {{should}} be singular.
**'''<code class="class-name">type::</code>''' the class name type identifies the identifier type.
**'''<code class="class-name">value::</code>''' label {{may}} be implied

=== Additional Details ===
'''Note:''' If hProduct markup is used in a "standalone" fashion (eg. a manufacturer site that's not commerce enabled, strictly informational), it is assumed that the price attribute represents the manufacturer's suggested retail price. Any transactional (commerce) representation of price should be delegated to [[hlisting|hListing]].

''Internationalization'': Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. Note that (X)HTML LANG attribute rules still apply as usual, for multilingual aggregators of hProduct.

=== Relationships with other microformats ===
Products can be complex structures with attributes and features that may fall outside the bounds of the proposed hProduct microformat. Care has been taken to provide just enough attributes to accurately represent products while not overloading the hProduct spec. This means that complete semantic solutions would rely on using hProduct in combination with other microformats to achieve their goals. Through [[hproduct-examples#Coded_examples|examples]] (see also: [[hproduct-recipes|recipes]]) and [[hproduct-examples#Analysis_of_Product.2FCommerce_Sites|analysis]], there are some clear relationships between hProduct and these microformats:

* [[hlisting|hListing]] :: provides additional context to the transaction side of a product, including crucial elements like "price".
* [[hReview|hReview]]/hAggregate(concept) :: research shows that many commerce sites include product reviews, and they are often aggregated to provide overall ratings and reviews on the web. Utilizing these microformats can provide additional data around a product or service.
* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a product.

Of course, these are just a few of many that could be used with the hProduct microformat.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hproduct</dt>
<dd>Used to identify and describe metadata universally common to products.</dd>
<dt>availability</dt>
<dd>The details around the availability of the product.</dd>
<dt>brand</dt>
<dd>The brand name of the product.</dd>
<dt>category</dt>
<dd>The product category/ categories the product belongs to.</dd>
<dt>condition</dt>
<dd>The condition of the product.</dd>
<dt>fn</dt>
<dd>The common name of the product.</dd>
<dt>photo</dt>
<dd>Accompanying image of the product.</dd>
<dt>url</dt>
<dd>A link to the product details.</dd>
<dt>identifier</dt>
<dd>The product identifier like Model, SKU, ISBN, or EAN associated with the product</dd>
</dl>
</dd>
</dl>
</pre>

=== Notes ===
This section is informative.
*...

=== Examples in Production ===
* Description of [http://jay.beweep.com/index.php/2008/10/14/reviving-shop-urls-with-hproduct BestBuy.com implementation]

=== Other examples ===

Please see examples at [[hproduct-examples|hProduct examples]].

== Copyright ==
* [[User:JayMyers|JayMyers]]: I release all of my contributions to the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== Related ==
* '''hproduct'''
* [[hproduct-issues]]
* [[hproduct-faq]]
* [[hproduct-examples]]
* [[hproduct-recipes]]

* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

[[Category:Draft Specifications]]
[[Category:hProduct]]

hproduct

2009-04-24T16:41:36Z

JayMyers: removing condition

<entry-title>hProduct</entry-title>
{{DraftSpecification}}
__TOC__
hProduct is a microformat suitable for publishing and embedding product data. hProduct is one of several open microformats standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

==hProduct Microformat Draft Specification==

; Editors/Authors
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

; Contributors
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

== Status ==
Draft, version 0.2.

== Introduction ==
The web is a thriving consumer marketplace with a plethora of manufacturers and vendors scattered across the globe. Sifting through massive amounts of unstructured product data is a difficult task for both browsers and machines alike. The hProduct microformat gives structure to this metadata by providing constructs to identify universal product attributes, plus a mechanism to accomodate the wide variation in product attributes.

The hProduct microformat can assist consumers, manufacturers and retailers in a number of ways. If a browser or application understands that a specific web page contains the hProduct microformat, it can inform and help facilitate the best product choice by the consumer to fulfill their needs. An adpoted, open standard will ensure the correct product data is published between manufacturers and retailers, to the benefit of the consumer. Bringing order and structure to product data makes it easy for people and organizations to list the products and services they offer, and easy for web services to consume that product data for analysis and syndication.

=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

=== Inspiration and Acknowledgment ===
Many thanks go out to the contributors who laid the foundation for the current hProduct draft spec.

=== Scope ===
Giving details about a particular product is sometimes very complex as parameters are different for books and CDs than they are for iPods or cars. It should be very easy to mark up an item using hProduct and the syntax should be simple yet flexible enough for more advanced applications.

=== Out of Scope ===
This microformat does not intend to replicate any of the content proposed within [[hListing]] and would defer all money/transactional matters to that microformat. This microformat also does not attempt to specify a product ontology, or category-specific attributes; instead, it aims to create a framework to allow for flexible expression of both.

== Format ==
{{rfc-2119-intro}}

=== In General ===
The hProduct format is based on a set of fields common to numerous ecommerce sites and formats in use today on the web.

=== Schema ===
The hProduct schema consists of the following (see existing class names for reference):

*hproduct
** brand. optional. text. can also use [[hcard|hCard]] for manufacturer.
** category. optional. text. can also use rel-tag. re-used from [[hcard|hCard]].
** price. optional. floating point number. can use currency format.
** description. optional. text. can also include valid HTML markup. re-used from [[hreview|hReview]].
** fn. '''required.''' text. product name or title. re-used from [[hcard|hCard]].
** photo. optional. image element or link. re-used from [[hcard|hCard]].
** url. optional. href. can contain rel-tag rel='product'. re-used from [[hcard|hCard]].
** review. optional. [[hreview|hReview]], or [[aggregate-microformat-template-examples|hReview-aggregate]].
** listing. optional. [[hlisting|hListing]], or [[aggregate-microformat-template-examples|hListing-aggregate]].
** identifier. optional.
*** type. required. - examples:
**** model
**** mpn
**** upc
**** isbn
**** issn
**** ean
**** jan
**** sn
**** vin
**** sku
*** value. required. - label may be implied

=== Field details ===
Class names <code class="class-name">category</code>, <code class="class-name">fn</code>, <code class="class-name">photo</code>, <code class="class-name">url</code> are reused from [[hcard|hCard]]. <code class="class-name">description</code> is reused from [[hreview|hReview]].

The fields of the hProduct schema represent the following:

*'''<code class="class-name">hproduct::</code>''' Root class name
*'''<code class="class-name">brand::</code>''' the class name brand is used identify brand of the product. {{should}} use [[hcard|hCard]] for manufacturer name. {{must}} be singular.
*'''<code class="class-name">category::</code>''' the class name category identifies product category. {{may}} use [[rel-tag]] microformat. {{may}} be plural to represent multiple categories.
*'''<code class="class-name">price::</code>''' the class name price is used to indicate the price of the product. {{must}} be singular.
*'''<code class="class-name">description::</code>''' the class name description is used to describe the product. {{must}} be singular.
*'''<code class="class-name">fn::</code>''' product text name. {{must}} be singular.
*'''<code class="class-name">photo::</code>''' the class name photo {{may}} be applied to an <img> or <a> element. {{may}} be plural.
*'''<code class="class-name">url::</code>''' the class name url {{should}} refer to the web page associated with product details. {{may}} use [[rel-tag]], rel='product'. {{must}} be singular.
*'''<code class="class-name">review::</code>''' the class name review identifies review(s) for the product. {{should}} use [[hreview|hReview]]. {{may}} be plural.
*'''<code class="class-name">listing::</code>''' the class name listing identifies product listings. {{should}} use [[hlisting|hListing]]. {{may}} be plural.
*'''<code class="class-name">identifier::</code>''' the identifier structure is used to describe product identifiers like Model, UPC or SKU, and is designed to accommodate new or as-yet-unidentified identifiers. {{should}} be singular.
**'''<code class="class-name">type::</code>''' the class name type identifies the identifier type.
**'''<code class="class-name">value::</code>''' label {{may}} be implied

=== Additional Details ===
'''Note:''' If hProduct markup is used in a "standalone" fashion (eg. a manufacturer site that's not commerce enabled, strictly informational), it is assumed that the price attribute represents the manufacturer's suggested retail price. Any transactional (commerce) representation of price should be delegated to [[hlisting|hListing]].

''Internationalization'': Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. Note that (X)HTML LANG attribute rules still apply as usual, for multilingual aggregators of hProduct.

=== Relationships with other microformats ===
Products can be complex structures with attributes and features that may fall outside the bounds of the proposed hProduct microformat. Care has been taken to provide just enough attributes to accurately represent products while not overloading the hProduct spec. This means that complete semantic solutions would rely on using hProduct in combination with other microformats to achieve their goals. Through [[hproduct-examples#Coded_examples|examples]] (see also: [[hproduct-recipes|recipes]]) and [[hproduct-examples#Analysis_of_Product.2FCommerce_Sites|analysis]], there are some clear relationships between hProduct and these microformats:

* [[hlisting|hListing]] :: provides additional context to the transaction side of a product, including crucial elements like "price".
* [[hReview|hReview]]/hAggregate(concept) :: research shows that many commerce sites include product reviews, and they are often aggregated to provide overall ratings and reviews on the web. Utilizing these microformats can provide additional data around a product or service.
* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a product.

Of course, these are just a few of many that could be used with the hProduct microformat.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hproduct</dt>
<dd>Used to identify and describe metadata universally common to products.</dd>
<dt>availability</dt>
<dd>The details around the availability of the product.</dd>
<dt>brand</dt>
<dd>The brand name of the product.</dd>
<dt>category</dt>
<dd>The product category/ categories the product belongs to.</dd>
<dt>condition</dt>
<dd>The condition of the product.</dd>
<dt>fn</dt>
<dd>The common name of the product.</dd>
<dt>photo</dt>
<dd>Accompanying image of the product.</dd>
<dt>url</dt>
<dd>A link to the product details.</dd>
<dt>identifier</dt>
<dd>The product identifier like Model, SKU, ISBN, or EAN associated with the product</dd>
</dl>
</dd>
</dl>
</pre>

=== Notes ===
This section is informative.
*...

=== Examples in Production ===
* Description of [http://jay.beweep.com/index.php/2008/10/14/reviving-shop-urls-with-hproduct BestBuy.com implementation]

=== Other examples ===

==== Simple Product ====

The Pick of Destiny
by Tenacious D
The Pick of Destiny is the highly anticipated soundtrack to the upcoming
New Line Cinema comedy, Tenacious D in the Pick of Destiny. An epic
musical adventure, the film follows Tenacious D (Jack Black and Kyle Gass)
on their quest to obtain the Pick and become The Greatest Band on Earth.
Released: November 14, 2006
Label: Sony
UPC: 82796948912

<pre><nowiki><div class="hproduct">
<h4 class="name">The Pick of Destiny</h4>
<h5 class="p-v">by <span class="property artist">Tenacious D</span></h5>
<p class="description summary">The Pick of Destiny is the highly
anticipated soundtrack to the upcoming New Line Cinema comedy, Tenacious
D in the Pick of Destiny. An epic musical adventure, the film follows
Tenacious D (Jack Black and Kyle Gass) on their quest to obtain the Pick
and become The Greatest Band on Earth.</p>
<ul>
<li class="p-v"><span class="property">Released</span>:
<span class="value"><abbr title="2006-11-14T12:00:01-05:00">November
14, 2006</abbr></span></li>
<li>Label: <span class="brand">Sony</span></li>
<li class="p-v"><span class="property">UPC</span>:
<span class="value">82796948912</span></li>
</ul>
</div></nowiki></pre>

* more complicated examples can be found at [[hproduct-examples|hProduct examples]]

== Copyright ==
* [[User:JayMyers|JayMyers]]: I release all of my contributions to the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== Related ==
* '''hproduct'''
* [[hproduct-issues]]
* [[hproduct-faq]]
* [[hproduct-examples]]
* [[hproduct-recipes]]

* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

[[Category:Draft Specifications]]
[[Category:hProduct]]

hproduct

2009-04-24T16:40:54Z

JayMyers: editing schema, removing condition and availability

<entry-title>hProduct</entry-title>
{{DraftSpecification}}
__TOC__
hProduct is a microformat suitable for publishing and embedding product data. hProduct is one of several open microformats standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

==hProduct Microformat Draft Specification==

; Editors/Authors
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

; Contributors
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

== Status ==
Draft, version 0.2.

== Introduction ==
The web is a thriving consumer marketplace with a plethora of manufacturers and vendors scattered across the globe. Sifting through massive amounts of unstructured product data is a difficult task for both browsers and machines alike. The hProduct microformat gives structure to this metadata by providing constructs to identify universal product attributes, plus a mechanism to accomodate the wide variation in product attributes.

The hProduct microformat can assist consumers, manufacturers and retailers in a number of ways. If a browser or application understands that a specific web page contains the hProduct microformat, it can inform and help facilitate the best product choice by the consumer to fulfill their needs. An adpoted, open standard will ensure the correct product data is published between manufacturers and retailers, to the benefit of the consumer. Bringing order and structure to product data makes it easy for people and organizations to list the products and services they offer, and easy for web services to consume that product data for analysis and syndication.

=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

=== Inspiration and Acknowledgment ===
Many thanks go out to the contributors who laid the foundation for the current hProduct draft spec.

=== Scope ===
Giving details about a particular product is sometimes very complex as parameters are different for books and CDs than they are for iPods or cars. It should be very easy to mark up an item using hProduct and the syntax should be simple yet flexible enough for more advanced applications.

=== Out of Scope ===
This microformat does not intend to replicate any of the content proposed within [[hListing]] and would defer all money/transactional matters to that microformat. This microformat also does not attempt to specify a product ontology, or category-specific attributes; instead, it aims to create a framework to allow for flexible expression of both.

== Format ==
{{rfc-2119-intro}}

=== In General ===
The hProduct format is based on a set of fields common to numerous ecommerce sites and formats in use today on the web.

=== Schema ===
The hProduct schema consists of the following (see existing class names for reference):

*hproduct
** brand. optional. text. can also use [[hcard|hCard]] for manufacturer.
** category. optional. text. can also use rel-tag. re-used from [[hcard|hCard]].
** price. optional. floating point number. can use currency format.
** description. optional. text. can also include valid HTML markup. re-used from [[hreview|hReview]].
** fn. '''required.''' text. product name or title. re-used from [[hcard|hCard]].
** photo. optional. image element or link. re-used from [[hcard|hCard]].
** url. optional. href. can contain rel-tag rel='product'. re-used from [[hcard|hCard]].
** review. optional. [[hreview|hReview]], or [[aggregate-microformat-template-examples|hReview-aggregate]].
** listing. optional. [[hlisting|hListing]], or [[aggregate-microformat-template-examples|hListing-aggregate]].
** identifier. optional.
*** type. required. - examples:
**** model
**** mpn
**** upc
**** isbn
**** issn
**** ean
**** jan
**** sn
**** vin
**** sku
*** value. required. - label may be implied

=== Field details ===
Class names <code class="class-name">category</code>, <code class="class-name">fn</code>, <code class="class-name">photo</code>, <code class="class-name">url</code> are reused from [[hcard|hCard]]. <code class="class-name">description</code> is reused from [[hreview|hReview]].

The fields of the hProduct schema represent the following:

*'''<code class="class-name">hproduct::</code>''' Root class name
*'''<code class="class-name">brand::</code>''' the class name brand is used identify brand of the product. {{should}} use [[hcard|hCard]] for manufacturer name. {{must}} be singular.
*'''<code class="class-name">category::</code>''' the class name category identifies product category. {{may}} use [[rel-tag]] microformat. {{may}} be plural to represent multiple categories.
*'''<code class="class-name">price::</code>''' the class name price is used to indicate the price of the product. {{must}} be singular.
*'''<code class="class-name">condition::</code>''' the class name condition identifies the product condition. {{may}} include text like "new", "used", "refurbished".{{must}} be singular.
*'''<code class="class-name">description::</code>''' the class name description is used to describe the product. {{must}} be singular.
*'''<code class="class-name">fn::</code>''' product text name. {{must}} be singular.
*'''<code class="class-name">photo::</code>''' the class name photo {{may}} be applied to an <img> or <a> element. {{may}} be plural.
*'''<code class="class-name">url::</code>''' the class name url {{should}} refer to the web page associated with product details. {{may}} use [[rel-tag]], rel='product'. {{must}} be singular.
*'''<code class="class-name">review::</code>''' the class name review identifies review(s) for the product. {{should}} use [[hreview|hReview]]. {{may}} be plural.
*'''<code class="class-name">listing::</code>''' the class name listing identifies product listings. {{should}} use [[hlisting|hListing]]. {{may}} be plural.
*'''<code class="class-name">identifier::</code>''' the identifier structure is used to describe product identifiers like Model, UPC or SKU, and is designed to accommodate new or as-yet-unidentified identifiers. {{should}} be singular.
**'''<code class="class-name">type::</code>''' the class name type identifies the identifier type.
**'''<code class="class-name">value::</code>''' label {{may}} be implied

=== Additional Details ===
'''Note:''' If hProduct markup is used in a "standalone" fashion (eg. a manufacturer site that's not commerce enabled, strictly informational), it is assumed that the price attribute represents the manufacturer's suggested retail price. Any transactional (commerce) representation of price should be delegated to [[hlisting|hListing]].

''Internationalization'': Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. Note that (X)HTML LANG attribute rules still apply as usual, for multilingual aggregators of hProduct.

=== Relationships with other microformats ===
Products can be complex structures with attributes and features that may fall outside the bounds of the proposed hProduct microformat. Care has been taken to provide just enough attributes to accurately represent products while not overloading the hProduct spec. This means that complete semantic solutions would rely on using hProduct in combination with other microformats to achieve their goals. Through [[hproduct-examples#Coded_examples|examples]] (see also: [[hproduct-recipes|recipes]]) and [[hproduct-examples#Analysis_of_Product.2FCommerce_Sites|analysis]], there are some clear relationships between hProduct and these microformats:

* [[hlisting|hListing]] :: provides additional context to the transaction side of a product, including crucial elements like "price".
* [[hReview|hReview]]/hAggregate(concept) :: research shows that many commerce sites include product reviews, and they are often aggregated to provide overall ratings and reviews on the web. Utilizing these microformats can provide additional data around a product or service.
* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a product.

Of course, these are just a few of many that could be used with the hProduct microformat.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hproduct</dt>
<dd>Used to identify and describe metadata universally common to products.</dd>
<dt>availability</dt>
<dd>The details around the availability of the product.</dd>
<dt>brand</dt>
<dd>The brand name of the product.</dd>
<dt>category</dt>
<dd>The product category/ categories the product belongs to.</dd>
<dt>condition</dt>
<dd>The condition of the product.</dd>
<dt>fn</dt>
<dd>The common name of the product.</dd>
<dt>photo</dt>
<dd>Accompanying image of the product.</dd>
<dt>url</dt>
<dd>A link to the product details.</dd>
<dt>identifier</dt>
<dd>The product identifier like Model, SKU, ISBN, or EAN associated with the product</dd>
</dl>
</dd>
</dl>
</pre>

=== Notes ===
This section is informative.
*...

=== Examples in Production ===
* Description of [http://jay.beweep.com/index.php/2008/10/14/reviving-shop-urls-with-hproduct BestBuy.com implementation]

=== Other examples ===

==== Simple Product ====

The Pick of Destiny
by Tenacious D
The Pick of Destiny is the highly anticipated soundtrack to the upcoming
New Line Cinema comedy, Tenacious D in the Pick of Destiny. An epic
musical adventure, the film follows Tenacious D (Jack Black and Kyle Gass)
on their quest to obtain the Pick and become The Greatest Band on Earth.
Released: November 14, 2006
Label: Sony
UPC: 82796948912

<pre><nowiki><div class="hproduct">
<h4 class="name">The Pick of Destiny</h4>
<h5 class="p-v">by <span class="property artist">Tenacious D</span></h5>
<p class="description summary">The Pick of Destiny is the highly
anticipated soundtrack to the upcoming New Line Cinema comedy, Tenacious
D in the Pick of Destiny. An epic musical adventure, the film follows
Tenacious D (Jack Black and Kyle Gass) on their quest to obtain the Pick
and become The Greatest Band on Earth.</p>
<ul>
<li class="p-v"><span class="property">Released</span>:
<span class="value"><abbr title="2006-11-14T12:00:01-05:00">November
14, 2006</abbr></span></li>
<li>Label: <span class="brand">Sony</span></li>
<li class="p-v"><span class="property">UPC</span>:
<span class="value">82796948912</span></li>
</ul>
</div></nowiki></pre>

* more complicated examples can be found at [[hproduct-examples|hProduct examples]]

== Copyright ==
* [[User:JayMyers|JayMyers]]: I release all of my contributions to the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== Related ==
* '''hproduct'''
* [[hproduct-issues]]
* [[hproduct-faq]]
* [[hproduct-examples]]
* [[hproduct-recipes]]

* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

[[Category:Draft Specifications]]
[[Category:hProduct]]

hproduct

2009-04-24T16:38:59Z

JayMyers: adding review, listing, price

<entry-title>hProduct</entry-title>
{{DraftSpecification}}
__TOC__
hProduct is a microformat suitable for publishing and embedding product data. hProduct is one of several open microformats standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

==hProduct Microformat Draft Specification==

; Editors/Authors
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

; Contributors
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

== Status ==
Draft, version 0.2.

== Introduction ==
The web is a thriving consumer marketplace with a plethora of manufacturers and vendors scattered across the globe. Sifting through massive amounts of unstructured product data is a difficult task for both browsers and machines alike. The hProduct microformat gives structure to this metadata by providing constructs to identify universal product attributes, plus a mechanism to accomodate the wide variation in product attributes.

The hProduct microformat can assist consumers, manufacturers and retailers in a number of ways. If a browser or application understands that a specific web page contains the hProduct microformat, it can inform and help facilitate the best product choice by the consumer to fulfill their needs. An adpoted, open standard will ensure the correct product data is published between manufacturers and retailers, to the benefit of the consumer. Bringing order and structure to product data makes it easy for people and organizations to list the products and services they offer, and easy for web services to consume that product data for analysis and syndication.

=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

=== Inspiration and Acknowledgment ===
Many thanks go out to the contributors who laid the foundation for the current hProduct draft spec.

=== Scope ===
Giving details about a particular product is sometimes very complex as parameters are different for books and CDs than they are for iPods or cars. It should be very easy to mark up an item using hProduct and the syntax should be simple yet flexible enough for more advanced applications.

=== Out of Scope ===
This microformat does not intend to replicate any of the content proposed within [[hListing]] and would defer all money/transactional matters to that microformat. This microformat also does not attempt to specify a product ontology, or category-specific attributes; instead, it aims to create a framework to allow for flexible expression of both.

== Format ==
{{rfc-2119-intro}}

=== In General ===
The hProduct format is based on a set of fields common to numerous ecommerce sites and formats in use today on the web.

=== Schema ===
The hProduct schema consists of the following (see existing class names for reference):

*hproduct
** availability. optional. text. can be further refined by type (instore, online, preorder, backorder, specialorder).
** brand. optional. text. can also use [[hcard|hCard]] for manufacturer.
** category. optional. text. can also use rel-tag. re-used from [[hcard|hCard]].
** price. optional. floating point number. can use currency format.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** description. optional. text. can also include valid HTML markup. re-used from [[hreview|hReview]].
** fn. '''required.''' text. product name or title. re-used from [[hcard|hCard]].
** photo. optional. image element or link. re-used from [[hcard|hCard]].
** url. optional. href. can contain rel-tag rel='product'. re-used from [[hcard|hCard]].
** review. optional. [[hreview|hReview]], or [[aggregate-microformat-template-examples|hReview-aggregate]].
** listing. optional. [[hlisting|hListing]], or [[aggregate-microformat-template-examples|hListing-aggregate]].
** identifier. optional.
*** type. required. - examples:
**** model
**** mpn
**** upc
**** isbn
**** issn
**** ean
**** jan
**** sn
**** vin
**** sku
*** value. required. - label may be implied

=== Field details ===
Class names <code class="class-name">category</code>, <code class="class-name">fn</code>, <code class="class-name">photo</code>, <code class="class-name">url</code> are reused from [[hcard|hCard]]. <code class="class-name">description</code> is reused from [[hreview|hReview]].

The fields of the hProduct schema represent the following:

*'''<code class="class-name">hproduct::</code>''' Root class name
*'''<code class="class-name">brand::</code>''' the class name brand is used identify brand of the product. {{should}} use [[hcard|hCard]] for manufacturer name. {{must}} be singular.
*'''<code class="class-name">category::</code>''' the class name category identifies product category. {{may}} use [[rel-tag]] microformat. {{may}} be plural to represent multiple categories.
*'''<code class="class-name">price::</code>''' the class name price is used to indicate the price of the product. {{must}} be singular.
*'''<code class="class-name">condition::</code>''' the class name condition identifies the product condition. {{may}} include text like "new", "used", "refurbished".{{must}} be singular.
*'''<code class="class-name">description::</code>''' the class name description is used to describe the product. {{must}} be singular.
*'''<code class="class-name">fn::</code>''' product text name. {{must}} be singular.
*'''<code class="class-name">photo::</code>''' the class name photo {{may}} be applied to an <img> or <a> element. {{may}} be plural.
*'''<code class="class-name">url::</code>''' the class name url {{should}} refer to the web page associated with product details. {{may}} use [[rel-tag]], rel='product'. {{must}} be singular.
*'''<code class="class-name">review::</code>''' the class name review identifies review(s) for the product. {{should}} use [[hreview|hReview]]. {{may}} be plural.
*'''<code class="class-name">listing::</code>''' the class name listing identifies product listings. {{should}} use [[hlisting|hListing]]. {{may}} be plural.
*'''<code class="class-name">identifier::</code>''' the identifier structure is used to describe product identifiers like Model, UPC or SKU, and is designed to accommodate new or as-yet-unidentified identifiers. {{should}} be singular.
**'''<code class="class-name">type::</code>''' the class name type identifies the identifier type.
**'''<code class="class-name">value::</code>''' label {{may}} be implied

=== Additional Details ===
'''Note:''' If hProduct markup is used in a "standalone" fashion (eg. a manufacturer site that's not commerce enabled, strictly informational), it is assumed that the price attribute represents the manufacturer's suggested retail price. Any transactional (commerce) representation of price should be delegated to [[hlisting|hListing]].

''Internationalization'': Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. Note that (X)HTML LANG attribute rules still apply as usual, for multilingual aggregators of hProduct.

=== Relationships with other microformats ===
Products can be complex structures with attributes and features that may fall outside the bounds of the proposed hProduct microformat. Care has been taken to provide just enough attributes to accurately represent products while not overloading the hProduct spec. This means that complete semantic solutions would rely on using hProduct in combination with other microformats to achieve their goals. Through [[hproduct-examples#Coded_examples|examples]] (see also: [[hproduct-recipes|recipes]]) and [[hproduct-examples#Analysis_of_Product.2FCommerce_Sites|analysis]], there are some clear relationships between hProduct and these microformats:

* [[hlisting|hListing]] :: provides additional context to the transaction side of a product, including crucial elements like "price".
* [[hReview|hReview]]/hAggregate(concept) :: research shows that many commerce sites include product reviews, and they are often aggregated to provide overall ratings and reviews on the web. Utilizing these microformats can provide additional data around a product or service.
* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a product.

Of course, these are just a few of many that could be used with the hProduct microformat.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hproduct</dt>
<dd>Used to identify and describe metadata universally common to products.</dd>
<dt>availability</dt>
<dd>The details around the availability of the product.</dd>
<dt>brand</dt>
<dd>The brand name of the product.</dd>
<dt>category</dt>
<dd>The product category/ categories the product belongs to.</dd>
<dt>condition</dt>
<dd>The condition of the product.</dd>
<dt>fn</dt>
<dd>The common name of the product.</dd>
<dt>photo</dt>
<dd>Accompanying image of the product.</dd>
<dt>url</dt>
<dd>A link to the product details.</dd>
<dt>identifier</dt>
<dd>The product identifier like Model, SKU, ISBN, or EAN associated with the product</dd>
</dl>
</dd>
</dl>
</pre>

=== Notes ===
This section is informative.
*...

=== Examples in Production ===
* Description of [http://jay.beweep.com/index.php/2008/10/14/reviving-shop-urls-with-hproduct BestBuy.com implementation]

=== Other examples ===

==== Simple Product ====

The Pick of Destiny
by Tenacious D
The Pick of Destiny is the highly anticipated soundtrack to the upcoming
New Line Cinema comedy, Tenacious D in the Pick of Destiny. An epic
musical adventure, the film follows Tenacious D (Jack Black and Kyle Gass)
on their quest to obtain the Pick and become The Greatest Band on Earth.
Released: November 14, 2006
Label: Sony
UPC: 82796948912

<pre><nowiki><div class="hproduct">
<h4 class="name">The Pick of Destiny</h4>
<h5 class="p-v">by <span class="property artist">Tenacious D</span></h5>
<p class="description summary">The Pick of Destiny is the highly
anticipated soundtrack to the upcoming New Line Cinema comedy, Tenacious
D in the Pick of Destiny. An epic musical adventure, the film follows
Tenacious D (Jack Black and Kyle Gass) on their quest to obtain the Pick
and become The Greatest Band on Earth.</p>
<ul>
<li class="p-v"><span class="property">Released</span>:
<span class="value"><abbr title="2006-11-14T12:00:01-05:00">November
14, 2006</abbr></span></li>
<li>Label: <span class="brand">Sony</span></li>
<li class="p-v"><span class="property">UPC</span>:
<span class="value">82796948912</span></li>
</ul>
</div></nowiki></pre>

* more complicated examples can be found at [[hproduct-examples|hProduct examples]]

== Copyright ==
* [[User:JayMyers|JayMyers]]: I release all of my contributions to the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== Related ==
* '''hproduct'''
* [[hproduct-issues]]
* [[hproduct-faq]]
* [[hproduct-examples]]
* [[hproduct-recipes]]

* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

[[Category:Draft Specifications]]
[[Category:hProduct]]

hproduct

2009-04-24T16:34:25Z

JayMyers: additional details

<entry-title>hProduct</entry-title>
{{DraftSpecification}}
__TOC__
hProduct is a microformat suitable for publishing and embedding product data. hProduct is one of several open microformats standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

==hProduct Microformat Draft Specification==

; Editors/Authors
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

; Contributors
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

== Status ==
Draft, version 0.2.

== Introduction ==
The web is a thriving consumer marketplace with a plethora of manufacturers and vendors scattered across the globe. Sifting through massive amounts of unstructured product data is a difficult task for both browsers and machines alike. The hProduct microformat gives structure to this metadata by providing constructs to identify universal product attributes, plus a mechanism to accomodate the wide variation in product attributes.

The hProduct microformat can assist consumers, manufacturers and retailers in a number of ways. If a browser or application understands that a specific web page contains the hProduct microformat, it can inform and help facilitate the best product choice by the consumer to fulfill their needs. An adpoted, open standard will ensure the correct product data is published between manufacturers and retailers, to the benefit of the consumer. Bringing order and structure to product data makes it easy for people and organizations to list the products and services they offer, and easy for web services to consume that product data for analysis and syndication.

=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

=== Inspiration and Acknowledgment ===
Many thanks go out to the contributors who laid the foundation for the current hProduct draft spec.

=== Scope ===
Giving details about a particular product is sometimes very complex as parameters are different for books and CDs than they are for iPods or cars. It should be very easy to mark up an item using hProduct and the syntax should be simple yet flexible enough for more advanced applications.

=== Out of Scope ===
This microformat does not intend to replicate any of the content proposed within [[hListing]] and would defer all money/transactional matters to that microformat. This microformat also does not attempt to specify a product ontology, or category-specific attributes; instead, it aims to create a framework to allow for flexible expression of both.

== Format ==
{{rfc-2119-intro}}

=== In General ===
The hProduct format is based on a set of fields common to numerous ecommerce sites and formats in use today on the web.

=== Schema ===
The hProduct schema consists of the following (see existing class names for reference):

*hproduct
** availability. optional. text. can be further refined by type (instore, online, preorder, backorder, specialorder).
** brand. optional. text. can also use [[hcard|hCard]] for manufacturer.
** category. optional. text. can also use rel-tag. re-used from [[hcard|hCard]].
** price. optional. floating point number. can use currency format.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** description. optional. text. can also include valid HTML markup. re-used from [[hreview|hReview]].
** fn. '''required.''' text. product name or title. re-used from [[hcard|hCard]].
** photo. optional. image element or link. re-used from [[hcard|hCard]].
** url. optional. href. can contain rel-tag rel='product'. re-used from [[hcard|hCard]].
** review. optional. [[hreview|hReview]], or [[aggregate-microformat-template-examples|hReview-aggregate]].
** listing. optional. [[hlisting|hListing]], or [[aggregate-microformat-template-examples|hListing-aggregate]].
** identifier. optional.
*** type. required. - examples:
**** model
**** mpn
**** upc
**** isbn
**** issn
**** ean
**** jan
**** sn
**** vin
**** sku
*** value. required. - label may be implied

=== Field details ===
Class names <code class="class-name">category</code>, <code class="class-name">fn</code>, <code class="class-name">photo</code>, <code class="class-name">url</code> are reused from [[hcard|hCard]]. <code class="class-name">description</code> is reused from [[hreview|hReview]].

The fields of the hProduct schema represent the following:

*'''<code class="class-name">hproduct::</code>''' Root class name
*'''<code class="class-name">availability::</code>''' the class name availability is used to determine availability of product. {{must}} be singular.
*'''<code class="class-name">brand::</code>''' the class name brand is used identify brand of the product. {{should}} use [[hcard|hCard]] for manufacturer name. {{must}} be singular.
*'''<code class="class-name">category::</code>''' the class name category identifies product category. {{may}} use [[rel-tag]] microformat. {{may}} be plural to represent multiple categories.
*'''<code class="class-name">condition::</code>''' the class name condition identifies the product condition. {{may}} include text like "new", "used", "refurbished".{{must}} be singular.
*'''<code class="class-name">description::</code>''' the class name description is used to describe the product. {{must}} be singular.
*'''<code class="class-name">fn::</code>''' product text name. {{must}} be singular.
*'''<code class="class-name">photo::</code>''' the class name photo {{may}} be applied to an <img> or <a> element. {{may}} be plural.
*'''<code class="class-name">url::</code>''' the class name url {{should}} refer to the web page associated with product details. {{may}} use [[rel-tag]], rel='product'. {{must}} be singular.
*'''<code class="class-name">identifier::</code>''' the identifier structure is used to describe product identifiers like Model, UPC or SKU, and is designed to accommodate new or as-yet-unidentified identifiers. {{should}} be singular.
**'''<code class="class-name">type::</code>''' the class name type identifies the identifier type.
**'''<code class="class-name">value::</code>''' label {{may}} be implied

=== Additional Details ===
'''Note:''' If hProduct markup is used in a "standalone" fashion (eg. a manufacturer site that's not commerce enabled, strictly informational), it is assumed that the price attribute represents the manufacturer's suggested retail price. Any transactional (commerce) representation of price should be delegated to [[hlisting|hListing]].

''Internationalization'': Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. Note that (X)HTML LANG attribute rules still apply as usual, for multilingual aggregators of hProduct.

=== Relationships with other microformats ===
Products can be complex structures with attributes and features that may fall outside the bounds of the proposed hProduct microformat. Care has been taken to provide just enough attributes to accurately represent products while not overloading the hProduct spec. This means that complete semantic solutions would rely on using hProduct in combination with other microformats to achieve their goals. Through [[hproduct-examples#Coded_examples|examples]] (see also: [[hproduct-recipes|recipes]]) and [[hproduct-examples#Analysis_of_Product.2FCommerce_Sites|analysis]], there are some clear relationships between hProduct and these microformats:

* [[hlisting|hListing]] :: provides additional context to the transaction side of a product, including crucial elements like "price".
* [[hReview|hReview]]/hAggregate(concept) :: research shows that many commerce sites include product reviews, and they are often aggregated to provide overall ratings and reviews on the web. Utilizing these microformats can provide additional data around a product or service.
* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a product.

Of course, these are just a few of many that could be used with the hProduct microformat.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hproduct</dt>
<dd>Used to identify and describe metadata universally common to products.</dd>
<dt>availability</dt>
<dd>The details around the availability of the product.</dd>
<dt>brand</dt>
<dd>The brand name of the product.</dd>
<dt>category</dt>
<dd>The product category/ categories the product belongs to.</dd>
<dt>condition</dt>
<dd>The condition of the product.</dd>
<dt>fn</dt>
<dd>The common name of the product.</dd>
<dt>photo</dt>
<dd>Accompanying image of the product.</dd>
<dt>url</dt>
<dd>A link to the product details.</dd>
<dt>identifier</dt>
<dd>The product identifier like Model, SKU, ISBN, or EAN associated with the product</dd>
</dl>
</dd>
</dl>
</pre>

=== Notes ===
This section is informative.
*...

=== Examples in Production ===
* Description of [http://jay.beweep.com/index.php/2008/10/14/reviving-shop-urls-with-hproduct BestBuy.com implementation]

=== Other examples ===

==== Simple Product ====

The Pick of Destiny
by Tenacious D
The Pick of Destiny is the highly anticipated soundtrack to the upcoming
New Line Cinema comedy, Tenacious D in the Pick of Destiny. An epic
musical adventure, the film follows Tenacious D (Jack Black and Kyle Gass)
on their quest to obtain the Pick and become The Greatest Band on Earth.
Released: November 14, 2006
Label: Sony
UPC: 82796948912

<pre><nowiki><div class="hproduct">
<h4 class="name">The Pick of Destiny</h4>
<h5 class="p-v">by <span class="property artist">Tenacious D</span></h5>
<p class="description summary">The Pick of Destiny is the highly
anticipated soundtrack to the upcoming New Line Cinema comedy, Tenacious
D in the Pick of Destiny. An epic musical adventure, the film follows
Tenacious D (Jack Black and Kyle Gass) on their quest to obtain the Pick
and become The Greatest Band on Earth.</p>
<ul>
<li class="p-v"><span class="property">Released</span>:
<span class="value"><abbr title="2006-11-14T12:00:01-05:00">November
14, 2006</abbr></span></li>
<li>Label: <span class="brand">Sony</span></li>
<li class="p-v"><span class="property">UPC</span>:
<span class="value">82796948912</span></li>
</ul>
</div></nowiki></pre>

* more complicated examples can be found at [[hproduct-examples|hProduct examples]]

== Copyright ==
* [[User:JayMyers|JayMyers]]: I release all of my contributions to the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== Related ==
* '''hproduct'''
* [[hproduct-issues]]
* [[hproduct-faq]]
* [[hproduct-examples]]
* [[hproduct-recipes]]

* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

[[Category:Draft Specifications]]
[[Category:hProduct]]

hproduct

2009-04-24T16:32:58Z

JayMyers: editing format again

<entry-title>hProduct</entry-title>
{{DraftSpecification}}
__TOC__
hProduct is a microformat suitable for publishing and embedding product data. hProduct is one of several open microformats standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

==hProduct Microformat Draft Specification==

; Editors/Authors
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

; Contributors
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

== Status ==
Draft, version 0.2.

== Introduction ==
The web is a thriving consumer marketplace with a plethora of manufacturers and vendors scattered across the globe. Sifting through massive amounts of unstructured product data is a difficult task for both browsers and machines alike. The hProduct microformat gives structure to this metadata by providing constructs to identify universal product attributes, plus a mechanism to accomodate the wide variation in product attributes.

The hProduct microformat can assist consumers, manufacturers and retailers in a number of ways. If a browser or application understands that a specific web page contains the hProduct microformat, it can inform and help facilitate the best product choice by the consumer to fulfill their needs. An adpoted, open standard will ensure the correct product data is published between manufacturers and retailers, to the benefit of the consumer. Bringing order and structure to product data makes it easy for people and organizations to list the products and services they offer, and easy for web services to consume that product data for analysis and syndication.

=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

=== Inspiration and Acknowledgment ===
Many thanks go out to the contributors who laid the foundation for the current hProduct draft spec.

=== Scope ===
Giving details about a particular product is sometimes very complex as parameters are different for books and CDs than they are for iPods or cars. It should be very easy to mark up an item using hProduct and the syntax should be simple yet flexible enough for more advanced applications.

=== Out of Scope ===
This microformat does not intend to replicate any of the content proposed within [[hListing]] and would defer all money/transactional matters to that microformat. This microformat also does not attempt to specify a product ontology, or category-specific attributes; instead, it aims to create a framework to allow for flexible expression of both.

== Format ==
{{rfc-2119-intro}}

=== In General ===
The hProduct format is based on a set of fields common to numerous ecommerce sites and formats in use today on the web.

=== Schema ===
The hProduct schema consists of the following (see existing class names for reference):

*hproduct
** availability. optional. text. can be further refined by type (instore, online, preorder, backorder, specialorder).
** brand. optional. text. can also use [[hcard|hCard]] for manufacturer.
** category. optional. text. can also use rel-tag. re-used from [[hcard|hCard]].
** price. optional. floating point number. can use currency format.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** description. optional. text. can also include valid HTML markup. re-used from [[hreview|hReview]].
** fn. '''required.''' text. product name or title. re-used from [[hcard|hCard]].
** photo. optional. image element or link. re-used from [[hcard|hCard]].
** url. optional. href. can contain rel-tag rel='product'. re-used from [[hcard|hCard]].
** review. optional. [[hreview|hReview]], or [[aggregate-microformat-template-examples|hReview-aggregate]].
** listing. optional. [[hlisting|hListing]], or [[aggregate-microformat-template-examples|hListing-aggregate]].
** identifier. optional.
*** type. required. - examples:
**** model
**** mpn
**** upc
**** isbn
**** issn
**** ean
**** jan
**** sn
**** vin
**** sku
*** value. required. - label may be implied

=== Field details ===
Class names <code class="class-name">category</code>, <code class="class-name">fn</code>, <code class="class-name">photo</code>, <code class="class-name">url</code> are reused from [[hcard|hCard]]. <code class="class-name">description</code> is reused from [[hreview|hReview]].

The fields of the hProduct schema represent the following:

*'''<code class="class-name">hproduct::</code>''' Root class name
*'''<code class="class-name">availability::</code>''' the class name availability is used to determine availability of product. {{must}} be singular.
*'''<code class="class-name">brand::</code>''' the class name brand is used identify brand of the product. {{should}} use [[hcard|hCard]] for manufacturer name. {{must}} be singular.
*'''<code class="class-name">category::</code>''' the class name category identifies product category. {{may}} use [[rel-tag]] microformat. {{may}} be plural to represent multiple categories.
*'''<code class="class-name">condition::</code>''' the class name condition identifies the product condition. {{may}} include text like "new", "used", "refurbished".{{must}} be singular.
*'''<code class="class-name">description::</code>''' the class name description is used to describe the product. {{must}} be singular.
*'''<code class="class-name">fn::</code>''' product text name. {{must}} be singular.
*'''<code class="class-name">photo::</code>''' the class name photo {{may}} be applied to an <img> or <a> element. {{may}} be plural.
*'''<code class="class-name">url::</code>''' the class name url {{should}} refer to the web page associated with product details. {{may}} use [[rel-tag]], rel='product'. {{must}} be singular.
*'''<code class="class-name">identifier::</code>''' the identifier structure is used to describe product identifiers like Model, UPC or SKU, and is designed to accommodate new or as-yet-unidentified identifiers. {{should}} be singular.
**'''<code class="class-name">type::</code>''' the class name type identifies the identifier type.
**'''<code class="class-name">value::</code>''' label {{may}} be implied

=== Additional Details ===
'''Note:''' If hProduct markup is used in a "standalone" fashion, it is assumed that the price attribute represents the manufacturer's suggested retail price. Any transactional (commerce) represntation of price should be
delegated to [[hlisting|hListing]]

''Internationalization'': Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. Note that (X)HTML LANG attribute rules still apply as usual, for multilingual aggregators of hProduct.

=== Relationships with other microformats ===
Products can be complex structures with attributes and features that may fall outside the bounds of the proposed hProduct microformat. Care has been taken to provide just enough attributes to accurately represent products while not overloading the hProduct spec. This means that complete semantic solutions would rely on using hProduct in combination with other microformats to achieve their goals. Through [[hproduct-examples#Coded_examples|examples]] (see also: [[hproduct-recipes|recipes]]) and [[hproduct-examples#Analysis_of_Product.2FCommerce_Sites|analysis]], there are some clear relationships between hProduct and these microformats:

* [[hlisting|hListing]] :: provides additional context to the transaction side of a product, including crucial elements like "price".
* [[hReview|hReview]]/hAggregate(concept) :: research shows that many commerce sites include product reviews, and they are often aggregated to provide overall ratings and reviews on the web. Utilizing these microformats can provide additional data around a product or service.
* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a product.

Of course, these are just a few of many that could be used with the hProduct microformat.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hproduct</dt>
<dd>Used to identify and describe metadata universally common to products.</dd>
<dt>availability</dt>
<dd>The details around the availability of the product.</dd>
<dt>brand</dt>
<dd>The brand name of the product.</dd>
<dt>category</dt>
<dd>The product category/ categories the product belongs to.</dd>
<dt>condition</dt>
<dd>The condition of the product.</dd>
<dt>fn</dt>
<dd>The common name of the product.</dd>
<dt>photo</dt>
<dd>Accompanying image of the product.</dd>
<dt>url</dt>
<dd>A link to the product details.</dd>
<dt>identifier</dt>
<dd>The product identifier like Model, SKU, ISBN, or EAN associated with the product</dd>
</dl>
</dd>
</dl>
</pre>

=== Notes ===
This section is informative.
*...

=== Examples in Production ===
* Description of [http://jay.beweep.com/index.php/2008/10/14/reviving-shop-urls-with-hproduct BestBuy.com implementation]

=== Other examples ===

==== Simple Product ====

The Pick of Destiny
by Tenacious D
The Pick of Destiny is the highly anticipated soundtrack to the upcoming
New Line Cinema comedy, Tenacious D in the Pick of Destiny. An epic
musical adventure, the film follows Tenacious D (Jack Black and Kyle Gass)
on their quest to obtain the Pick and become The Greatest Band on Earth.
Released: November 14, 2006
Label: Sony
UPC: 82796948912

<pre><nowiki><div class="hproduct">
<h4 class="name">The Pick of Destiny</h4>
<h5 class="p-v">by <span class="property artist">Tenacious D</span></h5>
<p class="description summary">The Pick of Destiny is the highly
anticipated soundtrack to the upcoming New Line Cinema comedy, Tenacious
D in the Pick of Destiny. An epic musical adventure, the film follows
Tenacious D (Jack Black and Kyle Gass) on their quest to obtain the Pick
and become The Greatest Band on Earth.</p>
<ul>
<li class="p-v"><span class="property">Released</span>:
<span class="value"><abbr title="2006-11-14T12:00:01-05:00">November
14, 2006</abbr></span></li>
<li>Label: <span class="brand">Sony</span></li>
<li class="p-v"><span class="property">UPC</span>:
<span class="value">82796948912</span></li>
</ul>
</div></nowiki></pre>

* more complicated examples can be found at [[hproduct-examples|hProduct examples]]

== Copyright ==
* [[User:JayMyers|JayMyers]]: I release all of my contributions to the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== Related ==
* '''hproduct'''
* [[hproduct-issues]]
* [[hproduct-faq]]
* [[hproduct-examples]]
* [[hproduct-recipes]]

* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

[[Category:Draft Specifications]]
[[Category:hProduct]]

hproduct

2009-04-24T16:31:42Z

JayMyers: editing format

<entry-title>hProduct</entry-title>
{{DraftSpecification}}
__TOC__
hProduct is a microformat suitable for publishing and embedding product data. hProduct is one of several open microformats standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

==hProduct Microformat Draft Specification==

; Editors/Authors
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

; Contributors
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

== Status ==
Draft, version 0.2.

== Introduction ==
The web is a thriving consumer marketplace with a plethora of manufacturers and vendors scattered across the globe. Sifting through massive amounts of unstructured product data is a difficult task for both browsers and machines alike. The hProduct microformat gives structure to this metadata by providing constructs to identify universal product attributes, plus a mechanism to accomodate the wide variation in product attributes.

The hProduct microformat can assist consumers, manufacturers and retailers in a number of ways. If a browser or application understands that a specific web page contains the hProduct microformat, it can inform and help facilitate the best product choice by the consumer to fulfill their needs. An adpoted, open standard will ensure the correct product data is published between manufacturers and retailers, to the benefit of the consumer. Bringing order and structure to product data makes it easy for people and organizations to list the products and services they offer, and easy for web services to consume that product data for analysis and syndication.

=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

=== Inspiration and Acknowledgment ===
Many thanks go out to the contributors who laid the foundation for the current hProduct draft spec.

=== Scope ===
Giving details about a particular product is sometimes very complex as parameters are different for books and CDs than they are for iPods or cars. It should be very easy to mark up an item using hProduct and the syntax should be simple yet flexible enough for more advanced applications.

=== Out of Scope ===
This microformat does not intend to replicate any of the content proposed within [[hListing]] and would defer all money/transactional matters to that microformat. This microformat also does not attempt to specify a product ontology, or category-specific attributes; instead, it aims to create a framework to allow for flexible expression of both.

== Format ==
{{rfc-2119-intro}}

=== In General ===
The hProduct format is based on a set of fields common to numerous ecommerce sites and formats in use today on the web.

=== Schema ===
The hProduct schema consists of the following (see existing class names for reference):

*hproduct
** availability. optional. text. can be further refined by type (instore, online, preorder, backorder, specialorder).
** brand. optional. text. can also use [[hcard|hCard]] for manufacturer.
** category. optional. text. can also use rel-tag. re-used from [[hcard|hCard]].
** price. optional. floating point number. can use currency format.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** description. optional. text. can also include valid HTML markup. re-used from [[hreview|hReview]].
** fn. '''required.''' text. product name or title. re-used from [[hcard|hCard]].
** photo. optional. image element or link. re-used from [[hcard|hCard]].
** url. optional. href. can contain rel-tag rel='product'. re-used from [[hcard|hCard]].
** review. optional. [[hreview|hReview]], or hReview-aggregate, see: [[aggregate-microformat-template-examples|aggregate microformat examples]].
** listing. optional. [[hlisting|hListing]], or hListing-aggregate, see: [[aggregate-microformat-template-examples|aggregate microformat examples]].
** identifier. optional.
*** type. required. - examples:
**** model
**** mpn
**** upc
**** isbn
**** issn
**** ean
**** jan
**** sn
**** vin
**** sku
*** value. required. - label may be implied

=== Field details ===
Class names <code class="class-name">category</code>, <code class="class-name">fn</code>, <code class="class-name">photo</code>, <code class="class-name">url</code> are reused from [[hcard|hCard]]. <code class="class-name">description</code> is reused from [[hreview|hReview]].

The fields of the hProduct schema represent the following:

*'''<code class="class-name">hproduct::</code>''' Root class name
*'''<code class="class-name">availability::</code>''' the class name availability is used to determine availability of product. {{must}} be singular.
*'''<code class="class-name">brand::</code>''' the class name brand is used identify brand of the product. {{should}} use [[hcard|hCard]] for manufacturer name. {{must}} be singular.
*'''<code class="class-name">category::</code>''' the class name category identifies product category. {{may}} use [[rel-tag]] microformat. {{may}} be plural to represent multiple categories.
*'''<code class="class-name">condition::</code>''' the class name condition identifies the product condition. {{may}} include text like "new", "used", "refurbished".{{must}} be singular.
*'''<code class="class-name">description::</code>''' the class name description is used to describe the product. {{must}} be singular.
*'''<code class="class-name">fn::</code>''' product text name. {{must}} be singular.
*'''<code class="class-name">photo::</code>''' the class name photo {{may}} be applied to an <img> or <a> element. {{may}} be plural.
*'''<code class="class-name">url::</code>''' the class name url {{should}} refer to the web page associated with product details. {{may}} use [[rel-tag]], rel='product'. {{must}} be singular.
*'''<code class="class-name">identifier::</code>''' the identifier structure is used to describe product identifiers like Model, UPC or SKU, and is designed to accommodate new or as-yet-unidentified identifiers. {{should}} be singular.
**'''<code class="class-name">type::</code>''' the class name type identifies the identifier type.
**'''<code class="class-name">value::</code>''' label {{may}} be implied

=== Additional Details ===
'''Note:''' If hProduct markup is used in a "standalone" fashion, it is assumed that the price attribute represents the manufacturer's suggested retail price. Any transactional (commerce) represntation of price should be
delegated to [[hlisting|hListing]]

''Internationalization'': Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. Note that (X)HTML LANG attribute rules still apply as usual, for multilingual aggregators of hProduct.

=== Relationships with other microformats ===
Products can be complex structures with attributes and features that may fall outside the bounds of the proposed hProduct microformat. Care has been taken to provide just enough attributes to accurately represent products while not overloading the hProduct spec. This means that complete semantic solutions would rely on using hProduct in combination with other microformats to achieve their goals. Through [[hproduct-examples#Coded_examples|examples]] (see also: [[hproduct-recipes|recipes]]) and [[hproduct-examples#Analysis_of_Product.2FCommerce_Sites|analysis]], there are some clear relationships between hProduct and these microformats:

* [[hlisting|hListing]] :: provides additional context to the transaction side of a product, including crucial elements like "price".
* [[hReview|hReview]]/hAggregate(concept) :: research shows that many commerce sites include product reviews, and they are often aggregated to provide overall ratings and reviews on the web. Utilizing these microformats can provide additional data around a product or service.
* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a product.

Of course, these are just a few of many that could be used with the hProduct microformat.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hproduct</dt>
<dd>Used to identify and describe metadata universally common to products.</dd>
<dt>availability</dt>
<dd>The details around the availability of the product.</dd>
<dt>brand</dt>
<dd>The brand name of the product.</dd>
<dt>category</dt>
<dd>The product category/ categories the product belongs to.</dd>
<dt>condition</dt>
<dd>The condition of the product.</dd>
<dt>fn</dt>
<dd>The common name of the product.</dd>
<dt>photo</dt>
<dd>Accompanying image of the product.</dd>
<dt>url</dt>
<dd>A link to the product details.</dd>
<dt>identifier</dt>
<dd>The product identifier like Model, SKU, ISBN, or EAN associated with the product</dd>
</dl>
</dd>
</dl>
</pre>

=== Notes ===
This section is informative.
*...

=== Examples in Production ===
* Description of [http://jay.beweep.com/index.php/2008/10/14/reviving-shop-urls-with-hproduct BestBuy.com implementation]

=== Other examples ===

==== Simple Product ====

The Pick of Destiny
by Tenacious D
The Pick of Destiny is the highly anticipated soundtrack to the upcoming
New Line Cinema comedy, Tenacious D in the Pick of Destiny. An epic
musical adventure, the film follows Tenacious D (Jack Black and Kyle Gass)
on their quest to obtain the Pick and become The Greatest Band on Earth.
Released: November 14, 2006
Label: Sony
UPC: 82796948912

<pre><nowiki><div class="hproduct">
<h4 class="name">The Pick of Destiny</h4>
<h5 class="p-v">by <span class="property artist">Tenacious D</span></h5>
<p class="description summary">The Pick of Destiny is the highly
anticipated soundtrack to the upcoming New Line Cinema comedy, Tenacious
D in the Pick of Destiny. An epic musical adventure, the film follows
Tenacious D (Jack Black and Kyle Gass) on their quest to obtain the Pick
and become The Greatest Band on Earth.</p>
<ul>
<li class="p-v"><span class="property">Released</span>:
<span class="value"><abbr title="2006-11-14T12:00:01-05:00">November
14, 2006</abbr></span></li>
<li>Label: <span class="brand">Sony</span></li>
<li class="p-v"><span class="property">UPC</span>:
<span class="value">82796948912</span></li>
</ul>
</div></nowiki></pre>

* more complicated examples can be found at [[hproduct-examples|hProduct examples]]

== Copyright ==
* [[User:JayMyers|JayMyers]]: I release all of my contributions to the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== Related ==
* '''hproduct'''
* [[hproduct-issues]]
* [[hproduct-faq]]
* [[hproduct-examples]]
* [[hproduct-recipes]]

* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

[[Category:Draft Specifications]]
[[Category:hProduct]]

hproduct

2009-04-24T16:30:56Z

JayMyers: adding note around standalone usage of hproduct/ price

<entry-title>hProduct</entry-title>
{{DraftSpecification}}
__TOC__
hProduct is a microformat suitable for publishing and embedding product data. hProduct is one of several open microformats standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

==hProduct Microformat Draft Specification==

; Editors/Authors
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

; Contributors
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

== Status ==
Draft, version 0.2.

== Introduction ==
The web is a thriving consumer marketplace with a plethora of manufacturers and vendors scattered across the globe. Sifting through massive amounts of unstructured product data is a difficult task for both browsers and machines alike. The hProduct microformat gives structure to this metadata by providing constructs to identify universal product attributes, plus a mechanism to accomodate the wide variation in product attributes.

The hProduct microformat can assist consumers, manufacturers and retailers in a number of ways. If a browser or application understands that a specific web page contains the hProduct microformat, it can inform and help facilitate the best product choice by the consumer to fulfill their needs. An adpoted, open standard will ensure the correct product data is published between manufacturers and retailers, to the benefit of the consumer. Bringing order and structure to product data makes it easy for people and organizations to list the products and services they offer, and easy for web services to consume that product data for analysis and syndication.

=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

=== Inspiration and Acknowledgment ===
Many thanks go out to the contributors who laid the foundation for the current hProduct draft spec.

=== Scope ===
Giving details about a particular product is sometimes very complex as parameters are different for books and CDs than they are for iPods or cars. It should be very easy to mark up an item using hProduct and the syntax should be simple yet flexible enough for more advanced applications.

=== Out of Scope ===
This microformat does not intend to replicate any of the content proposed within [[hListing]] and would defer all money/transactional matters to that microformat. This microformat also does not attempt to specify a product ontology, or category-specific attributes; instead, it aims to create a framework to allow for flexible expression of both.

== Format ==
{{rfc-2119-intro}}

=== In General ===
The hProduct format is based on a set of fields common to numerous ecommerce sites and formats in use today on the web.

=== Schema ===
The hProduct schema consists of the following (see existing class names for reference):

*hproduct
** availability. optional. text. can be further refined by type (instore, online, preorder, backorder, specialorder).
** brand. optional. text. can also use [[hcard|hCard]] for manufacturer.
** category. optional. text. can also use rel-tag. re-used from [[hcard|hCard]].
** price. optional. floating point number. can use currency format.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** description. optional. text. can also include valid HTML markup. re-used from [[hreview|hReview]].
** fn. '''required.''' text. product name or title. re-used from [[hcard|hCard]].
** photo. optional. image element or link. re-used from [[hcard|hCard]].
** url. optional. href. can contain rel-tag rel='product'. re-used from [[hcard|hCard]].
** review. optional. [[hreview|hReview]], or hReview-aggregate, see: [[aggregate-microformat-template-examples|aggregate microformat examples]]
** listing. optional. [[hlisting|hListing]], or hListing-aggregate, see: [[aggregate-microformat-template-examples|aggregate microformat examples]]
** identifier. optional.
*** type. required. - examples:
**** model
**** mpn
**** upc
**** isbn
**** issn
**** ean
**** jan
**** sn
**** vin
**** sku
*** value. required. - label may be implied

=== Field details ===
Class names <code class="class-name">category</code>, <code class="class-name">fn</code>, <code class="class-name">photo</code>, <code class="class-name">url</code> are reused from [[hcard|hCard]]. <code class="class-name">description</code> is reused from [[hreview|hReview]].

The fields of the hProduct schema represent the following:

*'''<code class="class-name">hproduct::</code>''' Root class name
*'''<code class="class-name">availability::</code>''' the class name availability is used to determine availability of product. {{must}} be singular.
*'''<code class="class-name">brand::</code>''' the class name brand is used identify brand of the product. {{should}} use [[hcard|hCard]] for manufacturer name. {{must}} be singular.
*'''<code class="class-name">category::</code>''' the class name category identifies product category. {{may}} use [[rel-tag]] microformat. {{may}} be plural to represent multiple categories.
*'''<code class="class-name">condition::</code>''' the class name condition identifies the product condition. {{may}} include text like "new", "used", "refurbished".{{must}} be singular.
*'''<code class="class-name">description::</code>''' the class name description is used to describe the product. {{must}} be singular.
*'''<code class="class-name">fn::</code>''' product text name. {{must}} be singular.
*'''<code class="class-name">photo::</code>''' the class name photo {{may}} be applied to an <img> or <a> element. {{may}} be plural.
*'''<code class="class-name">url::</code>''' the class name url {{should}} refer to the web page associated with product details. {{may}} use [[rel-tag]], rel='product'. {{must}} be singular.
*'''<code class="class-name">identifier::</code>''' the identifier structure is used to describe product identifiers like Model, UPC or SKU, and is designed to accommodate new or as-yet-unidentified identifiers. {{should}} be singular.
**'''<code class="class-name">type::</code>''' the class name type identifies the identifier type.
**'''<code class="class-name">value::</code>''' label {{may}} be implied

=== Additional Details ===
'''Note:''' If hProduct markup is used in a "standalone" fashion, it is assumed that the price attribute represents the manufacturer's suggested retail price. Any transactional (commerce) represntation of price should be
delegated to [[hlisting|hListing]]

''Internationalization'': Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. Note that (X)HTML LANG attribute rules still apply as usual, for multilingual aggregators of hProduct.

=== Relationships with other microformats ===
Products can be complex structures with attributes and features that may fall outside the bounds of the proposed hProduct microformat. Care has been taken to provide just enough attributes to accurately represent products while not overloading the hProduct spec. This means that complete semantic solutions would rely on using hProduct in combination with other microformats to achieve their goals. Through [[hproduct-examples#Coded_examples|examples]] (see also: [[hproduct-recipes|recipes]]) and [[hproduct-examples#Analysis_of_Product.2FCommerce_Sites|analysis]], there are some clear relationships between hProduct and these microformats:

* [[hlisting|hListing]] :: provides additional context to the transaction side of a product, including crucial elements like "price".
* [[hReview|hReview]]/hAggregate(concept) :: research shows that many commerce sites include product reviews, and they are often aggregated to provide overall ratings and reviews on the web. Utilizing these microformats can provide additional data around a product or service.
* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a product.

Of course, these are just a few of many that could be used with the hProduct microformat.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hproduct</dt>
<dd>Used to identify and describe metadata universally common to products.</dd>
<dt>availability</dt>
<dd>The details around the availability of the product.</dd>
<dt>brand</dt>
<dd>The brand name of the product.</dd>
<dt>category</dt>
<dd>The product category/ categories the product belongs to.</dd>
<dt>condition</dt>
<dd>The condition of the product.</dd>
<dt>fn</dt>
<dd>The common name of the product.</dd>
<dt>photo</dt>
<dd>Accompanying image of the product.</dd>
<dt>url</dt>
<dd>A link to the product details.</dd>
<dt>identifier</dt>
<dd>The product identifier like Model, SKU, ISBN, or EAN associated with the product</dd>
</dl>
</dd>
</dl>
</pre>

=== Notes ===
This section is informative.
*...

=== Examples in Production ===
* Description of [http://jay.beweep.com/index.php/2008/10/14/reviving-shop-urls-with-hproduct BestBuy.com implementation]

=== Other examples ===

==== Simple Product ====

The Pick of Destiny
by Tenacious D
The Pick of Destiny is the highly anticipated soundtrack to the upcoming
New Line Cinema comedy, Tenacious D in the Pick of Destiny. An epic
musical adventure, the film follows Tenacious D (Jack Black and Kyle Gass)
on their quest to obtain the Pick and become The Greatest Band on Earth.
Released: November 14, 2006
Label: Sony
UPC: 82796948912

<pre><nowiki><div class="hproduct">
<h4 class="name">The Pick of Destiny</h4>
<h5 class="p-v">by <span class="property artist">Tenacious D</span></h5>
<p class="description summary">The Pick of Destiny is the highly
anticipated soundtrack to the upcoming New Line Cinema comedy, Tenacious
D in the Pick of Destiny. An epic musical adventure, the film follows
Tenacious D (Jack Black and Kyle Gass) on their quest to obtain the Pick
and become The Greatest Band on Earth.</p>
<ul>
<li class="p-v"><span class="property">Released</span>:
<span class="value"><abbr title="2006-11-14T12:00:01-05:00">November
14, 2006</abbr></span></li>
<li>Label: <span class="brand">Sony</span></li>
<li class="p-v"><span class="property">UPC</span>:
<span class="value">82796948912</span></li>
</ul>
</div></nowiki></pre>

* more complicated examples can be found at [[hproduct-examples|hProduct examples]]

== Copyright ==
* [[User:JayMyers|JayMyers]]: I release all of my contributions to the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== Related ==
* '''hproduct'''
* [[hproduct-issues]]
* [[hproduct-faq]]
* [[hproduct-examples]]
* [[hproduct-recipes]]

* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

[[Category:Draft Specifications]]
[[Category:hProduct]]

hproduct

2009-04-24T16:29:50Z

JayMyers: editing format

<entry-title>hProduct</entry-title>
{{DraftSpecification}}
__TOC__
hProduct is a microformat suitable for publishing and embedding product data. hProduct is one of several open microformats standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

==hProduct Microformat Draft Specification==

; Editors/Authors
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

; Contributors
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

== Status ==
Draft, version 0.2.

== Introduction ==
The web is a thriving consumer marketplace with a plethora of manufacturers and vendors scattered across the globe. Sifting through massive amounts of unstructured product data is a difficult task for both browsers and machines alike. The hProduct microformat gives structure to this metadata by providing constructs to identify universal product attributes, plus a mechanism to accomodate the wide variation in product attributes.

The hProduct microformat can assist consumers, manufacturers and retailers in a number of ways. If a browser or application understands that a specific web page contains the hProduct microformat, it can inform and help facilitate the best product choice by the consumer to fulfill their needs. An adpoted, open standard will ensure the correct product data is published between manufacturers and retailers, to the benefit of the consumer. Bringing order and structure to product data makes it easy for people and organizations to list the products and services they offer, and easy for web services to consume that product data for analysis and syndication.

=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

=== Inspiration and Acknowledgment ===
Many thanks go out to the contributors who laid the foundation for the current hProduct draft spec.

=== Scope ===
Giving details about a particular product is sometimes very complex as parameters are different for books and CDs than they are for iPods or cars. It should be very easy to mark up an item using hProduct and the syntax should be simple yet flexible enough for more advanced applications.

=== Out of Scope ===
This microformat does not intend to replicate any of the content proposed within [[hListing]] and would defer all money/transactional matters to that microformat. This microformat also does not attempt to specify a product ontology, or category-specific attributes; instead, it aims to create a framework to allow for flexible expression of both.

== Format ==
{{rfc-2119-intro}}

=== In General ===
The hProduct format is based on a set of fields common to numerous ecommerce sites and formats in use today on the web.

=== Schema ===
The hProduct schema consists of the following (see existing class names for reference):

*hproduct
** availability. optional. text. can be further refined by type (instore, online, preorder, backorder, specialorder).
** brand. optional. text. can also use [[hcard|hCard]] for manufacturer.
** category. optional. text. can also use rel-tag. re-used from [[hcard|hCard]].
** price. optional. floating point number. can use currency format.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** description. optional. text. can also include valid HTML markup. re-used from [[hreview|hReview]].
** fn. '''required.''' text. product name or title. re-used from [[hcard|hCard]].
** photo. optional. image element or link. re-used from [[hcard|hCard]].
** url. optional. href. can contain rel-tag rel='product'. re-used from [[hcard|hCard]].
** review. optional. [[hreview|hReview]], or hReview-aggregate, see: [[aggregate-microformat-template-examples|aggregate microformat examples]]
** listing. optional. [[hlisting|hListing]], or hListing-aggregate, see: [[aggregate-microformat-template-examples|aggregate microformat examples]]
** identifier. optional.
*** type. required. - examples:
**** model
**** mpn
**** upc
**** isbn
**** issn
**** ean
**** jan
**** sn
**** vin
**** sku
*** value. required. - label may be implied

=== Field details ===
Class names <code class="class-name">category</code>, <code class="class-name">fn</code>, <code class="class-name">photo</code>, <code class="class-name">url</code> are reused from [[hcard|hCard]]. <code class="class-name">description</code> is reused from [[hreview|hReview]].

The fields of the hProduct schema represent the following:

*'''<code class="class-name">hproduct::</code>''' Root class name
*'''<code class="class-name">availability::</code>''' the class name availability is used to determine availability of product. {{must}} be singular.
*'''<code class="class-name">brand::</code>''' the class name brand is used identify brand of the product. {{should}} use [[hcard|hCard]] for manufacturer name. {{must}} be singular.
*'''<code class="class-name">category::</code>''' the class name category identifies product category. {{may}} use [[rel-tag]] microformat. {{may}} be plural to represent multiple categories.
*'''<code class="class-name">condition::</code>''' the class name condition identifies the product condition. {{may}} include text like "new", "used", "refurbished".{{must}} be singular.
*'''<code class="class-name">description::</code>''' the class name description is used to describe the product. {{must}} be singular.
*'''<code class="class-name">fn::</code>''' product text name. {{must}} be singular.
*'''<code class="class-name">photo::</code>''' the class name photo {{may}} be applied to an <img> or <a> element. {{may}} be plural.
*'''<code class="class-name">url::</code>''' the class name url {{should}} refer to the web page associated with product details. {{may}} use [[rel-tag]], rel='product'. {{must}} be singular.
*'''<code class="class-name">identifier::</code>''' the identifier structure is used to describe product identifiers like Model, UPC or SKU, and is designed to accommodate new or as-yet-unidentified identifiers. {{should}} be singular.
**'''<code class="class-name">type::</code>''' the class name type identifies the identifier type.
**'''<code class="class-name">value::</code>''' label {{may}} be implied

=== Additional Details ===
''Internationalization'': Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. Note that (X)HTML LANG attribute rules still apply as usual, for multilingual aggregators of hProduct.

=== Relationships with other microformats ===
Products can be complex structures with attributes and features that may fall outside the bounds of the proposed hProduct microformat. Care has been taken to provide just enough attributes to accurately represent products while not overloading the hProduct spec. This means that complete semantic solutions would rely on using hProduct in combination with other microformats to achieve their goals. Through [[hproduct-examples#Coded_examples|examples]] (see also: [[hproduct-recipes|recipes]]) and [[hproduct-examples#Analysis_of_Product.2FCommerce_Sites|analysis]], there are some clear relationships between hProduct and these microformats:

* [[hlisting|hListing]] :: provides additional context to the transaction side of a product, including crucial elements like "price".
* [[hReview|hReview]]/hAggregate(concept) :: research shows that many commerce sites include product reviews, and they are often aggregated to provide overall ratings and reviews on the web. Utilizing these microformats can provide additional data around a product or service.
* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a product.

Of course, these are just a few of many that could be used with the hProduct microformat.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hproduct</dt>
<dd>Used to identify and describe metadata universally common to products.</dd>
<dt>availability</dt>
<dd>The details around the availability of the product.</dd>
<dt>brand</dt>
<dd>The brand name of the product.</dd>
<dt>category</dt>
<dd>The product category/ categories the product belongs to.</dd>
<dt>condition</dt>
<dd>The condition of the product.</dd>
<dt>fn</dt>
<dd>The common name of the product.</dd>
<dt>photo</dt>
<dd>Accompanying image of the product.</dd>
<dt>url</dt>
<dd>A link to the product details.</dd>
<dt>identifier</dt>
<dd>The product identifier like Model, SKU, ISBN, or EAN associated with the product</dd>
</dl>
</dd>
</dl>
</pre>

=== Notes ===
This section is informative.
*...

=== Examples in Production ===
* Description of [http://jay.beweep.com/index.php/2008/10/14/reviving-shop-urls-with-hproduct BestBuy.com implementation]

=== Other examples ===

==== Simple Product ====

The Pick of Destiny
by Tenacious D
The Pick of Destiny is the highly anticipated soundtrack to the upcoming
New Line Cinema comedy, Tenacious D in the Pick of Destiny. An epic
musical adventure, the film follows Tenacious D (Jack Black and Kyle Gass)
on their quest to obtain the Pick and become The Greatest Band on Earth.
Released: November 14, 2006
Label: Sony
UPC: 82796948912

<pre><nowiki><div class="hproduct">
<h4 class="name">The Pick of Destiny</h4>
<h5 class="p-v">by <span class="property artist">Tenacious D</span></h5>
<p class="description summary">The Pick of Destiny is the highly
anticipated soundtrack to the upcoming New Line Cinema comedy, Tenacious
D in the Pick of Destiny. An epic musical adventure, the film follows
Tenacious D (Jack Black and Kyle Gass) on their quest to obtain the Pick
and become The Greatest Band on Earth.</p>
<ul>
<li class="p-v"><span class="property">Released</span>:
<span class="value"><abbr title="2006-11-14T12:00:01-05:00">November
14, 2006</abbr></span></li>
<li>Label: <span class="brand">Sony</span></li>
<li class="p-v"><span class="property">UPC</span>:
<span class="value">82796948912</span></li>
</ul>
</div></nowiki></pre>

* more complicated examples can be found at [[hproduct-examples|hProduct examples]]

== Copyright ==
* [[User:JayMyers|JayMyers]]: I release all of my contributions to the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== Related ==
* '''hproduct'''
* [[hproduct-issues]]
* [[hproduct-faq]]
* [[hproduct-examples]]
* [[hproduct-recipes]]

* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

[[Category:Draft Specifications]]
[[Category:hProduct]]

hproduct

2009-04-24T16:29:24Z

JayMyers: editing format

<entry-title>hProduct</entry-title>
{{DraftSpecification}}
__TOC__
hProduct is a microformat suitable for publishing and embedding product data. hProduct is one of several open microformats standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

==hProduct Microformat Draft Specification==

; Editors/Authors
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

; Contributors
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

== Status ==
Draft, version 0.2.

== Introduction ==
The web is a thriving consumer marketplace with a plethora of manufacturers and vendors scattered across the globe. Sifting through massive amounts of unstructured product data is a difficult task for both browsers and machines alike. The hProduct microformat gives structure to this metadata by providing constructs to identify universal product attributes, plus a mechanism to accomodate the wide variation in product attributes.

The hProduct microformat can assist consumers, manufacturers and retailers in a number of ways. If a browser or application understands that a specific web page contains the hProduct microformat, it can inform and help facilitate the best product choice by the consumer to fulfill their needs. An adpoted, open standard will ensure the correct product data is published between manufacturers and retailers, to the benefit of the consumer. Bringing order and structure to product data makes it easy for people and organizations to list the products and services they offer, and easy for web services to consume that product data for analysis and syndication.

=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

=== Inspiration and Acknowledgment ===
Many thanks go out to the contributors who laid the foundation for the current hProduct draft spec.

=== Scope ===
Giving details about a particular product is sometimes very complex as parameters are different for books and CDs than they are for iPods or cars. It should be very easy to mark up an item using hProduct and the syntax should be simple yet flexible enough for more advanced applications.

=== Out of Scope ===
This microformat does not intend to replicate any of the content proposed within [[hListing]] and would defer all money/transactional matters to that microformat. This microformat also does not attempt to specify a product ontology, or category-specific attributes; instead, it aims to create a framework to allow for flexible expression of both.

== Format ==
{{rfc-2119-intro}}

=== In General ===
The hProduct format is based on a set of fields common to numerous ecommerce sites and formats in use today on the web.

=== Schema ===
The hProduct schema consists of the following (see existing class names for reference):

*hproduct
** availability. optional. text. can be further refined by type (instore, online, preorder, backorder, specialorder).
** brand. optional. text. can also use [[hcard|hCard]] for manufacturer.
** category. optional. text. can also use rel-tag. re-used from [[hcard|hCard]].
** price. optional. floating point number. can use currency format.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** description. optional. text. can also include valid HTML markup. re-used from [[hreview|hReview]].
** fn. '''required.''' text. product name or title. re-used from [[hcard|hCard]].
** photo. optional. image element or link. re-used from [[hcard|hCard]].
** url. optional. href. can contain rel-tag rel='product'. re-used from [[hcard|hCard]].
** review. optional. [[hreview|hReview]], or hReview-aggregate. see [[aggregate-microformat-template-examples|aggregate microformat examples]]
** listing. optional. [[hlisting|hListing]], or hListing-aggregate. see [[aggregate-microformat-template-examples|aggregate microformat examples]]
** identifier. optional.
*** type. required. - examples:
**** model
**** mpn
**** upc
**** isbn
**** issn
**** ean
**** jan
**** sn
**** vin
**** sku
*** value. required. - label may be implied

=== Field details ===
Class names <code class="class-name">category</code>, <code class="class-name">fn</code>, <code class="class-name">photo</code>, <code class="class-name">url</code> are reused from [[hcard|hCard]]. <code class="class-name">description</code> is reused from [[hreview|hReview]].

The fields of the hProduct schema represent the following:

*'''<code class="class-name">hproduct::</code>''' Root class name
*'''<code class="class-name">availability::</code>''' the class name availability is used to determine availability of product. {{must}} be singular.
*'''<code class="class-name">brand::</code>''' the class name brand is used identify brand of the product. {{should}} use [[hcard|hCard]] for manufacturer name. {{must}} be singular.
*'''<code class="class-name">category::</code>''' the class name category identifies product category. {{may}} use [[rel-tag]] microformat. {{may}} be plural to represent multiple categories.
*'''<code class="class-name">condition::</code>''' the class name condition identifies the product condition. {{may}} include text like "new", "used", "refurbished".{{must}} be singular.
*'''<code class="class-name">description::</code>''' the class name description is used to describe the product. {{must}} be singular.
*'''<code class="class-name">fn::</code>''' product text name. {{must}} be singular.
*'''<code class="class-name">photo::</code>''' the class name photo {{may}} be applied to an <img> or <a> element. {{may}} be plural.
*'''<code class="class-name">url::</code>''' the class name url {{should}} refer to the web page associated with product details. {{may}} use [[rel-tag]], rel='product'. {{must}} be singular.
*'''<code class="class-name">identifier::</code>''' the identifier structure is used to describe product identifiers like Model, UPC or SKU, and is designed to accommodate new or as-yet-unidentified identifiers. {{should}} be singular.
**'''<code class="class-name">type::</code>''' the class name type identifies the identifier type.
**'''<code class="class-name">value::</code>''' label {{may}} be implied

=== Additional Details ===
''Internationalization'': Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. Note that (X)HTML LANG attribute rules still apply as usual, for multilingual aggregators of hProduct.

=== Relationships with other microformats ===
Products can be complex structures with attributes and features that may fall outside the bounds of the proposed hProduct microformat. Care has been taken to provide just enough attributes to accurately represent products while not overloading the hProduct spec. This means that complete semantic solutions would rely on using hProduct in combination with other microformats to achieve their goals. Through [[hproduct-examples#Coded_examples|examples]] (see also: [[hproduct-recipes|recipes]]) and [[hproduct-examples#Analysis_of_Product.2FCommerce_Sites|analysis]], there are some clear relationships between hProduct and these microformats:

* [[hlisting|hListing]] :: provides additional context to the transaction side of a product, including crucial elements like "price".
* [[hReview|hReview]]/hAggregate(concept) :: research shows that many commerce sites include product reviews, and they are often aggregated to provide overall ratings and reviews on the web. Utilizing these microformats can provide additional data around a product or service.
* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a product.

Of course, these are just a few of many that could be used with the hProduct microformat.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hproduct</dt>
<dd>Used to identify and describe metadata universally common to products.</dd>
<dt>availability</dt>
<dd>The details around the availability of the product.</dd>
<dt>brand</dt>
<dd>The brand name of the product.</dd>
<dt>category</dt>
<dd>The product category/ categories the product belongs to.</dd>
<dt>condition</dt>
<dd>The condition of the product.</dd>
<dt>fn</dt>
<dd>The common name of the product.</dd>
<dt>photo</dt>
<dd>Accompanying image of the product.</dd>
<dt>url</dt>
<dd>A link to the product details.</dd>
<dt>identifier</dt>
<dd>The product identifier like Model, SKU, ISBN, or EAN associated with the product</dd>
</dl>
</dd>
</dl>
</pre>

=== Notes ===
This section is informative.
*...

=== Examples in Production ===
* Description of [http://jay.beweep.com/index.php/2008/10/14/reviving-shop-urls-with-hproduct BestBuy.com implementation]

=== Other examples ===

==== Simple Product ====

The Pick of Destiny
by Tenacious D
The Pick of Destiny is the highly anticipated soundtrack to the upcoming
New Line Cinema comedy, Tenacious D in the Pick of Destiny. An epic
musical adventure, the film follows Tenacious D (Jack Black and Kyle Gass)
on their quest to obtain the Pick and become The Greatest Band on Earth.
Released: November 14, 2006
Label: Sony
UPC: 82796948912

<pre><nowiki><div class="hproduct">
<h4 class="name">The Pick of Destiny</h4>
<h5 class="p-v">by <span class="property artist">Tenacious D</span></h5>
<p class="description summary">The Pick of Destiny is the highly
anticipated soundtrack to the upcoming New Line Cinema comedy, Tenacious
D in the Pick of Destiny. An epic musical adventure, the film follows
Tenacious D (Jack Black and Kyle Gass) on their quest to obtain the Pick
and become The Greatest Band on Earth.</p>
<ul>
<li class="p-v"><span class="property">Released</span>:
<span class="value"><abbr title="2006-11-14T12:00:01-05:00">November
14, 2006</abbr></span></li>
<li>Label: <span class="brand">Sony</span></li>
<li class="p-v"><span class="property">UPC</span>:
<span class="value">82796948912</span></li>
</ul>
</div></nowiki></pre>

* more complicated examples can be found at [[hproduct-examples|hProduct examples]]

== Copyright ==
* [[User:JayMyers|JayMyers]]: I release all of my contributions to the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== Related ==
* '''hproduct'''
* [[hproduct-issues]]
* [[hproduct-faq]]
* [[hproduct-examples]]
* [[hproduct-recipes]]

* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

[[Category:Draft Specifications]]
[[Category:hProduct]]

hproduct

2009-04-24T16:28:18Z

JayMyers: updating hproduct schema, adding price back, review and listing new

<entry-title>hProduct</entry-title>
{{DraftSpecification}}
__TOC__
hProduct is a microformat suitable for publishing and embedding product data. hProduct is one of several open microformats standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

==hProduct Microformat Draft Specification==

; Editors/Authors
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

; Contributors
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

== Status ==
Draft, version 0.2.

== Introduction ==
The web is a thriving consumer marketplace with a plethora of manufacturers and vendors scattered across the globe. Sifting through massive amounts of unstructured product data is a difficult task for both browsers and machines alike. The hProduct microformat gives structure to this metadata by providing constructs to identify universal product attributes, plus a mechanism to accomodate the wide variation in product attributes.

The hProduct microformat can assist consumers, manufacturers and retailers in a number of ways. If a browser or application understands that a specific web page contains the hProduct microformat, it can inform and help facilitate the best product choice by the consumer to fulfill their needs. An adpoted, open standard will ensure the correct product data is published between manufacturers and retailers, to the benefit of the consumer. Bringing order and structure to product data makes it easy for people and organizations to list the products and services they offer, and easy for web services to consume that product data for analysis and syndication.

=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

=== Inspiration and Acknowledgment ===
Many thanks go out to the contributors who laid the foundation for the current hProduct draft spec.

=== Scope ===
Giving details about a particular product is sometimes very complex as parameters are different for books and CDs than they are for iPods or cars. It should be very easy to mark up an item using hProduct and the syntax should be simple yet flexible enough for more advanced applications.

=== Out of Scope ===
This microformat does not intend to replicate any of the content proposed within [[hListing]] and would defer all money/transactional matters to that microformat. This microformat also does not attempt to specify a product ontology, or category-specific attributes; instead, it aims to create a framework to allow for flexible expression of both.

== Format ==
{{rfc-2119-intro}}

=== In General ===
The hProduct format is based on a set of fields common to numerous ecommerce sites and formats in use today on the web.

=== Schema ===
The hProduct schema consists of the following (see existing class names for reference):

*hproduct
** availability. optional. text. can be further refined by type (instore, online, preorder, backorder, specialorder).
** brand. optional. text. can also use [[hcard|hCard]] for manufacturer.
** category. optional. text. can also use rel-tag. re-used from [[hcard|hCard]].
** price. optional. floating point number. can use currency format.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** description. optional. text. can also include valid HTML markup. re-used from [[hreview|hReview]].
** fn. '''required.''' text. product name or title. re-used from [[hcard|hCard]].
** photo. optional. image element or link. re-used from [[hcard|hCard]].
** url. optional. href. can contain rel-tag rel='product'. re-used from [[hcard|hCard]].
** review. optional. [[hreview|hReview]] (or hReview-aggregate -- see [[aggregate-microformat-template-examples|aggregate microformat examples]])
** listing. optional. [[hlisting|hListing]] (or hListing-aggregate -- see [[aggregate-microformat-template-examples|aggregate microformat examples]])
** identifier. optional.
*** type. required. - examples:
**** model
**** mpn
**** upc
**** isbn
**** issn
**** ean
**** jan
**** sn
**** vin
**** sku
*** value. required. - label may be implied

=== Field details ===
Class names <code class="class-name">category</code>, <code class="class-name">fn</code>, <code class="class-name">photo</code>, <code class="class-name">url</code> are reused from [[hcard|hCard]]. <code class="class-name">description</code> is reused from [[hreview|hReview]].

The fields of the hProduct schema represent the following:

*'''<code class="class-name">hproduct::</code>''' Root class name
*'''<code class="class-name">availability::</code>''' the class name availability is used to determine availability of product. {{must}} be singular.
*'''<code class="class-name">brand::</code>''' the class name brand is used identify brand of the product. {{should}} use [[hcard|hCard]] for manufacturer name. {{must}} be singular.
*'''<code class="class-name">category::</code>''' the class name category identifies product category. {{may}} use [[rel-tag]] microformat. {{may}} be plural to represent multiple categories.
*'''<code class="class-name">condition::</code>''' the class name condition identifies the product condition. {{may}} include text like "new", "used", "refurbished".{{must}} be singular.
*'''<code class="class-name">description::</code>''' the class name description is used to describe the product. {{must}} be singular.
*'''<code class="class-name">fn::</code>''' product text name. {{must}} be singular.
*'''<code class="class-name">photo::</code>''' the class name photo {{may}} be applied to an <img> or <a> element. {{may}} be plural.
*'''<code class="class-name">url::</code>''' the class name url {{should}} refer to the web page associated with product details. {{may}} use [[rel-tag]], rel='product'. {{must}} be singular.
*'''<code class="class-name">identifier::</code>''' the identifier structure is used to describe product identifiers like Model, UPC or SKU, and is designed to accommodate new or as-yet-unidentified identifiers. {{should}} be singular.
**'''<code class="class-name">type::</code>''' the class name type identifies the identifier type.
**'''<code class="class-name">value::</code>''' label {{may}} be implied

=== Additional Details ===
''Internationalization'': Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. Note that (X)HTML LANG attribute rules still apply as usual, for multilingual aggregators of hProduct.

=== Relationships with other microformats ===
Products can be complex structures with attributes and features that may fall outside the bounds of the proposed hProduct microformat. Care has been taken to provide just enough attributes to accurately represent products while not overloading the hProduct spec. This means that complete semantic solutions would rely on using hProduct in combination with other microformats to achieve their goals. Through [[hproduct-examples#Coded_examples|examples]] (see also: [[hproduct-recipes|recipes]]) and [[hproduct-examples#Analysis_of_Product.2FCommerce_Sites|analysis]], there are some clear relationships between hProduct and these microformats:

* [[hlisting|hListing]] :: provides additional context to the transaction side of a product, including crucial elements like "price".
* [[hReview|hReview]]/hAggregate(concept) :: research shows that many commerce sites include product reviews, and they are often aggregated to provide overall ratings and reviews on the web. Utilizing these microformats can provide additional data around a product or service.
* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a product.

Of course, these are just a few of many that could be used with the hProduct microformat.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hproduct</dt>
<dd>Used to identify and describe metadata universally common to products.</dd>
<dt>availability</dt>
<dd>The details around the availability of the product.</dd>
<dt>brand</dt>
<dd>The brand name of the product.</dd>
<dt>category</dt>
<dd>The product category/ categories the product belongs to.</dd>
<dt>condition</dt>
<dd>The condition of the product.</dd>
<dt>fn</dt>
<dd>The common name of the product.</dd>
<dt>photo</dt>
<dd>Accompanying image of the product.</dd>
<dt>url</dt>
<dd>A link to the product details.</dd>
<dt>identifier</dt>
<dd>The product identifier like Model, SKU, ISBN, or EAN associated with the product</dd>
</dl>
</dd>
</dl>
</pre>

=== Notes ===
This section is informative.
*...

=== Examples in Production ===
* Description of [http://jay.beweep.com/index.php/2008/10/14/reviving-shop-urls-with-hproduct BestBuy.com implementation]

=== Other examples ===

==== Simple Product ====

The Pick of Destiny
by Tenacious D
The Pick of Destiny is the highly anticipated soundtrack to the upcoming
New Line Cinema comedy, Tenacious D in the Pick of Destiny. An epic
musical adventure, the film follows Tenacious D (Jack Black and Kyle Gass)
on their quest to obtain the Pick and become The Greatest Band on Earth.
Released: November 14, 2006
Label: Sony
UPC: 82796948912

<pre><nowiki><div class="hproduct">
<h4 class="name">The Pick of Destiny</h4>
<h5 class="p-v">by <span class="property artist">Tenacious D</span></h5>
<p class="description summary">The Pick of Destiny is the highly
anticipated soundtrack to the upcoming New Line Cinema comedy, Tenacious
D in the Pick of Destiny. An epic musical adventure, the film follows
Tenacious D (Jack Black and Kyle Gass) on their quest to obtain the Pick
and become The Greatest Band on Earth.</p>
<ul>
<li class="p-v"><span class="property">Released</span>:
<span class="value"><abbr title="2006-11-14T12:00:01-05:00">November
14, 2006</abbr></span></li>
<li>Label: <span class="brand">Sony</span></li>
<li class="p-v"><span class="property">UPC</span>:
<span class="value">82796948912</span></li>
</ul>
</div></nowiki></pre>

* more complicated examples can be found at [[hproduct-examples|hProduct examples]]

== Copyright ==
* [[User:JayMyers|JayMyers]]: I release all of my contributions to the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== Related ==
* '''hproduct'''
* [[hproduct-issues]]
* [[hproduct-faq]]
* [[hproduct-examples]]
* [[hproduct-recipes]]

* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

[[Category:Draft Specifications]]
[[Category:hProduct]]

hlisting-brainstorming

2009-04-22T21:06:16Z

JayMyers: unbolding...

<h1>listing microformat brainstorming </h1>
This is brainstorming for a [[hlisting]] microformat per the [[process]].

{{TOC-right}}

=== Revised Base Schema Elements (proposed) ===

*hListing (hlisting)
** listing action. optional. one or more tags, suggested set: sell | rent | trade | meet | announce | offer | wanted | event | service
** lister. optional. hCard | (fn || email || url || tel).
** dtlisted. optional. ISO8601 absolute date time.
** dtexpired. optional. ISO8601 absolute date time.
** price. optional. text. [should include a floating-point number with optional ISO currency codes] - see the currency proposal
** item info. optional. (fn || url || photo || [[geo]] || [[adr]]) | [[hcard|hCard]] (for person or business).
** summary. optional. text.
** '''description'''. required. text with optional valid XHTML markup.
** item tags. optional. keywords or phrases describing the item being offered, using rel-tag
** permalink. optional.
** availability. optional. text.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** shipping. optional. text. text describing shipping and fulfillment

==== Items removed ====
* version. optional. text.

<div class=discussion>
* +1 I'm tending to agree with the removal of version, as in practice it has not been necessary for either [[hReview]] or [[hListing]].[[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
</div>

* item info. optional. (fn || url || photo || geo || adr) | hCard (for person or business).

<div class=discussion>
* Removal of <code>item</code> seems to be a mistake, as that is used to indicate the item itself being listed. E.g., a nested <code>hProduct</code> would be <code><p class='item hproduct'></p></code>. Removal appears to leave no way to include ''what'' is being listed. --[[User:BenWard|BenWard]] 17:38, 16 April 2009 (UTC)
** +1 completely agreed with Ben Ward's point. Wide use of [[hReview]] in the [[hreview-examples-in-wild|wild]] has shown that having an explicit "item" is both necessary and works in practice. [[User:Tantek|Tantek]] 17:40, 16 April 2009 (UTC)
* Indeed it was a mistake... left it out of my edits. Replaced. [[User:JayMyers|JayMyers]] 21:04, 22 April 2009 (UTC)
</div>

==== Items added ====
<div class=discussion>
* Each of the following should cite the analysis made of real world examples that demonstrates the 80%+ use case need, otherwise, they should not be added. [[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
</div>

* availability. optional. text.
* condition. optional. text. examples: 'new', 'used', 'refurbished'.
* shipping. optional. text. text describing shipping and fulfillment

==== Items changed: ====
* listing action => optional. if omitted, action assumed to be sell
* lister => optional. if omitted, the buyer/seller is assumed to be the site where the microformat exists
<div class=discussion>
* In that case, an algorithm should be provided for how to determine the hCard for the lister, if no explicit lister is given. [[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
</div>

hlisting-brainstorming

2009-04-22T21:05:47Z

JayMyers: adding item back

<h1>listing microformat brainstorming </h1>
This is brainstorming for a [[hlisting]] microformat per the [[process]].

{{TOC-right}}

=== Revised Base Schema Elements (proposed) ===

*hListing (hlisting)
** listing action. optional. one or more tags, suggested set: sell | rent | trade | meet | announce | offer | wanted | event | service
** lister. optional. hCard | (fn || email || url || tel).
** dtlisted. optional. ISO8601 absolute date time.
** dtexpired. optional. ISO8601 absolute date time.
** price. optional. text. [should include a floating-point number with optional ISO currency codes] - see the currency proposal
** item info. '''optional'''. (fn || url || photo || [[geo]] || [[adr]]) | [[hcard|hCard]] (for person or business).
** summary. optional. text.
** '''description'''. required. text with optional valid XHTML markup.
** item tags. optional. keywords or phrases describing the item being offered, using rel-tag
** permalink. optional.
** availability. optional. text.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** shipping. optional. text. text describing shipping and fulfillment

==== Items removed ====
* version. optional. text.

<div class=discussion>
* +1 I'm tending to agree with the removal of version, as in practice it has not been necessary for either [[hReview]] or [[hListing]].[[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
</div>

* item info. optional. (fn || url || photo || geo || adr) | hCard (for person or business).

<div class=discussion>
* Removal of <code>item</code> seems to be a mistake, as that is used to indicate the item itself being listed. E.g., a nested <code>hProduct</code> would be <code><p class='item hproduct'></p></code>. Removal appears to leave no way to include ''what'' is being listed. --[[User:BenWard|BenWard]] 17:38, 16 April 2009 (UTC)
** +1 completely agreed with Ben Ward's point. Wide use of [[hReview]] in the [[hreview-examples-in-wild|wild]] has shown that having an explicit "item" is both necessary and works in practice. [[User:Tantek|Tantek]] 17:40, 16 April 2009 (UTC)
* Indeed it was a mistake... left it out of my edits. Replaced. [[User:JayMyers|JayMyers]] 21:04, 22 April 2009 (UTC)
</div>

==== Items added ====
<div class=discussion>
* Each of the following should cite the analysis made of real world examples that demonstrates the 80%+ use case need, otherwise, they should not be added. [[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
</div>

* availability. optional. text.
* condition. optional. text. examples: 'new', 'used', 'refurbished'.
* shipping. optional. text. text describing shipping and fulfillment

==== Items changed: ====
* listing action => optional. if omitted, action assumed to be sell
* lister => optional. if omitted, the buyer/seller is assumed to be the site where the microformat exists
<div class=discussion>
* In that case, an algorithm should be provided for how to determine the hCard for the lister, if no explicit lister is given. [[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
</div>