http://microformats.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=XdhCtsMicroformats Wiki - User contributions [en]2026-04-10T00:50:01ZUser contributionsMediaWiki 1.38.4http://microformats.org/wiki/index.php?title=product-brainstorming&diff=19981product-brainstorming2007-06-16T22:46:10Z<p>XdhCts: </p>
<hr />
<div>= Brainstorming for hProduct Microformat =<br />
<br />
This is a brainstorm for the hProduct microformat. See also [[hproduct-examples|examples of hProduct]].<br />
<br />
== Contributors ==<br />
<br />
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]<br />
* Craig Cook, [http://focalcurve.com/ Focal Curve]<br />
<br />
== The Problem ==<br />
<br />
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<br />
<br />
* allow aggregated product details to be linked to from hListings or hReviews<br />
* match hListings to hReviews<br />
* aggregate product-specific information from across the web<br />
* aggregate and compare like products based on features<br />
<br />
== Elements that come up often in practice ==<br />
<br />
Examples of elements that might be included because they seem to come up often in user- and CMS-generated product publishing, include the following:<br />
<br />
=== Base Elements ===<br />
<br />
* name (or fn)<br />
* image (could be sub-categorized)<br />
** thumb (for thumbnail)<br />
** full (for full size image)<br />
** photo (for a photograph)<br />
** illo (for an illustration).<br />
* description (could be sub-categorized)<br />
** summary<br />
** extended<br />
* brand<br />
* uri (or url) - URI for the product at its brand website; not to be confused with the hListing 'permalink'.<br />
* msrp<br />
<br />
=== Extensibility ===<br />
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.<br />
<br />
==== Natural language property-value association ====<br />
<br />
<pre><nowiki><p class="p-v">The <span class="property">dimensions</span> of this book are <br />
<span class="value">6</nowiki></pre></div>XdhCts