Difference between revisions of "item-brainstorming"

From Microformats Wiki
Jump to navigation Jump to search
 
Line 15: Line 15:
  
 
* items/things are used in other micrformats
 
* items/things are used in other micrformats
** hListing
+
** [[hlisting|hListing]]
** hReview
+
** [[hreview|hReview]]
 
* 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
 
* 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 for new microformats about things (wine, houses, cars, ...)
 
* to cut down on the work required for new microformats about things (wine, houses, cars, ...)

Revision as of 22:38, 16 November 2006

Item Brainstorming

This page is to collect ideas about an "item" microformat or design pattern. At this point, my thinking is to aim for understanding the intersection not the union of attribute of things!

Editors

Authors

Introduction to the idea

Rationale

  • 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 for new microformats about things (wine, houses, cars, ...)

= Notes

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.

Future Microformats based on an Item microformat

Representation

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>

New Attributes

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.

See Also