- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 08 Jan 2010 06:48:39 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/md
In directory hutz:/tmp/cvs-serv826
Modified Files:
Overview.html
Log Message:
cleanup. This may introduce other problems; I'll clean them up too shortly. (whatwg r4543)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/md/Overview.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Overview.html 8 Jan 2010 02:03:48 -0000 1.1
+++ Overview.html 8 Jan 2010 06:48:37 -0000 1.2
@@ -380,55 +380,60 @@
permits reuse of the specification text.</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><h2 class="no-num no-toc" id="contents">Table of Contents</h2>
<!--begin-toc-->
<ol class="toc">
- <li><a href="#infrastructure"><span class="secno">1 </span>Common infrastructure</a>
+ <li><a href="#conformance"><span class="secno">1 </span>Conformance</a></li>
+ <li><a href="#infrastructure"><span class="secno">2 </span>Common infrastructure</a>
<ol>
- <li><a href="#htmlpropertiescollection-0"><span class="secno">1.1 </span>HTMLPropertiesCollection</a></ol></li>
- <li><a href="#introduction"><span class="secno">2 </span>Introduction</a>
+ <li><a href="#htmlpropertiescollection-0"><span class="secno">2.1 </span>HTMLPropertiesCollection</a></ol></li>
+ <li><a href="#introduction"><span class="secno">3 </span>Introduction</a>
<ol>
- <li><a href="#overview"><span class="secno">2.1 </span>Overview</a></li>
- <li><a href="#the-basic-syntax"><span class="secno">2.2 </span>The basic syntax</a></li>
- <li><a href="#typed-items"><span class="secno">2.3 </span>Typed items</a></li>
- <li><a href="#global-identifiers-for-items"><span class="secno">2.4 </span>Global identifiers for items</a></li>
- <li><a href="#selecting-names-when-defining-vocabularies"><span class="secno">2.5 </span>Selecting names when defining vocabularies</a></li>
- <li><a href="#using-the-microdata-dom-api"><span class="secno">2.6 </span>Using the microdata DOM API</a></ol></li>
- <li><a href="#encoding-microdata"><span class="secno">3 </span>Encoding microdata</a>
+ <li><a href="#overview"><span class="secno">3.1 </span>Overview</a></li>
+ <li><a href="#the-basic-syntax"><span class="secno">3.2 </span>The basic syntax</a></li>
+ <li><a href="#typed-items"><span class="secno">3.3 </span>Typed items</a></li>
+ <li><a href="#global-identifiers-for-items"><span class="secno">3.4 </span>Global identifiers for items</a></li>
+ <li><a href="#selecting-names-when-defining-vocabularies"><span class="secno">3.5 </span>Selecting names when defining vocabularies</a></li>
+ <li><a href="#using-the-microdata-dom-api"><span class="secno">3.6 </span>Using the microdata DOM API</a></ol></li>
+ <li><a href="#encoding-microdata"><span class="secno">4 </span>Encoding microdata</a>
<ol>
- <li><a href="#the-microdata-model"><span class="secno">3.1 </span>The microdata model</a></li>
- <li><a href="#items"><span class="secno">3.2 </span>Items</a></li>
- <li><a href="#names:-the-itemprop-attribute"><span class="secno">3.3 </span>Names: the <code>itemprop</code> attribute</a></li>
- <li><a href="#values"><span class="secno">3.4 </span>Values</a></li>
- <li><a href="#associating-names-with-items"><span class="secno">3.5 </span>Associating names with items</a></li>
- <li><a href="#examples"><span class="secno">3.6 </span>Examples</a></ol></li>
- <li><a href="#microdata-dom-api"><span class="secno">4 </span>Microdata DOM API</a></li>
- <li><a href="#other-changes-to-html5"><span class="secno">5 </span>Other changes to HTML5</a>
+ <li><a href="#the-microdata-model"><span class="secno">4.1 </span>The microdata model</a></li>
+ <li><a href="#items"><span class="secno">4.2 </span>Items</a></li>
+ <li><a href="#names:-the-itemprop-attribute"><span class="secno">4.3 </span>Names: the <code>itemprop</code> attribute</a></li>
+ <li><a href="#values"><span class="secno">4.4 </span>Values</a></li>
+ <li><a href="#associating-names-with-items"><span class="secno">4.5 </span>Associating names with items</a></li>
+ <li><a href="#examples"><span class="secno">4.6 </span>Examples</a></ol></li>
+ <li><a href="#microdata-dom-api"><span class="secno">5 </span>Microdata DOM API</a></li>
+ <li><a href="#other-changes-to-html5"><span class="secno">6 </span>Other changes to HTML5</a>
<ol>
- <li><a href="#content-models"><span class="secno">5.1 </span>Content models</a></li>
- <li><a href="#drag-and-drop"><span class="secno">5.2 </span>Drag-and-drop</a></ol></li>
- <li><a href="#microdata-vocabularies"><span class="secno">6 </span>Microdata vocabularies</a>
+ <li><a href="#content-models"><span class="secno">6.1 </span>Content models</a></li>
+ <li><a href="#drag-and-drop"><span class="secno">6.2 </span>Drag-and-drop</a></ol></li>
+ <li><a href="#microdata-vocabularies"><span class="secno">7 </span>Microdata vocabularies</a>
<ol>
- <li><a href="#vcard"><span class="secno">6.1 </span>vCard</a>
+ <li><a href="#vcard"><span class="secno">7.1 </span>vCard</a>
<ol>
- <li><a href="#conversion-to-vcard"><span class="secno">6.1.1 </span>Conversion to vCard</a></li>
- <li><a href="#examples-0"><span class="secno">6.1.2 </span>Examples</a></ol></li>
- <li><a href="#vevent"><span class="secno">6.2 </span>vEvent</a>
+ <li><a href="#conversion-to-vcard"><span class="secno">7.1.1 </span>Conversion to vCard</a></li>
+ <li><a href="#examples-0"><span class="secno">7.1.2 </span>Examples</a></ol></li>
+ <li><a href="#vevent"><span class="secno">7.2 </span>vEvent</a>
<ol>
- <li><a href="#conversion-to-icalendar"><span class="secno">6.2.1 </span>Conversion to iCalendar</a></li>
- <li><a href="#examples-1"><span class="secno">6.2.2 </span>Examples</a></ol></li>
- <li><a href="#licensing-works"><span class="secno">6.3 </span>Licensing works</a>
+ <li><a href="#conversion-to-icalendar"><span class="secno">7.2.1 </span>Conversion to iCalendar</a></li>
+ <li><a href="#examples-1"><span class="secno">7.2.2 </span>Examples</a></ol></li>
+ <li><a href="#licensing-works"><span class="secno">7.3 </span>Licensing works</a>
<ol>
- <li><a href="#conversion-to-rdf"><span class="secno">6.3.1 </span>Conversion to RDF</a></li>
- <li><a href="#examples-2"><span class="secno">6.3.2 </span>Examples</a></ol></ol></li>
- <li><a href="#converting-html-to-other-formats"><span class="secno">7 </span>Converting HTML to other formats</a>
+ <li><a href="#conversion-to-rdf"><span class="secno">7.3.1 </span>Conversion to RDF</a></li>
+ <li><a href="#examples-2"><span class="secno">7.3.2 </span>Examples</a></ol></ol></li>
+ <li><a href="#converting-html-to-other-formats"><span class="secno">8 </span>Converting HTML to other formats</a>
<ol>
- <li><a href="#json"><span class="secno">7.1 </span>JSON</a></li>
- <li><a href="#rdf"><span class="secno">7.2 </span>RDF</a></ol></li>
- <li><a href="#iana"><span class="secno">8 </span>IANA considerations</a>
+ <li><a href="#json"><span class="secno">8.1 </span>JSON</a></li>
+ <li><a href="#rdf"><span class="secno">8.2 </span>RDF</a></ol></li>
+ <li><a href="#iana"><span class="secno">9 </span>IANA considerations</a>
<ol>
- <li><a href="#application-microdata-json"><span class="secno">8.1 </span><code>application/microdata+json</code></a></ol></li>
- <li><a class="no-num" href="#references">References</a></ol>
-<!--end-toc--><hr><h2 id="infrastructure"><span class="secno">1 </span>Common infrastructure</h2><p>This specification relies on the infrastructure and conformance
+ <li><a href="#application-microdata-json"><span class="secno">9.1 </span><code>application/microdata+json</code></a></ol></li>
+ <li><a class="no-num" href="#references">References</a></li>
+ <li><a href="#acknowledgements"><span class="secno">10 </span>Acknowledgements</a></ol>
+<!--end-toc--><hr><h2 id="conformance"><span class="secno">1 </span>Conformance</h2><p>Definitions of terms and conformance classes used in this
+ specification, as well as a general introduction to the HTML5 series
+ of specifiations, can be found in the <a href="http://dev.w3.org/html5/spec/spec.html">HTML5 Core and
+ Vocabularies</a> specification.<h2 id="infrastructure"><span class="secno">2 </span>Common infrastructure</h2><p>This specification relies on the infrastructure and conformance
requirements defined in the HTML5 Core and Vocabulary
- specification.<h4 id="htmlpropertiescollection-0"><span class="secno">1.1 </span>HTMLPropertiesCollection</h4><p>The <code><a href="#htmlpropertiescollection">HTMLPropertiesCollection</a></code> interface represents a
+ specification.<h4 id="htmlpropertiescollection-0"><span class="secno">2.1 </span>HTMLPropertiesCollection</h4><p>The <code><a href="#htmlpropertiescollection">HTMLPropertiesCollection</a></code> interface represents a
<span title="collections">collection</span> of elements that add
name-value pairs to a particular <a href="#concept-item" title="concept-item">item</a> in the <span>microdata</span>
model.<pre class="idl">interface <dfn id="htmlpropertiescollection">HTMLPropertiesCollection</dfn> : <span>HTMLCollection</span> {
@@ -509,14 +514,14 @@
values obtained from the <code title="dom-itemValue"><a href="#dom-itemvalue">itemValue</a></code> DOM property of each of the
elements represented by the object, in <span>tree order</span>.</p>
- </div><h2 id="introduction"><span class="secno">2 </span>Introduction</h2><h3 id="overview"><span class="secno">2.1 </span>Overview</h3><p><i>This section is non-normative.</i><p>Sometimes, it is desirable to annotate content with specific
+ </div><h2 id="introduction"><span class="secno">3 </span>Introduction</h2><h3 id="overview"><span class="secno">3.1 </span>Overview</h3><p><i>This section is non-normative.</i><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
in a consistent manner.<p>For this purpose, authors can use the microdata features
described in this section. Microdata allows nested groups of
name-value pairs to be added to documents, in parallel with the
- existing content.<h3 id="the-basic-syntax"><span class="secno">2.2 </span>The basic syntax</h3><p><i>This section is non-normative.</i><p>At a high level, microdata consists of a group of name-value
+ existing content.<h3 id="the-basic-syntax"><span class="secno">3.2 </span>The basic syntax</h3><p><i>This section is non-normative.</i><p>At a high level, microdata consists of a group of name-value
pairs. The groups are called <a href="#concept-item" title="concept-item">items</a>, and each name-value pair is a
property. Items and properties are represented by regular
elements.<p>To create an item, the <code title="attr-itemscope"><a href="#attr-itemscope">itemscope</a></code> attribute is used.<p>To add a property to an item, the <code title="attr-itemprop"><a href="#names:-the-itemprop-attribute">itemprop</a></code> attribute is used on one of
@@ -664,7 +669,7 @@
drag-and-drop data. In neither case is the image in any way
associated with the item.</p>
- </div><h3 id="typed-items"><span class="secno">2.3 </span>Typed items</h3><p><i>This section is non-normative.</i><p>The examples in the previous section show how information could
+ </div><h3 id="typed-items"><span class="secno">3.3 </span>Typed items</h3><p><i>This section is non-normative.</i><p>The examples in the previous section show how information could
be marked up on a page that doesn't expect its microdata to be
re-used. Microdata is most useful, though, when it is used in
contexts where other authors and readers are able to cooperate to
@@ -692,7 +697,7 @@
given for an item with the type "http://census.example/person" might
refer to the economic class of an individual, while a property named
"class" given for an item with the type "http://example.com/school/teacher"
- might refer to the classroom a teacher has been assigned.<h3 id="global-identifiers-for-items"><span class="secno">2.4 </span>Global identifiers for items</h3><p><i>This section is non-normative.</i><p>Sometimes, an <a href="#concept-item" title="concept-item">item</a> gives
+ might refer to the classroom a teacher has been assigned.<h3 id="global-identifiers-for-items"><span class="secno">3.4 </span>Global identifiers for items</h3><p><i>This section is non-normative.</i><p>Sometimes, an <a href="#concept-item" title="concept-item">item</a> gives
information about a topic that has a global identifier. For example,
books can be identified by their ISBN number.<p>Vocabularies (as identified by the <code title="attr-itemtype"><a href="#attr-itemtype">itemtype</a></code> attribute) can be designed
such that <a href="#concept-item" title="concept-item">items</a> get associated
@@ -731,7 +736,7 @@
leads to a situation where it is ambiguous whether the identifier,
and thus the set of properties specified in the microdata,
references the page or something else.</p>
- --><h3 id="selecting-names-when-defining-vocabularies"><span class="secno">2.5 </span>Selecting names when defining vocabularies</h3><p><i>This section is non-normative.</i><p>Using microdata means using a vocabulary. For some purposes, an
+ --><h3 id="selecting-names-when-defining-vocabularies"><span class="secno">3.5 </span>Selecting names when defining vocabularies</h3><p><i>This section is non-normative.</i><p>Using microdata means using a vocabulary. For some purposes, an
ad-hoc vocabulary is adequate. For others, a vocabulary will need to
be designed. Where possible, authors are encouraged to re-use
existing vocabularies, as this makes content re-use easier.<p>When designing new vocabularies, identifiers can be created
@@ -786,7 +791,7 @@
<td>white
<tr><td>img
<td>.../hedral.jpeg
- </table></div><h3 id="using-the-microdata-dom-api"><span class="secno">2.6 </span>Using the microdata DOM API</h3><p><i>This section is non-normative.</i><p>The microdata becomes even more useful when scripts can use it to
+ </table></div><h3 id="using-the-microdata-dom-api"><span class="secno">3.6 </span>Using the microdata DOM API</h3><p><i>This section is non-normative.</i><p>The microdata becomes even more useful when scripts can use it to
expose information to the user, for example offering it in a form
that can be used by other applications.<p>The <code title="dom-document-getItems"><a href="#dom-document-getitems">document.getItems(<var title="">typeNames</var>)</a></code> method provides access to the
<a href="#top-level-microdata-items">top-level microdata items</a>. It returns a
@@ -891,13 +896,13 @@
</ul><p>(The duplicate occurrence of "http://example.com/color" is not included
in the list.)</p>
- </div><h2 id="encoding-microdata"><span class="secno">3 </span>Encoding microdata</h2><p>The following attributes are added as <span>global
+ </div><h2 id="encoding-microdata"><span class="secno">4 </span>Encoding microdata</h2><p>The following attributes are added as <span>global
attributes</span> to HTML elements:<ul class="brief"><li><code title="attr-itemid"><a href="#attr-itemid">itemid</a></code></li>
<li><code title="attr-itemprop"><a href="#names:-the-itemprop-attribute">itemprop</a></code></li>
<li><code title="attr-itemref"><a href="#attr-itemref">itemref</a></code></li>
<li><code title="attr-itemscope"><a href="#attr-itemscope">itemscope</a></code></li>
<li><code title="attr-itemtype"><a href="#attr-itemtype">itemtype</a></code></li>
- </ul><h3 id="the-microdata-model"><span class="secno">3.1 </span>The microdata model</h3><p>The microdata model consists of groups of name-value pairs known
+ </ul><h3 id="the-microdata-model"><span class="secno">4.1 </span>The microdata model</h3><p>The microdata model consists of groups of name-value pairs known
as <a href="#concept-item" title="concept-item">items</a>.<p>Each group is known as an <a href="#concept-item" title="concept-item">item</a>. Each <a href="#concept-item" title="concept-item">item</a> can have an <a href="#item-type">item type</a>,
a <a href="#global-identifier">global identifier</a> (if the <a href="#item-type">item type</a>
<a href="#support-global-identifiers-for-items" title="support global identifiers for items">supports global
@@ -910,7 +915,7 @@
item">property</a> of a <a href="#typed-item">typed item</a>. The
<dfn id="relevant-type">relevant type</dfn> for a <a href="#typed-item">typed item</a> is the <a href="#concept-item" title="concept-item">item</a>'s <a href="#item-type">item type</a>, if it has
one, or else is the <a href="#relevant-type">relevant type</a> of the <a href="#concept-item" title="concept-item">item</a> for which it is a <a href="#the-properties-of-an-item" title="the
- properties of an item">property</a>'s <a href="#concept-property-value" title="concept-property-value">value</a>.<h3 id="items"><span class="secno">3.2 </span>Items</h3><p>Every <span title="HTML elements">HTML element</span> may have an
+ properties of an item">property</a>'s <a href="#concept-property-value" title="concept-property-value">value</a>.<h3 id="items"><span class="secno">4.2 </span>Items</h3><p>Every <span title="HTML elements">HTML element</span> may have an
<dfn id="attr-itemscope" title="attr-itemscope"><code>itemscope</code></dfn> attribute
specified. The <code title="attr-itemscope"><a href="#attr-itemscope">itemscope</a></code>
attribute is a <span>boolean attribute</span>.<p>An element with the <code title="attr-itemscope"><a href="#attr-itemscope">itemscope</a></code>
@@ -949,7 +954,7 @@
unique space-separated tokens</span> consisting of <span title="concept-ID">IDs</span> of elements in the same document; for
each one, the element's nearest ancestor element with an <code title="attr-itemscope"><a href="#attr-itemscope">itemscope</a></code> attribute specified, if any,
must not be the element with the referencing <code title="attr-itemref"><a href="#attr-itemref">itemref</a></code> attribute specified.<p>The <code title="attr-itemref"><a href="#attr-itemref">itemref</a></code> attribute must not
- be specified on elements that do not have an <code title="attr-itemscope"><a href="#attr-itemscope">itemscope</a></code> attribute specified.<h3 id="names:-the-itemprop-attribute"><span class="secno">3.3 </span>Names: the <dfn title="attr-itemprop"><code>itemprop</code></dfn> attribute</h3><p>Every <span title="HTML elements">HTML element</span> may have an
+ be specified on elements that do not have an <code title="attr-itemscope"><a href="#attr-itemscope">itemscope</a></code> attribute specified.<h3 id="names:-the-itemprop-attribute"><span class="secno">4.3 </span>Names: the <dfn title="attr-itemprop"><code>itemprop</code></dfn> attribute</h3><p>Every <span title="HTML elements">HTML element</span> may have an
<code title="attr-itemprop"><a href="#names:-the-itemprop-attribute">itemprop</a></code> attribute specified, if
doing so <a href="#the-properties-of-an-item" title="the properties of an item">adds a
property</a> to one or more <a href="#concept-item" title="concept-item">items</a> (as defined below).<p>The <code title="attr-itemprop"><a href="#names:-the-itemprop-attribute">itemprop</a></code> attribute, if
@@ -1029,7 +1034,7 @@
</div>
</pre>
- </div><h3 id="values"><span class="secno">3.4 </span>Values</h3><p>The <dfn id="concept-property-value" title="concept-property-value">property value</dfn> of a
+ </div><h3 id="values"><span class="secno">4.4 </span>Values</h3><p>The <dfn id="concept-property-value" title="concept-property-value">property value</dfn> of a
name-value pair added by an element with an <code title="attr-itemprop"><a href="#names:-the-itemprop-attribute">itemprop</a></code> attribute depends on the
element, as follows:<dl><dt>If the element also has an <code title="attr-itemscope"><a href="#attr-itemscope">itemscope</a></code> attribute</dt>
@@ -1093,7 +1098,7 @@
elements.<p>If a property's <a href="#concept-property-value" title="concept-property-value">value</a>
is an <span>absolute URL</span>, the property must be specified
using a <a href="#url-property-elements" title="URL property elements">URL property
- element</a>.<h3 id="associating-names-with-items"><span class="secno">3.5 </span>Associating names with items</h3><p>To find <dfn id="the-properties-of-an-item">the properties of an item</dfn>, the user agent must
+ element</a>.<h3 id="associating-names-with-items"><span class="secno">4.5 </span>Associating names with items</h3><p>To find <dfn id="the-properties-of-an-item">the properties of an item</dfn>, the user agent must
run the following steps:<ol><li><p>Let <var title="">root</var> be the element with the <code title="attr-itemscope"><a href="#attr-itemscope">itemscope</a></code> attribute.</li>
<li><p>Let <var title="">pending</var> be a stack of elements
@@ -1156,7 +1161,7 @@
</ol><p>A document must not contain any elements that have an <code title="attr-itemprop"><a href="#names:-the-itemprop-attribute">itemprop</a></code> attribute that would not be
found to be a property of any of the <a href="#concept-item" title="concept-item">items</a> in that document were their <a href="#the-properties-of-an-item" title="the properties of an item">properties</a> all to be
determined.<p>An <a href="#concept-item" title="concept-item">item</a> is a <dfn id="top-level-microdata-items" title="top-level microdata items">top-level microdata item</dfn> if
- its element does not have an <code title="attr-itemprop"><a href="#names:-the-itemprop-attribute">itemprop</a></code> attribute.<h3 id="examples"><span class="secno">3.6 </span>Examples</h3><p>Here is an example of some HTML using Microdata to express RDF
+ its element does not have an <code title="attr-itemprop"><a href="#names:-the-itemprop-attribute">itemprop</a></code> attribute.<h3 id="examples"><span class="secno">4.6 </span>Examples</h3><p>Here is an example of some HTML using Microdata to express RDF
statements:<pre><dl itemscope
itemtype="http://purl.org/vocab/frbr/core#Work"
itemid="http://purl.oreilly.com/works/45U8QJGZSQKDH8N">
@@ -1192,7 +1197,7 @@
dc:type <http://purl.oreilly.com/product-types/BOOK> .
<http://purl.oreilly.com/products/9780596802189.EBOOK> a frbr:Expression ;
- dc:type <http://purl.oreilly.com/product-types/EBOOK> .</pre><h2 id="microdata-dom-api"><span class="secno">4 </span>Microdata DOM API</h2><pre class="idl">[Supplemental] interface <span>HTMLDocument</span> { <!--WARNING: ALSO DUPLICATED IN HTMLDocument SECTION-->
+ dc:type <http://purl.oreilly.com/product-types/EBOOK> .</pre><h2 id="microdata-dom-api"><span class="secno">5 </span>Microdata DOM API</h2><pre class="idl">[Supplemental] interface <span>HTMLDocument</span> { <!--WARNING: ALSO DUPLICATED IN HTMLDocument SECTION-->
NodeList <a href="#dom-document-getitems" title="dom-document-getItems">getItems</a>(in optional DOMString typeNames); // <span>microdata</span>
};
@@ -1331,7 +1336,7 @@
the IDL <code title="">DOMString</code> value before using it
according to the mappings described above.</p>
- </div><h2 id="other-changes-to-html5"><span class="secno">5 </span>Other changes to HTML5</h2><h3 id="content-models"><span class="secno">5.1 </span>Content models</h3><p>If the <code title="attr-itemprop"><a href="#names:-the-itemprop-attribute">itemprop</a></code> attribute is
+ </div><h2 id="other-changes-to-html5"><span class="secno">6 </span>Other changes to HTML5</h2><h3 id="content-models"><span class="secno">6.1 </span>Content models</h3><p>If the <code title="attr-itemprop"><a href="#names:-the-itemprop-attribute">itemprop</a></code> attribute is
present on <code>link</code> or <code>meta</code>, they are
<span>phrasing content</span>. The <code>link</code> and
<code>meta</code> elements may be used where <span>phrasing
@@ -1339,7 +1344,7 @@
and the <code title="attr-meta-content">content</code> attribute
must be present.<div class="impl">
- <h3 id="drag-and-drop"><span class="secno">5.2 </span>Drag-and-drop</h3>
+ <h3 id="drag-and-drop"><span class="secno">6.2 </span>Drag-and-drop</h3>
<p>The <span>drag-and-drop initialization steps</span> are:
@@ -1350,7 +1355,7 @@
string to the <code title="dom-DragEvent-dataTransfer">dataTransfer</code> member,
associated with the <code title="">application/microdata+json</code> format.</p>
</li>
- </ol></div><h2 id="microdata-vocabularies"><span class="secno">6 </span>Microdata vocabularies</h2><h3 id="vcard"><span class="secno">6.1 </span>vCard</h3><p>An item with the <a href="#item-type">item type</a> <dfn id="md-vcard" title="md-vcard"><code>http://microformats.org/profile/hcard</code></dfn>
+ </ol></div><h2 id="microdata-vocabularies"><span class="secno">7 </span>Microdata vocabularies</h2><h3 id="vcard"><span class="secno">7.1 </span>vCard</h3><p>An item with the <a href="#item-type">item type</a> <dfn id="md-vcard" title="md-vcard"><code>http://microformats.org/profile/hcard</code></dfn>
represents a person's or organization's contact information.<p>This vocabulary <a href="#support-global-identifiers-for-items" title="support global identifiers for
items">supports global identifiers for items</a>.<p>The following are the type's <a href="#defined-property-name" title="defined property
name">defined property names</a>. They are based on the
@@ -2466,7 +2471,7 @@
<span>URL</span>s are specified.</p>
<dd>
- </dl><h4 id="conversion-to-vcard"><span class="secno">6.1.1 </span>Conversion to vCard</h4><p>Given a list of nodes <var title="">nodes</var> in a
+ </dl><h4 id="conversion-to-vcard"><span class="secno">7.1.1 </span>Conversion to vCard</h4><p>Given a list of nodes <var title="">nodes</var> in a
<code>Document</code>, a user agent must run the following algorithm
to <dfn id="extracting-a-vcard" title="extracting a vCard">extract any vCard data
represented by those nodes</dfn> (only the first vCard is
@@ -2970,7 +2975,7 @@
the input does not conform to the rules described for the <code title="md-vcard"><a href="#md-vcard">http://microformats.org/profile/hcard</a></code>
<a href="#item-type">item type</a> and <a href="#defined-property-name" title="defined property
name">defined property names</a>.</p><!-- of course since vcard
- doesn't define error handling, this is somewhat problematic. --><h4 id="examples-0"><span class="secno">6.1.2 </span>Examples</h4><div class="example">
+ doesn't define error handling, this is somewhat problematic. --><h4 id="examples-0"><span class="secno">7.1.2 </span>Examples</h4><div class="example">
<p>Here is a long example vCard for a fictional character called
"Jack Bauer":</p>
@@ -3064,7 +3069,7 @@
N:Washington;George;;;
END:VCARD</pre>
- </div><!--END vCard--><h3 id="vevent"><span class="secno">6.2 </span>vEvent</h3><p>An item with the <a href="#item-type">item type</a> <dfn id="md-vevent" title="md-vevent"><code>http://microformats.org/profile/hcalendar#vevent</code></dfn>
+ </div><h3 id="vevent"><span class="secno">7.2 </span>vEvent</h3><p>An item with the <a href="#item-type">item type</a> <dfn id="md-vevent" title="md-vevent"><code>http://microformats.org/profile/hcalendar#vevent</code></dfn>
represents an event.<p>This vocabulary <a href="#support-global-identifiers-for-items" title="support global identifiers for
items">supports global identifiers for items</a>.<p>The following are the type's <a href="#defined-property-name" title="defined property
name">defined property names</a>. They are based on the
@@ -3580,7 +3585,7 @@
</ul></li>
- </ol><h4 id="conversion-to-icalendar"><span class="secno">6.2.1 </span>Conversion to iCalendar</h4><p>Given a list of nodes <var title="">nodes</var> in a
+ </ol><h4 id="conversion-to-icalendar"><span class="secno">7.2.1 </span>Conversion to iCalendar</h4><p>Given a list of nodes <var title="">nodes</var> in a
<code>Document</code>, a user agent must run the following algorithm
to <dfn id="extracting-vevent-data" title="extracting vEvent data">extract any vEvent data
represented by those nodes</dfn>:<ol><li><p>If none of the nodes in <var title="">nodes</var> are <a href="#concept-item" title="concept-item">items</a> with the type <code title="md-vevent"><a href="#md-vevent">http://microformats.org/profile/hcalendar#vevent</a></code>,
@@ -3749,7 +3754,7 @@
<a href="#item-type">item type</a> and <a href="#defined-property-name" title="defined property
name">defined property names</a>.</p><!-- of course since
iCalendar doesn't define error handling, this is somewhat
- problematic. --><h4 id="examples-1"><span class="secno">6.2.2 </span>Examples</h4><!-- get more from http://www.ietf.org/rfc/rfc2445.txt --><div class="example">
+ problematic. --><h4 id="examples-1"><span class="secno">7.2.2 </span>Examples</h4><!-- get more from http://www.ietf.org/rfc/rfc2445.txt --><div class="example">
<p>Here is an example of a page that uses the vEvent vocabulary to
mark up an event:</p>
@@ -3828,7 +3833,7 @@
<meta itemprop="description" content="via livebrum.co.uk">
</div></pre>
- </div><!--END vEvent--><h3 id="licensing-works"><span class="secno">6.3 </span>Licensing works</h3><p>An item with the <a href="#item-type">item type</a> <dfn id="md-work" title="md-work"><code>http://n.whatwg.org/work</code></dfn>
+ </div><h3 id="licensing-works"><span class="secno">7.3 </span>Licensing works</h3><p>An item with the <a href="#item-type">item type</a> <dfn id="md-work" title="md-work"><code>http://n.whatwg.org/work</code></dfn>
represents a work (e.g. an article, an image, a video, a song,
etc). This type is primarily intended to allow authors to include
licensing information for works.<p>The following are the type's <a href="#defined-property-name" title="defined property
@@ -3891,7 +3896,7 @@
</dd>
- </dl><h4 id="conversion-to-rdf"><span class="secno">6.3.1 </span>Conversion to RDF</h4><p>For the purposes of RDF processors, blank nodes that are the
+ </dl><h4 id="conversion-to-rdf"><span class="secno">7.3.1 </span>Conversion to RDF</h4><p>For the purposes of RDF processors, blank nodes that are the
subject of a triple with the predicate "<code title="">http://www.w3.org/1999/xhtml/microdata#http%3A%2F%2Fn.whatwg.org%2Fwork%23%3Awork</code>"
and the object <var title="">s</var> must be treated as if the node
was identified by <var title="">s</var>.<p>For the purposes of RDF processors, the predicate "<code title="">http://www.w3.org/1999/xhtml/microdata#http%3A%2F%2Fn.whatwg.org%2Fwork%23%3Atitle</code>"
@@ -3906,7 +3911,7 @@
- <h4 id="examples-2"><span class="secno">6.3.2 </span>Examples</h4><div class="example">
+ <h4 id="examples-2"><span class="secno">7.3.2 </span>Examples</h4><div class="example">
<p>This example shows an embedded image entitled <cite>My
Pond</cite>, licensed under the Creative Commons Attribution-Share
@@ -3927,12 +3932,12 @@
</div><div class="impl">
- <h2 id="converting-html-to-other-formats"><span class="secno">7 </span>Converting HTML to other formats</h2>
+ <h2 id="converting-html-to-other-formats"><span class="secno">8 </span>Converting HTML to other formats</h2>
- <h3 id="json"><span class="secno">7.1 </span>JSON</h3>
+ <h3 id="json"><span class="secno">8.1 </span>JSON</h3>
<p>Given a list of nodes <var title="">nodes</var> in a
<code>Document</code>, a user agent must run the following algorithm
@@ -4004,7 +4009,7 @@
<li><p>Return <var title="">result</var>.</li>
- </ol><h3 id="rdf"><span class="secno">7.2 </span>RDF</h3>
+ </ol><h3 id="rdf"><span class="secno">8.2 </span>RDF</h3>
<p>To convert a <code>Document</code> to RDF, a user agent must run
the following algorithm:</p>
@@ -4238,7 +4243,7 @@
<li><p>Return <var title="">subject</var>.</li>
- </ol></div><h2 id="iana"><span class="secno">8 </span>IANA considerations</h2><!-- http://www.w3.org/2002/06/registering-mediatype.html --><h3 id="application-microdata-json"><span class="secno">8.1 </span><dfn><code>application/microdata+json</code></dfn></h3><p>This registration is for community review and will be submitted
+ </ol></div><h2 id="iana"><span class="secno">9 </span>IANA considerations</h2><!-- http://www.w3.org/2002/06/registering-mediatype.html --><h3 id="application-microdata-json"><span class="secno">9.1 </span><dfn><code>application/microdata+json</code></dfn></h3><p>This registration is for community review and will be submitted
to the IESG for review, approval, and registration with IANA.</p><!--
To: ietf-types@iana.org
Subject: Registration of media type application/microdata+json
@@ -4295,7 +4300,7 @@
<dd>W3C and WHATWG</dd>
</dl><p>Fragment identifiers used with
<code><a href="#application-microdata-json">application/microdata+json</a></code> resources have the same
- semantics as when used with <code>application/json</code>. <a href="#refsJSON">[JSON]</a></p><!--START vCard--><!--START vEvent--><h2 class="no-num" id="references">References</h2><!--REFS--><!--END vCard--><!--END vEvent--><p>All references are normative unless marked "Non-normative".</p><!--START vCard--><!--START vEvent--><!-- XXX really should remove dates and version numbers from these references once and for all --><dl><dt id="refsE163">[E163]</dt>
+ semantics as when used with <code>application/json</code>. <a href="#refsJSON">[JSON]</a><h2 class="no-num" id="references">References</h2><!--REFS--><p>All references are normative unless marked "Non-normative".</p><!-- XXX really should remove dates and version numbers from these references once and for all --><dl><dt id="refsE163">[E163]</dt>
<dd><cite>Recommendation E.163 — Numbering Plan for The International
Telephone Service</cite>, CCITT Blue Book, Fascicle II.2, pp. 128-134, November
1988.</dd>
@@ -4329,4 +4334,5 @@
Public Data Networks</cite>, CCITT Blue Book, Fascicle VIII.3,
pp. 317-332, November 1988.</dd>
- </dl><!--END vCard--><!--END vEvent-->
+ </dl><h2 id="acknowledgements"><span class="secno">10 </span>Acknowledgements</h2><p>For a full list of acknowledgements, please see the HTML5
+ specification.
Received on Friday, 8 January 2010 06:48:42 UTC