--- a/microdata-rdf/index.html Sat Mar 03 22:06:10 2012 -0800
+++ b/microdata-rdf/index.html Sun Jul 22 14:03:34 2012 -0700
@@ -9,14 +9,14 @@
out in the same tree and use relative links so that they'll work offline,
-->
<script type="text/javascript"
- src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove">
+ src="http://darobin.github.com/respec/builds/respec-w3c-common-3.1.14.js" class="remove">
</script>
<script type="text/javascript" class="remove">
// <!--
var preProc = {
apply: function(c) {
// extend the bibliography entries
- berjon.biblio["MICRODATA"] = "<cite><a href=\"http://dev.w3.org/html5/md/\">HTML Microdata</a></cite> Ian Hickson Editor. World Wide Web Consortium (work in progress). 18 November 2011. This edition of the HTML Microdata specification is http://dev.w3.org/html5/md/. The <a href=\"http://dev.w3.org/html5/md/\">latest edition of HTML Microdata</a> is available at http://www.w3.org/TR/microdata/";
+ 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.";
@@ -114,9 +114,9 @@
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "IG-NOTE",
+ specStatus: "ED",
charterDisclosureURI: "http://www.w3.org/2006/07/swig-charter#Ipr",
- publishDate: "2012-03-08",
+ //publishDate: "2012-03-08",
copyrightStart: "2011",
// the specification's short name, as in http://www.w3.org/TR/short-name/
@@ -125,21 +125,23 @@
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
- previousPublishDate: "2012-01-12",
- previousMaturity: "FPWD-NOTE",
+ previousPublishDate: "2012-03-08",
+ previousMaturity: "IG-NOTE",
//diffTool: "http://www.aptest.com/standards/htmldiff/htmldiff.pl",
// if there a publicly available Editor's Draft, this is the link
- //edDraftURI: "https://dvcs.w3.org/hg/htmldata/raw-file/default/microdata-rdf/index.html",
+ edDraftURI: "https://dvcs.w3.org/hg/htmldata/raw-file/default/microdata-rdf/index.html",
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2009-08-05",
// if you want to have extra CSS, append them to this list
// it is recommended that the respec.css stylesheet be kept
- extraCSS: [
- "http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"
- ],
+ //extraCSS: [
+ // "http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"
+ //],
+
+ issueBase: "http://www.w3.org/2011/htmldata/track/issues/",
// editors, add as many as you like
// only "name" is required
@@ -164,7 +166,7 @@
],
// name of the WG
- wg: "HTML Data Task Force, Semantic Web Interest Group",
+ wg: "Semantic Web Interest Group",
// URI of the public WG page
wgURI: "http://www.w3.org/2001/sw/interest/",
@@ -180,53 +182,29 @@
wgPatentURI: "",
maxTocLevel: 4,
preProcess: [ preProc ]
- , alternateFormats: [ {uri: "diff-20120112.html", label: "diff to previous version"} ]
+ //, alternateFormats: [ {uri: "diff-20120112.html", label: "diff to previous version"} ]
};
+ function _esc(s) {
+ s = s.replace(/&/g,'&');
+ s = s.replace(/>/g,'>');
+ s = s.replace(/"/g,'"');
+ s = s.replace(/</g,'<');
+ return s;
+ }
+
function updateExample(doc, content) {
// perform transformations to make it render and prettier
content = content.replace(/<!--/, '');
content = content.replace(/-->/, '');
- content = doc._esc(content);
+ content = _esc(content);
content = content.replace(/\*\*\*\*([^*]*)\*\*\*\*/g, '<span class="diff">$1</span>') ;
return content ;
}
-
- function updateDTD(doc, content) {
- // perform transformations to
- // make it render and prettier
- content = '<pre class="dtd">' + doc._esc(content) + '</pre>';
- content = content.replace(/!ENTITY % ([^ \t\r\n]*)/g, '!ENTITY <span class="entity">% $1</span>');
- content = content.replace(/!ELEMENT ([^ \t$]*)/mg, '!ELEMENT <span class="element">$1</span>');
- return content;
- }
-
- function updateSchema(doc, content) {
- // perform transformations to
- // make it render and prettier
- content = '<pre class="dtd">' + doc._esc(content) + '</pre>';
- content = content.replace(/<xs:element\s+name="([^&]*)"/g, '<xs:element name="<span class="element" id="schema_element_$1">$1</span>"') ;
- return content;
- }
-
- function updateTTL(doc, content) {
- // perform transformations to
- // make it render and prettier
- content = '<pre class="sh_sourceCode">' + doc._esc(content) + '</pre>';
- content = content.replace(/@prefix/g, '<span class="sh_keyword">@prefix</span>');
- return content;
- }
-// -->
+ // -->
</script>
<style type="text/css">
.diff { font-weight:bold; color:#0a3; }
-ol.algorithm { counter-reset:numsection; list-style-type: none; }
-ol.algorithm li { margin: 0.5em 0; }
-ol.algorithm li:before {
- font-weight: bold;
- counter-increment: numsection;
- content: counters(numsection, ".") ") ";
-}
dl.triple { padding: 0 0 0 1em; }
dl.triple dt, dl.triple dd { margin: 0; display: inline }
dl.triple dt:after { content: ':'; }
@@ -242,10 +220,6 @@
font-weight: bold;
color: #ff4500 !important;
}
-
-span.entity { color: red; }
-
-span.element { color: green; }
</style>
</head>
@@ -375,23 +349,18 @@
<p>Decisions or open issues in the specification are tracked on the
<a href="http://www.w3.org/2011/htmldata/track/issues">Task Force Issue Tracker</a>. These include the
following:</p>
- <dl>
- <dt><a href="http://www.w3.org/2011/htmldata/track/issues/1">ISSUE 1</a></dt><dd>
- Vocabulary specific parsing for Microdata. This specification attempts to create generic
- rules for processing microdata with typical RDF vocabularies. A <tref>registry</tref> allows
- for exceptions to the default processing rules for certain well-known vocabularies.
- </dd>
- <dt><a href="http://www.w3.org/2011/htmldata/track/issues/2">ISSUE 2</a></dt><dd>
- Should Microdata-RDF generate XMLLiteral values. This issue has been closed with no change
- as this would violate microdata's data model.
- </dd>
- <dt><a href="http://www.w3.org/2011/htmldata/track/issues/3">ISSUE 3</a></dt><dd>
- Should the <tref>registry</tref> 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.
- </dd>
- <dt><a href="http://www.w3.org/2011/htmldata/track/issues/4">ISSUE 4</a></dt><dd>
- Should the <tref>registry</tref> allow a <tref>name</tref> or URL to be used as an alias for <aref>itemid</aref>.
- </dd>
- </dl>
+ <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
+ 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.
+ 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>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
@@ -543,12 +512,6 @@
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
defining its representation or update policies.</p>
- <p class="issue">Richard Ciganiak has
- <cite><a href="http://richard.cyganiak.de/2011/10/microdata.html#whitelists">pointed out</a></cite> that
- "Registry" may be the wrong term, as the proposed <tref>registry</tref> doesn't assign identifiers or manage
- namespace, it simply provides a mapping between <tref>URI prefix</tref>ss and processor behavior and suggests the term
- "Whitelist". As more than two values are required, and it describes more than binary behavior, this term
- isn't appropriate either.</p>
<section class="informative">
<h2>Property URI Generation</h2>
@@ -834,11 +797,25 @@
determining its datatype, that information is used by this specification.</p>
<p>This concept is not explored further at this time, but could be developed further in
a future revision of this document.</p>
+
+ <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>
</section>
-<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>
+<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>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>,
+ Friend of a Friend ([[FOAF]]) and
+ Dublin Core ([[DC11]])).</p>
+ <p>Vocabulary Expansion is intended to allow terms to be mixed in from other vocabularies, using
+ a mechanism based on that in RDFa Core 1.1 Vocabulary Expansion [[RDFA-CORE]].</p>
+</section>
</section>
<section>
@@ -1022,11 +999,11 @@
valid non-negative integer
</a></cite>
having the lexical form of
- <cite><a href="http://www.w3.org/TR/xmlschema-2/#gYearMonth">xsd:gYear</a></cite> [[!RDF-SCHEMA]].
+ <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
- <code>http://www.w3.org/2001/XMLSchema#gYearMonth</code>.
+ <code>http://www.w3.org/2001/XMLSchema#gYear</code>.
</dd>
<dt>
If the value has the lexical form of