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
(Fuzzy dates)
Line 10: Line 10:
 
<div class="discussion">
 
<div class="discussion">
 
Opinions / discusion:
 
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 [[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. [http://www.casino-spielen.biz online casino spielen]
 
* -1 [[Hixie]] - "Without clear use cases, I don't intend to change the spec here." (ibid)
 
* -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])
 
* +1 [[Tantek]] (per [http://www.zeldman.com/superfriends/guide/#time HTML5 Super Friends Technical Details: time element])

Revision as of 11:19, 13 July 2010

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)
  • +1 Tantek I think the blog archives use case (where blogs often link to their archives by a specific month and year) is sufficient to justify adding this capability to the time element. Content hosting sites like Flickr also list archives by specific year/month, e.g. see http://www.flickr.com/photos/tantek/archives/
  • +1 Andy Mabbett (Per use cases in VCARDDAV - see external links)
  • ...

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

Opinions / discusion:

Calendar

The time element should accept a calendar scale (default is GREGORIAN) per the emergent vCard 4 specification, to facilitate the mark-up of non-Gregorian (e.g. Julian) dates.

Opinions / discussion:

  • +1 Andy Mabbett (Per use cases in VCARDDAV - see external links)
  • ...

Fuzzy dates

The time element should accept fuzzy (uncertain, approximate) dates.

Opinions / discussion:

  • +1 Andy Mabbett (Per use cases in "Extended Date Time Format efforts" discussions - see external links)
  • ...

External links