W3C home > Mailing lists > Public > public-html@w3.org > February 2013

[Bug12318] <time> vs. <data> semantic tags for machine-readable content

From: Travis Leithead <travis.leithead@microsoft.com>
Date: Fri, 1 Feb 2013 22:56:52 +0000
To: "public-html@w3.org" <public-html@w3.org>, "cmhjones@gmail.com" <cmhjones@gmail.com>, "philipj@opera.com" <philipj@opera.com>, "giorgio.liscio@email.it" <giorgio.liscio@email.it>
Message-ID: <9768D477C67135458BF978A45BCF9B3853BC75F5@TK5EX14MBXW602.wingroup.windeploy.ntdev.microsoft.com>
Bug 12318 [1] requests a new semantic element: <measure> to be able to mark up additional measurements for machine readable processing. This is very similar in principle to the <time> element, but somewhat more generic (for measurements). It was proposed that either the <time> element be extended to support more generic scenarios, or that a new element (like <measure>) be created but for the specific purposes of marking up machine-readable content. 

Since this bug was filed, a proposal exists [2] for a new <data> element which looks like it meets the use case described in this bug.

Is <data> a useful new tag?

Is <time> still useful? Should it be enhanced to allow for additional scenarios?

If <data> seems useful, then we could resolve this bug by either bringing <data> directly into HTML5.1, or creating an extension spec for <data> (or something like it). Otherwise, we might as well resolve this bug won't fix.


[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=12318
[2] http://www.whatwg.org/specs/web-apps/current-work/#the-data-element
Received on Friday, 1 February 2013 22:57:40 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:31 UTC