W3C home > Mailing lists > Public > public-html-commits@w3.org > August 2009

html5/spec Overview.html,1.2858,1.2859

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 26 Aug 2009 22:25:04 +0000
To: public-html-commits@w3.org
Message-Id: <E1MgQvQ-0000qS-Tt@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv3232

Modified Files:
	Overview.html 
Log Message:
Adjust terminology around time-zone offsets. (whatwg r3680)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2858
retrieving revision 1.2859
diff -u -d -r1.2858 -r1.2859
--- Overview.html	26 Aug 2009 03:56:41 -0000	1.2858
+++ Overview.html	26 Aug 2009 22:25:01 -0000	1.2859
@@ -3313,8 +3313,8 @@
   </ol></div><h5 id="global-dates-and-times"><span class="secno">2.4.5.5 </span>Global dates and times</h5><p>A <dfn id="concept-datetime" title="concept-datetime">global date and time</dfn>
   consists of a specific proleptic Gregorian date, consisting of a
   year, a month, and a day, and a time, consisting of an hour, a
-  minute, a second, and a fraction of a second, expressed with a time
-  zone, consisting of a number of hours and minutes. <a href="#refsGREGORIAN">[GREGORIAN]</a><p>A string is a <dfn id="valid-global-date-and-time-string">valid global date and time string</dfn>
+  minute, a second, and a fraction of a second, expressed with a
+  time-zone offset, consisting of a number of hours and minutes. <a href="#refsGREGORIAN">[GREGORIAN]</a><p>A string is a <dfn id="valid-global-date-and-time-string">valid global date and time string</dfn>
   representing a date, time, and a time-zone offset if it consists of
   the following components in the given order:<ol><li>A <a href="#valid-date-string">valid date string</a> representing the date</li>
 
@@ -3347,10 +3347,10 @@
 
     </ul></li>
 
-  </ol><p class="note">This format allows for time zone offsets from -23:59
-  to +23:59. In practice, however, the range of actual time zones is
-  -12:00 to +14:00, and the minutes component of actual time zones is
-  always either 00, 30, or 45.<div class="example">
+  </ol><p class="note">This format allows for time-zone offsets from -23:59
+  to +23:59. In practice, however, the range of offsets of actual time
+  zones is -12:00 to +14:00, and the minutes component of offsets of
+  actual time zones is always either 00, 30, or 45.<div class="example">
 
    <p>The following are some examples of dates written as <a href="#valid-global-date-and-time-string" title="valid global date and time string">valid global date and
    time strings</a>.</p>
@@ -3388,19 +3388,19 @@
     used. However, it seems unlikely that it would be given in the
     Gregorian calendar, so I assume sites use the Julian one. -->
 
-    <li>The time and time-zone components are not optional.</li>
+    <li>The time and time-zone offset components are not optional.</li>
 
     <li>Dates before the year zero can't be represented as a datetime
     in this version of HTML.</li>
 
-    <li>Time zones differ based on daylight savings time.</li>
+    <li>Time-zone offsets differ based on daylight savings time.</li>
 
    </ul></div><div class="impl">
 
   <p>The rules to <dfn id="parse-a-global-date-and-time-string">parse a global date and time string</dfn> are
   as follows. This will either return a time in UTC, with associated
-  time-zone information for round tripping or display purposes, or
-  nothing. If at any point the algorithm says that it "fails", this
+  time-zone offset information for round tripping or display purposes,
+  or nothing. If at any point the algorithm says that it "fails", this
   means that it is aborted at that point and returns nothing.</p>
 
   <ol><li><p>Let <var title="">input</var> be the string being
@@ -3419,7 +3419,8 @@
 
    <li><p>If <var title="">position</var> is beyond the end of <var title="">input</var>, then fail.</li>
 
-   <li><p><a href="#parse-a-time-zone-component">Parse a time-zone component</a> to obtain <var title="">timezone<sub title="">hours</sub></var> and <var title="">timezone<sub title="">minutes</sub></var>. If this returns
+   <li><p><a href="#parse-a-time-zone-offset-component">Parse a time-zone offset component</a> to obtain
+   <var title="">timezone<sub title="">hours</sub></var> and <var title="">timezone<sub title="">minutes</sub></var>. If this returns
    nothing, then fail.</p>
 
    <li><p>If <var title="">position</var> is <em>not</em> beyond the
@@ -3437,11 +3438,11 @@
 
    <li><p>Return <var title="">time</var> and <var title="">timezone</var>.</li>
 
-  </ol><p>The rules to <dfn id="parse-a-time-zone-component">parse a time-zone component</dfn>, given an <var title="">input</var> string and a <var title="">position</var>, are
-  as follows. This will either return time-zone hours and time-zone
-  minutes, or nothing. If at any point the algorithm says that it
-  "fails", this means that it is aborted at that point and returns
-  nothing.</p>
+  </ol><p>The rules to <dfn id="parse-a-time-zone-offset-component">parse a time-zone offset component</dfn>, given
+  an <var title="">input</var> string and a <var title="">position</var>, are as follows. This will either return
+  time-zone hours and time-zone minutes, or nothing. If at any point
+  the algorithm says that it "fails", this means that it is aborted at
+  that point and returns nothing.</p>
 
   <ol><li>
 
@@ -3637,9 +3638,9 @@
 
    <li><p>If the <var title="">date present</var> and <var title="">time present</var> flags are both true, but <var title="">position</var> is beyond the end of <var title="">input</var>, then fail.</li>
 
-   <li><p>If the <var title="">date present</var> and <var title="">time present</var> flags are both true, <a href="#parse-a-time-zone-component">parse a
-   time-zone component</a> to obtain <var title="">timezone<sub title="">hours</sub></var> and <var title="">timezone<sub title="">minutes</sub></var>. If this returns nothing, then
-   fail.</p>
+   <li><p>If the <var title="">date present</var> and <var title="">time present</var> flags are both true, <a href="#parse-a-time-zone-offset-component">parse a
+   time-zone offset component</a> to obtain <var title="">timezone<sub title="">hours</sub></var> and <var title="">timezone<sub title="">minutes</sub></var>. If this returns
+   nothing, then fail.</p>
 
    <li><p>For the <i>in content</i> variant: <a href="#skip-white_space-characters">skip White_Space
    characters</a>.</li>
@@ -14436,7 +14437,8 @@
    </dd>
   </dl><p>The <code><a href="#the-time-element">time</a></code> element <a href="#represents">represents</a> either a
   time on a 24 hour clock, or a precise date in the proleptic
-  Gregorian calendar, optionally with a time and a time zone. <a href="#refsGREGORIAN">[GREGORIAN]</a><p>This element is intended as a way to encode modern dates and
+  Gregorian calendar, optionally with a time and a time-zone
+  offset. <a href="#refsGREGORIAN">[GREGORIAN]</a><p>This element is intended as a way to encode modern dates and
   times in a machine-readable way so that user agents can offer to add
   them to the user's calendar. For example, adding birthday reminders
   or scheduling events.</p><!-- it's also intended for restyling to local conventions
@@ -14507,8 +14509,8 @@
   <p>The <dfn id="dom-time-datetime" title="dom-time-datetime"><code>dateTime</code></dfn> DOM
   attribute must <a href="#reflect">reflect</a> the <code title="attr-time-datetime"><a href="#attr-time-datetime">datetime</a></code> content attribute.</p>
 
-  <p>User agents, to obtain the <dfn id="concept-time-date" title="concept-time-date">date</dfn>, <dfn id="concept-time-time" title="concept-time-time">time</dfn>, and <dfn id="concept-time-timezone" title="concept-time-timezone">time zone</dfn> represented by a
-  <code><a href="#the-time-element">time</a></code> element, must follow these steps:</p>
+  <p>User agents, to obtain the <dfn id="concept-time-date" title="concept-time-date">date</dfn>, <dfn id="concept-time-time" title="concept-time-time">time</dfn>, and <dfn id="concept-time-timezone" title="concept-time-timezone">time-zone offset</dfn> represented by
+  a <code><a href="#the-time-element">time</a></code> element, must follow these steps:</p>
 
   <ol><li>If the <code title="attr-time-datetime"><a href="#attr-time-datetime">datetime</a></code>
    attribute is present, then use the rules to <a href="#parse-a-date-or-time-string">parse a date or
@@ -14521,14 +14523,14 @@
 
    <li>If <var title="">result</var> is empty (because the parsing
    failed), then the <a href="#concept-time-date" title="concept-time-date">date</a> is
-   unknown, the <a href="#concept-time-time" title="concept-time-time">time</a> is unknown,
-   and the <a href="#concept-time-timezone" title="concept-time-timezone">time zone</a> is
-   unknown.</li>
+   unknown, the <a href="#concept-time-time" title="concept-time-time">time</a> is
+   unknown, and the <a href="#concept-time-timezone" title="concept-time-timezone">time-zone
+   offset</a> is unknown.</li>
 
    <li>Otherwise: if <var title="">result</var> contains a date, then
-   that is the <a href="#concept-time-date" title="concept-time-date">date</a>; if <var title="">result</var> contains a time, then that is the <a href="#concept-time-time" title="concept-time-time">time</a>; and if <var title="">result</var> contains a time zone, then the time zone is the
-   element's <a href="#concept-time-timezone" title="concept-time-timezone">time zone</a>. (A
-   time zone can only be present if both a date and a time are also
+   that is the <a href="#concept-time-date" title="concept-time-date">date</a>; if <var title="">result</var> contains a time, then that is the <a href="#concept-time-time" title="concept-time-time">time</a>; and if <var title="">result</var> contains a time-zone offset, then the
+   time-zone offset is the element's <a href="#concept-time-timezone" title="concept-time-timezone">time-zone offset</a>. (A time-zone
+   offset can only be present if both a date and a time are also
    present.)</li>
 
   </ol></div><dl class="domintro"><dt><var title="">time</var> . <code title="dom-time-date"><a href="#dom-time-date">date</a></code></dt>
@@ -14580,12 +14582,12 @@
   given <a href="#concept-time-time" title="concept-time-time">time</a> of 1970-01-01, with
   the time zone UTC.</p>
 
-  <p>The <dfn id="dom-time-timezone" title="dom-time-timezone"><code>timezone</code></dfn> DOM
-  attribute must return null if the <a href="#concept-time-timezone" title="concept-time-timezone">time zone</a> is unknown, and otherwise
-  must return the time corresponding to 1970-01-01 00:00 UTC in the
-  given <a href="#concept-time-timezone" title="concept-time-timezone">time zone</a>, with the
-  time zone set to UTC (i.e. the time corresponding to 1970-01-01 at
-  00:00 UTC plus the offset corresponding to the time zone).</p>
+  <p>The <dfn id="dom-time-timezone" title="dom-time-timezone"><code>timezone</code></dfn>
+  DOM attribute must return null if the <a href="#concept-time-timezone" title="concept-time-timezone">time-zone offset</a> is unknown,
+  and otherwise must return the time corresponding to 1970-01-01 00:00
+  UTC in the given <a href="#concept-time-timezone" title="concept-time-timezone">time-zone
+  offset</a>, with the time zone set to UTC (i.e. the time
+  corresponding to 1970-01-01 at 00:00 UTC plus the offset).</p>
 
   </div><div class="example">
 
@@ -15119,8 +15121,8 @@
   timestamp (the value is non-conforming; it is not a <a href="#valid-global-date-and-time-string">valid
   global date and time string</a>). Otherwise, the modification is
   marked as having been made at the given datetime. User agents should
-  use the associated time-zone information to determine which time zone
-  to present the given datetime in.</p>
+  use the associated time-zone offset information to determine which
+  time zone to present the given datetime in.</p>
 
   </div><p>The <code><a href="#the-ins-element">ins</a></code> and <code><a href="#the-del-element">del</a></code> elements <span class="impl">must</span> implement the <code><a href="#htmlmodelement">HTMLModElement</a></code>
   interface:<pre class="idl">interface <dfn id="htmlmodelement">HTMLModElement</dfn> : <a href="#htmlelement">HTMLElement</a> {
@@ -17580,7 +17582,7 @@
   <a href="#reflect">reflect</a> the respective content attributes of the same
   name.</p>
 
-  </div><h4 id="video"><span class="secno">4.8.7 </span>The <dfn><code>video</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/9">ISSUE-9</a> (video-synchronization), <a href="http://www.w3.org/html/wg/tracker/issues/7">ISSUE-7</a> (video-codecs) and <a href="http://www.w3.org/html/wg/tracker/issues/10">ISSUE-10</a> (video-smil) block progress to Last Call</span><dl class="element"><dt>Categories</dt>
+  </div><h4 id="video"><span class="secno">4.8.7 </span>The <dfn><code>video</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/10">ISSUE-10</a> (video-smil), <a href="http://www.w3.org/html/wg/tracker/issues/7">ISSUE-7</a> (video-codecs) and <a href="http://www.w3.org/html/wg/tracker/issues/9">ISSUE-9</a> (video-synchronization) block progress to Last Call</span><dl class="element"><dt>Categories</dt>
    <dd><a href="#flow-content">Flow content</a>.</dd>
    <dd><a href="#phrasing-content">Phrasing content</a>.</dd>
    <dd><a href="#embedded-content">Embedded content</a>.</dd>
@@ -28847,7 +28849,7 @@
   </div><p>The <code><a href="#the-input-element">input</a></code> element <a href="#represents">represents</a> a control
   for setting the element's <a href="#concept-fe-value" title="concept-fe-value">value</a> to a string representing a
   <a href="#concept-datetime-local" title="concept-datetime-local">local date and time</a>,
-  with no time zone information.<div class="impl">
+  with no time-zone offset information.<div class="impl">
 
   <p>If the element is <i title="concept-input-mutable"><a href="#concept-input-mutable">mutable</a></i>,
   the user agent should allow the user to change the <a href="#concept-datetime-local" title="concept-datetime-local">date and time</a> represented by
@@ -48382,7 +48384,7 @@
   <a href="#source-browsing-context">source browsing context</a>.</p>
 
 
-  <h5 id="hyperlink-auditing"><span class="secno">6.12.2.1 </span><dfn>Hyperlink auditing</dfn></h5><p class="XXX annotation"><b>Status: </b><i>Controversial Working Draft. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/63">ISSUE-63</a> (origin-req-scope), <a href="http://www.w3.org/html/wg/tracker/issues/1">ISSUE-1</a> (PINGPOST) and <a href="http://www.w3.org/html/wg/tracker/issues/2">ISSUE-2</a> (PINGUI) block progress to Last Call</span></p>
+  <h5 id="hyperlink-auditing"><span class="secno">6.12.2.1 </span><dfn>Hyperlink auditing</dfn></h5><p class="XXX annotation"><b>Status: </b><i>Controversial Working Draft. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/1">ISSUE-1</a> (PINGPOST), <a href="http://www.w3.org/html/wg/tracker/issues/2">ISSUE-2</a> (PINGUI) and <a href="http://www.w3.org/html/wg/tracker/issues/63">ISSUE-63</a> (origin-req-scope) block progress to Last Call</span></p>
 
   <p>If an <code><a href="#the-a-element">a</a></code> or <code><a href="#the-area-element">area</a></code> hyperlink element has a
   <code title="attr-hyperlink-ping"><a href="#ping">ping</a></code> attribute, and the
@@ -53435,7 +53437,7 @@
   the ranges U+0041 .. U+005A (LATIN CAPITAL LETTER A to LATIN CAPITAL
   LETTER Z) and U+0061 .. U+007A (LATIN SMALL LETTER A to LATIN SMALL
   LETTER Z). For convenience, in this section this is just referred to
-  as "case-insensitive".<h4 id="the-doctype"><span class="secno">9.1.1 </span>The DOCTYPE</h4><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/4">ISSUE-4</a> (html-versioning) and <a href="http://www.w3.org/html/wg/tracker/issues/54">ISSUE-54</a> (doctype-legacy-compat) block progress to Last Call</span><p>A <dfn id="syntax-doctype" title="syntax-doctype">DOCTYPE</dfn> is a mostly useless,
+  as "case-insensitive".<h4 id="the-doctype"><span class="secno">9.1.1 </span>The DOCTYPE</h4><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/54">ISSUE-54</a> (doctype-legacy-compat) and <a href="http://www.w3.org/html/wg/tracker/issues/4">ISSUE-4</a> (html-versioning) block progress to Last Call</span><p>A <dfn id="syntax-doctype" title="syntax-doctype">DOCTYPE</dfn> is a mostly useless,
   but required, header.<p class="note">DOCTYPEs are required for legacy reasons. When
   omitted, browsers tend to use a different rendering mode that is
   incompatible with some specifications. Including the DOCTYPE in a
@@ -64933,7 +64935,7 @@
 
   <p>When the <i title="">time</i> binding applies to a
   <code><a href="#the-time-element">time</a></code> element, the element is expected to render as if
-  it contained text conveying the <a href="#concept-time-date" title="concept-time-date">date</a> (if known), <a href="#concept-time-time" title="concept-time-time">time</a> (if known), and <a href="#concept-time-timezone" title="concept-time-timezone">time zone</a> (if known)
+  it contained text conveying the <a href="#concept-time-date" title="concept-time-date">date</a> (if known), <a href="#concept-time-time" title="concept-time-time">time</a> (if known), and <a href="#concept-time-timezone" title="concept-time-timezone">time-zone offset</a> (if known)
   represented by the element, in the fashion most convenient for the
   user.</p>
 
Received on Wednesday, 26 August 2009 22:25:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 26 August 2009 22:25:22 GMT