- From: poot <cvsmail@w3.org>
- Date: Wed, 13 Apr 2011 18:03:15 -0400
- To: public-html-diffs@w3.org
microdata; hixie: apply wg decision (whatwg r6002)
http://dev.w3.org/cvsweb/html5/md/Overview.html?r1=1.119&r2=1.120&f=h
http://html5.org/tools/web-apps-tracker?from=6001&to=6002
===================================================================
RCS file: /sources/public/html5/md/Overview.html,v
retrieving revision 1.119
retrieving revision 1.120
diff -u -d -r1.119 -r1.120
--- Overview.html 12 Apr 2011 00:10:21 -0000 1.119
+++ Overview.html 13 Apr 2011 21:58:55 -0000 1.120
@@ -1,8 +1,4 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"><!-- when publishing, change bits marked ZZZ
- ZZZ: Set PUB to 1 for TR/ drafts, 0 for dev drafts; PUB-Y lines are used if it's 1 and PUB-N lines if it's 0.
- ZZZ: Set YEAR, SHORTDAY, and LONGDAY accordingly. They are used by the INSERT FOO bits below.
- bits marked YYY are for not depending on HTML5 (also see working-copy).
- --><html lang="en-US-x-Hixie"><title>HTML Microdata</title><style type="text/css">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"><html lang="en-US-x-Hixie"><title>HTML Microdata</title><style type="text/css">
pre { margin-left: 2em; white-space: pre-wrap; }
h2 { margin: 3em 0 1em 0; }
h3 { margin: 2.5em 0 1em 0; }
@@ -344,12 +340,11 @@
<h1>HTML Microdata</h1>
<h2 class="no-num no-toc" id="generatedID"></h2>
- <h2 class="no-num no-toc" id="editor-s-draft-12-april-2011">Editor's Draft 12 April 2011</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-13-april-2011">Editor's Draft 13 April 2011</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/microdata/">http://www.w3.org/TR/microdata/</a></dd>
<dt>Latest Editor's Draft:</dt>
<dd><a class="latest-link" href="http://dev.w3.org/html5/md/">http://dev.w3.org/html5/md/</a></dd>
-<!-- ZZZ: add the new version after it has shipped -->
<dt>Previous Versions:</dt>
<dd><a href="http://www.w3.org/TR/2011/WD-microdata-20110405/">http://www.w3.org/TR/2011/WD-microdata-20110405/</a></dd>
<dd><a href="http://www.w3.org/TR/2011/WD-microdata-20110113/">http://www.w3.org/TR/2011/WD-microdata-20110113/</a></dd>
@@ -382,12 +377,12 @@
mechanism allows machine-readable data to be embedded in HTML
documents in an easy-to-write manner, with an unambiguous parsing
model. It is compatible with numerous other data formats including
- RDF and JSON.<h2 class="no-num no-toc" id="status-of-this-document">Status of This document</h2><!-- intro boilerplate (required) --><p><em>This section describes the status of this document at the
+ RDF and JSON.<h2 class="no-num no-toc" id="status-of-this-document">Status of This document</h2><p><em>This section describes the status of this document at the
time of its publication. Other documents may supersede this
document. A list of current W3C publications and the most recently
formally published revision of this technical report can be found in
the <a href="http://www.w3.org/TR/">W3C technical reports index</a>
- at http://www.w3.org/TR/.</em></p><!-- where to send feedback (required) --><p>If you wish to make comments regarding this document in a manner
+ at http://www.w3.org/TR/.</em></p><p>If you wish to make comments regarding this document in a manner
that is tracked by the W3C, please submit them via using <a href="http://www.w3.org/Bugs/Public/enter_bug.cgi?product=HTML%20WG">our
public bug database</a>. If you do not have an account then you can
enter feedback using this form:<form action="http://www.whatwg.org/specs/web-apps/current-work/file-spam.cgi" method="post">
@@ -442,21 +437,21 @@
editor also maintains <a href="http://www.whatwg.org/issues/">a list
of all e-mails that he has not yet tried to address</a>. These bugs,
issues, and e-mails apply to multiple HTML-related specifications,
- not just this one.</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- stability (required) --><p>Implementors should be aware that this specification is not
+ not just this one.</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Implementors should be aware that this specification is not
stable. <strong>Implementors who are not taking part in the
discussions are likely to find the specification changing out from
under them in incompatible ways.</strong> Vendors interested in
implementing this specification before it eventually reaches the
Candidate Recommendation stage should join the aforementioned
mailing lists and take part in the discussions.<div id="multipage-common">
- </div><!-- not everyone agrees with this (requested before html5 fpwd) --><p>The publication of this document by the W3C as a W3C Working
+ </div><p>The publication of this document by the W3C as a W3C Working
Draft does not imply that all of the participants in the W3C HTML
working group endorse the contents of the specification. Indeed, for
any section of the specification, one can usually find many members
of the working group or of the W3C as a whole who object strongly to
the current text, the existence of the section at all, or the idea
that the working group should even spend time discussing the concept
- of that section.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- version history or list of changes (required) --><p>The latest stable version of the editor's draft of this
+ of that section.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>The latest stable version of the editor's draft of this
specification is always available on <a href="http://dev.w3.org/html5/">the W3C CVS server</a> and in the <a href="http://svn.whatwg.org/webapps/">WHATWG Subversion
repository</a>. The <a href="http://www.whatwg.org/specs/web-apps/current-work/complete.html">latest
editor's working copy</a> (which may contain unfinished text in the
@@ -472,14 +467,14 @@
<dd>CVSWeb interface with side-by-side diffs: <a href="http://dev.w3.org/cvsweb/html5/">http://dev.w3.org/cvsweb/html5/</a></dd>
<dd>Annotated summary with unified diffs: <a href="http://html5.org/tools/web-apps-tracker">http://html5.org/tools/web-apps-tracker</a></dd>
<dd>Raw Subversion interface: <code>svn checkout http://svn.whatwg.org/webapps/</code></dd>
- </dl><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING LIST TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- status of document, group responsible (required) --><p>The W3C <a href="http://www.w3.org/html/wg/">HTML Working
+ </dl><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING LIST TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>The W3C <a href="http://www.w3.org/html/wg/">HTML Working
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 12 April 2011 Editor's Draft.
- </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
+ This specification is the 13 April 2011 Editor's Draft.
+ </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
- group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!--YYY BOILERPLATE middle-w3c-html-module-status--><!-- required patent boilerplate --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
+ group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/40318/status" rel="disclosure">public list of
any patent disclosures</a> made in connection with the deliverables
of the group; that page also includes instructions for disclosing a
@@ -487,7 +482,6 @@
individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
6 of the W3C Patent Policy</a>.<h2 class="no-num no-toc" id="contents">Table of Contents</h2>
-<!--begin-toc-->
<ol class="toc">
<li><a href="#common-infrastructure"><span class="secno">1 </span>Common infrastructure</a>
<ol>
@@ -522,7 +516,7 @@
<li><a href="#application-microdata-json"><span class="secno">6.1 </span><code>application/microdata+json</code></a></ol></li>
<li><a class="no-num" href="#references">References</a></li>
<li><a class="no-num" href="#acknowledgements">Acknowledgements</a></ol>
-<!--end-toc--><hr><h2 id="common-infrastructure"><span class="secno">1 </span>Common infrastructure</h2><p>This specification is designed to be used with a <dfn id="host-language">host
+<hr><h2 id="common-infrastructure"><span class="secno">1 </span>Common infrastructure</h2><p>This specification is designed to be used with a <dfn id="host-language">host
language</dfn> that defines the following terms:<ul class="brief"><li>DOM <dfn id="collections">collections</dfn>
<li>The <dfn id="htmlcollection-interface"><code>HTMLCollection</code> interface</dfn>
<li><dfn id="reflect" title="reflect">Reflection</dfn> of IDL attributes
@@ -558,66 +552,9 @@
<li><dfn id="drag-and-drop-initialization-steps">Drag-and-drop initialization steps</dfn>
<li>The <dfn id="list-of-dragged-nodes">list of dragged nodes</dfn>
</ul><p>The <a href="#host-language">host language</a> also defines the elements used in
- this specification.</p><!-- YYY
- <h3>Dependencies</h3>
-
- <p>This specification depends on the Web IDL and HTML5
- specifications. <a href="#refsWEBIDL">[WEBIDL]</a> <a
- href="#refsHTML5">[HTML5]</a></p>
-
-
- <h3>Terminology</h3>
-
- <p>This specification relies heavily on the HTML5 specification to
- define underlying terms.</p>
-
- <p>HTML5 defines the concept of DOM <dfn>collections</dfn> and the
- <dfn><code>HTMLCollection</code></dfn> interface, as well as the
- concept of IDL attributes <dfn title="reflect">reflecting</dfn>
- content attributes. It also defines <dfn>tree order</dfn> and the
- concept of a node's <dfn>home subtree</dfn>.</p>
-
- <p>HTML5 defines the terms <dfn>URL</dfn>, <dfn>valid URL</dfn>,
- <dfn>absolute URL</dfn>, and <dfn>resolve a URL</dfn>.</p>
-
- <p>HTML5 defines the terms <dfn>alphanumeric ASCII characters</dfn>,
- <dfn>space characters</dfn> <dfn>split a string on spaces</dfn>,
- <dfn>converted to ASCII uppercase</dfn>, and <dfn>prefix
- match</dfn>.</p>
-
- <p>HTML5 defines the meaning of the term <dfn>HTML elements</dfn>, as
- well as all the elements referenced in this specification. It also
- defines the <dfn><code>HTMLElement</code></dfn> and
- <dfn><code>HTMLDocument</code></dfn> interfaces. It defines the
- specific concept of <dfn>the <code>title</code> element</dfn> in the
- context of an <code>HTMLDocument</code>. In the context of content
- models it defines the terms <dfn>flow content</dfn> and
- <dfn>phrasing content</dfn>. It also defines what an element's <dfn
- title="concept-ID">ID</dfn> or <dfn>language</dfn> is in HTML.</p>
-
- <p>HTML5 defines the set of <dfn>global attributes</dfn>, as well as
- terms used in describing attributes and their processing, such as
- the concept of a <dfn>boolean attribute</dfn>, of an <dfn>unordered
- set of unique space-separated tokens</dfn>, of a <dfn>valid
- non-negative integer</dfn>, of a <dfn
- title="concept-date">date</dfn>, a <dfn
- title="concept-time">time</dfn>, a <dfn
- title="concept-datetime">global date and time</dfn>, a <dfn>valid
- date string</dfn>, and a <dfn>valid global date and time
- string</dfn>.</p>
-
- <p>HTML5 defines what <dfn>the document's current address</dfn>
- is.</p>
-
- <p>Finally, HTML5 also defines the concepts of <dfn>drag-and-drop
- initialization steps</dfn> and of the <dfn>list of dragged
- nodes</dfn>, which come up in the context of drag-and-drop
- interfaces.</p>
-
---><h3 id="conformance-requirements"><span class="secno">1.1 </span>Conformance requirements</h3><p>All diagrams, examples, and notes in this specification are
+ this specification.</p><h3 id="conformance-requirements"><span class="secno">1.1 </span>Conformance requirements</h3><p>All diagrams, examples, and notes in this specification are
non-normative, as are all sections explicitly marked non-normative.
- Everything else in this specification is normative.<p>The key words "MUST", "MUST NOT", "REQUIRED", <!--"SHALL", "SHALL
- NOT",--> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
+ Everything else in this specification is normative.<p>The key words "MUST", "MUST NOT", "REQUIRED", <!-- NOT",--> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in the normative parts of this document are to be
interpreted as described in RFC2119. For readability, these words do
not appear in all uppercase letters in this specification. <a href="#refsRFC2119">[RFC2119]</a><div class="impl">
@@ -922,19 +859,7 @@
vocabulary in this example would define that the <code title="attr-itemid"><a href="#attr-itemid">itemid</a></code> attribute takes a <code title="">urn:</code> <a href="#url">URL</a> pointing to the ISBN of the
book.</p>
- </div><!-- (commented out since itemtype="" defines the meaning of the
- identifier for now)
- <p>Although it is common practice, authors are encouraged not to use
- the same URL to identify multiple topics; in particular, an HTTP URL
- usually identifies a specific resource (such as an image or
- document), and authors are encouraged to not use them to identify
- people, non-Web resources like companies, movies, and products, or
- other abstract concepts. Using an HTTP URL as a global identifier
- for something other than the resource actually designated by the URL
- 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
+ </div><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
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
@@ -1122,9 +1047,7 @@
specified, to give the <a href="#item-type">item type</a> of the <a href="#concept-item" title="concept-item">item</a>.<p>The <code title="attr-itemtype"><a href="#attr-itemtype">itemtype</a></code> attribute, if
specified, must have a value that is a <a href="#valid-url">valid URL</a> that
is an <a href="#absolute-url">absolute URL</a> for which the string "<code title="">http://www.w3.org/1999/xhtml/microdata#</code>" is not a
- <a href="#prefix-match">prefix match</a>.</p><!-- we disallow that prefix so that
- we have somewhere to put future extensions, e.g. if we ever support
- short type names --><p>The <dfn id="item-type">item type</dfn> of an <a href="#concept-item" title="concept-item">item</a> is the value of its element's <code title="attr-itemtype"><a href="#attr-itemtype">itemtype</a></code> attribute, if it has one and
+ <a href="#prefix-match">prefix match</a>.</p><p>The <dfn id="item-type">item type</dfn> of an <a href="#concept-item" title="concept-item">item</a> is the value of its element's <code title="attr-itemtype"><a href="#attr-itemtype">itemtype</a></code> attribute, if it has one and
its value is not the empty string. If the <code title="attr-itemtype"><a href="#attr-itemtype">itemtype</a></code> attribute is missing or its
value is the empty string, the <a href="#concept-item" title="concept-item">item</a> is said to have no <a href="#item-type">item
type</a>.<p>The <a href="#item-type">item type</a> must be a type defined in an <span title="other applicable specifications">applicable
@@ -1197,17 +1120,7 @@
characters</span>.<p>When an element with an <code title="concept-itemprop">itemprop</code> attribute <a href="#the-properties-of-an-item" title="the
properties of an item">adds a property</a> to multiple <a href="#concept-item" title="concept-item">items</a>, the requirement above regarding
the tokens applies for each <a href="#concept-item" title="concept-item">item</a>
- individually.</p><!--
-
- e.g.:
-
- <div itemscope itemtype="http://example.com/a"> <ref refid="x"> </div>
- <div itemscope itemtype="http://example.com/b"> <ref refid="x"> </div>
- <meta id="x" itemprop="z" content="">
-
- "z" had better be valid for both http://example.com/a and http://example.com/b
-
- --><p>The <dfn id="property-names">property names</dfn> of an element are the tokens that
+ individually.</p><p>The <dfn id="property-names">property names</dfn> of an element are the tokens that
the element's <code title="attr-itemprop"><a href="#names:-the-itemprop-attribute">itemprop</a></code> attribute
is found to contain when its value is <a href="#split-a-string-on-spaces" title="split a string on
spaces">split on spaces</a>, with the order preserved but with
@@ -1417,11 +1330,11 @@
<body>
<h1>My photos</h1>
<figure itemscope itemtype="http://n.whatwg.org/work" itemref="licenses">
- <img itemprop="work" src="images/house.jpeg" alt="A white house, boarded up, sits in a forest.">
+ src="images/house.jpeg" alt="A white house, boarded up, sits in a forest.">
<figcaption itemprop="title">The house I found.</figcaption>
</figure>
<figure itemscope itemtype="http://n.whatwg.org/work" itemref="licenses">
- <img itemprop="work" src="images/mailbox.jpeg" alt="Outside the house is a mailbox. It has a leaflet inside.">
+ src="images/mailbox.jpeg" alt="Outside the house is a mailbox. It has a leaflet inside.">
<figcaption itemprop="title">The mailbox.</figcaption>
</figure>
<footer>
@@ -1448,12 +1361,12 @@
<dd>The mailbox.
<dt>license
<dd><code title="">http://www.opensource.org/licenses/mit-license.php</code>
- </dl></div><h2 id="microdata-dom-api"><span class="secno">4 </span>Microdata DOM API</h2><pre class="idl">[Supplemental] interface <a href="#htmldocument">HTMLDocument</a> { <!--WARNING: ALSO DUPLICATED IN HTMLDocument SECTION-->
+ </dl></div><h2 id="microdata-dom-api"><span class="secno">4 </span>Microdata DOM API</h2><pre class="idl">[Supplemental] interface <a href="#htmldocument">HTMLDocument</a> {
NodeList <a href="#dom-document-getitems" title="dom-document-getItems">getItems</a>(in optional DOMString typeNames); // <span>microdata</span>
};
[Supplemental] interface <a href="#htmlelement">HTMLElement</a> {
- // <span>microdata</span> <!--WARNING: ALSO DUPLICATED IN HTMLElement SECTION-->
+ // <span>microdata</span>
attribute boolean <a href="#dom-itemscope" title="dom-itemScope">itemScope</a>;
attribute DOMString <a href="#dom-itemtype" title="dom-itemType">itemType</a>;
attribute DOMString <a href="#dom-itemid" title="dom-itemId">itemId</a>;
@@ -1612,30 +1525,7 @@
<pre>for (var index = 0; index < element.itemRef.length; index += 1)
process(document.getElementById(element.itemRef[index]));</pre>
- </div><!--YYY
- <h2>Other changes to HTML5</h2>
-
- <h3>Content models</h3>
-
- <p>If the <code title="attr-itemprop">itemprop</code> attribute is
- present on <code>link</code> or <code>meta</code>, they are
- <span>flow content</span> and <span>phrasing content</span>. The
- <code>link</code> and <code>meta</code> elements may be used where
- <span>phrasing content</span> is expected if the <code
- title="attr-itemprop">itemprop</code> attribute is present.</p>
-
- <p>If a <code>link</code> element has an <code
- title="attr-itemprop">itemprop</code> attribute, the <code
- title="attr-link-rel">rel</code> attribute may be omitted.</p>
-
- <p>If a <code>meta</code> element has an <code
- title="attr-itemprop">itemprop</code> attribute, the <code
- title="attr-meta-name">name</code>, <code
- title="attr-meta-http-equiv">http-equiv</code>, and <code
- title="attr-meta-charset">charset</code> attributes must be omitted,
- and the <code title="attr-meta-content">content</code> attribute
- must be present.</p>
---><div class="impl">
+ </div><div class="impl">
<h3 id="drag-and-drop"><span class="secno">4.1 </span>Drag-and-drop</h3>
@@ -1879,11 +1769,7 @@
type</a>. Otherwise, let <var title="">type</var> be the empty
string.</li>
- <!-- The special characters used in URLs beyond this point are
- intended to make it so that a different type/name combination
- couldn't generate the same string. ":" and "%20" are used because
- they can't be put in /name/ when all this is used. -->
-
+
<li>
<p>If <var title="">type</var> is not the empty string, run the
@@ -1917,11 +1803,7 @@
NUMBER SIGN character (#), then append a U+0023 NUMBER SIGN
character (#) to <var title="">type</var>.</li>
- <!-- Special characters beyond this point have to be something
- not in /name/ when this is used below, so either ":", %20, %0D,
- or %0A. This is so that a different type/name combination
- couldn't generate the same string. -->
-
+
<li><p>If <var title="">type</var> does not have a U+003A COLON
character (:) after its U+0023 NUMBER SIGN character (#), append
a U+003A COLON character (:) to <var title="">type</var>.</li>
@@ -1960,10 +1842,7 @@
the triples for an item">generate the triples</a> for <var title="">value</var>. Pass a reference to <var title="">memory</var> as the item/subject list, and pass <var title="">type</var> as the fallback type and <var title="">name</var> as the fallback property name. Replace <var title="">value</var> by the subject returned from those
steps.</li>
- <!-- could support <time> here somehow, though we'd have to
- reserialise it, check if the <time> was valid, check if it had a
- date, a time, a timezone, etc. -->
-
+
<li><p>Otherwise, if <var title="">element</var> is not one of
the <a href="#url-property-elements">URL property elements</a>, let <var title="">value</var> be a plain literal, with the language
information set from the <a href="#language">language</a> of the element, if
@@ -2002,9 +1881,7 @@
of the string "<code title="">http://www.w3.org/1999/xhtml/microdata#</code>"
and <var title="">s</var>, with any characters in <var title="">s</var> that are not valid in the <ifragment>
production of the IRI syntax being %-escaped, but without
- double-escaping existing %-escapes. <a href="#refsRFC3987">[RFC3987]</a></p> <!-- this ensures
- you can't use a URL to get the same effect -->
-
+ double-escaping existing %-escapes. <a href="#refsRFC3987">[RFC3987]</a></p>
<p class="example">For example if the string <var title="">s</var> is "<code title="">http://example.com/a#:q%20r</code>", the
resulting <var title="">predicate</var> would be "<code title="">http://www.w3.org/1999/xhtml/microdata#http://example.com/a%23:q%20r</code>".</p>
@@ -2124,11 +2001,8 @@
</div>
- </div><h2 id="iana"><span class="secno">6 </span>IANA considerations</h2><!-- http://www.w3.org/2002/06/registering-mediatype.html --><h3 id="application-microdata-json"><span class="secno">6.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
- --><dl><dt>Type name:</dt>
+ </div><h2 id="iana"><span class="secno">6 </span>IANA considerations</h2><h3 id="application-microdata-json"><span class="secno">6.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><dl><dt>Type name:</dt>
<dd>application</dd>
<dt>Subtype name:</dt>
<dd>microdata+json</dd>
@@ -2181,11 +2055,9 @@
<dd>W3C</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><h2 class="no-num" id="references">References</h2><!--REFS--><p>All references are normative unless marked "Non-normative".</p><!-- Dates are only included for standards older than the Web, because the newer ones keep changing. --><dl><dt id="refsHTML5">[HTML5]</dt>
+ semantics as when used with <code>application/json</code>. <a href="#refsJSON">[JSON]</a><h2 class="no-num" id="references">References</h2><p>All references are normative unless marked "Non-normative".</p><dl><dt id="refsHTML5">[HTML5]</dt>
<dd>
-<!--YYYEND microdata-->
(Non-normative)
-<!--YYYSTART microdata-->
<cite><a href="http://dev.w3.org/html5/spec/">HTML5</a></cite>,
I. Hickson. W3C.</dd>
@@ -2203,12 +2075,10 @@
Resource Identifiers (IRIs)</a></cite>, M. Dürst, M. Suignard. IETF.</dd>
<dt id="refsWEBIDL">[WEBIDL]</dt>
- <!--
- <dd><cite><a href="http://www.w3.org/TR/WebIDL/">Web
- IDL</a></cite>, C. McCormack. W3C.</dd>
- -->
- <dd><cite><a href="http://dev.w3.org/2006/webapi/WebIDL/">Web
+ <dd><cite><a href="http://dev.w3.org/2006/webapi/WebIDL/">Web
IDL</a></cite>, C. McCormack. W3C.</dd>
- </dl><h2 class="no-num" id="acknowledgements">Acknowledgements</h2><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/139">ISSUE-139</a> (ack-microdata) blocks progress to Last Call</span><p>For a full list of acknowledgements, please see the HTML5
+ </dl><h2 class="no-num" id="acknowledgements">Acknowledgements</h2><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/139">ISSUE-139</a> (ack-microdata) blocks progress to Last Call</span><p>Thanks to the participants of the microdata usability study for
+ allowing us to use their mistakes as a guide for designing the
+ microdata feature.<p>For a full list of acknowledgements, please see the HTML5
specification. <a href="#refsHTML5">[HTML5]</a>
Received on Wednesday, 13 April 2011 22:03:18 UTC