--- a/microdata-rdf/index.html Sun Jul 22 14:03:34 2012 -0700
+++ b/microdata-rdf/index.html Sun Jul 22 14:41:58 2012 -0700
@@ -14,102 +14,13 @@
<script type="text/javascript" class="remove">
// <!--
var preProc = {
- apply: function(c) {
- // extend the bibliography entries
- berjon.biblio["MICRODATA"] = "<cite><a href=\"http://www.w3.org/TR/2012/WD-microdata-20120329/\">HTML Microdata</a></cite> Ian Hickson Editor. W3C Working Draft. (Work in progress). 29 March 2012. This edition of the HTML Microdata specification is http://www.w3.org/TR/2012/WD-microdata-20120329/. The <a href=\"http://www.w3.org/TR/microdata/\">latest edition of HTML Microdata</a> is available at http://www.w3.org/TR/microdata/";
- berjon.biblio["MICRODATA-RDF-SUPPLEMENT"] = "<cite><a href=\"https://dvcs.w3.org/hg/htmldata/raw-file/default/microdata-supplement/index.html\">Microdata to RDF Supplement</a></cite> Gregg Kellogg Editor. World Wide Web Consortium (work in progress). 22 January 2012.";
- berjon.biblio["MICRODATA-RDF-TESTS"] = "<cite><a href=\"https://dvcs.w3.org/hg/htmldata/raw-file/default/microdata-rdf/tests/index.html\">Microdata to RDF Tests</a></cite> Gregg Kellogg, Ivan Herman Editors. World Wide Web Consortium (work in progress). 22 March 2012.";
-
- // process the document before anything else is done
- var refs = document.querySelectorAll('adef') ;
- var adefs = [];
- for (var i = 0; i < refs.length; i++) {
- var item = refs[i];
- var p = item.parentNode ;
- var con = item.innerHTML ;
- var sp = document.createElement( 'dfn' ) ;
- var tit = item.getAttribute('title') ;
- if (!tit) {
- tit = con;
- }
-
- if ( adefs[tit]) {
- throw "Duplicate definition of attribute '" + tit + "'" ;
- }
- adefs[tit] = sp ;
-
- sp.className = 'adef' ;
- sp.title=tit ;
- sp.innerHTML = con ;
- p.replaceChild(sp, item) ;
- }
- refs = document.querySelectorAll('aref') ;
- for (var i = 0; i < refs.length; i++) {
- var item = refs[i];
- var p = item.parentNode ;
- var con = item.innerHTML ;
- var sp = document.createElement( 'a' ) ;
- if ( !adefs[con]) {
- throw "Reference to undefined attribute '" + con + "'" ;
- }
- sp.className = 'aref' ;
- sp.setAttribute('title', con);
- sp.innerHTML = '@'+con ;
- p.replaceChild(sp, item) ;
- }
- // now do terms
- refs = document.querySelectorAll('tdef') ;
- var tdefs = [];
- for (var i = 0; i < refs.length; i++) {
- var item = refs[i];
- if (!item) continue ;
- var p = item.parentNode ;
- var con = item.innerHTML ;
- var ref = item.getAttribute('title') ;
- if (!ref) {
- ref = item.textContent ;
- }
- if (ref) {
- ref = ref.replace(/\s+/g, '_').toLowerCase() ;
- }
-
- if ( tdefs[ref]) {
- throw "Duplicate definition of term '" + ref + "'" ;
- }
-
- var sp = document.createElement( 'dfn' ) ;
- tdefs[ref] = sp ;
- sp.title = ref ;
- sp.innerHTML = con ;
- p.replaceChild(sp, item) ;
- }
- // now term references
- refs = document.querySelectorAll('tref') ;
- for (var i = 0; i < refs.length; i++) {
- var item = refs[i];
- if (!item) continue ;
- var p = item.parentNode ;
- var con = item.innerHTML ;
- var ref = item.getAttribute('title') ;
- if (!ref) {
- ref = item.textContent ;
- }
- if (ref) {
- ref = ref.replace(/\s+/g, '_').toLowerCase() ;
- }
-
- if ( !tdefs[ref]) {
- throw "Reference to undefined term '" + ref + "'" ;
- }
- var sp = document.createElement( 'a' ) ;
- var id = item.textContent ;
- sp.className = 'tref' ;
- sp.title = ref ;
- sp.innerHTML = con ;
- p.replaceChild(sp, item) ;
- }
- }
- } ;
+ apply: function(c) {
+ // extend the bibliography entries
+ berjon.biblio["MICRODATA"] = "<cite><a href=\"http://www.w3.org/TR/2012/WD-microdata-20120329/\">HTML Microdata</a></cite> Ian Hickson Editor. W3C Working Draft. (Work in progress). 29 March 2012. This edition of the HTML Microdata specification is http://www.w3.org/TR/2012/WD-microdata-20120329/. The <a href=\"http://www.w3.org/TR/microdata/\">latest edition of HTML Microdata</a> is available at http://www.w3.org/TR/microdata/";
+ berjon.biblio["MICRODATA-RDF-SUPPLEMENT"] = "<cite><a href=\"https://dvcs.w3.org/hg/htmldata/raw-file/default/microdata-supplement/index.html\">Microdata to RDF Supplement</a></cite> Gregg Kellogg Editor. World Wide Web Consortium (work in progress). 22 January 2012.";
+ berjon.biblio["MICRODATA-RDF-TESTS"] = "<cite><a href=\"https://dvcs.w3.org/hg/htmldata/raw-file/default/microdata-rdf/tests/index.html\">Microdata to RDF Tests</a></cite> Gregg Kellogg, Ivan Herman Editors. World Wide Web Consortium (work in progress). 22 March 2012.";
+ }
+ } ;
var respecConfig = {
@@ -220,6 +131,7 @@
font-weight: bold;
color: #ff4500 !important;
}
+.aref:before {content: "@"; }
</style>
</head>
@@ -247,11 +159,11 @@
<p>There are a variety of ways in which a mapping from microdata to
RDF might be configured to give a result that is closer to the required result for a particular vocabulary. This
specification defines terms that can be used as hooks for vocabulary-specific behavior, which could be defined
- within a <tref>registry</tref> or on an implementation-defined basis. However, the HTML Data TF recommends the
+ within a <a>registry</a> or on an implementation-defined basis. However, the HTML Data TF recommends the
adoption of a single method of mapping in which every vocabulary is treated as if:</p>
<ul>
- <li><tref><code>propertyURI</code></tref> is set to <code>vocabulary</code> </li>
- <li><tref><code>multipleValues</code></tref> is set to <code>unordered</code></li>
+ <li><a><code>propertyURI</code></a> is set to <code>vocabulary</code> </li>
+ <li><a><code>multipleValues</code></a> is set to <code>unordered</code></li>
</ul>
<p>For background on the trade-offs between these options, see
<a
@@ -274,14 +186,14 @@
<p>Microdata's data model does not align neatly with RDF.</p>
<ul>
<li>Non-URL microdata properties are disambiguated based on microdata
- <tref>item type</tref>; an <tref>item</tref> with the type <code>http://example.org/Cat</code> can have
+ <a>item type</a>; an <a>item</a> with the type <code>http://example.org/Cat</code> can have
both the property <code>color</code> and the property <code>http://example.org/color</code>,
and these properties are semantically distinct under microdata. In
RDF, all properties have IRIs.</li>
<li>When an item has multiple properties with the same name, the values are
always ordered; in RDF, property values are unordered unless they
- are explicitly listed in an <tref>RDF Collection</tref>.</li>
+ are explicitly listed in an <a>RDF Collection</a>.</li>
<li>A value in microdata is always a simple string which is interpreted
by the consuming application. In RDF, values can be tagged with a
@@ -297,14 +209,14 @@
violations occur and the reasons for them.</p>
<p>This specification allows for
- <tref>vocabulary</tref>-specific rules that affect the generation of property URIs and value serializations.
- This is facilitated by a <tref>registry</tref> that associates URIs with specific rules based on matching
- <aref>itemtype</aref> values against registered URI prefixes do determine a vocabulary and potentially
+ <a>vocabulary</a>-specific rules that affect the generation of property URIs and value serializations.
+ This is facilitated by a <a>registry</a> that associates URIs with specific rules based on matching
+ <a class="aref">itemtype</a> values against registered URI prefixes do determine a vocabulary and potentially
vocabulary-specific processing rules.</p>
<p>This specification also assumes that consumers of RDF generated from
microdata may have to process the results in order to, for example,
- assign appropriate datatypes to <tref>property value</tref>s.</p>
+ assign appropriate datatypes to <a>property value</a>s.</p>
</section>
<section class="informative">
@@ -317,16 +229,16 @@
and make it available to others to use, as a service. In these cases, the ultimate consumer, who will need to
understand the vocabularies used within the microdata, is the program or person who pulls out data from Sindice.
Sindice needs to retain the distinctions in the original microdata (e.g. ordering of items) and might not have
- built-in knowledge about the <tref>vocabulary</tref> of interest to the ultimate consumer. In this case, the ultimate consumer
+ built-in knowledge about the <a>vocabulary</a> of interest to the ultimate consumer. In this case, the ultimate consumer
is likely to have to map/validate/handle errors in the data they get from Sindice.</li>
<li>A consumer such as <a href="http://openelectiondata.org">openelectiondata.org</a> wants to support
- microdata-based markup of their <tref>vocabulary</tref> as well as RDFa-based markup, both going into an RDF-based data store.
+ microdata-based markup of their <a>vocabulary</a> as well as RDFa-based markup, both going into an RDF-based data store.
They want to use an off-the-shelf tool to extract the microdata. They want to configure the tool to give them the
- RDF that is appropriate for their known <tref>vocabulary</tref>.</li>
+ RDF that is appropriate for their known <a>vocabulary</a>.</li>
<li>A browser plugin that captures data for the user uses an RDF model as its backend store.
Any time it encounters microdata on a page, it wants to pull that microdata into the store on the fly.</li>
<li><a href="http://purl.org/goodrelations/">GoodRelations</a> properties do not take
- <tref title="rdf collection">rdf:List</tref> values; when they take
+ <a title="rdf collection">rdf:List</a> values; when they take
multiple values they are unordered. The <code>rdfs:range</code> of a GoodRelations
property indicates the datatype of the expected value, and GoodRelations
processors will expect values to be cast to that type. Language
@@ -352,31 +264,31 @@
<p class="issue" data-number="1">Vocabulary specific parsing for Microdata.
This specification attempts to create generic
rules for processing microdata with typical RDF vocabularies.
- A <tref>registry</tref> allows
+ A <a>registry</a> allows
for exceptions to the default processing rules for certain well-known vocabularies.</p>
<p class="issue" data-number="2">Should Microdata-RDF generate XMLLiteral values.
This issue has been closed with no change
as this would violate microdata's data model.</p>
- <p class="issue" data-number="3">Should the <tref>registry</tref> allow property datatype specification.
+ <p class="issue" data-number="3">Should the <a>registry</a> allow property datatype specification.
The consensus is that datatypes are only derived from HTML semantics, so that only <time> values have a datatype other than plain.</p>
- <p class="issue" data-number="4">Should the <tref>registry</tref> allow a <tref>name</tref> or URL
- to be used as an alias for <aref>itemid</aref>.</p>
+ <p class="issue" data-number="4">Should the <a>registry</a> allow a <a>name</a> or URL
+ to be used as an alias for <a class="aref">itemid</a>.</p>
<p>The purpose of this specification is to provide input to a future working group that can make decisions
- about the need for a <tref>registry</tref> and the details of processing. Among the options investigated by
+ about the need for a <a>registry</a> and the details of processing. Among the options investigated by
the Task Force are the following:</p>
<ul>
<li>Property URI generation using the original microdata specification with a base URI and
- <cite><a href="http://tools.ietf.org/html/rfc3986#section-3.5">fragment</a></cite> made up of the in-scope <tref>item
- type</tref> and <tref>properties</tref>.</li>
- <li>Vocabulary-based URI generation, where the <tref>vocabulary</tref> is determined from the
- in-scope <tref>item type</tref>, either through an algorithmic modification of the type URL or by matching the
- URL against a <tref>registry</tref>. The vocabulary URI is then used to generate property URIs in a namespace
+ <cite><a href="http://tools.ietf.org/html/rfc3986#section-3.5">fragment</a></cite> made up of the in-scope <a>item
+ type</a> and <a>properties</a>.</li>
+ <li>Vocabulary-based URI generation, where the <a>vocabulary</a> is determined from the
+ in-scope <a>item type</a>, either through an algorithmic modification of the type URL or by matching the
+ URL against a <a>registry</a>. The vocabulary URI is then used to generate property URIs in a namespace
parallel to the type URI.</li>
- <li>When there are multiple <tref>top-level item</tref>s in a document, place items in an RDF Collection.
+ <li>When there are multiple <a>top-level item</a>s in a document, place items in an RDF Collection.
Alternatively, simply list the items as multiple values, or do not generate an
<code>http://www.w3.org/ns/md#item</code> mapping at all.</li>
- <li>When an item has multiple values for a given <tref>property</tref>, place the values in an RDF Collection.
+ <li>When an item has multiple values for a given <a>property</a>, place the values in an RDF Collection.
Alternatively, do not use collections, use an alternative such as <code>rdf:Seq</code>, or place all values,
whether or not multiple, into some form of collection.</li>
</ul>
@@ -394,36 +306,36 @@
provides methods and attributes for retrieving microdata from the HTML DOM.</p>
<p>For reference, attributes used for specifying and retrieving HTML microdata are referenced here:</p>
<dl>
- <dt><adef>itemid</adef></dt><dd>
- An attribute containing a URL used to identify the subject of triples associated with this <tref>item</tref>.
+ <dt><dfn class="adef">itemid</a></dt><dd>
+ An attribute containing a URL used to identify the subject of triples associated with this <a>item</a>.
(See <cite><a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#attr-itemid">Items</a></cite>
in [[!MICRODATA]]).
</dd>
- <dt><adef>itemprop</adef></dt><dd>
- An attribute used to identify one or more <tref>name</tref>s of an <tref>item</tref>s. An <aref>itemprop</aref>
- contains a space separated list of <tdef>name</tdef>s which may either by <tref>absolute URL</tref>s or terms
- associated with the type of the <tref>item</tref> as defined by the referencing <tref>item</tref>'s
- <tref>item type</tref>.
+ <dt><dfn class="adef">itemprop</a></dt><dd>
+ An attribute used to identify one or more <a>name</a>s of an <a>item</a>s. An <a class="aref">itemprop</a>
+ contains a space separated list of <dfn>name</dfn>s which may either by <a>absolute URL</a>s or terms
+ associated with the type of the <a>item</a> as defined by the referencing <a>item</a>'s
+ <a>item type</a>.
(See <cite><a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#names:-the-itemprop-attribute">Items</a></cite>
in [[!MICRODATA]]).
</dd>
- <dt><adef>itemref</adef></dt><dd>
+ <dt><dfn class="adef">itemref</a></dt><dd>
An additional attribute on an element that references additional elements containing property
- definitions to be applied to the referencing <tref>item</tref>.
+ definitions to be applied to the referencing <a>item</a>.
(See <cite><a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#attr-itemref">Items</a></cite>
in [[!MICRODATA]]).
</dd>
- <dt><adef>itemscope</adef></dt><dd>
- An boolean attribute identifying an element as an <tref>item</tref>.
+ <dt><dfn class="adef">itemscope</a></dt><dd>
+ An boolean attribute identifying an element as an <a>item</a>.
(See <cite><a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#attr-itemscope">Items</a></cite>
in [[!MICRODATA]]).
</dd>
- <dt><adef>itemtype</adef></dt><dd>
- An additional attribute on an element used to specify one or more types of an <tref>item</tref>.
- The <tdef>item type</tdef> of an <tref>item</tref> is the first value returned from
+ <dt><dfn class="adef">itemtype</a></dt><dd>
+ An additional attribute on an element used to specify one or more types of an <a>item</a>.
+ The <dfn>item type</dfn> of an <a>item</a> is the first value returned from
<code><cite><a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#dom-itemtype">element.itemType</a></cite></code>
on the element.
- The <tref>item type</tref> is also used to resolve non-URL <tref>name</tref>s to <tref>absolute URL</tref>s.
+ The <a>item type</a> is also used to resolve non-URL <a>name</a>s to <a>absolute URL</a>s.
Available through the
<cite><a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#microdata-dom-api">Microdata DOM API</a></cite> as
<code><cite><a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#dom-itemtype">element.itemType</a></cite></code>.
@@ -468,12 +380,12 @@
<section class="informative">
<h1>Vocabulary Registry</h1>
<p>In a perfect world, all processors would be able to generate the same output for a given input
- without regards to the requirements of a particular <tref>vocabulary</tref>. However, microdata doesn't
+ without regards to the requirements of a particular <a>vocabulary</a>. However, microdata doesn't
provide sufficient syntactic help in making these decisions. Different vocabularies have different
needs.</p>
<p>The registry is located at the namespace defined for microdata: <code>http://www.w3.org/ns/md</code> in
a variety of formats.</p>
- <p>The <tdef>registry</tdef> associates a <tdef>URI prefix</tdef> with one or more key-value pairs denoting
+ <p>The <dfn>registry</dfn> associates a <dfn>URI prefix</dfn> with one or more key-value pairs denoting
processor behavior. A hypothetical JSON representation of such a registry might be the following:</p>
<pre class="example" data-transform="updateExample">
<!--
@@ -496,42 +408,42 @@
-->
</pre>
<p>This structure associates mappings for two URIs, <code>http://schema.org/</code> and
- <code>http://microformats.org/profile/hcard</code>. Items having an <tref>item type</tref> with a <tref>URI
- prefix</tref> from this <tref>registry</tref> use the the rules described for that prefix within the scope of that
- <tref>item type</tref>. This mapping currently defines two rules: <tref><code>propertyURI</code></tref> and
- <tref><code>multipleValues</code></tref> with values to indicate specific behavior. It also allows overrides
- on a per-property basis; the <tref><code>properties</code></tref> key associates an individual <tref>name</tref>
+ <code>http://microformats.org/profile/hcard</code>. Items having an <a>item type</a> with a <a>URI
+ prefix</a> from this <a>registry</a> use the the rules described for that prefix within the scope of that
+ <a>item type</a>. This mapping currently defines two rules: <a><code>propertyURI</code></a> and
+ <a><code>multipleValues</code></a> with values to indicate specific behavior. It also allows overrides
+ on a per-property basis; the <a><code>properties</code></a> key associates an individual <a>name</a>
with overrides for default behavior.
The interpretation of these
- rules is defined in the following sections. If an item has no <tref>current type</tref> or the
- <tref>registry</tref> contains no <tref>URI prefix</tref> matching <tref>current type</tref>, a conforming
+ rules is defined in the following sections. If an item has no <a>current type</a> or the
+ <a>registry</a> contains no <a>URI prefix</a> matching <a>current type</a>, a conforming
processor MUST use the default values defined for these rules.</p>
- <p class="note">The concept of a <tref>registry</tref>, including a hypothetical format, location and updating rules
+ <p class="note">The concept of a <a>registry</a>, including a hypothetical format, location and updating rules
is presented as an abstract concept useful for describing the function of a microdata processor.
There are issues surrounding update
frequency, URL naming, and how updates are authorized. This spec
- just considers the semantic content of such a <tref>registry</tref> and how it can be used to affect processing without
+ just considers the semantic content of such a <a>registry</a> and how it can be used to affect processing without
defining its representation or update policies.</p>
<section class="informative">
<h2>Property URI Generation</h2>
- <p>For <tref>name</tref>s which are not <tref>absolute URL</tref>s,
- the <tdef><code>propertyURI</code></tdef> rule defines the algorithm for generating an <tref>absolute URL</tref>
- given an <tref>evaluation context</tref> including a <tref>current type</tref>, <tref>current name</tref> and
- <tref>current vocabulary</tref>.</p>
+ <p>For <a>name</a>s which are not <a>absolute URL</a>s,
+ the <dfn><code>propertyURI</code></dfn> rule defines the algorithm for generating an <a>absolute URL</a>
+ given an <a>evaluation context</a> including a <a>current type</a>, <a>current name</a> and
+ <a>current vocabulary</a>.</p>
<p>The procedure for generating property URIs is defined in
<a href="#generate-predicate-uri">Generate Predicate URI</a>.</p>
- <p>Possible values for <tref><code>propertyURI</code></tref> are the following:</p>
+ <p>Possible values for <a><code>propertyURI</code></a> are the following:</p>
<dl>
<dt><code>contextual</code></dt><dd>
The <code>contextual</code> URI generation scheme guarantees that generated property URIs are
- unique based on the value of <tref>current name</tref>. This is
- required as the microdata data model requires that <tref>name</tref>s are associated with specific
+ unique based on the value of <a>current name</a>. This is
+ required as the microdata data model requires that <a>name</a>s are associated with specific
items and do not have a global scope. (See <a href="#scheme-context">Step 5</a> in
<a href="#generate-predicate-uri">Generate Predicate URI</a>).
<div>
<p>URI creation uses a base URI with query parameters to indicate the in-scope
- type and <tref>name</tref> list. Consider the following example:</p>
+ type and <a>name</a> list. Consider the following example:</p>
<pre class="example" data-transform="updateExample">
<!--
<span itemscope itemtype="http://microformats.org/profile/hcard">
@@ -543,9 +455,9 @@
</span>
-->
</pre>
- <p>The first <tref>name</tref> <em>n</em> generates the URI
+ <p>The first <a>name</a> <em>n</em> generates the URI
<code>http://www.w3.org/ns/md?type=http://microformats.org/profile/hcard?prop=n</code>.
- However, the included <tref>name</tref> <em>given-name</em> is included in untyped item.
+ However, the included <a>name</a> <em>given-name</em> is included in untyped item.
The inherited property URI is used to create a new property URI:
<code>http://www.w3.org/ns/md?type=http://microformats.org/profile/hcard?prop=n.given-name</code>.</p>
<p>This scheme is compatible with the needs of other RDF serialization formats such as
@@ -578,14 +490,14 @@
</div>
</dd>
<dt><code>vocabulary</code></dt><dd>
- The <code>vocabulary</code> URI generation scheme appends <tref>name</tref>s that are not
- <tref>absolute URL</tref>s to the <tref>URI prefix</tref>. When generating property URIs, if the <tref>URI prefix</tref>
- does not end with a '/' or '#', a '#' is appended to the <tref>URI prefix</tref>. (See <a href="#scheme-vocab">Step 4</a>
+ The <code>vocabulary</code> URI generation scheme appends <a>name</a>s that are not
+ <a>absolute URL</a>s to the <a>URI prefix</a>. When generating property URIs, if the <a>URI prefix</a>
+ does not end with a '/' or '#', a '#' is appended to the <a>URI prefix</a>. (See <a href="#scheme-vocab">Step 4</a>
in
<a href="#generate-predicate-uri">Generate Predicate URI</a>.)
<div>
<p>URI creation uses a base URL with query parameters to indicate the in-scope
- type and <tref>name</tref> list. Consider the following example:</p>
+ type and <a>name</a> list. Consider the following example:</p>
<pre class="example" data-transform="updateExample">
<!--
<span itemscope itemtype="http://microformats.org/profile/hcard">
@@ -597,7 +509,7 @@
</span>
-->
</pre>
- <p>Given the <tref>URI prefix</tref> <code>http://microformats.org/profile/hcard</code>, this
+ <p>Given the <a>URI prefix</a> <code>http://microformats.org/profile/hcard</code>, this
would generate <code>http://microformats.org/profile/hcard#n</code> and
<code>http://microformats.org/profile/hcard#given-name</code>. Note that the '#' is automatically
added as a separator.</p>
@@ -609,22 +521,22 @@
</div>
-->
</pre>
- <p>Given the <tref>URI prefix</tref> <code>http://schema.org/</code>,
- this would generate <code>http://schema.org/name</code>. Note that if the <aref>itemtype</aref>
+ <p>Given the <a>URI prefix</a> <code>http://schema.org/</code>,
+ this would generate <code>http://schema.org/name</code>. Note that if the <a class="aref">itemtype</a>
were <code>http://schema.org/Person/Teacher</code>, this would generate the same property URI.</p>
</div>
</dd>
</dl>
- <p>If the <tref>registry</tref> contains no match for <tref>current type</tref> implementations act as if
- there is a <tref>URI prefix</tref> made from the first <aref>itemtype</aref> value by stripping either the <cite><a
+ <p>If the <a>registry</a> contains no match for <a>current type</a> implementations act as if
+ there is a <a>URI prefix</a> made from the first <a class="aref">itemtype</a> value by stripping either the <cite><a
href="http://tools.ietf.org/html/rfc3986#section-3.5">fragment</a></cite> content or <cite><a
href="http://tools.ietf.org/html/rfc3986#section-3.3">last path segment</a></cite>, if the value has no fragment (See
[[!RFC3986]]).</p>
- <p class="note">Deconstructing the <aref>itemtype</aref> URL to create or identify a vocabulary URI
+ <p class="note">Deconstructing the <a class="aref">itemtype</a> URL to create or identify a vocabulary URI
is a violation of the microdata specification which is necessary to
support the use of existing vocabularies designed for use with RDF, and
shared or inherited properties within all vocabularies.</p>
- <p>The default value of <tref><code>propertyURI</code></tref> is <code>vocabulary</code>.</p>
+ <p>The default value of <a><code>propertyURI</code></a> is <code>vocabulary</code>.</p>
<pre class="example" data-transform="updateExample">
<!--
<div itemscope itemtype="http://schema.org/Book">
@@ -632,25 +544,25 @@
</div>
-->
</pre>
- <p>In this example, assuming no matching entry in the <tref>registry</tref>,
- the <tref>URI prefix</tref> is constructed by removing the
+ <p>In this example, assuming no matching entry in the <a>registry</a>,
+ the <a>URI prefix</a> is constructed by removing the
<cite><a href="http://tools.ietf.org/html/rfc3986#section-3.3">last path segment</a></cite>, leaving the URI
- <code>http://schema.org/</code>. As there is no explicit <tref><code>propertyURI</code></tref>,
+ <code>http://schema.org/</code>. As there is no explicit <a><code>propertyURI</code></a>,
the default <code>vocabulary</code> is used, and the resulting property URI would be
<code>http://schema.org/title</code>.</p>
</section>
<section class="informative">
<h2>Value Ordering</h2>
- <p>For items having multiple values for a given <tref>property</tref>,
- the <tdef><code>multipleValues</code></tdef> rule defines the algorithm for serializing these values.
- Microdata uses document order when generating <tref>property value</tref>s, as defined in
+ <p>For items having multiple values for a given <a>property</a>,
+ the <dfn><code>multipleValues</code></dfn> rule defines the algorithm for serializing these values.
+ Microdata uses document order when generating <a>property value</a>s, as defined in
<cite><a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#microdata-dom-api">Microdata DOM API</a></cite>
as <code>element.itemValue</code>. However, many RDF vocabularies expect multiple values to be generated
as triples sharing a common subject and predicate. In some cases, it may be useful to retain value ordering.</p>
- <p>The procedure for generating <tref>property value</tref>s is defined in
+ <p>The procedure for generating <a>property value</a>s is defined in
<a href="#generate-property-values">Generate Property Values</a>.</p>
- <p>Possible values for <tref><code>multipleValues</code></tref> are the following:</p>
+ <p>Possible values for <a><code>multipleValues</code></a> are the following:</p>
<dl>
<dt><code>unordered</code></dt><dd>
Values are serialized without ordering using a common subject and predicate.
@@ -658,12 +570,12 @@
<a href="#generate-property-values">Generate Property Values</a>).
</dd>
<dt><code>list</code></dt><dd>
- Multi-valued <aref>itemprop</aref>s are serialized using an <tref>RDF Collection</tref>.
+ Multi-valued <a class="aref">itemprop</a>s are serialized using an <a>RDF Collection</a>.
(See <a href="#values-list">Step 8</a> in
<a href="#generate-property-values">Generate Property Values</a>).
</dd>
</dl>
- <p>An example of how this might be specified in a <tref>registry</tref> is the following:</p>
+ <p>An example of how this might be specified in a <a>registry</a> is the following:</p>
<pre class="example" data-transform="updateExample">
<!--
{
@@ -694,11 +606,11 @@
}
-->
</pre>
- <p>The <tdef><code>properties</code></tdef> key takes a JSON Object as a value, which in turn has keys for each
- property that is to be given alternate semantics. Each <tref>name</tref> is implicitly expanded to it's URI
+ <p>The <dfn><code>properties</code></dfn> key takes a JSON Object as a value, which in turn has keys for each
+ property that is to be given alternate semantics. Each <a>name</a> is implicitly expanded to it's URI
representation as defined in <a href="#generate-predicate-uri">Generate Predicate URI</a>, so that
- the behavior is the same whether or not the <tref>name</tref> is listed as an <tref>absolute URL</tref>.</p>
- <p>The default value of <tref><code>multipleValues</code></tref> is <code>unordered</code>.</p>
+ the behavior is the same whether or not the <a>name</a> is listed as an <a>absolute URL</a>.</p>
+ <p>The default value of <a><code>multipleValues</code></a> is <code>unordered</code>.</p>
<div class="note">
<p>An alternative mechanism would output <em>both</em> unordered and ordered values, to allow an application
to choose the most useful representation. For example, consider the following:</p>
@@ -768,7 +680,7 @@
is marked up <em>might</em> be a violation of the spirit of the microdata specification, though it does not explicitly say in
normative text that consumers cannot use other information from the HTML DOM to interpret microdata.</p>
- <p>Additionally, one possible use of a <tref>registry</tref> would allow vocabularies to be marked with datatype information,
+ <p>Additionally, one possible use of a <a>registry</a> would allow vocabularies to be marked with datatype information,
so that a <code>dc:time</code> value, for example, would be understood to represent a literal with datatype
<code>xsd:date</code>. This could be done by adding information for each property in the vocabulary requiring
special treatment.</p>
@@ -786,7 +698,7 @@
}
-->
</pre>
- <p>The <code>datatype</code> identifies a URI to be used in constructing a <tref>typed literal</tref>.</p>
+ <p>The <code>datatype</code> identifies a URI to be used in constructing a <a>typed literal</a>.</p>
<p>In most cases, the relevant datatype for a value can be derived from
knowledge of what property the value is for and the syntax of the value
@@ -800,14 +712,14 @@
<p class="note">If property URI generation was fixed to <code>vocabulary</code>, multiple values always
generated both <code>unordered</code> and <code>ordered</code> representations, and there were <code>datatype</code>
- support, the <tref>registry</tref> could be reduced to a simple list of URLs without any further structure necessary.</p>
+ support, the <a>registry</a> could be reduced to a simple list of URLs without any further structure necessary.</p>
</section>
<section>
<h2>Vocabulary Expansion</h2>
- <p>Microdata requires that all values of <aref>itemtype</aref> come from the same vocabulary. This
- is required as <aref>itemprop</aref> values are resolved relative to that vocabulary. However,
- it is often useful to define an <tref>item</tref> to have types from multiple different vocabularies.</p>
+ <p>Microdata requires that all values of <a class="aref">itemtype</a> come from the same vocabulary. This
+ is required as <a class="aref">itemprop</a> values are resolved relative to that vocabulary. However,
+ it is often useful to define an <a>item</a> to have types from multiple different vocabularies.</p>
<p>Similarly, there may be cases when a single vocabulary is used, but vocabulary classes or properties
have equivalents in other common vocabularies (e.g.,
<cite><a href="http://www.heppnetz.de/ontologies/goodrelations/v1.html">Good Relations</a></cite>,
@@ -822,63 +734,63 @@
<h1>Algorithm</h1>
<p>
Transformation of Microdata to RDF makes use of general processing rules described in [[!MICRODATA]]
- for the treatment of <tref>item</tref>s.
+ for the treatment of <a>item</a>s.
</p>
<section>
<h2>Algorithm Terms</h2>
<dl>
- <dt><tdef>absolute URL</tdef></dt><dd>
+ <dt><dfn>absolute URL</dfn></dt><dd>
The term <cite><a href="http://www.w3.org/TR/2011/WD-html5-20110525/urls.html#absolute-url">absolute URL</a></cite>
is defined in [[!HTML5]].
</dd>
- <dt><tdef>blank node</tdef></dt><dd>
- A blank node is a node in a graph that is neither a <tref>URI reference</tref> nor a <tref>literal</tref>.
- <tref>Item</tref>s without a <tref>global identifier</tref> have a blank node allocated to them.
+ <dt><dfn>blank node</dfn></dt><dd>
+ A blank node is a node in a graph that is neither a <a>URI reference</a> nor a <a>literal</a>.
+ <a>Item</a>s without a <a>global identifier</a> have a blank node allocated to them.
(See [[RDF-CONCEPTS]]).
</dd>
- <dt><tdef>document base</tdef></dt><dd>
+ <dt><dfn>document base</dfn></dt><dd>
The base address of the document being processed, as defined in <cite><a
href="http://www.w3.org/TR/2011/WD-html5-20110525/urls.html#resolving-urls">Resolving URLs</a></cite> in
[[!HTML5]].
</dd>
- <dt><tdef>evaluation context</tdef></dt><dd>
+ <dt><dfn>evaluation context</dfn></dt><dd>
A data structure including the following elements:
<dl>
- <dt><tdef>memory</tdef></dt><dd>
+ <dt><dfn>memory</dfn></dt><dd>
a mapping of items to subjects, initially empty;
</dd>
- <dt><tdef>current name</tdef></dt><dd>
- an <tref>absolute URL</tref> for the in-scope <tref>name</tref>, used for generating URIs
- for properties of items without an <tref>item type</tref>;
+ <dt><dfn>current name</dfn></dt><dd>
+ an <a>absolute URL</a> for the in-scope <a>name</a>, used for generating URIs
+ for properties of items without an <a>item type</a>;
<div class="note">
- <tref>current name</tref> is required for the <code>contextual</code> property URI generation
+ <a>current name</a> is required for the <code>contextual</code> property URI generation
scheme. Without this scheme, this evaluation context component would not be required.
</div>
</dd>
- <dt><tdef>current type</tdef></dt><dd>
- an <tref>absolute URL</tref> for the <em>current type</em>, used when an <tref>item</tref> does not
- contain an <tref>item type</tref>;
+ <dt><dfn>current type</dfn></dt><dd>
+ an <a>absolute URL</a> for the <em>current type</em>, used when an <a>item</a> does not
+ contain an <a>item type</a>;
</dd>
- <dt><tdef>current vocabulary</tdef></dt><dd>
- an <tref>absolute URL</tref> for the <em>current vocabulary</em>, from the <tref>registry</tref>.
+ <dt><dfn>current vocabulary</dfn></dt><dd>
+ an <a>absolute URL</a> for the <em>current vocabulary</em>, from the <a>registry</a>.
</dd>
</dl>
</dd>
- <dt><tdef>item</tdef></dt><dd>
- An <tref>item</tref> is described by an element containing an <aref>itemscope</aref> attribute. The list
+ <dt><dfn>item</dfn></dt><dd>
+ An <a>item</a> is described by an element containing an <a class="aref">itemscope</a> attribute. The list
of top-level microdata items may be retrieved using the
<cite><a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#microdata-dom-api">Microdata DOM API</a></cite>
<code><cite><a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#dom-document-getitems">document.getItems</a></cite></code>
method.
</dd>
- <dt><tdef>item properties</tdef></dt><dd>
- The mechanism for finding the <tref title="item properties">properties of an item</tref> The list
+ <dt><dfn>item properties</dfn></dt><dd>
+ The mechanism for finding the <a title="item properties">properties of an item</a> The list
of item properties items may be retrieved using the
<cite><a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#microdata-dom-api">Microdata DOM API</a></cite>
<code><cite><a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#dom-properties">element.properties</a></cite></code>
attribute.
</dd>
- <dt><tdef>fragment-escape</tdef></dt><dd>
+ <dt><dfn>fragment-escape</dfn></dt><dd>
The term <cite><a href="http://www.w3.org/TR/2011/WD-html5-20110525/urls.html#fragment-escaped">fragment-escape</a></cite>
is defined in [[!HTML5]]. This involves transforming elements added to URLs to ensure that the result
remains a valid URL. The following characters are subject to percent escaping:
@@ -897,47 +809,47 @@
<li>U+007D RIGHT CURLY BRACKET character (})</li>
</ul>
</dd>
- <dt><tdef>global identifier</tdef></dt><dd>
- The value of an <tref>item</tref>'s <aref>itemid</aref> attribute, if it has one. (See <cite><a
+ <dt><dfn>global identifier</dfn></dt><dd>
+ The value of an <a>item</a>'s <a>itemid</a> attribute, if it has one. (See <cite><a
href="http://www.w3.org/TR/2011/WD-microdata-20110525/#attr-itemscope">Items</a></cite> in
[[!MICRODATA]]).
</dd>
- <dt><tdef>literal</tdef></dt><dd>
- Literals are values such as strings and dates, including <tdef>typed literal</tdef>s and
- <tdef>plain literal</tdef>s.
+ <dt><dfn>literal</dfn></dt><dd>
+ Literals are values such as strings and dates, including <dfn>typed literal</dfn>s and
+ <dfn>plain literal</dfn>s.
(See [[RDF-CONCEPTS]]).
</dd>
- <dt><tdef>property</tdef></dt><dd>
- Each <tref>name</tref> identifies a <tref>property</tref> of an <tref>item</tref>.
- An <tref>item</tref> may have multiple elements sharing the same <tref>name</tref>, creating
- a multi-valued <tref>property</tref>.
+ <dt><dfn>property</dfn></dt><dd>
+ Each <a>name</a> identifies a <a>property</a> of an <a>item</a>.
+ An <a>item</a> may have multiple elements sharing the same <a>name</a>, creating
+ a multi-valued <a>property</a>.
</dd>
- <dt><tdef>property names</tdef></dt><dd>
- The tokens of an element's <aref>itemprop</aref> attribute. Each token is a <tref>name</tref>.
+ <dt><dfn>property names</dfn></dt><dd>
+ The tokens of an element's <a class="aref">itemprop</a> attribute. Each token is a <a>name</a>.
(See <cite><a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#property-names">Names: the
itemprop attribute</a></cite> in [[!MICRODATA]]).
</dd>
- <dt><tdef>property value</tdef></dt><dd>
- The <tref>property value</tref> of a name-value pair added by an element with an <aref>itemprop</aref>
+ <dt><dfn>property value</dfn></dt><dd>
+ The <a>property value</a> of a name-value pair added by an element with an <a class="aref">itemprop</a>
attribute depends on the element.
<dl>
- <dt>If the element has no <aref>itemprop</aref> attribute</dt>
+ <dt>If the element has no <a class="aref">itemprop</a> attribute</dt>
<dd>The value is null and no triple should be generated.</dd>
- <dt>If the element creates an <tref>item</tref> (by having an <aref>itemscope</aref> attribute)</dt>
+ <dt>If the element creates an <a>item</a> (by having an <a class="aref">itemscope</a> attribute)</dt>
<dd>
- The value is the <tref>URI reference</tref> or <tref>blank node</tref> returned from
- <a href="#generate-the-triples">generate the triples</a> for that <tref>item</tref>.
+ The value is the <a>URI reference</a> or <a>blank node</a> returned from
+ <a href="#generate-the-triples">generate the triples</a> for that <a>item</a>.
</dd>
<dt>If the element is a URL property element (<code>a</code>, <code>area</code>, <code>audio</code>,
<code>embed</code>, <code>iframe</code>, <code>img</code>, <code>link</code>, <code>object</code>,
<code>source</code>, <code>track</code> or <code>video</code>)</dt>
<dd>
- The value is a <tref>URI reference</tref> created from <code><cite>
+ The value is a <a>URI reference</a> created from <code><cite>
<a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#dom-itemvalue">element.itemValue</a></cite></code>.
(See relevant attribute descriptions in [[!HTML5]]).
</dd>
<dt>If the element is a <code>time</code> element.</dt>
- <dd>The value is a <tref>literal</tref> made from <code><cite>
+ <dd>The value is a <a>literal</a> made from <code><cite>
<a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#dom-itemvalue">element.itemValue</a></cite></code>.
<dl>
<dt>
@@ -950,7 +862,7 @@
href="http://www.w3.org/TR/xmlschema-2/#date">xsd:date</a></cite> [[!RDF-SCHEMA]].
</dt>
<dd>
- The value is a <tref>typed literal</tref> composed of the value and
+ The value is a <a>typed literal</a> composed of the value and
<code>http://www.w3.org/2001/XMLSchema#date</code>.
</dd>
<dt>
@@ -962,7 +874,7 @@
<cite><a href="http://www.w3.org/TR/xmlschema-2/#time">xsd:time</a></cite> [[!RDF-SCHEMA]].
</dt>
<dd>
- The value is a <tref>typed literal</tref> composed of the value and
+ The value is a <a>typed literal</a> composed of the value and
<code>http://www.w3.org/2001/XMLSchema#time</code>.
</dd>
<dt>
@@ -978,7 +890,7 @@
<cite><a href="http://www.w3.org/TR/xmlschema-2/#dateTime">xsd:dateTime</a></cite> [[!RDF-SCHEMA]].
</dt>
<dd>
- The value is a <tref>typed literal</tref> composed of the value and
+ The value is a <a>typed literal</a> composed of the value and
<code>http://www.w3.org/2001/XMLSchema#dateTime</code>.
</dd>
<dt>
@@ -990,7 +902,7 @@
<cite><a href="http://www.w3.org/TR/xmlschema-2/#gYearMonth">xsd:gYearMonth</a></cite> [[!RDF-SCHEMA]].
</dt>
<dd>
- The value is a <tref>typed literal</tref> composed of the value and
+ The value is a <a>typed literal</a> composed of the value and
<code>http://www.w3.org/2001/XMLSchema#gYearMonth</code>.
</dd>
<dt>
@@ -1002,7 +914,7 @@
<cite><a href="http://www.w3.org/TR/xmlschema-2/#gYear">xsd:gYear</a></cite> [[!RDF-SCHEMA]].
</dt>
<dd>
- The value is a <tref>typed literal</tref> composed of the value and
+ The value is a <a>typed literal</a> composed of the value and
<code>http://www.w3.org/2001/XMLSchema#gYear</code>.
</dd>
<dt>
@@ -1019,7 +931,7 @@
-->
</dt>
<dd>
- The value is a <tref>typed literal</tref> composed of the value and
+ The value is a <a>typed literal</a> composed of the value and
<code>http://www.w3.org/2001/XMLSchema#duration</code>.
<p class="note">The referenced version of [[!HTML5]] does not include a <em>duration</em> data type,
but it is in the Editor's Draft and is expected to be included in a
@@ -1027,7 +939,7 @@
</dd>
<dt>Otherwise</dt>
<dd>
- The value is a <tref>plain literal</tref> created from the value with language information set from the <cite><a
+ The value is a <a>plain literal</a> created from the value with language information set from the <cite><a
href="http://www.w3.org/TR/2011/WD-html5-20110525/elements.html#the-lang-and-xml:lang-attributes">lang</a></cite> IDL attribute
of the property element.
<p class="note">The HTML
@@ -1044,7 +956,7 @@
in [[!HTML5]].</p>
</dd>
<dt>Otherwise</dt>
- <dd>The value is a <tref>plain literal</tref> created from <code><cite>
+ <dd>The value is a <a>plain literal</a> created from <code><cite>
<a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#dom-itemvalue">element.itemValue</a></cite></code>
with language information set from the
<cite><a href="http://www.w3.org/TR/2011/WD-html5-20110525/elements.html#the-lang-and-xml:lang-attributes">lang</a></cite>
@@ -1052,33 +964,33 @@
</dd>
</dl>
</dd>
- <dt><tdef>top-level item</tdef></dt><dd>
- An <tref>item</tref> which does not contain an <aref>itemprop</aref> attribute.
+ <dt><dfn>top-level item</dfn></dt><dd>
+ An <a>item</a> which does not contain an <a class="aref">itemprop</a> attribute.
Available through the <cite><a
href="http://www.w3.org/TR/2011/WD-microdata-20110525/#microdata-dom-api">Microdata DOM API</a></cite> as
<code>document.getItems</code>.
(See <cite><a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#top-level-microdata-items">Associating names with items</a></cite> in [[!MICRODATA]]).
</dd>
- <dt><tdef>URI reference</tdef></dt><dd>
+ <dt><dfn>URI reference</dfn></dt><dd>
URI references are suitable to be used in <em>subject</em>, <em>predicate</em> or <em>object</em> positions
- within an RDF triple, as opposed to a <tref>literal</tref> value that may contain a string representation of a
+ within an RDF triple, as opposed to a <a>literal</a> value that may contain a string representation of a
URI. (See [[RDF-CONCEPTS]]).
<div class="issue">
<p>The HTML5/microdata content model for <code>@href</code>, <code>@src</code>,
- <code>@data</code>, <aref>itemtype</aref> and <aref>itemprop</aref> and <aref>itemid</aref> is that of
+ <code>@data</code>, <a class="aref">itemtype</a> and <a class="aref">itemprop</a> and <a class="aref">itemid</a> is that of
a URL, not a URI or IRI.</p>
- <p>A proposed mechanism for specifying the range of <tref>property value</tref>s to be URI reference or IRI could
+ <p>A proposed mechanism for specifying the range of <a>property value</a>s to be URI reference or IRI could
allow these to be specified as subject or object using a <code>@content</code> attribute.</p>
</div>
</dd>
- <dt><tdef>vocabulary</tdef></dt><dd>
- A vocabulary is a collection of URIs, suitable for use as an <aref>itemtype</aref> or <aref>itemprop</aref>
- value, that share a common <tref>URI prefix</tref>. That prefix is the vocabulary URI. A vocabulary URI is not
+ <dt><dfn>vocabulary</dfn></dt><dd>
+ A vocabulary is a collection of URIs, suitable for use as an <a class="aref">itemtype</a> or <a class="aref">itemprop</a>
+ value, that share a common <a>URI prefix</a>. That prefix is the vocabulary URI. A vocabulary URI is not
allowed to be a prefix of another vocabulary URI.
<div class="note">
This definition differs from the language in the HTML spec and is just for the purpose of this
document. In HTML, a vocabulary is a specification, and doesn't have a URI. In our view, if one
- specification defines ten <aref>itemtype</aref>s, then these could be treated as one vocabulary or as ten
+ specification defines ten <a class="aref">itemtype</a>s, then these could be treated as one vocabulary or as ten
distinct vocabularies; it is entirely up to the vocabulary creator.
</div>
</dd>
@@ -1096,12 +1008,12 @@
<p>Set <em>item list</em> to an empty list.</p>
<ol class="algorithm">
- <li>For each element that is also a <tref>top-level item</tref> run the following algorithm:
+ <li>For each element that is also a <a>top-level item</a> run the following algorithm:
<ol class="algorithm">
<li>
<a href="#generate-the-triples">Generate the triples</a> for an item <em>item</em>, using the
- <tref>evaluation context</tref>.
- Let <em>result</em> be the (<tref>URI reference</tref> or <tref>blank node</tref>) subject returned.
+ <a>evaluation context</a>.
+ Let <em>result</em> be the (<a>URI reference</a> or <a>blank node</a>) subject returned.
</li>
<li>
Append <em>result</em> to <em>item list</em>.
@@ -1118,7 +1030,7 @@
Generate the following triple:
<dl class="triple">
<dt>subject</dt>
- <dd><tref>Document base</tref></dd>
+ <dd><a>Document base</a></dd>
<dt>predicate</dt>
<dd><code>http://www.w3.org/ns/md#item</code></dd>
<dt>object</dt>
@@ -1131,33 +1043,33 @@
<section>
<h2>Generate the triples</h2>
<p>
- When the user agent is to Generate triples for an <tref>item</tref> <em>item</em>, given
- <tref>evaluation context</tref>, it must run the following steps:
+ When the user agent is to Generate triples for an <a>item</a> <em>item</em>, given
+ <a>evaluation context</a>, it must run the following steps:
</p>
<p class="note">
This algorithm has undergone substantial change from the original microdata specification [[!MICRODATA]].
</p>
<ol class="algorithm">
<li>
- If there is an entry for <em>item</em> in <tref>memory</tref>, then let <em>subject</em> be the subject of
- that entry. Otherwise, if <em>item</em> has a <tref>global identifier</tref> and that
- <tref>global identifier</tref> is an <tref>absolute URL</tref>, let <em>subject</em> be that
- <tref>global identifier</tref>. Otherwise, let <em>subject</em> be a new <tref>blank node</tref>.
+ If there is an entry for <em>item</em> in <a>memory</a>, then let <em>subject</em> be the subject of
+ that entry. Otherwise, if <em>item</em> has a <a>global identifier</a> and that
+ <a>global identifier</a> is an <a>absolute URL</a>, let <em>subject</em> be that
+ <a>global identifier</a>. Otherwise, let <em>subject</em> be a new <a>blank node</a>.
</li>
- <li>Add a mapping from <em>item</em> to <em>subject</em> in <tref>memory</tref></li>
+ <li>Add a mapping from <em>item</em> to <em>subject</em> in <a>memory</a></li>
<li>
For each <em>type</em> returned from
<code><cite><a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#dom-itemtype">element.itemType</a></cite></code>
- of the element defining the <tref>item</tref>.
+ of the element defining the <a>item</a>.
<ol class="algorithm">
- <li>If <em>type</em> is an <tref>absolute URL</tref>, generate the following triple:
+ <li>If <em>type</em> is an <a>absolute URL</a>, generate the following triple:
<dl class="triple">
<dt>subject</dt>
<dd><em>subject</em></dd>
<dt>predicate</dt>
<dd><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</code></dd>
<dt>object</dt>
- <dd><em>type</em> (as a <tref>URI reference</tref>)</dd>
+ <dd><em>type</em> (as a <a>URI reference</a>)</dd>
</dl>
</li>
</ol>
@@ -1165,47 +1077,47 @@
<li>
Set <em>type</em> to the first value returned from
<code><cite><a href="http://www.w3.org/TR/2011/WD-microdata-20110525/#dom-itemtype">element.itemType</a></cite></code>
- of the element defining the <tref>item</tref>.
+ of the element defining the <a>item</a>.
</li>
- <li>If <em>type</em> is an <tref>absolute URL</tref>, set <tref>current name</tref> in
- <tref>evaluation context</tref> to null.</li>
+ <li>If <em>type</em> is an <a>absolute URL</a>, set <a>current name</a> in
+ <a>evaluation context</a> to null.</li>
<li>
- Otherwise, set <em>type</em> to <tref>current type</tref> from
- <tref>evaluation context</tref> if not empty.
+ Otherwise, set <em>type</em> to <a>current type</a> from
+ <a>evaluation context</a> if not empty.
</li>
- <li>If the <tref>registry</tref> contains a <tref>URI prefix</tref> that is a character for character match of <em>type</em>
- up to the length of the <tref>URI prefix</tref>, set <em>vocab</em> as that <tref>URI prefix</tref>.
+ <li>If the <a>registry</a> contains a <a>URI prefix</a> that is a character for character match of <em>type</em>
+ up to the length of the <a>URI prefix</a>, set <em>vocab</em> as that <a>URI prefix</a>.
</li>
<li>Otherwise, if type is not empty, construct <em>vocab</em> by removing everything following the last
SOLIDUS U+002F ("/") or NUMBER SIGN U+0023 ("#") from the <em>path</em> component of <em>type</em>.</li>
- <li>Update <tref>evaluation context</tref> setting <tref>current vocabulary</tref> to <em>vocab</em>.</li>
+ <li>Update <a>evaluation context</a> setting <a>current vocabulary</a> to <em>vocab</em>.</li>
<li>
Set <em>property list</em> to an empty array mapping properties to one or more
<em>value</em>s as established below.
</li>
<li>
- For each element <em>element</em> that has one or more <tref>property names</tref> and is one of the
- <tref title="item properties">properties of the item</tref> <em>item</em>, in the order those elements
- are given by the algorithm that returns the <tref title="item properties">properties of the item</tref>,
+ For each element <em>element</em> that has one or more <a>property names</a> and is one of the
+ <a title="item properties">properties of the item</a> <em>item</em>, in the order those elements
+ are given by the algorithm that returns the <a title="item properties">properties of the item</a>,
run the following substep:
<ol class="algorithm">
<li>
- For each <em>name</em> in the element's <tref>property names</tref>, run the following substeps:
+ For each <em>name</em> in the element's <a>property names</a>, run the following substeps:
<ol class="algorithm">
<li>
- Let <em>context</em> be a copy of <tref>evaluation context</tref> with <tref>current type</tref> set
+ Let <em>context</em> be a copy of <a>evaluation context</a> with <a>current type</a> set
to <em>type</em>.
</li>
<li>
Let <em>predicate</em> be the result of <a href="#generate-predicate-uri">generate predicate URI</a>
using <em>context</em> and <em>name</em>.
- Update <em>context</em> by setting <tref>current name</tref> to <em>predicate</em>.
+ Update <em>context</em> by setting <a>current name</a> to <em>predicate</em>.
</li>
<li>
- Let <em>value</em> be the <tref>property value</tref> of <em>element</em>.
+ Let <em>value</em> be the <a>property value</a> of <em>element</em>.
</li>
<li>
- If <em>value</em> is an <tref>item</tref>, then <a href="#generate-the-triples">generate the
+ If <em>value</em> is an <a>item</a>, then <a href="#generate-the-triples">generate the
triples</a> for <em>value</em> using <em>context</em>. Replace <em>value</em> by the subject returned
from those steps.
</li>
@@ -1230,43 +1142,43 @@
<section>
<h3>Generate Predicate URI</h3>
- <p>Predicate URI generation makes use of <tref>current type</tref>, <tref>current name</tref>,
- and <tref>current vocabulary</tref> from an <tref>evaluation context</tref> <em>context</em>
+ <p>Predicate URI generation makes use of <a>current type</a>, <a>current name</a>,
+ and <a>current vocabulary</a> from an <a>evaluation context</a> <em>context</em>
along with <em>name</em>.</p>
<ol class="algorithm">
- <li>If <em>name</em> is an <tref>absolute URL</tref>, return <em>name</em>
- as a <tref>URI reference</tref>.</li>
- <li>If <tref>current type</tref> from <em>context</em> is null, there can be no <tref>current vocabulary</tref>.
- Return the <tref>URI reference</tref> that is the <tref>document base</tref> with its <cite><a
- href="http://tools.ietf.org/html/rfc3986#section-3.5">fragment</a></cite> set to the <tref>fragment-escape</tref>d value
+ <li>If <em>name</em> is an <a>absolute URL</a>, return <em>name</em>
+ as a <a>URI reference</a>.</li>
+ <li>If <a>current type</a> from <em>context</em> is null, there can be no <a>current vocabulary</a>.
+ Return the <a>URI reference</a> that is the <a>document base</a> with its <cite><a
+ href="http://tools.ietf.org/html/rfc3986#section-3.5">fragment</a></cite> set to the <a>fragment-escape</a>d value
of <em>name</em>.
<div class="note">
This rule is intended to allow for a the case where no type is set, and therefore there is no
- vocabulary from which to extract rules. For example, if there is a <tref>document base</tref> of
- <code>http://example.org/doc</code> and an <aref>itemprop</aref> of 'title', a URI will be constructed
+ vocabulary from which to extract rules. For example, if there is a <a>document base</a> of
+ <code>http://example.org/doc</code> and an <a class="aref">itemprop</a> of 'title', a URI will be constructed
to be <code>http://example.org/doc#title</code>.
</div>
</li>
- <li>Otherwise, if <tref>current vocabulary</tref> from <em>context</em> is not null
- and <tref>registry</tref> has an entry for <tref>current vocabulary</tref> having a
- <tref>propertyURI</tref> entry that is not null, set that as <em>scheme</em>. Otherwise,
+ <li>Otherwise, if <a>current vocabulary</a> from <em>context</em> is not null
+ and <a>registry</a> has an entry for <a>current vocabulary</a> having a
+ <a>propertyURI</a> entry that is not null, set that as <em>scheme</em>. Otherwise,
set <em>scheme</em> to <code>vocabulary</code>.</li>
- <li id="scheme-vocab">If <em>scheme</em> is <code>vocabulary</code> return the <tref>URI reference</tref> constructed
- by appending the <tref>fragment-escape</tref>d value of <em>name</em> to <tref>current vocabulary</tref>,
- separated by a U+0023 NUMBER SIGN character (#) unless the <tref>current vocabulary</tref> ends
+ <li id="scheme-vocab">If <em>scheme</em> is <code>vocabulary</code> return the <a>URI reference</a> constructed
+ by appending the <a>fragment-escape</a>d value of <em>name</em> to <a>current vocabulary</a>,
+ separated by a U+0023 NUMBER SIGN character (#) unless the <a>current vocabulary</a> ends
with either a U+0023 NUMBER SIGN character (#) or SOLIDUS U+002F (/).</li>
- <li id="scheme-context">If <em>scheme</em> is <code>contextual</code>, return the <tref>URI reference</tref>
+ <li id="scheme-context">If <em>scheme</em> is <code>contextual</code>, return the <a>URI reference</a>
constructed as follows:
<ol class="algorithm">
- <li>Let <em>s</em> be <tref>current name</tref> from <em>context</em>.</li>
+ <li>Let <em>s</em> be <a>current name</a> from <em>context</em>.</li>
<li>If <code>http://www.w3.org/ns/md?type=</code> is a prefix of <em>s</em>,
return the concatenation of <em>s</em>, a U+002E FULL STOP character (.) and
- the <tref>fragment-escape</tref>d value of <em>name</em>.
+ the <a>fragment-escape</a>d value of <em>name</em>.
</li>
<li>Otherwise, return the concatenation of <code>http://www.w3.org/ns/md?type=</code>,
- the <tref>fragment-escape</tref>d value of <tref>current type</tref>, the string <code>&prop=</code>,
- and the <tref>fragment-escape</tref>d value of <em>name</em>.
+ the <a>fragment-escape</a>d value of <a>current type</a>, the string <code>&prop=</code>,
+ and the <a>fragment-escape</a>d value of <em>name</em>.
</li>
</ol>
</li>
@@ -1278,23 +1190,23 @@
<p>Property value serialization makes use of <em>subject</em>, <em>predicate</em> and <em>values</em>.</p>
<ol class="algorithm">
- <li>If the <tref>registry</tref> contains a URI prefix that is a character for character match of
+ <li>If the <a>registry</a> contains a URI prefix that is a character for character match of
<em>predicate</em> up to the length of the URI prefix, set <em>vocab</em> as that URI prefix.
Otherwise set <em>vocab</em> to null.</li>
<li>If <em>vocab</em> is not null
- and <tref>registry</tref> has an entry for <em>vocab</em> that is a JSON Object, let
+ and <a>registry</a> has an entry for <em>vocab</em> that is a JSON Object, let
<em>registry object</em> be that value. Otherwise set <em>registry object</em> to null.</li>
<li>If <em>registry object</em> is not null and <em>registry object</em> contains key
- <tref><code>properties</code></tref>
+ <a><code>properties</code></a>
which has a JSON Object value, let <em>properties</em> be that value. Otherwise, set <em>properties</em>
to null.</li>
<li>If <em>properties</em> is not null, and <em>properties</em> contains a key, which after
<a href="#generate-predicate-uri">Generate Predicate URI</a> expansion has a value which is a JSON Object, let
<em>property override</em> be that value. Otherwise, set <em>property override</em> to null.</li>
<li>If <em>property override</em> contains the key
- <tref><code>multipleValues</code></tref>, set that as <em>method</em>.</li>
+ <a><code>multipleValues</code></a>, set that as <em>method</em>.</li>
<li>Otherwise, if <em>registry object</em> con contains the key
- <tref><code>multipleValues</code></tref>, set that as <em>method</em>.</li>
+ <a><code>multipleValues</code></a>, set that as <em>method</em>.</li>
<li>Otherwise, set <em>method</em> to <code>unordered</code>.</li>
<li id="values-unordered">If <em>method</em> is <code>unordered</code>,
for each <em>value</em> in <em>values</em>, generate the following triple:
@@ -1331,20 +1243,20 @@
<section id="generate-collection">
<h2>Generate RDF Collection</h2>
<p>
- An <tdef>RDF Collection</tdef> is a mechanism for defining ordered sequences of objects in RDF (See <cite><a
+ An <dfn>RDF Collection</dfn> is a mechanism for defining ordered sequences of objects in RDF (See <cite><a
href="http://www.w3.org/TR/rdf-syntax/#collections">RDF Collections</a></cite> in
[[!RDF-SCHEMA]]). As the RDF data-model is that of an unordered graph, a linking method using properties
<code>rdf:first</code> and <code>rdf:next </code>is required to be able to specify a particular order.
</p>
<p>
- In the microdata to RDF mapping, <tref>RDF Collection</tref>s are used when an item has more than one value
+ In the microdata to RDF mapping, <a>RDF Collection</a>s are used when an item has more than one value
associated with a given property to ensure that the original document order is maintained. The following
- procedure should be used to generate triples when an <tref>item</tref> property has more than one value
+ procedure should be used to generate triples when an <a>item</a> property has more than one value
(contained in <em>list</em>):
</p>
<ol class="algorithm">
<li>
- Create a new array <em>array</em> containing a <tref>blank node</tref> for every value in <em>list</em>.
+ Create a new array <em>array</em> containing a <a>blank node</a> for every value in <em>list</em>.
</li>
<li>
For each pair of <em>bnode</em> from <em>array</em> and <em>value</em> from <em>list</em> the following
@@ -1373,7 +1285,7 @@
</dl>
</li>
<li>
- Return the first <tref>blank node</tref> from <em>array</em>.
+ Return the first <a>blank node</a> from <em>array</em>.
</li>
</ol>
</section>
@@ -1419,8 +1331,8 @@
-->
</pre>
-<p>Assuming that <tref>registry</tref> contains a an entry for <code>http://purl.org/vocab/frbr/core#</code>
- with <tref><code>propertyURI</code></tref> set to <code>vocabulary</code>,
+<p>Assuming that <a>registry</a> contains a an entry for <code>http://purl.org/vocab/frbr/core#</code>
+ with <a><code>propertyURI</code></a> set to <code>vocabulary</code>,
this is equivalent to the following Turtle:</p>
<pre class="example" data-transform="updateExample">
<!--
@@ -1445,7 +1357,7 @@
</pre>
<p>The following snippet of HTML has microdata for two people with the same address. This illustrates two
- <tref>item</tref>s referencing a third item, and how only a single RDF resource definition is created
+ <a>item</a>s referencing a third item, and how only a single RDF resource definition is created
for that third item.</p>
<pre class="example" data-transform="updateExample">
<!--
@@ -1470,8 +1382,8 @@
-->
</pre>
-<p>Assuming that <tref>registry</tref> contains a an entry for <code>http://microformats.org/profile/hcard</code>
- with <tref><code>propertyURI</code></tref> set to <code>vocabulary</code>,
+<p>Assuming that <a>registry</a> contains a an entry for <code>http://microformats.org/profile/hcard</code>
+ with <a><code>propertyURI</code></a> set to <code>vocabulary</code>,
it generates these triples expressed in Turtle:</p>
<pre class="example" data-transform="updateExample">
@@ -1521,10 +1433,10 @@
-->
</pre>
-<p>Assuming that <tref>registry</tref> contains a an entry for <code>http://schema.org/</code>
- with <tref><code>propertyURI</code></tref> set to <code>vocabulary</code>,
- <tref><code>multipleValues</code></tref> set to <code>unordered</code> with the properties
- <code>track</code> and <code>byArtist</code> having <tref><code>multipleValues</code></tref> set to <code>list</code>,
+<p>Assuming that <a>registry</a> contains a an entry for <code>http://schema.org/</code>
+ with <a><code>propertyURI</code></a> set to <code>vocabulary</code>,
+ <a><code>multipleValues</code></a> set to <code>unordered</code> with the properties
+ <code>track</code> and <code>byArtist</code> having <a><code>multipleValues</code></a> set to <code>list</code>,
it generates these triples expressed in Turtle:</p>
<pre class="example" data-transform="updateExample">
@@ -1553,8 +1465,8 @@
</section>
<section class="appendix informative">
- <h1>Example <tref>registry</tref></h1>
- <p>The following is an example <tref>registry</tref> in JSON format.</p>
+ <h1>Example <a>registry</a></h1>
+ <p>The following is an example <a>registry</a> in JSON format.</p>
<pre class="example">
{