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

html5/spec Overview.html,1.2391,1.2392

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Sat, 13 Jun 2009 23:51:41 +0000
To: public-html-commits@w3.org
Message-Id: <E1MFd0f-0007Cr-Db@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv27687

Modified Files:
	Overview.html 
Log Message:
editorial cleanup (whatwg r3244)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2391
retrieving revision 1.2392
diff -u -d -r1.2391 -r1.2392
--- Overview.html	13 Jun 2009 20:08:38 -0000	1.2391
+++ Overview.html	13 Jun 2009 23:51:38 -0000	1.2392
@@ -1717,8 +1717,7 @@
   <code>application/xhtml+xml</code> and must not be served as
   <code>text/html</code>. <a href="#references">[RFC3023]</a><p id="authors-using-html">Documents that use <a href="#syntax">the HTML
   syntax</a>, if they are served over the wire (e.g. by HTTP) must
-  be labeled with the <code>text/html</code> MIME type.</p><!-- XXX
-  update RFC 2854 --><p class="impl" id="entity-references">The language in this
+  be labeled with the <code>text/html</code> MIME type.<p class="impl" id="entity-references">The language in this
   specification assumes that the user agent expands all entity
   references, and therefore does not include entity reference nodes in
   the DOM. If user agents do include entity reference nodes in the
@@ -1888,11 +1887,7 @@
   two strings as matches of each other.<h3 id="common-microsyntaxes"><span class="secno">2.4 </span>Common microsyntaxes</h3><p>There are various places in HTML that accept particular data
   types, such as dates or numbers. This section describes what the
   conformance criteria for content in those formats is, and how to
-  parse them.</p><!-- XXX need to define how to handle U+000A LINE FEED and U+000D
-  CARRIAGE RETURN in attributes (for HTML) --><p class="XXX">Need to go through the whole spec and make sure
-  all the attribute values are clearly defined either in terms of
-  microsyntaxes or in terms of other specs, or as "Text" or some
-  such.<div class="impl">
+  parse them.<div class="impl">
 
   <h4 id="common-parser-idioms"><span class="secno">2.4.1 </span>Common parser idioms</h4>
 
@@ -3157,10 +3152,7 @@
   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="#references">[GREGORIAN]</a></p><!--XXX [GREGORIAN] should point to
-  <dd id="refsGREGORIAN">[GREGORIAN]</dd>
-  <dd>(Non-normative) <cite>Inter Gravissimas</cite>, A. Lilius, C. Clavius. Gregory XIII Papal Bulls, February 1582.</dd>
-  --><p>A string is a <dfn id="valid-global-date-and-time-string">valid global date and time string</dfn>
+  zone, consisting of a number of hours and minutes. <a href="#references">[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>
 
@@ -3229,8 +3221,8 @@
     the time (e.g. from the Julian calendar). The date of Nero's birth
     is the 15th of December 37, in the Julian Calendar, which is the
     13th of December 37 in the proleptic Gregorian Calendar.</li> <!--
-    XXX this might not be true. I can't find a reference that gives
-    his birthday with an explicit statement about the calendar being
+    This might not be true. I can't find a reference that gives his
+    birthday with an explicit statement about the calendar being
     used. However, it seems unlikely that it would be given in the
     Gregorian calendar, so I assume sites use the Julian one. -->
 
@@ -4079,9 +4071,7 @@
 
     </dl></li>
 
-  </ol><!-- XXX we might want to define "server-based naming authority",
-  it's not clear RFC3986 does a good job of defining that anymore
-  (earlier URI specs did) --><p class="note">These parsing rules are a <a href="#willful-violation">willful
+  </ol><p class="note">These parsing rules are a <a href="#willful-violation">willful
   violation</a> of RFC 3986 and RFC 3987 (which do not define error
   handling), motivated by a desire to handle legacy content. <a href="#references">[RFC3986]</a> <a href="#references">[RFC3987]</a></p>
 
@@ -64051,6 +64041,9 @@
   1937. http://www.turingarchive.org/browse.php/B/12 (referenced:
   2007-03-03)
 
+  <dd id="refsGREGORIAN">[GREGORIAN]</dd>
+  <dd>(Non-normative) <cite>Inter Gravissimas</cite>, A. Lilius, C. Clavius. Gregory XIII Papal Bulls, February 1582.</dd>
+
   [UNICODECASE] Unicode Standard Annex #21, Case Mappings
 
   --><h2 class="no-num" id="acknowledgements">Acknowledgements</h2><!-- ACKS --><p>Thanks to
@@ -64719,4 +64712,5 @@
  XXX * s/raise/throw/g
  XXX * be clearer about arrays/lists/collections being zero-based
        despite using the term "/index/th".
+ XXX * update RFC 2854 (text/html reg)
 -->
Received on Saturday, 13 June 2009 23:51:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 13 June 2009 23:51:50 GMT