W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2009

[whatwg] Historic dates in HTML5

From: Bruce Lawson <brucel@opera.com>
Date: Thu, 05 Mar 2009 11:50:41 -0000
Message-ID: <op.uqbhurt4h8on37@bruce-pc>
Henri Sivonen said  
(http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-March/018687.html)

"The <time> element is meant as a replacement for the microformat
<abbr> design pattern in hCalendar (if the microformat community
embraces <time>; if not, <time> in pretty much pointless in HTML5).
The expected use cases of hCalendar are mainly transferring *future*
event entries from a Web page into an application like iCal."

If there's one thing that getting involved in specs of markup languages  
has taught me, it's that "expected use cases" don't matter. People always  
do other things.

And if there is a limit on  a use case, it should be in the spec. There is  
nothing I can see in the editors draft that limits the use of <time>. (I  
use it on my website to markup publication dates of blog entries and  
comments; why on earth wouldn't I?)

What it does limit is the format: no "fuzzy dates" like "July 1897" for my  
great grandmother's birthday (no-one remembers the exact day) or the  
precise date of Charlemagne death "28 January 814"

Henri is right: <code>time</code> is pretty much pointless in HTML5 if  
it's not embraced by the microformats community, but why would they  
embrace it? It prevents them doing a lot of what they do - like fuzzy or  
ancient dates -  so what do they gain by adopting it?



-- 
Bruce Lawson
Web Evangelist
www.opera.com (work)
www.brucelawson.co.uk (personal)
Received on Thursday, 5 March 2009 03:50:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:47:49 GMT