In message
<7c2a12e20902241613v7ba27c60q433fd84a74279...@mail.gmail.com>, Aryeh
Gregor <simetrical+...@gmail.com> writes
>the emphasis on clear and immediate use-cases. I didn't notice you
>mentioning any of those in your posts. What are some examples of
>actual, concrete applications with user-visible functionality that
>would be aided by extending <time> as you propose?
I'm surprised that you missed all this:
I have considerable experience of marking up dates in
microformats, [...] for historic events, on Wikipedia and
Wikimedia Commons.
[...]
Use-cases for machine-readable date mark-up are many: as well as
the aforesaid calendar interactions, they can be used for
sorting; for searching ("find me all the pages about events in
1923" — recent developments in Yahoo's YQL searching API
(which now supports searching for microformats):
<http://developer.yahoo.net/blog/archives/2009/01/yql_with_microformats.html>
have opened up a whole new set of possibilities, which is only
just beginning to be explored). They can be mapped visually on a
"SIMILE"
<http://simile.mit.edu/timeline/>
or similar time-line. They can be translated into other
languages more effectively than raw prose; they can be
disambiguated (does “5/6/09" mean “5th June 2009? or “6th
May 2009"?); and they can be presented in the user's preferred
format (I might want to see “5th June 2009"; you might see
“June 5, 2009" — such presentational preferences have
generated arguments of little-endian proportions on Wikipedia).
hCalendar microformats are already used to mark up imprecise
dates ("June 1977"; "2009")
[...]
Surely the use case for marking-up a sortable table of Roman
emperors, should allow all such emperors, and not just those who
ruled from 0001AD, to be included?
in my original post.
--
Andy Mabbett
