- From: <bugzilla@jessica.w3.org>
- Date: Thu, 03 Nov 2011 08:33:07 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13240 --- Comment #69 from Ben Buchanan <7xnm24bdza@snkmail.com> 2011-11-03 08:33:06 UTC --- (In reply to comment #67) > It looks like for giving plugins (scripts) access to the timestamps, <data > class=date value="..."> would do the exact same thing, but if <time> exists > then it is of course the better match. You could also achieve the result with data- attributes, but both options rely on page-level convention instead of setting a standard. I think relying on a custom class or attribute is a retrograde step from having an element with universally defined semantics/purpose. I can see the value of adding the data element as a workhorse for microformats; I just think <time> is a common enough use case that a single, dedicated element is the way to go. Much as I like microformats, I don't think we should need one just to mark up a timestamp :) -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 3 November 2011 08:35:16 UTC