Add the ability to annotate custom microdata in HTML. (whatwg r3074)

Add the ability to annotate custom microdata in HTML. (whatwg r3074)

Diffs for this change per section: 
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2232.html#mediamodeabstractview
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2232.html#status-of-this-document
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2232.html#localization
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2232.html#editor-s-draft-date-1-january-1970
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2232.html#no
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2232.html#a-vocabulary-and-associated-apis-for-html-and-xhtml
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2232.html#declarative-3d-scenes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2232.html#rendering-and-the-dom

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2231&r2=1.2232&f=h
http://html5.org/tools/web-apps-tracker?from=3073&to=3074

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2231
retrieving revision 1.2232
diff -u -d -r1.2231 -r1.2232
--- Overview.html 7 May 2009 08:47:58 -0000 1.2231
+++ Overview.html 10 May 2009 10:31:43 -0000 1.2232
@@ -148,7 +148,7 @@
    <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>
    <!--ZZZ:-->
    <!--<h2 class="no-num no-toc">W3C Working Draft 23 April 2009</h2>-->
-   <h2 class="no-num no-toc" id="editor-s-draft-date-1-january-1970">Editor's Draft 7 May 2009</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-date-1-january-1970">Editor's Draft 10 May 2009</h2>
    <!--:ZZZ-->
    <dl><!-- ZZZ: update the month/day (twice), (un)comment out
     <dt>This Version:</dt>
@@ -241,7 +241,7 @@
   track.
   <!--ZZZ:-->
[...4278 lines suppressed...]
 
-  </ul></div><h2 id="no"><span class="secno">12 </span>Things that you can't do with this specification because
+  </ul></div><h2 id="no"><span class="secno">13 </span>Things that you can't do with this specification because
   they are better handled using other technologies that are further
   described herein</h2><p><em>This section is non-normative.</em><p>There are certain features that are not handled by this
   specification because a client side markup language is not the right
@@ -58995,10 +59639,10 @@
       DOM proper, and <pre>, where it is.)
 
   XXX should ensure these are filed with the relevant people and groups
-  --><h3 id="localization"><span class="secno">12.1 </span>Localization</h3><p>If you wish to create localized versions of an HTML application,
+  --><h3 id="localization"><span class="secno">13.1 </span>Localization</h3><p>If you wish to create localized versions of an HTML application,
   the best solution is to preprocess the files on the server, and then
-  use HTTP content negotiation to serve the appropriate language.</p><!-- <p>XXX example here</p> --><h3 id="declarative-3d-scenes"><span class="secno">12.2 </span>Declarative 3D scenes</h3><p>Embedding 3D imagery into XHTML documents is the domain of X3D,
-  or technologies based on X3D that are namespace-aware.</p><!-- <p>XXX example here</p> --><h3 id="rendering-and-the-dom"><span class="secno">12.3 </span>Rendering and the DOM</h3><p class="XXX">This section is expected to be moved to its own
+  use HTTP content negotiation to serve the appropriate language.</p><!-- <p>XXX example here</p> --><h3 id="declarative-3d-scenes"><span class="secno">13.2 </span>Declarative 3D scenes</h3><p>Embedding 3D imagery into XHTML documents is the domain of X3D,
+  or technologies based on X3D that are namespace-aware.</p><!-- <p>XXX example here</p> --><h3 id="rendering-and-the-dom"><span class="secno">13.3 </span>Rendering and the DOM</h3><p class="XXX">This section is expected to be moved to its own
   specification in due course. It needs a lot of work to actually make
   it into a semi-decent spec.<p>Any object implement the <code>AbstractView</code> interface must
   also implement the <code><a href="#mediamodeabstractview">MediaModeAbstractView</a></code> interface.<pre class="idl">[NoInterfaceObject, ImplementedOn=<span>AbstractView</span>] interface <dfn id="mediamodeabstractview">MediaModeAbstractView</dfn> {

Received on Monday, 18 May 2009 10:27:43 UTC