W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > May 2012

Re: ISSUE-141 (@datetime datatype matching): How many of the possible datatypes for @datetime should be supported? [RDFa 1.1 in HTML5]

From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Thu, 3 May 2012 01:47:00 -0400
To: RDF Web Applications Working Group <public-rdfa-wg@w3.org>
Message-ID: <95EAC3D8-7D01-4A65-9A27-38AA9CAFAD80@greggkellogg.net>
>From http://www.w3.org/2010/02/rdfa/meetings/2011-11-17#resolution_1

[[[
RESOLVED: HTML5+RDFa will add the time element with date, time, and dateTime, and will also express the intention to follow the time element discussion for subsequent datatypes
]]]

We intended to allow gYear, gYearMonth and duration once the HTML5 spec was actually updated to include these, which it has.

We also discussed using the value of the time element, as HTML5 suggests and we discussed, but did not resolve.

Gregg

On May 2, 2012, at 12:53 PM, RDF Web Applications Working Group Issue Tracker wrote:

> ISSUE-141 (@datetime datatype matching): How many of the possible datatypes for @datetime should be supported? [RDFa 1.1 in HTML5]
> 
> http://www.w3.org/2010/02/rdfa/track/issues/141
> 
> Raised by: Gregg Kellogg
> On product: RDFa 1.1 in HTML5
> 
> Should gYear, gYearMonth and duration datatype matching be performed on @datetime attributes in HTML5? Are there any other date and/or time types that should be supported?
> 
> 
> 
Received on Thursday, 3 May 2012 05:47:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 3 May 2012 05:47:39 GMT