- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Sun, 10 May 2009 11:20:16 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv2430
Modified Files:
Overview.html
Log Message:
Fix some typos and add the first draft of an intro section for microdata. (whatwg r3075)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2232
retrieving revision 1.2233
diff -u -d -r1.2232 -r1.2233
--- Overview.html 10 May 2009 10:31:43 -0000 1.2232
+++ Overview.html 10 May 2009 11:20:13 -0000 1.2233
@@ -54,6 +54,10 @@
dl.switch { padding-left: 2em; }
dl.switch > dt { text-indent: -1.5em; }
dl.switch > dt:before { content: '\21AA'; padding: 0 0.5em 0 0; display: inline-block; width: 1em; text-align: right; line-height: 0.5em; }
+ dl.triple { padding: 0 0 0 1em; }
+ dl.triple dt, dl.triple dd { margin: 0; display: inline }
+ dl.triple dt:after { content: ':'; }
+ dl.triple dd:after { content: '\A'; white-space: pre; }
.diff-old { text-decoration: line-through; color: silver; background: transparent; }
.diff-chg, .diff-new { text-decoration: underline; color: green; background: transparent; }
a .diff-new { border-bottom: 1px blue solid; }
@@ -725,7 +729,10 @@
<li><a href="#matching-html-elements-using-selectors"><span class="secno">4.13 </span>Matching HTML elements using selectors</a></ol></li>
<li><a href="#microdata"><span class="secno">5 </span>Microdata</a>
<ol>
- <li><a href="#introduction-2"><span class="secno">5.1 </span>Introduction</a></li>
+ <li><a href="#introduction-2"><span class="secno">5.1 </span>Introduction</a>
+ <ol>
+ <li><a href="#the-basic-syntax"><span class="secno">5.1.1 </span>The basic syntax</a></li>
+ <li><a href="#defining-vocabularies"><span class="secno">5.1.2 </span>Defining vocabularies</a></ol></li>
<li><a href="#encoding-microdata"><span class="secno">5.2 </span>Encoding microdata</a>
<ol>
<li><a href="#the-microdata-model"><span class="secno">5.2.1 </span>The microdata model</a></li>
@@ -734,7 +741,7 @@
<li><a href="#names:-the-property-attribute"><span class="secno">5.2.4 </span>Names: the <code>property</code> attribute</a></li>
<li><a href="#values"><span class="secno">5.2.5 </span>Values</a></ol></li>
<li><a href="#microdata-dom-api"><span class="secno">5.3 </span>Microdata DOM API</a></li>
- <li><a href="#converting-html-to-oher-formats"><span class="secno">5.4 </span>Converting HTML to oher formats</a>
+ <li><a href="#converting-html-to-other-formats"><span class="secno">5.4 </span>Converting HTML to other formats</a>
<ol>
<li><a href="#json"><span class="secno">5.4.1 </span>JSON</a></li>
<li><a href="#rdf"><span class="secno">5.4.2 </span>RDF</a></ol></ol></li>
@@ -36213,7 +36220,92 @@
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><p class="XXX">...<h3 id="encoding-microdata"><span class="secno">5.2 </span>Encoding microdata</h3><h4 id="the-microdata-model"><span class="secno">5.2.1 </span>The microdata model</h4><p>The microdata model consists of groups of name-value pairs known
+ </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 desireable 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.<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.<div class="example">
+
+ <p>Here there are two items, each of which have the property "name":</p>
+
+ <pre><div item>
+ <p>My name is <span property="name">Elizabeth</span>.</p>
+</div>
+
+<div item>
+ <p>My name is <span property="name">Daniel</span>.</p>
+</div></pre>
+
+ </div><p>Properties generally have values that are strings.<div class="example">
+
+ <p>Here the item has three properties:</p>
+
+ <pre><div item>
+ <p>My name is <span property="name">Neil</span>.</p>
+ <p>My band is called <span property="band">Four Parts Water</span>.</p>
+ <p>I am <span property="nationality">British</span>.</p>
+</div></pre>
+
+ </div><p>Properties can also have values that are URLs. This is achieved
+ using the <code title="">a</code> element and its <code title="attr-hyperlink-href"><a href="#attr-hyperlink-href">href</a></code> attribute.<div class="example">
+
+ <p>In this example, the item has one property, "image", whose value is a URL:</p>
+
+ <pre><div item>
+ <img property="image" src="google-logo.png" alt="Google">
+</div></pre>
+
+ </div><p>Properties can also have values that are dates, times, or dates
+ and times. This is achieved using the <code title="">time</code>
+ element and its <code title="attr-time-datetime"><a href="#attr-time-datetime">datetime</a></code>
+ attribute.<div class="example">
+
+ <p>In this example, the item has one property, "birthday", whose
+ value is a date:</p>
+
+ <pre><div item>
+ I was born on <time property="birthday" datetime="2009-05-10">May 10th 2009</time>.
+</div></pre>
+
+ </div><p>Properties can also themselves be groups of name-value pairs, by
+ putting the <code title="attr-item"><a href="#items:-the-item-attribute">item</a></code> attribute on the
+ element that declares the property.<div class="example">
+
+ <p>In this example, the outer item represents a person, and the
+ inner one represents a band:</p>
+
+ <pre><div item>
+ <p>Name: <span property="name">Amanda</span></p>
+ <p>Band: <span property="band" item> <span property="name">Jazz Band</span> (<span property="size">12</span> players)</span></span></p>
+</div></pre>
+
+ <p>In this example, the outer item has two properties, "name" and
+ "band". The "name" is "Amanda",and the "band" is an item in its own
+ right, with two properties, "name" and "size". The "name" of the
+ band is "Jazz Band", and the "size" is "12".</p>
+
+ </div><h4 id="defining-vocabularies"><span class="secno">5.1.2 </span>Defining vocabularies</h4><p><em>This section is non-normative.</em><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
+ either using <a href="#url" title="URL">URLs</a> or <a href="#valid-reversed-dns-identifier" title="valid
+ reversed DNS identifier">reversed DNS labels</a>. For URLs
+ conflicts with other vocabularies can be avoided by only using
+ identifiers that correspond to pages that the author has control
+ over. Similarly, for reversed DNS labels conflicts can be avoided by
+ using a domain name that the author has control over, or by using
+ suffixes that correspond to the path components of pages that the
+ author has control over.<div class="example">
+
+ <p>For instance, if Jon and Adam both write content at <code title="">example.com</code>, at <code title="">http://example.com/jon/...</code> and <code title="">http://example.com/adam/...</code> respectively, then they
+ could select identifiers of the form "com.example.jon.name" and
+ "com.example.adam.name" respectively.</p>
+
+ </div><h3 id="encoding-microdata"><span class="secno">5.2 </span>Encoding microdata</h3><h4 id="the-microdata-model"><span class="secno">5.2.1 </span>The microdata model</h4><p>The microdata model consists of groups of name-value pairs known
as <dfn id="concept-item" title="concept-item">items</dfn>.<p>Each group has zero or more types, each name has one or more
values, and each value is either a string or another group of
name-value pairs.<h4 id="items:-the-item-attribute"><span class="secno">5.2.2 </span>Items: the <dfn title="attr-item"><code>item</code></dfn> attribute</h4><p>Every <a href="#html-elements" title="HTML elements">HTML element</a> may have an
@@ -36282,8 +36374,8 @@
<li>If its <a href="#concept-item-corresponding" title="concept-item-corresponding">corresponding
item</a>'s <code title="attr-item"><a href="#items:-the-item-attribute">item</a></code> attribute has no
- tokens: a string containing neither a U+003A COLON character (:), a
- U+002E FULL STOP character (.), nor a U+0020 SPACE character, or</li>
+ tokens: a string containing neither a U+003A COLON character (:)
+ nor a U+002E FULL STOP character (.), or</li>
<!--
<li>If its <span title="concept-item-corresponding">corresponding
item</span>'s <code title="attr-item">item</code> attribute
@@ -36441,7 +36533,7 @@
</dl><p>The <dfn id="dom-subject" title="dom-subject"><code>subject</code></dfn> DOM
attribute on elements must <a href="#reflect">reflect</a> the element's <code title="attr-subject"><a href="#attr-subject">subject</a></code> content attribute.</p>
- </div><h3 id="converting-html-to-oher-formats"><span class="secno">5.4 </span>Converting HTML to oher formats</h3><h4 id="json"><span class="secno">5.4.1 </span>JSON</h4><p>Given a node <var title="">node</var> in a <code>Document</code>,
+ </div><h3 id="converting-html-to-other-formats"><span class="secno">5.4 </span>Converting HTML to other formats</h3><h4 id="json"><span class="secno">5.4.1 </span>JSON</h4><p>Given a node <var title="">node</var> in a <code>Document</code>,
a user agent must run the following algorithm to extract that node's
microdata into a JSON form:<ol><li><p>Let <var title="">result</var> be an empty object.</li>
@@ -36508,7 +36600,7 @@
<p>If <a href="#the-title-element-0">the <code>title</code> element</a> is not null,
then generate the following triple:</p>
- <dl><dt>subject <dd> <a href="#the-document-s-current-address">the document's current address</a>
+ <dl class="triple"><dt>subject <dd> <a href="#the-document-s-current-address">the document's current address</a>
<dt>predicate <dd> <code title="">http://purl.org/dc/terms/title</code>
<dt>object <dd> the <code><a href="#textcontent">textContent</a></code> of <a href="#the-title-element-0">the <code>title</code> element</a>
</dl></li>
@@ -36550,7 +36642,7 @@
COLON character (:) nor a U+002E FULL STOP character (.),
generate the following triple:</p>
- <dl><dt>subject <dd> <a href="#the-document-s-current-address">the document's current address</a>
+ <dl class="triple"><dt>subject <dd> <a href="#the-document-s-current-address">the document's current address</a>
<dt>predicate <dd> the concatenation of the string "<code title="">http://www.w3.org/1999/xhtml/vocab#</code>" and <var title="">token</var>
<dt>object <dd> the <a href="#absolute-url">absolute URL</a> that results from <a href="#resolve-a-url" title="resolve a URL">resolving</a> the value of the element's <code title="">href</code> attribute relative to the element
</dl></li>
@@ -36566,7 +36658,7 @@
contains neither a U+003A COLON character (:) nor a U+002E FULL
STOP character (.), generate the following triple:</p>
- <dl><dt>subject <dd> <a href="#the-document-s-current-address">the document's current address</a>
+ <dl class="triple"><dt>subject <dd> <a href="#the-document-s-current-address">the document's current address</a>
<dt>predicate <dd> the concatenation of the string "<code title="">http://www.w3.org/1999/xhtml/vocab#</code>" and value of the element's <code title="attr-meta-name"><a href="#attr-meta-name">name</a></code> attribute, <a href="#converted-to-lowercase">converted to lowercase</a>
<dt>object <dd> the value of the element's <code title="attr-meta-content"><a href="#attr-meta-content">content</a></code> attribute
</dl></li>
@@ -36580,7 +36672,7 @@
successfully relative to the element, generate the following
triple:</p>
- <dl><dt>subject <dd> <a href="#the-document-s-current-address">the document's current address</a>
+ <dl class="triple"><dt>subject <dd> <a href="#the-document-s-current-address">the document's current address</a>
<dt>predicate <dd> <code title="">http://purl.org/dc/terms/source</code>
<dt>object <dd> the <a href="#absolute-url">absolute URL</a> that results from <a href="#resolve-a-url" title="resolve a URL">resolving</a> the value of the element's <code title="">cite</code> attribute relative to the element
</dl></li>
@@ -36616,7 +36708,7 @@
<p>Generate the following triple:</p>
- <dl><dt>subject <dd> <var title="">subject</var>
+ <dl class="triple"><dt>subject <dd> <var title="">subject</var>
<dt>predicate <dd> <code title="">http://www.w3.org/1999/02/22-rdf-syntax-ns#type</code>
<dt>object <dd> <var title="">type</var>
</dl></li>
@@ -36649,7 +36741,7 @@
<p>Generate the following triple:</p>
- <dl><dt>subject <dd> <var title="">subject</var>
+ <dl class="triple"><dt>subject <dd> <var title="">subject</var>
<dt>predicate <dd> <var title="">name</var>
<dt>object <dd> <var title="">value</var>
</dl></li>
Received on Sunday, 10 May 2009 11:20:26 UTC