datetime-design-pattern: Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 16: | Line 16: | ||
--[[DimitriGlazkov]] | --[[DimitriGlazkov]] | ||
It could, but inventing a microformat for the sake of inventing a microformat is against the microformat principles. | |||
If there is a specific real world problem (and uses cases) that such an elemental microformat would solve, then it would be worth considering. | |||
Until then it is best to keep the <abbr> datetime concept merely as a microformat design pattern, to be used in _actual_ microformats that have a demonstrated practical need. | |||
-- [http://tantek.com/log/ Tantek] | |||
Revision as of 22:31, 29 July 2005
This page is a draft.
This is a page for exploring a datetime design pattern.
The pattern which is now used in hCalendar and hReview is something like this:
<abbr class="foo" title="YYYYMMDDTHH:MM:SS+ZZZZ">Date Time</abbr>
where foo is the semantic classname which is being applied to this date/time, the title of the <abbr> is an ISO 8601 date/time and "Date Time" is a human-friendly representation of the same date/time.
This pattern is likely to be highly resuable.
--RyanKing
Can this not be viewed as a microformat in itself?
It could, but inventing a microformat for the sake of inventing a microformat is against the microformat principles. If there is a specific real world problem (and uses cases) that such an elemental microformat would solve, then it would be worth considering.
Until then it is best to keep the <abbr> datetime concept merely as a microformat design pattern, to be used in _actual_ microformats that have a demonstrated practical need.
-- Tantek