A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on IRC (such as one of these permanent autoconfirmed members).

Difference between revisions of "Time element"

From WHATWG Wiki
Jump to: navigation, search
m (Synopsis of the issue(s))
(restructured page by different issues/enhancements rather than sections around a clustering of issues from one bug report)
Line 1: Line 1:
== Bugzilla links ==
+
Research, data, use cases, issues, and enhancements related to the HTML5 <code>time</code> element.
  
[http://www.w3.org/Bugs/Public/show_bug.cgi?id=7145 Bug 7145 - Valid date strings should accept ambiguous inputs, like "2009" or "2007-01"]
+
== year only ==
 +
The time element should accept just a year.
 +
;ISO8601 syntax
 +
:YYYY
 +
;use case research
 +
:http://microformats.org/wiki/birthday-examples#year_only
  
== Synopsis of the issue(s) ==
+
<div class="discussion">
 +
Opinions / discusion:
 +
* +1 [[Faruk]] (per [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7145 Bug 7145 - Valid date strings should accept ambiguous inputs, like "2009" or "2007-01"]) One example is the very common archive view found on most blogs, which contain distinct links or headers for each year, each month per year, and often each date within a chosen or highlighted month. Currently, the <code>&lt;time&gt;</code> element only allows for <code>datetime</code> values as precise as a specific day, e.g. YYYY-MM-DD.
 +
* -1 [[Hixie]] - "Without clear use cases, I don't intend to change the spec here." (ibid)
 +
* +1 [[Tantek]] (per [http://www.zeldman.com/superfriends/guide/#time HTML5 Super Friends Technical Details: time element])
 +
</div>
  
==== Bug 7145 ====
+
== year month only  ==
The <code>&lt;time&gt;</code> element should accept date and/or time inputs of varying precision, such as YYYY or YYYY-MD. One example is the very common archive view found on most blogs, which contain distinct links or headers for each year, each month per year, and often each date within a chosen or highlighted month. Currently, the <code>&lt;time&gt;</code> element only allows for <code>datetime</code> values as imprecise as a specific day, e.g. YYYY-MM-DD.
+
The time element should accept just a year and a month.
 +
;ISO8601 syntax
 +
:YYYY-MM
 +
 
 +
<div class="discussion">
 +
Opinions / discusion:
 +
* +1 [[Faruk]] (per [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7145 Bug 7145 - Valid date strings should accept ambiguous inputs, like "2009" or "2007-01"]) One example is the very common archive view found on most blogs, which contain distinct links or headers for each year, each month per year, and often each date within a chosen or highlighted month. Currently, the <code>&lt;time&gt;</code> element only allows for <code>datetime</code> values as precise as a specific day, e.g. YYYY-MM-DD.
 +
* -1 [[Hixie]] - "Without clear use cases, I don't intend to change the spec here." (ibid)
 +
</div>
 +
 
 +
== month day only ==
 +
The time element should accept just a month and a day.
 +
;ISO8601 syntax
 +
:--MM-DD
 +
;use case research
 +
:http://microformats.org/wiki/birthday-examples#month_and_day_only
 +
 
 +
<div class="discussion">
 +
Opinions / discusion:
 +
* +1 [[Tantek]] (per [http://www.zeldman.com/superfriends/guide/#time HTML5 Super Friends Technical Details: time element])
 +
</div>

Revision as of 01:38, 18 September 2009

Research, data, use cases, issues, and enhancements related to the HTML5 time element.

year only

The time element should accept just a year.

ISO8601 syntax
YYYY
use case research
http://microformats.org/wiki/birthday-examples#year_only

Opinions / discusion:

year month only

The time element should accept just a year and a month.

ISO8601 syntax
YYYY-MM

Opinions / discusion:

  • +1 Faruk (per Bug 7145 - Valid date strings should accept ambiguous inputs, like "2009" or "2007-01") One example is the very common archive view found on most blogs, which contain distinct links or headers for each year, each month per year, and often each date within a chosen or highlighted month. Currently, the <time> element only allows for datetime values as precise as a specific day, e.g. YYYY-MM-DD.
  • -1 Hixie - "Without clear use cases, I don't intend to change the spec here." (ibid)

month day only

The time element should accept just a month and a day.

ISO8601 syntax
--MM-DD
use case research
http://microformats.org/wiki/birthday-examples#month_and_day_only