W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > November 2011

Re: Looking at the time element (again) (ISSUE-97)

From: Ivan Herman <ivan@w3.org>
Date: Fri, 11 Nov 2011 16:23:21 +0100
Cc: Gregg Kellogg <gregg@kellogg-assoc.com>, RDFa WG <public-rdfa-wg@w3.org>
Message-Id: <8FF4BBFD-6F92-4B0B-9533-D6631E0FCC8F@w3.org>
To: Toby Inkster <tai@g5n.co.uk>

On Nov 11, 2011, at 16:09 , Toby Inkster wrote:

> On Thu, 10 Nov 2011 09:52:04 -0500
> Gregg Kellogg <gregg@kellogg-assoc.com> wrote:
> 
>> In my version of the proposals, I perform lexical analysis of
>> @datetime against xsd:date, xsd:dateTime and xsd:time and choose the
>> datatype based on the match. It's quite simple.
> 
> This is what I do for <time> handling in my Microdata parser (though
> IIRC I also support all of the xsd:gFoo types too). I'd support adding
> something like this to (X)HTML+RDFa 1.1, but I think it's too
> HTML-specific to be added to Core.
> 
> Note that this should be trigger specifically by the <time> element,
> and should not apply to all elements with a @datetime attribute. This
> is because we probably wouldn't want to pick up @datetime on <ins> and
> <del>.
> 

Agree on all account! This should go to the HTML5 stuff.

Note also Jeni's comment: it is not only the datetime attribute: if the attribute is not around, the content of the date element should also be considered.

Ivan


> -- 
> Toby A Inkster
> <mailto:mail@tobyinkster.co.uk>
> <http://tobyinkster.co.uk>
> 


----
Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
FOAF: http://www.ivan-herman.net/foaf.rdf
Received on Friday, 11 November 2011 15:20:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:55:18 GMT