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 Chat (such as one of these permanent autoconfirmed members).
Time element: Difference between revisions
Jump to navigation
Jump to search
(→Calendar: EDTF) |
m (→External links: use-cases) |
||
| Line 66: | Line 66: | ||
== External links == | == External links == | ||
* [http://www.loc.gov/standards/datetime/ Extended Date Time Format efforts] based at the USA's Library of Congress (Covers unspecific dates; date periods and non-Gregorian dates) | * [http://www.loc.gov/standards/datetime/ Extended Date Time Format efforts] based at the USA's Library of Congress (Covers unspecific dates; date periods and non-Gregorian dates) | ||
** [http://www.loc.gov/standards/datetime/proposals.html EDTF proposals] | ** [http://www.loc.gov/standards/datetime/proposals.html EDTF proposals] (use-cases) | ||
* [http://pigsonthewing.wordpress.com/2009/02/23/dates-and-coordinates-in-html5/ Dates and coordinates in HTML5] - blog post by [[User:Pigsonthewing|Andy Mabbett]] | * [http://pigsonthewing.wordpress.com/2009/02/23/dates-and-coordinates-in-html5/ Dates and coordinates in HTML5] - blog post by [[User:Pigsonthewing|Andy Mabbett]] | ||
** [http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-February/018639.html Feb 2009 whatwg mailing list discussion of the above] | ** [http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-February/018639.html Feb 2009 whatwg mailing list discussion of the above] | ||
Revision as of 11:44, 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:
- +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 fordatetimevalues 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 HTML5 Super Friends Technical Details: time element)
- +1 Andy Mabbett (Per use cases in VCARDDAV & EDTF - see external links)
- ...
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 fordatetimevalues 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 & EDTF - see external links)
- Portable contacts allows this using a "0000" year value.
- ...
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:
- +1 Tantek (per HTML5 Super Friends Technical Details: time element)
- +1 "radiz" implied support for --MM-DD with the use case question: "How to use <time> with a date in astrology?" in the article http://html5doctor.com/your-questions-answered-6/
- +1 Andy Mabbett (Per use cases discussed in VCARDDAV & EDTF, e.g. birthdays, wedding anniversaries - see external links)
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 & EDTF - see external links)
- ...
Fuzzy dates
The time element should accept fuzzy (uncertain, approximate) dates and eras.
Opinions / discussion:
- +1 Andy Mabbett (Per use cases in "Extended Date Time Format" proposals - see external links)
- ...
External links
- Extended Date Time Format efforts based at the USA's Library of Congress (Covers unspecific dates; date periods and non-Gregorian dates)
- EDTF proposals (use-cases)
- Dates and coordinates in HTML5 - blog post by Andy Mabbett
- vCard Format Specification draft-ietf-vcarddav-vcardrev-11 (latest draft as at July 2010)
- Section 4.3, date & time
- Section 5.7, CALSCALE (specifies Gregorian or other (e.g. Julian) calendar)
- ISO 8601 (Wikipedia article)