Re: <time> values in HTML5

months and years durations were deliberately excluded due to
1. Lack of documented use-cases/publishing examples for them.
2. Precedent. Explicit exclusion of month and year durations from iCalendar (which was the basis for hCalendar, which was a key design driver for the time element).

Tantek

-----Original Message-----
From: John Cowan <cowan@mercury.ccil.org>
Sender: John Cowan <cowan@ccil.org>
Date: Mon, 21 Nov 2011 04:40:06 
To: Jeni Tennison<jeni@jenitennison.com>
Cc: <www-xml-schema-comments@w3.org>; HTML Data Task Force WG<public-html-data-tf@w3.org>; RDFa WG<public-rdfa-wg@w3.org>; <public-html-xml@w3.org>
Subject: Re: <time> values in HTML5

Jeni Tennison scripsit:

> As specced, it (a) accepts a bunch of syntaxes that aren't in the
> lexical space of any XML Schema datatype and (b) accepts some values
> that aren't in the value space of any XML Schema datatype, namely
> timezones and weeks.

What is more, it pukes on durations that include months, apparently
because someone thought that M is ambiguous as between months and minutes.
This is not the case, because M means minutes only after a T has been seen
in 8601, whereas HTML5 is apparently permissive about T.  I do wish the
spec would provide either prose or code, rather than code masquerading
as prose.

So this is a case of failing to accept a syntax that is in the lexical
and the value space of XML Schema.

-- 
John Cowan   cowan@ccil.org
    "Mr. Lane, if you ever wish anything that I can do, all you will have
        to do will be to send me a telegram asking and it will be done."
    "Mr. Hearst, if you ever get a telegram from me asking you to do
        anything, you can put the telegram down as a forgery."

Received on Monday, 21 November 2011 09:51:47 UTC