This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section: http://whatwg.org/specs/web-apps/current-work/#valid-date-or-time-string Comment: Valid date strings should accept ambiguous inputs, like "2009" or "2007-01". Posted from: 208.80.69.102
(This bug was posted by me) Currently, the HTML 5 TIME element's datetime attribute does not allow for ambiguous date inputs, such as just a year or a year and a month. These are very common occurrences on the web (archive views are full of them) and currently they could not be marked up with the TIME element in any valid form that makes sense. Proposal: Add additional options to the "valid date or time string": * A valid date string can also be a less granular date format, such as YYYY or YYYY-MM, indicating the entirety of the year y or month m in year y.
This has been discussed a number of times. For an overview of the topic, please see these e-mails: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-March/018888.html http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-August/021745.html It's not clear why this: <p>Dolly was born in <time>2009</time>.</p> ...is any better than this: <p>Dolly was born in 2009.</p> It's not like the year is going to be used in calendar data or localised in special ways. Without clear use cases, I don't intend to change the spec here.
This bug predates the HTML Working Group Decision Policy. If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.