- From: Jeremy Keith <jeremy@adactio.com>
- Date: Fri, 27 Nov 2009 11:07:09 +0000
Henri wrote: > On Nov 26, 2009, at 18:50, Jeremy Keith wrote: > >> "The following extract shows how an IM conversation log could be >> marked up. >> <p> <time>14:22</time> <b>egof</b> I'm not that nerdy, I've only >> seen 30% of the star trek episodes" > > What's the point of having the time semantically marked up in this > example? What kind of processing scenario would benefit? 1. Mashups. A user agent/spider/web service parses the time elements and mashes them up with other timestamped data (photos, status updates, etc.). 2. Graphing. A user agent/spider/web service parses the time elements and generates a graph of activity e.g a sparkline. But the scenario I can't imagine is: a user adds one or all of the events to their calendar. That's why I think it's ridiculous that the *definition* of the time element explicitly states that the purpose of the element is to allow users to add events to their calendar. It's one example of usage. It is not the only possible usage. Bye, Jeremy -- Jeremy Keith a d a c t i o http://adactio.com/
Received on Friday, 27 November 2009 03:07:09 UTC