Microformats Wiki - User contributions [en]

product-brainstorming

2007-06-05T14:18:34Z

Adam Craven: /* Adam Craven */

= Brainstorming for hProduct Microformat =

This is a brainstorm for the hProduct microformat. See also [[hproduct-examples|examples of hProduct]].

== Contributors ==

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

== The Problem ==

There are numerous ways to publish product information on the web, but nothing is stanardized. It would be useful to have standardized product information on the web for creating mash-up applications which could

* allow aggregated product details to be linked to from hListings or hReviews
* match hListings to hReviews
* aggregate product-specific information from across the web
* aggregate and compare like products based on features

== Elements that come up often in practice ==

Examples of elements that might be included because they seem to come up often in user- and CMS-generated product publishing, include the following:

=== Base Elements ===

* name (or fn)
* image (could be sub-categorized)
** thumb (for thumbnail)
** full (for full size image)
** photo (for a photograph)
** illo (for an illustration).
* description (could be sub-categorized)
** summary
** extended
* brand
* uri (or url) - URI for the product at its brand website; not to be confused with the hListing 'permalink'.
* msrp

=== Extensibility ===
Being that so many products in the world have specific charachteristics or properties, we thought it might be wise to create a means of standardizing the listing of that information, setting the stage for possible subformats of hProduct. This could be done by setting up property value pairs or groups using a <code>CLASS</code> of "p-v". It would be possible to offer a few means of doing this.

==== Natural language property-value association ====

<pre><nowiki><p class="p-v">The <span class="property">dimensions</span> of this book are
<span class="value">6½"(<abbr title="width">W</abbr>) ×
12"(<abbr title="height">H</abbr>) ×
1¾"(<abbr title="depth">D</abbr>)</span></p></nowiki></pre>

==== List property-value association (pairs) ====

<pre><nowiki><ul>
<li class="p-v">
<span class="property">Mileage</span>:
<em class="value">34,787</em>
</li>
<li class="p-v">
<span class="property">Year</span>:
<em class="value">2006</em>
</li>
<li class="p-v">
<span class="property">Exterior Color</span>:
<em class="value">Burgundy</em>
</li>
<li class="p-v">
<span class="property">Body Style</span>:
<em class="value">Hatchback</em>
</li>
</ul></nowiki></pre>

==== List property-value association (groups) ====

Note: as a <code>DL</code> contains semantic property-value pairs/groups, setting a <code>CLASS</code> of "p-v" should be enough (reducing extra markup).

<pre><nowiki><dl class="p-v">
<dt>Mileage</dt>
<dd>34,787</dd>
<dt>Color</dt>
<dd>Burgundy (Exterior)</dd>
<dd>Tan (Interior)</dd>
</dl></nowiki></pre>

==== Non-visible property names ====

We have considered the possibility of allowing property names to be invisible to users by allowing the addition of the property name as a class immediately following the "propery" <code>CLASS</code> keyword:

<pre><nowiki><ul class="p-v">
<li class="property mileage">34,787</li>
<li class="property year">2006</li>
<li class="property color-exterior">Burgundy</li>
<li class="property body-style>Hatchback</li>
</ul></nowiki></pre>

Parsing would be a bit trickier, but from the perspective of someone marking up the document, it is pretty simple and straightforward.

=== Suggested Additions ===

* image sub-categorization (could make use of [[media-info|Media microformat]]?):
** thumb (for thumbnail)
** full (for full size image)
** photo (for a photograph)
** illo (for an illustration).
* description sub-categorization:
** summary
** extended
* uri (or url) - URI for the product at its brand website; not to be confused with the hListing 'permalink'.

== Isn't this duplicating hListing and hReview? ==

No, hProduct would not seek to compete with [[hlisting|hListing]] or [[hreview|hReview]], it simply aims to enhance them. In either of these microformats, the <em>item</em> could easily contain the hProduct. Also, hProduct is the more appropriate place for Manufacturer's Suggested Retail Price (MSRP), which is not likely to be the final price of the product being listed. The actual price/sale price/final price should be solely in the domain of hListing.

== Random Thoughts ==

Please add your thoughts & feelings below. If you are interested in getting involved in the development of this microformat. Please contact aaron [at] easy-designs [dot] net and/or join the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats mailing list].

===Ronnos===

Wouldn't the release date of the product be a good addition? I'm writing product re- and previews. I use hReviews to give my opinion about the product, but there's now way to indicate that the product is or is not in stores yet. As far as i can see, the release date is a usefull product attribute, not only usefull in combination with other Microformats, but also for indicating the "age" of a product.

* Release date is a good idea but how to specify it? Is it the date on which the product first becomes available in shops? Would you have a per-region release date (certainly applicable to DVDs, CDs and at least some electronic devices such as gaming consoles) --[[User:SMulcahy|SMulcahy]] 13:38, 15 Feb 2007 (PST)

===Aaron Gustafson===

Actual price, savings, discounts, etc. should be part of hListing instead of hProduct. MSRP (suggested retail price) should be part of the hProduct, however.
*Not all products have a MSRP. [[User:AndyMabbett|Andy Mabbett]] 09:08, 19 Nov 2006 (PST)
**I agree, they don't which is why it should not be required. [[User:AaronGustafson|Aaron Gustafson]] 16:60, 20 Nov 2006 (MST)

===Andy Mabbett===
Please see my [http://microformats.org/discuss/mail/microformats-discuss/2006-November/007281.html proposal, on the mailing list] -- [[User:AndyMabbett|Andy Mabbett]] 09:08, 19 Nov 2006 (PST)
* I agree with the idea of enabling sub-product formats, but am not sure I like the idea of a "wrapper" for hReview or hListing, I think the item should exist ''within'' an instance of one of those microformats. [[User:AaronGustafson|Aaron Gustafson]] 16:60, 20 Nov 2006 (MST)
**There may be more than one review of a product, on one page e.g. [http://www.amazon.co.uk/o/ASIN/B000I0SGSA/ref=pd_rvi_gw_1/026-5782158-8338825] [[User:AndyMabbett|Andy Mabbett]] 00:54, 21 Nov 2006 (PST)

===Adam Craven===

hProduct will definitely be one of the largest microformats.

What about specifications of products, which is important for data aggregation. To categories every type and variation of a product would be mad. So how should the hurdle be crossed, if at all?

The nearest related uF is the citation format, although it isn't overly suited.

===Stephen Mulcahy===

As with microformats in general maybe the approach to take to specifications of products is to let people who need/want them start specifying the ones they are interested in - we don't need an exhaustive universe of potential things categorised. See my posting for some other comments here - http://microformats.org/discuss/mail/microformats-discuss/2007-January/008379.html , in particular note that I think the hard part of this is defining the specifications of individual products. I'm happy to start on the laptop one ... it would be good to have some laptop vendor on board but maybe its too soon for anyone to be interested.

* Some potential subformats (what kind of naming scheme do we want to use here)
** hNotebook (or hProductNotebook ?) - for products like laptops, notebooks, tablets
*** os
*** bundledSoftware
*** size (height, width, depth)
*** weight (units?)
*** processor
*** display
**** size
**** resolution
*** video (for video card)
*** embeddedVideo (boolean)
*** hard drive (maybe manufacturer,model,size? .. eeek is hard drive a hProduct subformat itself?)
*** memory (type and size?)
*** optical drive (types?)
*** battery
*** warranty
*** videoOut (types supported - is it acceptable have a bunch of boolean options for laptop features that may or may not exist on a particular model?)
** hDesktop - for desktop PCs and similar
** hConsole - for gaming consoles such as the Wii, PS3 and XBox360
** hMobilePhone (or hMobileDevice .. not sure we generally want generic subcategory since the whole point of subformats is to give a concrete set of characteristics, or do we want to have nesting of subformats to capture general characteristics at higher levels?).
** hPda (maybe a hMobileDevice .. it starts getting a bit fuzzy here)

Maybe we should talk to some projects like the Linux on Laptops [http://www.linux-laptop.net/] project and get them to encourage contributors to mark-up their laptop reviews in hProductNotebook? --[[User:SMulcahy|SMulcahy]] 07:51, 20 Feb 2007 (PST)

===Robbie van der Blom===
What about unique identifiers for products like ISBN nr. and the UPC codes for a product? My gut feeling is that they should be part of the hProduct format.

With respect to the above, do we really need to talk about hProductNotebook etc. this seems odd.

===Adam Craven===

In relation to the p-v and general property values. The [[abbr-design-pattern]] could be used over the hidden class variable. So
<pre><nowiki>
<h1 class="name">Breitling SuperOcean Chrono</h1>
Water resistant up to <span class="p-v"><abbr class="property value" title="water-resistance">1500m</abbr></span></nowiki></pre>

In this second example, the color is embedded within the name of the shirt itself.
<pre><nowiki><h1 class="name"><span class="p-v"><abbr class="property value" title="color">White</abbr> Coxmoor shirt</h1>
<img src="white-coxmoor-shirt.jpg" rel="image thumb" /></nowiki></pre>

For items such as books, whereby authors sometimes aren't explicitly denoted visibly (http://www.thebookpeople.co.uk/webapp/wcs/stores/servlet/product_10001_10051_47517_100_10014_10013_category_10013), rather inferred by convention. Could arguably still use the abbr pattern:

<pre><nowiki><h1><span class="name">Great Tales From English History</span> - 3 Books</h1>
by <span class="p-v"><abbr class="property value" title="author">Robert Lacey</abbr></span></nowiki></pre>

Or even
<pre><nowiki><h1><span class="name">Great Tales From English History</span> - 3 Books</h1>
<span class="p-v"><abbr class="property" title="author">by</abbr> <span class="value">Robert Lacey</span></span></nowiki></pre>

A final thought to throw in. If the property and values are within the same HTML tag, it might be possible to remove the property & value class, as the p-v indicates a property value relationship itself.

<pre><nowiki><abbr class="p-v" title="author">Robert Lacey</abbr></nowiki></pre>
What do you think?

product-brainstorming

2007-06-04T14:26:19Z

Adam Craven: /* Thoughts on property values */

= Brainstorming for hProduct Microformat =

This is a brainstorm for the hProduct microformat. See also [[hproduct-examples|examples of hProduct]].

== Contributors ==

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

== The Problem ==

There are numerous ways to publish product information on the web, but nothing is stanardized. It would be useful to have standardized product information on the web for creating mash-up applications which could

* allow aggregated product details to be linked to from hListings or hReviews
* match hListings to hReviews
* aggregate product-specific information from across the web
* aggregate and compare like products based on features

== Elements that come up often in practice ==

Examples of elements that might be included because they seem to come up often in user- and CMS-generated product publishing, include the following:

=== Base Elements ===

* name (or fn)
* image (could be sub-categorized)
** thumb (for thumbnail)
** full (for full size image)
** photo (for a photograph)
** illo (for an illustration).
* description (could be sub-categorized)
** summary
** extended
* brand
* uri (or url) - URI for the product at its brand website; not to be confused with the hListing 'permalink'.
* msrp

=== Extensibility ===
Being that so many products in the world have specific charachteristics or properties, we thought it might be wise to create a means of standardizing the listing of that information, setting the stage for possible subformats of hProduct. This could be done by setting up property value pairs or groups using a <code>CLASS</code> of "p-v". It would be possible to offer a few means of doing this.

==== Natural language property-value association ====

<pre><nowiki><p class="p-v">The <span class="property">dimensions</span> of this book are
<span class="value">6½"(<abbr title="width">W</abbr>) ×
12"(<abbr title="height">H</abbr>) ×
1¾"(<abbr title="depth">D</abbr>)</span></p></nowiki></pre>

==== List property-value association (pairs) ====

<pre><nowiki><ul>
<li class="p-v">
<span class="property">Mileage</span>:
<em class="value">34,787</em>
</li>
<li class="p-v">
<span class="property">Year</span>:
<em class="value">2006</em>
</li>
<li class="p-v">
<span class="property">Exterior Color</span>:
<em class="value">Burgundy</em>
</li>
<li class="p-v">
<span class="property">Body Style</span>:
<em class="value">Hatchback</em>
</li>
</ul></nowiki></pre>

==== List property-value association (groups) ====

Note: as a <code>DL</code> contains semantic property-value pairs/groups, setting a <code>CLASS</code> of "p-v" should be enough (reducing extra markup).

<pre><nowiki><dl class="p-v">
<dt>Mileage</dt>
<dd>34,787</dd>
<dt>Color</dt>
<dd>Burgundy (Exterior)</dd>
<dd>Tan (Interior)</dd>
</dl></nowiki></pre>

==== Non-visible property names ====

We have considered the possibility of allowing property names to be invisible to users by allowing the addition of the property name as a class immediately following the "propery" <code>CLASS</code> keyword:

<pre><nowiki><ul class="p-v">
<li class="property mileage">34,787</li>
<li class="property year">2006</li>
<li class="property color-exterior">Burgundy</li>
<li class="property body-style>Hatchback</li>
</ul></nowiki></pre>

Parsing would be a bit trickier, but from the perspective of someone marking up the document, it is pretty simple and straightforward.

=== Suggested Additions ===

* image sub-categorization (could make use of [[media-info|Media microformat]]?):
** thumb (for thumbnail)
** full (for full size image)
** photo (for a photograph)
** illo (for an illustration).
* description sub-categorization:
** summary
** extended
* uri (or url) - URI for the product at its brand website; not to be confused with the hListing 'permalink'.

== Isn't this duplicating hListing and hReview? ==

No, hProduct would not seek to compete with [[hlisting|hListing]] or [[hreview|hReview]], it simply aims to enhance them. In either of these microformats, the <em>item</em> could easily contain the hProduct. Also, hProduct is the more appropriate place for Manufacturer's Suggested Retail Price (MSRP), which is not likely to be the final price of the product being listed. The actual price/sale price/final price should be solely in the domain of hListing.

== Random Thoughts ==

Please add your thoughts & feelings below. If you are interested in getting involved in the development of this microformat. Please contact aaron [at] easy-designs [dot] net and/or join the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats mailing list].

===Ronnos===

Wouldn't the release date of the product be a good addition? I'm writing product re- and previews. I use hReviews to give my opinion about the product, but there's now way to indicate that the product is or is not in stores yet. As far as i can see, the release date is a usefull product attribute, not only usefull in combination with other Microformats, but also for indicating the "age" of a product.

* Release date is a good idea but how to specify it? Is it the date on which the product first becomes available in shops? Would you have a per-region release date (certainly applicable to DVDs, CDs and at least some electronic devices such as gaming consoles) --[[User:SMulcahy|SMulcahy]] 13:38, 15 Feb 2007 (PST)

===Aaron Gustafson===

Actual price, savings, discounts, etc. should be part of hListing instead of hProduct. MSRP (suggested retail price) should be part of the hProduct, however.
*Not all products have a MSRP. [[User:AndyMabbett|Andy Mabbett]] 09:08, 19 Nov 2006 (PST)
**I agree, they don't which is why it should not be required. [[User:AaronGustafson|Aaron Gustafson]] 16:60, 20 Nov 2006 (MST)

===Andy Mabbett===
Please see my [http://microformats.org/discuss/mail/microformats-discuss/2006-November/007281.html proposal, on the mailing list] -- [[User:AndyMabbett|Andy Mabbett]] 09:08, 19 Nov 2006 (PST)
* I agree with the idea of enabling sub-product formats, but am not sure I like the idea of a "wrapper" for hReview or hListing, I think the item should exist ''within'' an instance of one of those microformats. [[User:AaronGustafson|Aaron Gustafson]] 16:60, 20 Nov 2006 (MST)
**There may be more than one review of a product, on one page e.g. [http://www.amazon.co.uk/o/ASIN/B000I0SGSA/ref=pd_rvi_gw_1/026-5782158-8338825] [[User:AndyMabbett|Andy Mabbett]] 00:54, 21 Nov 2006 (PST)

===Adam Craven===

hProduct will definitely be one of the largest microformats.

What about specifications of products, which is important for data aggregation. To categories every type and variation of a product would be mad. So how should the hurdle be crossed, if at all?

The nearest related uF is the citation format, although it isn't overly suited.

===Stephen Mulcahy===

As with microformats in general maybe the approach to take to specifications of products is to let people who need/want them start specifying the ones they are interested in - we don't need an exhaustive universe of potential things categorised. See my posting for some other comments here - http://microformats.org/discuss/mail/microformats-discuss/2007-January/008379.html , in particular note that I think the hard part of this is defining the specifications of individual products. I'm happy to start on the laptop one ... it would be good to have some laptop vendor on board but maybe its too soon for anyone to be interested.

* Some potential subformats (what kind of naming scheme do we want to use here)
** hNotebook (or hProductNotebook ?) - for products like laptops, notebooks, tablets
*** os
*** bundledSoftware
*** size (height, width, depth)
*** weight (units?)
*** processor
*** display
**** size
**** resolution
*** video (for video card)
*** embeddedVideo (boolean)
*** hard drive (maybe manufacturer,model,size? .. eeek is hard drive a hProduct subformat itself?)
*** memory (type and size?)
*** optical drive (types?)
*** battery
*** warranty
*** videoOut (types supported - is it acceptable have a bunch of boolean options for laptop features that may or may not exist on a particular model?)
** hDesktop - for desktop PCs and similar
** hConsole - for gaming consoles such as the Wii, PS3 and XBox360
** hMobilePhone (or hMobileDevice .. not sure we generally want generic subcategory since the whole point of subformats is to give a concrete set of characteristics, or do we want to have nesting of subformats to capture general characteristics at higher levels?).
** hPda (maybe a hMobileDevice .. it starts getting a bit fuzzy here)

Maybe we should talk to some projects like the Linux on Laptops [http://www.linux-laptop.net/] project and get them to encourage contributors to mark-up their laptop reviews in hProductNotebook? --[[User:SMulcahy|SMulcahy]] 07:51, 20 Feb 2007 (PST)

===Robbie van der Blom===
What about unique identifiers for products like ISBN nr. and the UPC codes for a product? My gut feeling is that they should be part of the hProduct format.

With respect to the above, do we really need to talk about hProductNotebook etc. this seems odd.

===Adam Craven===

In relation to the p-v and general property values. The [[abbr-design-pattern]] could be used over the hidden class variable. So
<pre><nowiki>
<h1 class="name">Breitling SuperOcean Chrono</h1>
Water resistant up to <span class="p-v"><abbr class="property value" title="water-resistance">1500m</abbr></span></nowiki></pre>

In this second example, the color is embedded within the actual name class
<pre><nowiki><h1 class="name"><span class="p-v"><abbr class="property value" title="color">White</abbr> Coxmoor shirt</h1>
<img src="white-coxmoor-shirt.jpg" rel="image thumb" /></nowiki></pre>

For items such as books, whereby authors sometimes aren't explicitly denoted visibly (http://www.thebookpeople.co.uk/webapp/wcs/stores/servlet/product_10001_10051_47517_100_10014_10013_category_10013), rather inferred by convention. Could arguably still use the abbr pattern:

<pre><nowiki><h1><span class="name">Great Tales From English History</span> - 3 Books</h1>
by <span class="p-v"><abbr class="property value" title="author">Robert Lacey</abbr></span></nowiki></pre>

Or even
<pre><nowiki><h1><span class="name">Great Tales From English History</span> - 3 Books</h1>
<span class="p-v"><abbr class="property" title="author">by</abbr> <span class="value">Robert Lacey</span></span></nowiki></pre>

A final thought to throw in. If the property and values are within the same HTML tag, it might be possible to remove the property & value class, as the p-v indicates a property value relationship itself.

<pre><nowiki><abbr class="p-v" title="author">Robert Lacey</abbr></nowiki></pre>
What do you think?

User:Adam Craven

2007-05-22T16:12:06Z

Adam Craven:

http://fourshapes.com - A web developer; currently living in London, UK.

product-examples

2007-02-03T09:04:31Z

Adam Craven: /* CDs */

= Product Examples =

This is an exploratory page to document product examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed product microformat.

== Authors ==

* Aaron Gustafson
* Adam Craven
* Craig Cook
* Ronnos

== Examples ==

=== Amazon ===

==== CD ====
* buying - contains unstructured data
** album (product name)
** artist
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** release date
** # of discs
** label
** ASIN

==== Book ====
* buying - contains unstructured data
** title (product name)
** format
** author
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** page count
** publisher
** publication date
** language
** ISBN
** dimensions
** weight

==== Video Game ====
* buying - contains unstructured data
** title (product name)
** publisher
** platform
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (game info)
** ESRB Rating
** genre
* productDetails - contains unstructured data
** ASIN
** SKN
** release date

==== Outdoor Product ====
* buying - contains unstructured data
** product name
** brand
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (product features)
* productDetails - contains unstructured data
** dimensions
** weight
** ASIN
** model number

=== Buy.com ===

==== CD ====
* productTitle
* artist (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** label
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Book ====
* productTitle
* author (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** ISBN
** publication date
** publisher
** dimensions
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Video Game ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** publisher
** sku
* prodInfoSec_1 - additional details
** description

==== TV ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** list price (msrp)
** you save
** price
** shipping
** actual price
* prodPriceSec_2 - actually product details
** manufacturer (brand)
** part #
** SKU
** item #
* prodInfoSec_1 - additional details
** description
* prodInfoSec_2 - tech specs (unstructured)
** type (product description summary)
** display area
** native resolution
** contrast ratio
** viewing angles
** power
** weight
** warranty
** etc.

=== Ben Sherman ===

==== Clothes ====

Link to product rather than actual product immediately available for sale. Personally marked-up and used rel-product ideas to link to the shop.

* Image
** Thumbnail
* Product
** Type
** Title
* Properties
** Colour
* Link
** Buy this Online (rel=product)

'''Mark-up:'''

<pre><nowiki>
<div class="hproduct">
<img src="#" alt="polo shirt" class="product-thumb" />
<h3 class="product-type">Polo Shirt</h3>
<h4 class="product-title">Coxmoor</h4>
<p class="p-v"><span class="property">Colour:</span> <span class="value">289 Rush</span></p>
<p><a href="poloshirt/coxmoor/" title="Buy This Online" rel="product">Buy This Online</a></p>
</div>
</nowiki></pre>

==== CDs ====

Additionally the site has links to products on Amazon.

* Image
** Thumbnail
* Product
** Title
* Properties
** Artist
* Link
** Buy this Online (rel=product)
* Currency implementation

'''Mark-up:'''

<pre><nowiki>
<div class="hproduct">
<a href="#" rel="product"><img src="assets/images/timeline/amazon/small-faces.gif" alt="Small Faces Album" class="product-thumb" /></a>
<h3 class="product-title"><a href="#" rel="product">Ogdens' Nut Gone Flakes</a></h3>
<h4 class="p-v"><span class="property artist">Small Faces</span></h4>
<p class="product-buy"><a href="#" title="Buy this online" rel="product">Buy from Amazon</a></p>
<p class="money"><abbr class="currency" title="GBP">£</abbr><span class="amount">6.99</span></p>
</div>
</nowiki></pre>

The use of [[hproduct-brainstorming#Non-visible_property_names|Non-visible property names]] made it possible to have an invisible property of 'artist'. Having 'Artist: Small Faces' was not in the visual specification of the Ben Sherman site.

=== Atomic Books ===

==== Books ====
* Image
** Thumbnail
* Product
** Title (productname)
** Author
** Publisher
* Properties
** Page Count
** Size
* Notes
* Date Published (can be in future to indicate "not yet released")

=== Walmart ===

=== Cell phone ===
* Productname
* Photo's (Photo)
** Productimage (Pdi)
** Thumbnails (PdiThumbs)
* Price (PriceInfo)
** Productprice (ProdPrice)
** Shipping options (Ship)
** Availability (Avail)
** Pricing options (PriceOptions)
* Description (Description)
* Features
* Included Accessories

== See Also ==
* [[currency]]
* [[hproduct-brainstorming|hProduct Brainstorming]]
* [[hproduct-feedback|hProduct Discussion]]
* [[hproduct-formats|hProduct Formats]]
* [[hproduct-challenges|hProduct Challenge Examples]]

product-examples

2007-02-03T09:04:15Z

Adam Craven: /* Cell phone */

= Product Examples =

This is an exploratory page to document product examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed product microformat.

== Authors ==

* Aaron Gustafson
* Adam Craven
* Craig Cook
* Ronnos

== Examples ==

=== Amazon ===

==== CD ====
* buying - contains unstructured data
** album (product name)
** artist
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** release date
** # of discs
** label
** ASIN

==== Book ====
* buying - contains unstructured data
** title (product name)
** format
** author
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** page count
** publisher
** publication date
** language
** ISBN
** dimensions
** weight

==== Video Game ====
* buying - contains unstructured data
** title (product name)
** publisher
** platform
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (game info)
** ESRB Rating
** genre
* productDetails - contains unstructured data
** ASIN
** SKN
** release date

==== Outdoor Product ====
* buying - contains unstructured data
** product name
** brand
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (product features)
* productDetails - contains unstructured data
** dimensions
** weight
** ASIN
** model number

=== Buy.com ===

==== CD ====
* productTitle
* artist (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** label
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Book ====
* productTitle
* author (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** ISBN
** publication date
** publisher
** dimensions
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Video Game ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** publisher
** sku
* prodInfoSec_1 - additional details
** description

==== TV ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** list price (msrp)
** you save
** price
** shipping
** actual price
* prodPriceSec_2 - actually product details
** manufacturer (brand)
** part #
** SKU
** item #
* prodInfoSec_1 - additional details
** description
* prodInfoSec_2 - tech specs (unstructured)
** type (product description summary)
** display area
** native resolution
** contrast ratio
** viewing angles
** power
** weight
** warranty
** etc.

=== Ben Sherman ===

==== Clothes ====

Link to product rather than actual product immediately available for sale. Personally marked-up and used rel-product ideas to link to the shop.

* Image
** Thumbnail
* Product
** Type
** Title
* Properties
** Colour
* Link
** Buy this Online (rel=product)

'''Mark-up:'''

<pre><nowiki>
<div class="hproduct">
<img src="#" alt="polo shirt" class="product-thumb" />
<h3 class="product-type">Polo Shirt</h3>
<h4 class="product-title">Coxmoor</h4>
<p class="p-v"><span class="property">Colour:</span> <span class="value">289 Rush</span></p>
<p><a href="poloshirt/coxmoor/" title="Buy This Online" rel="product">Buy This Online</a></p>
</div>
</nowiki></pre>

==== CDs ====

Additionally the site has links to products on Amazon.

* Image
** Thumbnail
* Product
** Title
* Properties
** Artist
* Link
** Buy this Online (rel=product)
* Currency implementation

'''Mark-up:'''

<pre><nowiki>
<div class="hproduct">
<a href="#" rel="product"><img src="assets/images/timeline/amazon/small-faces.gif" alt="Small Faces Album" class="product-thumb" /></a>
<h3 class="product-title"><a href="#" rel="product">Ogdens' Nut Gone Flakes</a></h3>
<h4 class="p-v"><span class="property artist">Small Faces</span></h4>
<p class="product-buy"><a href="#" title="Buy this online" rel="product">Buy from Amazon</a></p>
<p class="money"><abbr class="currency" title="GBP">£</abbr><span class="amount">6.99</span></p>
</div>
</nowiki></pre>

=== Atomic Books ===

==== Books ====
* Image
** Thumbnail
* Product
** Title (productname)
** Author
** Publisher
* Properties
** Page Count
** Size
* Notes
* Date Published (can be in future to indicate "not yet released")

=== Walmart ===

=== Cell phone ===
* Productname
* Photo's (Photo)
** Productimage (Pdi)
** Thumbnails (PdiThumbs)
* Price (PriceInfo)
** Productprice (ProdPrice)
** Shipping options (Ship)
** Availability (Avail)
** Pricing options (PriceOptions)
* Description (Description)
* Features
* Included Accessories

== See Also ==
* [[currency]]
* [[hproduct-brainstorming|hProduct Brainstorming]]
* [[hproduct-feedback|hProduct Discussion]]
* [[hproduct-formats|hProduct Formats]]
* [[hproduct-challenges|hProduct Challenge Examples]]

hproduct

2007-02-03T08:52:36Z

Adam Craven: hproduct still shows up on google, direct traffic to proper area.

Follow this link for [[product]] microformat discussions

product-examples

2007-01-17T17:14:18Z

Adam Craven: /* CDs */

= Product Examples =

This is an exploratory page to document product examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed product microformat.

== Authors ==

* Aaron Gustafson
* Adam Craven
* Craig Cook

== Examples ==

=== Amazon ===

==== CD ====
* buying - contains unstructured data
** album (product name)
** artist
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** release date
** # of discs
** label
** ASIN

==== Book ====
* buying - contains unstructured data
** title (product name)
** format
** author
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** page count
** publisher
** publication date
** language
** ISBN
** dimensions
** weight

==== Video Game ====
* buying - contains unstructured data
** title (product name)
** publisher
** platform
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (game info)
** ESRB Rating
** genre
* productDetails - contains unstructured data
** ASIN
** SKN
** release date

==== Outdoor Product ====
* buying - contains unstructured data
** product name
** brand
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (product features)
* productDetails - contains unstructured data
** dimensions
** weight
** ASIN
** model number

=== Buy.com ===

==== CD ====
* productTitle
* artist (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** label
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Book ====
* productTitle
* author (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** ISBN
** publication date
** publisher
** dimensions
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Video Game ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** publisher
** sku
* prodInfoSec_1 - additional details
** description

==== TV ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** list price (msrp)
** you save
** price
** shipping
** actual price
* prodPriceSec_2 - actually product details
** manufacturer (brand)
** part #
** SKU
** item #
* prodInfoSec_1 - additional details
** description
* prodInfoSec_2 - tech specs (unstructured)
** type (product description summary)
** display area
** native resolution
** contrast ratio
** viewing angles
** power
** weight
** warranty
** etc.

=== Ben Sherman ===

==== Clothes ====

Link to product rather than actual product immediately available for sale. Personally marked-up and used rel-product ideas to link to the shop.

* Image
** Thumbnail
* Product
** Type
** Title
* Properties
** Colour
* Link
** Buy this Online (rel=product)

'''Mark-up:'''

<pre><nowiki>
<div class="hproduct">
<img src="#" alt="polo shirt" class="product-thumb" />
<h3 class="product-type">Polo Shirt</h3>
<h4 class="product-title">Coxmoor</h4>
<p class="p-v"><span class="property">Colour:</span> <span class="value">289 Rush</span></p>
<p><a href="poloshirt/coxmoor/" title="Buy This Online" rel="product">Buy This Online</a></p>
</div>
</nowiki></pre>

==== CDs ====

Additionally the site has links to products on Amazon.

* Image
** Thumbnail
* Product
** Title
* Properties
** Artist
* Link
** Buy this Online (rel=product)
* Currency implementation

<pre><nowiki>
<div class="hproduct">
<a href="#" rel="product"><img src="assets/images/timeline/amazon/small-faces.gif" alt="Small Faces Album" class="product-thumb" /></a>
<h3 class="product-title"><a href="#" rel="product">Nut Gone Flakes</a></h3>
<h4 class="p-v"><span class="property artist">Small Faces</span></h4>
<p class="product-buy"><a href="#" title="Buy this online" rel="product">Buy from Amazon</a></p>
<p class="money"><abbr class="currency" title="GBP">£</abbr><span class="amount">6.99</span></p>
</div>
</nowiki></pre>

The use of [[hproduct-brainstorming#Non-visible_property_names|Non-visible property names]] made it possible to have an invisible property of 'artist'. Having 'Artist: Small Faces' was not in the visual specification of the Ben Sherman site.

== See Also ==
* [[currency]]
* [[hproduct-brainstorming|hProduct Brainstorming]]
* [[hproduct-feedback|hProduct Discussion]]
* [[hproduct-formats|hProduct Formats]]
* [[hproduct-challenges|hProduct Challenge Examples]]

product-examples

2007-01-17T17:12:26Z

Adam Craven: /* CDs */

= Product Examples =

This is an exploratory page to document product examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed product microformat.

== Authors ==

* Aaron Gustafson
* Adam Craven
* Craig Cook

== Examples ==

=== Amazon ===

==== CD ====
* buying - contains unstructured data
** album (product name)
** artist
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** release date
** # of discs
** label
** ASIN

==== Book ====
* buying - contains unstructured data
** title (product name)
** format
** author
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** page count
** publisher
** publication date
** language
** ISBN
** dimensions
** weight

==== Video Game ====
* buying - contains unstructured data
** title (product name)
** publisher
** platform
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (game info)
** ESRB Rating
** genre
* productDetails - contains unstructured data
** ASIN
** SKN
** release date

==== Outdoor Product ====
* buying - contains unstructured data
** product name
** brand
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (product features)
* productDetails - contains unstructured data
** dimensions
** weight
** ASIN
** model number

=== Buy.com ===

==== CD ====
* productTitle
* artist (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** label
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Book ====
* productTitle
* author (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** ISBN
** publication date
** publisher
** dimensions
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Video Game ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** publisher
** sku
* prodInfoSec_1 - additional details
** description

==== TV ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** list price (msrp)
** you save
** price
** shipping
** actual price
* prodPriceSec_2 - actually product details
** manufacturer (brand)
** part #
** SKU
** item #
* prodInfoSec_1 - additional details
** description
* prodInfoSec_2 - tech specs (unstructured)
** type (product description summary)
** display area
** native resolution
** contrast ratio
** viewing angles
** power
** weight
** warranty
** etc.

=== Ben Sherman ===

==== Clothes ====

Link to product rather than actual product immediately available for sale. Personally marked-up and used rel-product ideas to link to the shop.

* Image
** Thumbnail
* Product
** Type
** Title
* Properties
** Colour
* Link
** Buy this Online (rel=product)

'''Mark-up:'''

<pre><nowiki>
<div class="hproduct">
<img src="#" alt="polo shirt" class="product-thumb" />
<h3 class="product-type">Polo Shirt</h3>
<h4 class="product-title">Coxmoor</h4>
<p class="p-v"><span class="property">Colour:</span> <span class="value">289 Rush</span></p>
<p><a href="poloshirt/coxmoor/" title="Buy This Online" rel="product">Buy This Online</a></p>
</div>
</nowiki></pre>

==== CDs ====

Additionally the site has links to products on Amazon.

* Image
** Thumbnail
* Product
** Title
* Properties
** Artist
* Link
** Buy this Online (rel=product)
* Currency implementation

<pre><nowiki>
<div class="hproduct">
<a href="#" rel="product"><img src="assets/images/timeline/amazon/small-faces.gif" alt="Small Faces Album" class="product-thumb" /></a>
<h3 class="product-title"><a href="#" rel="product">Nut Gone Flakes</a></h3>
<h4 class="p-v"><span class="property artist">Small Faces</span></h4>
<p class="product-buy"><a href="#" title="Buy this online" rel="product">Buy from Amazon</a></p>
<p class="money"><abbr class="currency" title="GBP">£</abbr><span class="amount">6.99</span></p>
</div>
</nowiki></pre>

The use of [[hproduct-brainstorming#Non-visible_property_names|Non-visible property names]] made it possible to have an invisible property of 'artist'. Having Artist: The Kinks was not in the visual specification of the Ben Sherman site.

== See Also ==
* [[currency]]
* [[hproduct-brainstorming|hProduct Brainstorming]]
* [[hproduct-feedback|hProduct Discussion]]
* [[hproduct-formats|hProduct Formats]]
* [[hproduct-challenges|hProduct Challenge Examples]]

product-examples

2007-01-17T15:04:35Z

Adam Craven: /* CDs */

= Product Examples =

This is an exploratory page to document product examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed product microformat.

== Authors ==

* Aaron Gustafson
* Adam Craven
* Craig Cook

== Examples ==

=== Amazon ===

==== CD ====
* buying - contains unstructured data
** album (product name)
** artist
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** release date
** # of discs
** label
** ASIN

==== Book ====
* buying - contains unstructured data
** title (product name)
** format
** author
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** page count
** publisher
** publication date
** language
** ISBN
** dimensions
** weight

==== Video Game ====
* buying - contains unstructured data
** title (product name)
** publisher
** platform
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (game info)
** ESRB Rating
** genre
* productDetails - contains unstructured data
** ASIN
** SKN
** release date

==== Outdoor Product ====
* buying - contains unstructured data
** product name
** brand
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (product features)
* productDetails - contains unstructured data
** dimensions
** weight
** ASIN
** model number

=== Buy.com ===

==== CD ====
* productTitle
* artist (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** label
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Book ====
* productTitle
* author (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** ISBN
** publication date
** publisher
** dimensions
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Video Game ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** publisher
** sku
* prodInfoSec_1 - additional details
** description

==== TV ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** list price (msrp)
** you save
** price
** shipping
** actual price
* prodPriceSec_2 - actually product details
** manufacturer (brand)
** part #
** SKU
** item #
* prodInfoSec_1 - additional details
** description
* prodInfoSec_2 - tech specs (unstructured)
** type (product description summary)
** display area
** native resolution
** contrast ratio
** viewing angles
** power
** weight
** warranty
** etc.

=== Ben Sherman ===

==== Clothes ====

Link to product rather than actual product immediately available for sale. Personally marked-up and used rel-product ideas to link to the shop.

* Image
** Thumbnail
* Product
** Type
** Title
* Properties
** Colour
* Link
** Buy this Online (rel=product)

'''Mark-up:'''

<pre><nowiki>
<div class="hproduct">
<img src="#" alt="polo shirt" class="product-thumb" />
<h3 class="product-type">Polo Shirt</h3>
<h4 class="product-title">Coxmoor</h4>
<p class="p-v"><span class="property">Colour:</span> <span class="value">289 Rush</span></p>
<p><a href="poloshirt/coxmoor/" title="Buy This Online" rel="product">Buy This Online</a></p>
</div>
</nowiki></pre>

==== CDs ====

Additionally the site has links to products on Amazon.

* Image
** Thumbnail
* Product
** Title
* Properties
** Artist
* Link
** Buy this Online (rel=product)
* Currency implementation

<pre><nowiki>
<div class="hproduct">
<a href="#" rel="product"><img src="assets/images/timeline/amazon/kinks.gif" alt="Kinks Album" class="product-thumb" /></a>
<h3 class="product-title" rel="product"><a href="#">Kinda Kins</a></h3>
<h4 class="p-v"><span class="property artist">The Kinks</h4>
<p class="product-buy"><a href="#" title="Buy this online" rel="product">Buy from Amazon</a></p>
<p class="money"><abbr class="currency" title="GBP">£</abbr><span class="amount">6.99</span></p>
</div>
</nowiki></pre>

The use of [[hproduct-brainstorming#Non-visible_property_names|Non-visible property names]] made it possible to have an invisible property of 'artist'. Having Artist: The Kinks was not in the visual specification of the Ben Sherman site.

== See Also ==
* [[currency]]
* [[hproduct-brainstorming|hProduct Brainstorming]]
* [[hproduct-feedback|hProduct Discussion]]
* [[hproduct-formats|hProduct Formats]]
* [[hproduct-challenges|hProduct Challenge Examples]]

product-examples

2007-01-17T15:02:57Z

Adam Craven: /* Added CDs under Ben Sherman*/

= Product Examples =

This is an exploratory page to document product examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed product microformat.

== Authors ==

* Aaron Gustafson
* Adam Craven
* Craig Cook

== Examples ==

=== Amazon ===

==== CD ====
* buying - contains unstructured data
** album (product name)
** artist
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** release date
** # of discs
** label
** ASIN

==== Book ====
* buying - contains unstructured data
** title (product name)
** format
** author
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** page count
** publisher
** publication date
** language
** ISBN
** dimensions
** weight

==== Video Game ====
* buying - contains unstructured data
** title (product name)
** publisher
** platform
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (game info)
** ESRB Rating
** genre
* productDetails - contains unstructured data
** ASIN
** SKN
** release date

==== Outdoor Product ====
* buying - contains unstructured data
** product name
** brand
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (product features)
* productDetails - contains unstructured data
** dimensions
** weight
** ASIN
** model number

=== Buy.com ===

==== CD ====
* productTitle
* artist (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** label
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Book ====
* productTitle
* author (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** ISBN
** publication date
** publisher
** dimensions
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Video Game ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** publisher
** sku
* prodInfoSec_1 - additional details
** description

==== TV ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** list price (msrp)
** you save
** price
** shipping
** actual price
* prodPriceSec_2 - actually product details
** manufacturer (brand)
** part #
** SKU
** item #
* prodInfoSec_1 - additional details
** description
* prodInfoSec_2 - tech specs (unstructured)
** type (product description summary)
** display area
** native resolution
** contrast ratio
** viewing angles
** power
** weight
** warranty
** etc.

=== Ben Sherman ===

==== Clothes ====

Link to product rather than actual product immediately available for sale. Personally marked-up and used rel-product ideas to link to the shop.

* Image
** Thumbnail
* Product
** Type
** Title
* Properties
** Colour
* Link
** Buy this Online (rel=product)

'''Mark-up:'''

<pre><nowiki>
<div class="hproduct">
<img src="#" alt="polo shirt" class="product-thumb" />
<h3 class="product-type">Polo Shirt</h3>
<h4 class="product-title">Coxmoor</h4>
<p class="p-v"><span class="property">Colour:</span> <span class="value">289 Rush</span></p>
<p><a href="poloshirt/coxmoor/" title="Buy This Online" rel="product">Buy This Online</a></p>
</div>
</nowiki></pre>

==== CDs ====

Additionally the site has links to products on Amazon.

* Image
** Thumbnail
* Product
** Title
* Properties
** Artist
* Link
** Buy this Online (rel=product)
* Currency implementation

<pre><nowiki>
<div class="hproduct">
<a href="#" rel="product"><img src="assets/images/timeline/amazon/kinks.gif" alt="Kinks Album" class="product-thumb" /></a>
<h3 class="product-title" rel="product"><a href="#">Kinda Kins</a></h3>
<h4 class="p-v"><span class="property artist">The Kinks</h4>
<p class="product-buy"><a href="#" title="Buy this online" rel="product">Buy from Amazon</a></p>
<p class="money"><abbr class="currency" title="GBP">£</abbr><span class="amount">6.99</span></p>
</div>
</nowiki></pre>

The use of [[hproduct-brainstorming#Non-visible_property_names|Non-visible property names]] solved the problem of having to include a visible property of 'artist', as this was not in the visual specification of the Ben Sherman site.

== See Also ==
* [[currency]]
* [[hproduct-brainstorming|hProduct Brainstorming]]
* [[hproduct-feedback|hProduct Discussion]]
* [[hproduct-formats|hProduct Formats]]
* [[hproduct-challenges|hProduct Challenge Examples]]

currency

2007-01-17T14:46:31Z

Adam Craven: /* Related microformats */

= currency microformat efforts =

==Introduction==

All over the web, we see amounts of money, most usually as prices on eCommerce sites, but also in other contexts - salaries in job offers, fines mentioned in news reports and prices in product reviews, for example.

Wouldn't it be useful to be able to have them converted to your local currency, easily and quickly? Or to see the modern equivalent of an historical figure?

Those are just two of the things which a currency microformat might do for you.

==Related microformats==

The following is a non-exhaustive lists of microformats which might include an amount of money as a data item:

*[[job-listing]]
*[[hlisting]]
*[[hReview]]
*[[hresume]]
*[[product]]

==Contributors==
* [http://weblog.200ok.com.au/ Ben Buchanan] (original proponent)
*[[User:AndyMabbett|Andy Mabbett]] (second proponent)
* Guillaume Lebleu

==Related pages==
{{currency-related-pages}}

product-examples

2007-01-09T13:54:29Z

Adam Craven: /* Clothes */

= Product Examples =

This is an exploratory page to document product examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed product microformat.

== Authors ==

* Aaron Gustafson
* Adam Craven
* Craig Cook

== Examples ==

=== Amazon ===

==== CD ====
* buying - contains unstructured data
** album (product name)
** artist
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** release date
** # of discs
** label
** ASIN

==== Book ====
* buying - contains unstructured data
** title (product name)
** format
** author
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** page count
** publisher
** publication date
** language
** ISBN
** dimensions
** weight

==== Video Game ====
* buying - contains unstructured data
** title (product name)
** publisher
** platform
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (game info)
** ESRB Rating
** genre
* productDetails - contains unstructured data
** ASIN
** SKN
** release date

==== Outdoor Product ====
* buying - contains unstructured data
** product name
** brand
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (product features)
* productDetails - contains unstructured data
** dimensions
** weight
** ASIN
** model number

=== Buy.com ===

==== CD ====
* productTitle
* artist (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** label
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Book ====
* productTitle
* author (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** ISBN
** publication date
** publisher
** dimensions
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Video Game ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** publisher
** sku
* prodInfoSec_1 - additional details
** description

==== TV ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** list price (msrp)
** you save
** price
** shipping
** actual price
* prodPriceSec_2 - actually product details
** manufacturer (brand)
** part #
** SKU
** item #
* prodInfoSec_1 - additional details
** description
* prodInfoSec_2 - tech specs (unstructured)
** type (product description summary)
** display area
** native resolution
** contrast ratio
** viewing angles
** power
** weight
** warranty
** etc.

=== Ben Sherman ===

==== Clothes ====

Link to product rather than actual product immediately available for sale. Personally marked-up and used rel-product ideas to link to the shop.

* Image
** Thumbnail
* Product
** Type
** Title
* Properties
** Colour
* Link
** Buy this Online (rel=product)

'''Mark-up:'''

<pre><nowiki>
<div class="hproduct">
<img src="#" alt="polo shirt" class="product-thumb" />
<h3 class="product-type">Polo Shirt</h3>
<h4 class="product-title">Coxmoor</h4>
<p class="p-v"><span class="property">Colour:</span> <span class="value">289 Rush</span></p>
<p><a href="poloshirt/coxmoor/" title="Buy This Online" rel="product">Buy This Online</a></p>
</div>
</nowiki></pre>

== See Also ==
* [[currency]]
* [[hproduct-brainstorming|hProduct Brainstorming]]
* [[hproduct-feedback|hProduct Discussion]]
* [[hproduct-formats|hProduct Formats]]
* [[hproduct-challenges|hProduct Challenge Examples]]

product-examples

2007-01-09T13:52:42Z

Adam Craven: Added Clothes link to

= Product Examples =

This is an exploratory page to document product examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed product microformat.

== Authors ==

* Aaron Gustafson
* Adam Craven
* Craig Cook

== Examples ==

=== Amazon ===

==== CD ====
* buying - contains unstructured data
** album (product name)
** artist
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** release date
** # of discs
** label
** ASIN

==== Book ====
* buying - contains unstructured data
** title (product name)
** format
** author
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** page count
** publisher
** publication date
** language
** ISBN
** dimensions
** weight

==== Video Game ====
* buying - contains unstructured data
** title (product name)
** publisher
** platform
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (game info)
** ESRB Rating
** genre
* productDetails - contains unstructured data
** ASIN
** SKN
** release date

==== Outdoor Product ====
* buying - contains unstructured data
** product name
** brand
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (product features)
* productDetails - contains unstructured data
** dimensions
** weight
** ASIN
** model number

=== Buy.com ===

==== CD ====
* productTitle
* artist (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** label
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Book ====
* productTitle
* author (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** ISBN
** publication date
** publisher
** dimensions
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Video Game ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** publisher
** sku
* prodInfoSec_1 - additional details
** description

==== TV ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** list price (msrp)
** you save
** price
** shipping
** actual price
* prodPriceSec_2 - actually product details
** manufacturer (brand)
** part #
** SKU
** item #
* prodInfoSec_1 - additional details
** description
* prodInfoSec_2 - tech specs (unstructured)
** type (product description summary)
** display area
** native resolution
** contrast ratio
** viewing angles
** power
** weight
** warranty
** etc.

=== Ben Sherman ===

==== Clothes ====

Link to product rather than actual product immediately available for sale. Personally marked-up and used rel-product ideas to link to the shop.

* Image
** Thumbnail
* Product
** Type
** Title
* Properties
** Colour
* Link
** Buy this Online (rel=product)

<pre><nowiki>
<div class="hproduct">
<img src="#" alt="polo shirt" class="product-thumb" />
<h3 class="product-type">Polo Shirt</h3>
<h4 class="product-title">Coxmoor</h4>
<p class="p-v"><span class="property">Colour:</span> <span class="value">289 Rush</span></p>
<p><a href="poloshirt/coxmoor/" title="Buy This Online" rel="product">Buy This Online</a></p>
</div>
</nowiki></pre>

== See Also ==
* [[currency]]
* [[hproduct-brainstorming|hProduct Brainstorming]]
* [[hproduct-feedback|hProduct Discussion]]
* [[hproduct-formats|hProduct Formats]]
* [[hproduct-challenges|hProduct Challenge Examples]]

product-examples

2007-01-09T13:44:05Z

Adam Craven: Added Rel Product brainstorming

product-examples

2007-01-09T13:22:33Z

Adam Craven: /* Authors */

User:Adam Craven

2006-07-12T02:05:25Z

Adam Craven:

http://fourshapes.com - A web developer; currently living at Chesterfield, UK.

User:Adam Craven

2006-07-12T02:04:46Z

Adam Craven:

http://fourshapes.com A Web Developer, currently residing at Chesterfield, UK.

irc

2006-07-12T02:02:42Z

Adam Craven: /* People on irc */

__NOTOC__
= Microformats IRC =

We have an IRC channel, [irc://irc.freenode.net#microformats #microformats on the freenode network].

There's typically someone there at any point during the day, though there isn't always active discussion. Sometimes, though this is the best place to discuss issues that need lots of back and forth discussion.

== People on irc ==
A list of IRC regulars and their normal timezones. (winter/summer)

* [[User:Adam Craven|AdamCraven]] (+0000)
* [[User:Amette|amette]] (+1000)
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)
* [[User:Ben Ward|BenWard]] (+0000)
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)
* [[User:Boneill|boneill]] (+0000)
* [[User:Brian|briansuda]] (-0600/-0500)
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)
* [[User:Cgriego|cgriego]] (-0600/-0500)
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)
* [[User:ChristopherStJohn|cks]] (-0600/-0500)
* [[User:DanC|DanC]] (-0600/-0500)
** office hours: Wednesday afternoons, America/Chicago time
* [[User:Dave Cardwell|davecardwell]] (+0000)
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)
* [[User:DrewMcLellan|drewinthehead]] (+0000/+0100)
* [[User:EdwardOConnor|hober]] (-0800/-0700)
* [[User:Enric|enric]] (-0800/-0700)
* [[User:Evan|evanpro]] (-0500)
* [[User:Fil|Fil]] (+0200)
* [[User:Grantbow|Grantbow]] (-0800/-0700)
* [[User:Hlb|hlb]] (+0800-0700)
* [[User:IanHickson|Hixie]] (-0800/-0700)
* [[User:Izo|IZO]]
* [[User:JoeGregorio|jcgregorio]]
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)
* [[User:Keri Henare|kerihenare]] (+1200)
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* [[User:Mark Mansour|Mark Mansour]] (+1100)
* [[User:neuro|neuro`]]
* [[User:Remi|Remi]] (-0500/-0400)
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)
** Office hours: Wednesday, 18:00-20:00 UTC
* [[User:RyanKing|kingryan]] (-0800/-0700)
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* [[User:Dana Benson|Snowden]] (-0800/-0700)
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)
* [[User:Tantek|Tantek]] (-0800/-0700)
* [[User:Dan Kubb|dkubb]] (-0800/-0700)
* [[User:Ed Summers|edsu]] (-0500/-0400)
* [[User:Smackman|Steve Farrell]] (-0800/-0700)
* [[User:Enric|Enric]] (-0800/-0700)
* [[User:Charlvn|Charl]] (+0200/+0200)
* [[User:MarkoMrdjenovic|friedcell]] (+0100/+0200)

=== Greetings ===
To display a brief description of who you are each time you join the channel, you can create a definition for your username. To do so pass the <tt>?def</tt> command using something like the following convention (be brief):

<code>?def jdoe is John Doe and can be found online at <nowiki>http://www.jdoewebsite.com</nowiki></code>

More information about using JiBot commands can be found on the [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot website]

=== bots ===

* [[mfbot]]
* [[mflogbot]]
* [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot]

== Logs ==

Available here: http://rbach.priv.at/Microformats-IRC/

Atom feed of logs available here: http://microformat.makedatamakesense.com/log_feed/

== IRC meetups ==

The idea of having IRC meetups (that is, a set time for meeting on IRC) has been suggested by [[User:RyanKing|Ryan King]], as it appears to work well for the WordPress community and may help us from time-to-time. As of yet, there are no plans to have meetups, though.

irc

2006-07-12T02:00:36Z

Adam Craven: /* People on irc */

__NOTOC__
= Microformats IRC =

We have an IRC channel, [irc://irc.freenode.net#microformats #microformats on the freenode network].

There's typically someone there at any point during the day, though there isn't always active discussion. Sometimes, though this is the best place to discuss issues that need lots of back and forth discussion.

== People on irc ==
A list of IRC regulars and their normal timezones. (winter/summer)

* [[User:AdamCraven|Adam Craven]] (+0000)
* [[User:Amette|amette]] (+1000)
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)
* [[User:Ben Ward|BenWard]] (+0000)
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)
* [[User:Boneill|boneill]] (+0000)
* [[User:Brian|briansuda]] (-0600/-0500)
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)
* [[User:Cgriego|cgriego]] (-0600/-0500)
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)
* [[User:ChristopherStJohn|cks]] (-0600/-0500)
* [[User:DanC|DanC]] (-0600/-0500)
** office hours: Wednesday afternoons, America/Chicago time
* [[User:Dave Cardwell|davecardwell]] (+0000)
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)
* [[User:DrewMcLellan|drewinthehead]] (+0000/+0100)
* [[User:EdwardOConnor|hober]] (-0800/-0700)
* [[User:Enric|enric]] (-0800/-0700)
* [[User:Evan|evanpro]] (-0500)
* [[User:Fil|Fil]] (+0200)
* [[User:Grantbow|Grantbow]] (-0800/-0700)
* [[User:Hlb|hlb]] (+0800-0700)
* [[User:IanHickson|Hixie]] (-0800/-0700)
* [[User:Izo|IZO]]
* [[User:JoeGregorio|jcgregorio]]
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)
* [[User:Keri Henare|kerihenare]] (+1200)
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* [[User:Mark Mansour|Mark Mansour]] (+1100)
* [[User:neuro|neuro`]]
* [[User:Remi|Remi]] (-0500/-0400)
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)
** Office hours: Wednesday, 18:00-20:00 UTC
* [[User:RyanKing|kingryan]] (-0800/-0700)
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* [[User:Dana Benson|Snowden]] (-0800/-0700)
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)
* [[User:Tantek|Tantek]] (-0800/-0700)
* [[User:Dan Kubb|dkubb]] (-0800/-0700)
* [[User:Ed Summers|edsu]] (-0500/-0400)
* [[User:Smackman|Steve Farrell]] (-0800/-0700)
* [[User:Enric|Enric]] (-0800/-0700)
* [[User:Charlvn|Charl]] (+0200/+0200)
* [[User:MarkoMrdjenovic|friedcell]] (+0100/+0200)

=== Greetings ===
To display a brief description of who you are each time you join the channel, you can create a definition for your username. To do so pass the <tt>?def</tt> command using something like the following convention (be brief):

<code>?def jdoe is John Doe and can be found online at <nowiki>http://www.jdoewebsite.com</nowiki></code>

More information about using JiBot commands can be found on the [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot website]

=== bots ===

* [[mfbot]]
* [[mflogbot]]
* [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot]

== Logs ==

Available here: http://rbach.priv.at/Microformats-IRC/

Atom feed of logs available here: http://microformat.makedatamakesense.com/log_feed/

== IRC meetups ==

The idea of having IRC meetups (that is, a set time for meeting on IRC) has been suggested by [[User:RyanKing|Ryan King]], as it appears to work well for the WordPress community and may help us from time-to-time. As of yet, there are no plans to have meetups, though.

hlisting-feedback

2006-07-12T01:57:40Z

Adam Craven:

== Default Action ==
I think it's good form to have a default for every required field, since someone out there is going to drop any given requried field in the land of microformats. In that spirit, the default for listing type is offer, since wanted ads are << 10% in the real world. What I don't know is what the default action should be; the most neutral of them is ''announce'', which I am using in my parser.

-- Rohit

== Donations ==

Sell and Rent are obvious enough verbs; what does Trade mean, though? Barter? And what about one-sided gifts, like donations or "free to recycle"? Should we replace Trade and offer Donate in its place?

-- Rohit

== Desire to Inherit Context ==

When it comes to blog posting, I’d like to see us address the following:

1. '''Less is more'''. Or in reverse, people are lazy, and the less fields they need to fill in order to sell a couch or find a date, the more they'll use the plugin. So I'm trying to visualize how this plays in with the user interface and how we can keep it as simple as possible.

2. '''DRY'''. We want to capture as much information as possible from what is already available in the blog post. We already have summary (title), listing date/time (post date/time), permalink, author information, tags/categories.

3. '''Keep it simple'''. And here I'm talking about setup and being able to extend your blog's functionality without too much fuss. This one is a bit more tricky, so I'll go into details.

WordPress uses templates to render the blog post. The template then calls the WordPress API to render the title, a second call to render the content, and another call to render any additional metadata (e.g.
publish date, categories, author). These separate calls allow people to play with the formatting and apply any styling they like.

The way uPress works, is by processing the blog post before it goes back to the filter, creating the hEvent (to be: hListing) element around it, and adding any relevant fields into the blog post. So what you fill in the form, finds its way to the post content. As a result, setting up the plugin requires two steps: drop it to the plugins directory, and activate.

Unfortunately, I only get to process the content of the post. I can't easily include the title inside the hListing element, or any other metadata about the post, even though I have access to it. If I duplicate that information, the post stops being readable. And to wrap the entire post (not just body) inside a microformat element, I need to tweak the template. Except people use different templates, and I can't tweak all of them.

So the more context we use, the better the plugin becomes.

-- Assaf Arkin

== '''Make Info/Photo fields Optional''' ==

WordPress has a great WYSIWYG editor that lets you drag & drop images.
But the only semantic identification it uses is the HTML <img> element.
So how do we get a photo to be identified from all the images inside the description?

1. Manually edit the HTML that WordPress creates to add the class.
2. Add another UI doubling the one already used by WordPress, sans drag & drop, strictly for images designated as photos.
3. Tag every single image as photo.
4. Have the crawler interpret every single image as photo.

I'm not sure we want to push the complexity to the edge, that's like asking people to create only valid XHTML pages and not rendering anything that refuses to validate. This is about humans first, machines second. If complexity needs to exist, it should be not in the blog, but in the crawlers.

-- Assaf Arkin

== '''On hReview''' ==

This draft was heavily influenced by hReview. That's a good thing. We don’t want to duplicate efforts; are learning from the mistakes of others; and converging on a cohesive set of specifications. I want to eventually add hReview and hCard to my plugin. So this strategy of borrowing from existing microformats helps me get it done quicker. It took me all of five minutes to leverage address formatting from hEvent.

But we also need to recognize that hReview could also be more blogging friendly. The specification is great, but the implementations are lacking. I think the reason is that hReview was designed for greenfield applications that specifically deal with emitting reviews. The design did not take into consideration applications that already deal with content, but want to supplement it with reviews, listings, etc. There's no mention of such consideration in the spec.

We want to appeal to the wide populace of bloggers who just want to get stuff done. Rather than put the burden on millions of bloggers out there, we should place the burden on the few companies developing crawlers.

What would Tantek say? I think he'd ask us to focus on use cases, real examples. I'm presenting one such example. The use case involves a blogger who just wants to sell something on their blog, with the minimum amount of effort and cognitive friction. They want the listing to be discovered, aggregated and searched by others.

-- Assaf Arkin

== '''Neighborhood Name''' ==

With the exception of housing, most classified listings don’t contain a specific address (e.g., if I’m selling my couch, you don’t need to know where I live in the listing). Some location information, however, is important. In most suburban areas, the name of the town is sufficient. In cities, however, neighborhood is important and more contextually relevant than zipcode (simply a region defined by the post office).

This is a tough problem that needs to be solved but outside the context of this discussion. We think there are other cases the could benefit from it, including hReview and hEvent. We recommend that this debate be surface in the adr microformation discussion (e.g., perhaps extend the locality field (city) to optionally include a neighborhood)

-- Craig Donato & Assaf Arkin

== '''Listing Action, Listing Type, Item Type''' ==

We heavily debated how to classify a listing. Search engines or marketplaces typically need to understand what type of listing it is (e.g., personal ad, house for sale, music) to effectively reference or index a listing.

We initially considered proposing a single category field that contained tags (in addition to the tags field). Not only did this seem duplicative, it also seemed like too much of a good thing. In a previous project, Assaf managed to successfully overload everything into tags (including dates and locations), and run time-based and location-based searches, and ended up concluding it's a bad idea.

We eventually decided to propose the use three parametric field that when used together could define any type of listing independent of the words use to describe. These ended up being: listing-type (are you offering something or looking for something; listing-action (are you trying to sell, rent, or announce something); and item type (what item is referenced by the action such as a job opening, product, housing). By making small modifications to this vocabulary, users can specify an extremely wide range of potential transactions. This seemed more feasible given that the UI used to produce the hListing could abstract some of this from the user (as Assaf demonstrated in his demo plugin).

For example:

{|
!Desired Transaction
!Listing Type
!Listing Action
!Item Type
|-
|Merchandise For Sale
|Offer
|Sell
|Product
|-
|Looking to Buy Merchandise
|Wanted
|Sell
|Product
|-
|Selling Tickets
|Offer
|Sell
|Event
|-
|Apartment For Rent
|Offer
|Rent
|Housing
|-
|Looking for Apartment
|Wanted
|Rent
|Housing
|-
|Room for Rent (Roommate)
|Offer
|Rent
|Housing
|-
|Looking for a Date
|Offer||Wanted
|Announce, Meet
|-
|Job Opening
|Offer
|Announce
|Opening
|-
|Looking for a Job (Resume)
|Wanted
|Announce
|Opening
|-
|Music Lessons
|Offer
|Service
|Business
|-
|Trade Couch for TV
|Offer
|Trade
|Product
|-
|Pet for Adoption
|Offer
|Announce
|Animal?
|}
-- Craig Donato

== Eliminate Item Type ==

Can we eliminate item type and simply use tags? Or perhaps inferred item type from the item info?

== hClassified? ==

There are meanings of "listing" that wouldn't fit this format.. might not hClassified be a more descriptive name? It's not overconstraining... 'classifieds' being very broad in practice and the meaning very informally/functionally defined. Or has the 'listing' train left the station?

== What about retail? ==

Retail is out of scope for hListing, sure -- but what microformat should a retail seller of (e.g. mass-produced) goods use? hForSale? hProduct?

== Retail ==

Funnily enough, hProduct is always something that I've thought about.

I'd be bold enough to say that it will be one of the main uses of microformats in the future. Imagine the amount of shops, price comparison, product review and many more type of sites. It doesn't have to be for profit, it could just be someones product, on their site, that they are displaying.

I'd be willing to help and continue development of a spec for 'hProduct'.

Adam Craven