My intention is to stick to (1) analyzing existing behavior/use on the
web and (2) using the 80/20 rule. I think we'll be fine. If
compositing objects becomes an issue (for example, describing an Audi
with 4 Pirelli tires) then we'll hash it out.
Regards, etc...
On 11/17/06, Andy Mabbett <[EMAIL PROTECTED]> wrote:
In message
<[EMAIL PROTECTED]>, Eric
Skiff <[EMAIL PROTECTED]> writes
>hItem is a bit vague on purpose to make it flexible, but in general, i
>think it will be most useful for describing physical goods.
Consider these two examples.
A bottle of wine is an item. So is the case of 12 bottles in
which it is sold.
Is the wine inside the bottle also an object in its own right?
and
A brick is an object.
So is the wall of which that forms part.
So is the room of which that forms part.
So is the apartment of which that forms part.
So is the apartment block of which that forms part.
Is the city of which the apartment block forms a part, also an object?
If I mark up the apartment block with all of its aforesaid components,
in a nested manner, and apply a height, does it apply to the block, or
the brick?
--
Andy Mabbett
Say "NO!" to compulsory ID Cards: <http://www.no2id.net/>
Free Our Data: <http://www.freeourdata.org.uk>
_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss
--
David Janes
Founder, BlogMatrix
http://www.blogmatrix.com
http://www.onamine.com
http://blogmatrix.blogmatrix.com
_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss
