... です >>94。
This would be most useful when combined with a new HTML tag used to identify dates, such as this theoretical example:<p>The campaign started on <date value="1874-oct-21"> the twenty-first of that month</date> and finished <date value="1874-oct-28">a week later</date>
Some have advocated the creation of a <date> tag that would display dates according the locale of the user agent. This is subject to the same practical issues as described for dynamic date generation with the Japanese example. The appropriate format is generally a function of the linguistic context of a page, rather than the user's platform.
My first instinct was to try the <object> tag, since it has a nice mechanism for providing data within its 'data' attribute, and fallback plain text inside the element itself, e.g. (simplified for sake of discussion):<object data="20050125">January 25</object>This worked great in typical modern browsers, except for one: Safari (v1.2.1). Unfortunately, to put it mildly, Safari's <object> support sucks. It doesn't handle <object> fallbacks, it doesn't know when not to handle <object> mime types that it doesn't support, it doesn't support display:inline on <object>, and it doesn't do proper intrinsic sizing of <object> replaced elements. These are all trivial to reproduce bugs.
Humans don't think of dates and times in terms of fully qualified year, month, date, hour, minute, second, time-zone values. Humans think of dates and times in terms of only that which is necessary. The day, or the day and the month, or perhaps just the hour. What do all these have in common? They are all abbreviations for a fully qualified date and time.
Lucky for us, XHTML has an element for abbreviations: <abbr>.
Thus, the ISO8601 date 20050125 should be marked up as:<abbr title="20050125">January 25th</abbr>
<t> (or an equivalent) has been widely requested, especially in the microformats and CSS communities. Several microformats have need for encoding specific times and/or dates, and are currently (ab?)using <abbr> for this purpose. The CSS community has requested a <date> or <time> element because they want to restyle dates and times according to locale. The blogging and content publishing communities have also raised the need for a way to unambiguously mark up what part of their document is a date and/or time, though in their case (as with microformats) they need a way to then mark each date/time element as being a particular semantic (publishing date, birth date, calendar event time etc).
Also, the aforementioned research indicated that there are substantial amounts of content on the Web that uses invented elements, IDs, and class attributes to mark up dates and times. For example, I found about the same number of pages with the obscure ID "updatedtime" as I did pages with a <button> element; "date" was the 14th most frequently seen class name.
 Sam Ruby: The <time> element ( 版) http://www.intertwingly.net/blog/2007/04/17/The-time-element (名無しさん 2007-04-18 23:39:35 +00:00)
 しかしこの変更への反発から W3C HTML WG を中心に大きな混乱が生じ、 それまで WHATWG の HTML5 の複製だった W3C の HTML5 に独自の変更が加えられ、それをきっかけに両者が同期されなくなりました (それまでは W3C が独自の変更を決議しても、 Ian Hickson が編集している WHATWG HTML5 のソースファイルから W3C HTML5 を生成していました)。 W3C の HTML5 はこの騒動の後しばらく放置されていましたが、最終的には W3C が独自の編集者を雇用し、 WHATWG と決別して独自の仕様書を発行するようになります。
 Web Applications 1.0 r6783 Drop <time> and replace it with <data>. Drop the Atom conversion section entirely. Convert a bunch of examples that used to use <time pubdate> to using schema.org, to show how to annotate publication dates and the like in a machine-processable way. ( ( 版)) http://html5.org/tools/web-apps-tracker?from=6782&to=6783
 Web Applications 1.0 r6845 Update the date-and-time microsyntaxes to support having the 'T' replaced by a single space. (Note: multiple spaces are invalid and will cause parse failures. Only a single space is supported.) Based on proposal and implementation evidence from Tantek documented at http://wiki.whatwg.org/wiki/Time_element#permit_space_instead_of_T_in_datetimesAffected topics: HTML, Microdata ( ( 版)) http://html5.org/tools/web-apps-tracker?from=6844&to=6845