http://microformats.org/wiki/hproduct-issues#HP5_-_The_format_for_the_contents_of_SHIPPING_are_vague
The definition of shipping is:
> shipping:: the class name shipping MAY define the method, timeframe,
> and cost associated with shipping the product. MUST be
> singular.
I realize that this is all important information, but why mash method,
timeframe AND cost into one attribute? It would be nice if an
application could use each of those pieces of information out without
having to resort to some sort of natural language processing.
For example, why don't we have:
shipping-method, shipping-timeframe, and shipping-price?
or something like this:
<div class="shipping">
<div class="price">
<abbr class="currency" title="USD">$</abbr>
<span class="amount">3.95</span>
</div>
<span class="method">UPS Ground</span>, expect
<span class="timeframe">4-6 days</span> for delivery.
</div>
-- manu
--
Manu Sporny
President/CEO - Digital Bazaar, Inc.
blog: Scaling Past 100,000 Concurrent Web Service Requests
http://blog.digitalbazaar.com/2008/09/30/scaling-webservices-part-1
_______________________________________________
microformats-new mailing list
microformats-new@microformats.org
http://microformats.org/mailman/listinfo/microformats-new
