- From: poot <cvsmail@w3.org>
- Date: Fri, 14 Oct 2011 18:23:07 -0400
- To: public-html-diffs@w3.org
microdata; hixie: Microdata: add an example of multiple types. (whatwg
r6686)
http://dev.w3.org/cvsweb/html5/md/Overview.html?r1=1.168&r2=1.169&f=h
http://html5.org/tools/web-apps-tracker?from=6685&to=6686
===================================================================
RCS file: /sources/public/html5/md/Overview.html,v
retrieving revision 1.168
retrieving revision 1.169
diff -u -d -r1.168 -r1.169
--- Overview.html 13 Oct 2011 17:06:53 -0000 1.168
+++ Overview.html 14 Oct 2011 22:22:45 -0000 1.169
@@ -320,7 +320,7 @@
<h1>HTML Microdata</h1>
<h2 class="no-num no-toc" id="generatedID"></h2>
- <h2 class="no-num no-toc" id="editor-s-draft-13-october-2011">Editor's Draft 13 October 2011</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-14-october-2011">Editor's Draft 14 October 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>
@@ -454,7 +454,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 13 October 2011 Editor's Draft.
+ This specification is the 14 October 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 --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This specification is an extension to the HTML5 language. All
@@ -1123,7 +1123,85 @@
where the data to be annotated does not follow a convenient tree
structure. For example, it allows authors to mark up data in a table
so that each column defines a separate <a href="#concept-item" title="concept-item">item</a>, while keeping the properties in
- the cells.<h3 id="names:-the-itemprop-attribute"><span class="secno">2.3 </span>Names: the <dfn title="attr-itemprop"><code>itemprop</code></dfn> attribute</h3><p>Every <a href="#html-elements" title="HTML elements">HTML element</a> may have an
+ the cells.<div class="example">
+
+ <p>This example shows a simple vocabulary used to describe the
+ products of a model railway manufacturer. The vocabulary has just
+ five property names:</p>
+
+ <dl><dt>product-code</dt>
+ <dd>An integer that names the product in the manufacturer's catalog.</dd>
+ <dt>name</dt>
+ <dd>A brief description of the product.</dd>
+ <dt>scale</dt>
+ <dd>One of "HO", "1", or "Z" (potentially with leading or trailing
+ whitespace), indicating the scale of the product.</dd>
+ <dt>digital</dt>
+ <dd>If present, one of "Digital", "Delta", or "Systems"
+ (potentially with leading or trailing whitespace) indicating that
+ the product has a digital decoder of the given type.</dd>
+ <dt>track-type</dt>
+ <dd>For track-specific products, one of "K", "M", "C" (potentially
+ with leading or trailing whitespace) indicating the type of track
+ for which the product is intended.</dd>
+ </dl><p>This vocabulary has four defined <a href="#item-types">item types</a>:</p>
+
+ <dl><dt>http://md.example.com/loco</dt>
+ <dd>Rolling stock with an engine</dd>
+ <dt>http://md.example.com/passengers</dt>
+ <dd>Passenger rolling stock</dd>
+ <dt>http://md.example.com/track</dt>
+ <dd>Track pieces</dd>
+ <dt>http://md.example.com/lighting</dt>
+ <dd>Equipment with lighting</dd>
+ </dl><p>Each <a href="#concept-item" title="concept-item">item</a> that uses this
+ vocabulary can be given one or more of these types, depending on
+ what the product is.</p>
+
+ <p>Thus, a locomotive might be marked up as:</p>
+
+<pre><dl itemscope itemtype="http://md.example.com/loco
+ http://md.example.com/lighting">
+ <dt>Name:
+ <dd itemprop="name">Tank Locomotive (DB 80)
+ <dt>Product code:
+ <dd itemprop="product-code">33041
+ <dt>Scale:
+ <dd itemprop="scale">HO
+ <dt>Digital:
+ <dd itemprop="digital">Delta
+</dl></pre>
+
+ <p>A turnout lantern retrofit kit might be marked up as:</p>
+
+ <pre><dl itemscope itemtype="http://md.example.com/track
+ http://md.example.com/lighting">
+ <dt>Name:
+ <dd itemprop="name">Turnout Lantern Kit
+ <dt>Product code:
+ <dd itemprop="product-code">74470
+ <dt>Purpose:
+ <dd>For retrofitting 2 <span itemprop="track-type">C</span> Track
+ turnouts. <meta itemprop="scale" content="HO">
+</dl></pre>
+
+ <p>A passenger car with no lighting might be marked up as:</p>
+
+ <pre><dl itemscope itemtype="http://md.example.com/passengers">
+ <dt>Name:
+ <dd itemprop="name">Express Train Passenger Car (DB Am 203)
+ <dt>Product code:
+ <dd itemprop="product-code">8710
+ <dt>Scale:
+ <dd itemprop="scale">Z
+</dl></pre>
+
+ <p>Great care is necessary when creating new vocabularies. Often, a
+ hierarchical approach to types can be taken that results in a
+ vocabulary where each item only ever has a single type, which is
+ generally much simpler to manage.</p>
+
+ </div><h3 id="names:-the-itemprop-attribute"><span class="secno">2.3 </span>Names: the <dfn title="attr-itemprop"><code>itemprop</code></dfn> attribute</h3><p>Every <a href="#html-elements" title="HTML elements">HTML element</a> 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 one or more
properties</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
Received on Friday, 14 October 2011 22:23:10 UTC