- From: Michael[tm] Smith <mike@w3.org>
- Date: Fri, 26 Oct 2012 15:24:51 +0900
- To: KANZAKI Masahide <mkanzaki@gmail.com>
- Cc: www-validator@w3.org
Kanzaki-san, OK, I finally pushed a change for this to the W3C Nu validator: http://validator.w3.org/nu/ It attempts to conform to the current spec. Please test it and let me know if you find any problems. Sorry for taking so long to get this change done. --Mike "Michael[tm] Smith" <mike@w3.org>, 2012-09-27 14:35 +0900: > Hi Kanzaki-san, > > > @2012-09-27 14:02 +0900: > > Hello, > > > > The validator seems to check <time> element value (and its datetime > > attribute value) based on HTML5 "Dates and times microsyntax" [1], > > resulting year only (YYYY) or year-month (YYYY-MM) invalid. e.g. > > > > <time>2012</time> > > <time datetime="2012-04">April 2012</time> > > > > However, HTML5 spec explicitly allows these values (and more) for time > > element [2]. I guess the validator should follow the time element > > definition [2] rather than microsyntax definition [1]. > > > > cheers, > > > > > > [1] http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#dates-and-times > > [2] http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#the-time-element > > I think that's just a matter of the validator not being up to date with the > current spec. Sorry about that -- I'll try to get it fixed soon. We've got > a bit of a backlog of validator issues like this at the moment. Hopefully > can get most of them fixed over the next few weeks. > > --Mike > -- Michael[tm] Smith http://people.w3.org/mike
Received on Friday, 26 October 2012 06:24:54 UTC