html5/spec Overview.html,1.2257,1.2258

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv20389

Modified Files:
	Overview.html 
Log Message:
note future extension ideas for microdata (whatwg r3100)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2257
retrieving revision 1.2258
diff -u -d -r1.2257 -r1.2258
--- Overview.html	14 May 2009 23:08:47 -0000	1.2257
+++ Overview.html	14 May 2009 23:12:03 -0000	1.2258
@@ -36233,7 +36233,28 @@
   those are all defined in sufficient detail in a language-agnostic
   fashion in the Selectors specification. <a href="#references">[SELECTORS]</a></p>
 
-  </div><h2 id="microdata"><span class="secno">5 </span><dfn>Microdata</dfn></h2><h3 id="introduction-2"><span class="secno">5.1 </span>Introduction</h3><h4 id="the-basic-syntax"><span class="secno">5.1.1 </span>The basic syntax</h4><p><em>This section is non-normative.</em><p>Sometimes, it is desirable to annotate content with specific
+  </div><h2 id="microdata"><span class="secno">5 </span><dfn>Microdata</dfn></h2><!-- v2
+
+  * <ref property="foo" content="id"> to import the item with id="id"
+    into the current microdata block
+
+  * splitting the 'content' part of a property into multiple sub-bits,
+    as in:
+
+     <span property="tel" content-in-bits>
+       Telephone:
+       <span content-bit>+44</span> (0) <span content-bit>1223 123 123</span>
+     </span>
+
+    maybe vocabs that need this can use a sub vocabulary specifically
+    for this:
+
+     <span property="tel" item="bits">
+       Telephone:
+       <span property=bit>+44</span> (0) <span property=bit>1223 123 123</span>
+     </span>
+
+--><h3 id="introduction-2"><span class="secno">5.1 </span>Introduction</h3><h4 id="the-basic-syntax"><span class="secno">5.1.1 </span>The basic syntax</h4><p><em>This section is non-normative.</em><p>Sometimes, it is desirable to annotate content with specific
   machine-readable labels, e.g. to allow generic scripts to provide
   services that are customised to the page, or to enable content from
   a variety of cooperating authors to be processed by a single script

Received on Thursday, 14 May 2009 23:12:15 UTC