- From: poot <cvsmail@w3.org>
- Date: Fri, 20 Jan 2012 17:42:22 -0500
- To: public-html-diffs@w3.org
hixie: Introduce some documentation about wire formats vs presented
formats for date and time data. (whatwg r6904)
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.5501&r2=1.5502&f=h
http://html5.org/tools/web-apps-tracker?from=6903&to=6904
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5501
retrieving revision 1.5502
diff -u -d -r1.5501 -r1.5502
--- Overview.html 18 Jan 2012 22:56:54 -0000 1.5501
+++ Overview.html 20 Jan 2012 22:42:05 -0000 1.5502
@@ -320,7 +320,7 @@
<h1>HTML5</h1>
<h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
- <h2 class="no-num no-toc" id="editor-s-draft-18-january-2012">Editor's Draft 18 January 2012</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-19-january-2012">Editor's Draft 19 January 2012</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -467,7 +467,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 18 January 2012 Editor's Draft.
+ This specification is the 19 January 2012 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -835,7 +835,8 @@
<li><a href="#writing-a-form-s-user-interface"><span class="secno">4.10.1.1 </span>Writing a form's user interface</a></li>
<li><a href="#implementing-the-server-side-processing-for-a-form"><span class="secno">4.10.1.2 </span>Implementing the server-side processing for a form</a></li>
<li><a href="#configuring-a-form-to-communicate-with-a-server"><span class="secno">4.10.1.3 </span>Configuring a form to communicate with a server</a></li>
- <li><a href="#client-side-form-validation"><span class="secno">4.10.1.4 </span>Client-side form validation</a></ol></li>
+ <li><a href="#client-side-form-validation"><span class="secno">4.10.1.4 </span>Client-side form validation</a></li>
+ <li><a href="#date-and-time-formats"><span class="secno">4.10.1.5 </span>Date and time formats</a></ol></li>
<li><a href="#categories"><span class="secno">4.10.2 </span>Categories</a></li>
<li><a href="#the-form-element"><span class="secno">4.10.3 </span>The <code>form</code> element</a></li>
<li><a href="#the-fieldset-element"><span class="secno">4.10.4 </span>The <code>fieldset</code> element</a></li>
@@ -32718,7 +32719,34 @@
<p><label>Preferred delivery time: <input type=time min="11:00" max="21:00" step="900" name="delivery" required></label></p>
<p><label>Delivery instructions: <textarea name="comments"<strong> maxlength=1000</strong>></textarea></label></p>
<p><button>Submit order</button></p>
-</form></pre><h4 id="categories"><span class="secno">4.10.2 </span>Categories</h4><p>Mostly for historical reasons, elements in this section fall into
+</form></pre><h5 id="date-and-time-formats"><span class="secno">4.10.1.5 </span>Date and time formats</h5><p><i>This section is non-normative.</i><p>In this pizze delivery example, the times are specified in the
+ format "HH:MM": two digits for the hour, in 24-hour format, and two
+ digits for the time. (Seconds could also be specified, though they
+ are not necessary in this example.)<p>In some locales, however, times are often expressed differently
+ when presented to users. For example, in the United States, it is
+ still common to use the 12-hour clock with an am/pm indicator, as in
+ "2pm". In France, it is common to separate the hours from the
+ minutes using an "h" character, as in "14h00".<p>Similar issues exist with dates, with the added complication that
+ even the order of the components is not always consistent; for
+ example, in Cyprus the first of February 2003 would typically be
+ written "1/2/03", while that same date in Japan would typically be
+ written as "2003年02月01日".<p>It therefore is important to distinguish the time and date format
+ used in HTML and in form submissions, which are always the formats
+ defined in this specification (and based on the well-established ISO
+ 8601 standard for computer-readable date and time formats), from the
+ time and date formats presented to the user by the browser and
+ accepted as input from the user by the browser.<p>The format used "on the wire", i.e. in HTML markup and in form
+ submissions, is intended to be computer-readable and consistent
+ irrespective of the user's locale. Dates, for instance, are always
+ written in the format "YYYY-MM-DD", as in "2003-02-01". Users are
+ not expected to ever see this format.<p>The date or time given by the page in the wire format is then
+ translated to the user's preferred presentation (based on user
+ preferences or on the locale of the page itself), before being
+ displayed to the user. Similarly, after the user inputs a date or
+ time using their preferred format, the user agent converts it back
+ to the wire format before putting it in the DOM or submitting it.<p>This allows scripts in pages and on servers to process dates and
+ times in a consistent manner without needing to support dozens of
+ different formats, while still supporting the users' needs.<h4 id="categories"><span class="secno">4.10.2 </span>Categories</h4><p>Mostly for historical reasons, elements in this section fall into
several overlapping (but subtly different) categories in addition to
the usual ones like <a href="#flow-content">flow content</a>, <a href="#phrasing-content">phrasing
content</a>, and <a href="#interactive-content">interactive content</a>.<p>A number of the elements are <dfn id="form-associated-element" title="form-associated
Received on Friday, 20 January 2012 22:42:28 UTC