item-brainstorming: Difference between revisions
m (Reverted edit of DavidJanes, changed back to last version by Tantek)
m (tried to revert only most recent change with erroneous see also self-reference, but somehow it reverted two changes. adding back what i didn't mean to revert.)
|Line 53:||Line 53:|
= See Also =
= See Also =
Revision as of 03:45, 17 November 2006
This page is to collect ideas about an "item" microformat or design pattern, for representing things that physically exist. At this point, my thinking is to aim for understanding the intersection not the union of attribute of things!
Per the The microformats process, this page is premature as there first needs to be the respective item-examples and item-formats pages, and a clear statement of what specific problem is being solved.
- David Janes
- James Darling
- your name here...
Introduction to the idea
- items/things are used in other micrformats
- unlike people and places, items do not currently get a "container"; thus, attributes being associated with a (say) Review actually should be attached the thing itself
- to cut down on the work required to create new microformats about things (wine, houses, cars, ...)
This is very much analogous to hCard and there is no reason that this shouldn't reuse as much as possible of this. In particular:
- fn - the name of an item
- url - the web address of an item
- photo - a photo of an item
- adr - the address of an item (for example, a house)
- geo - likewise
More of this will be discovered in the examples discovery.
This may just be a design pattern -- that is, a template for create new microformats in the future. If it is a microformat, how we identify the type of thing is an open question -- we could do it like phone number types in hCard or it could be a new class element (or both). I.e. do we create a top-level class "hWine" or do we do <span class="type">wine</a>
One can see that there are many common properties that can be shared about different types of things. Manufactor, brand name, generic name, color.... The base item microformat may avoid trying to define this and instead allow new/future microformats to do the discovery.
- Quantity - can be assumed to be 1 unless specified.
hItem and hCard
Immediately the idea of a hItem demands the idea of the option for a contained hCard for the owner, but what about a large qauntity of items owned by a single owner. Would a hCard be required in each hItem, or would it be possible to wrap all the hItems in a hCard?