--- a/local-biblio.js Fri Dec 13 08:05:45 2013 -0500
+++ b/local-biblio.js Fri Dec 13 08:06:03 2013 -0500
@@ -8,9 +8,10 @@
"N-TRIPLES": "Gavin Carothers, Editor. <cite><a href=\"http://www.w3.org/TR/2013/CR-n-triples-20131105/\">RDF 1.1 N-Triples</cite></a></cite>. 5 November 2013. W3C Candidate Recommendation (work in progress). URL: <a href=\"http://www.w3.org/TR/2013/CR-n-triples-20131105/\">http://www.w3.org/TR/2013/CR-n-triples-20131105/</a>. The latest edition is available at <a href=\"http://www.w3.org/TR/n-triples/\">http://www.w3.org/TR/n-triples/</a>",
"N-QUADS": "Gavin Carothers, Editor. <cite><a href=\"http://www.w3.org/TR/2013/CR-n-quads-20131105/\">RDF 1.1 N-Quads</cite></a></cite>. 5 November 2013. W3C Candidate Recommendation (work in progress). URL: <a href=\"http://www.w3.org/TR/2013/CR-n-quads-20131105/\">http://www.w3.org/TR/2013/CR-n-quads-20131105/</a>. The latest edition is available at <a href=\"http://www.w3.org/TR/n-quads/\">http://www.w3.org/TR/n-quads/</a>",
"TRIG": "Gavin Carothers, Andy Seaborne, Editors. <cite><a href=\"http://www.w3.org/TR/2013/WD-trig-20130919/\">TriG: RDF Dataset Language</a></cite>. 19 September 2013. W3C Candidate Recommendation (work in progress). URL: <a href=\"http://www.w3.org/TR/2013/WD-trig-20130919/\">http://www.w3.org/TR/2013/WD-trig-20130919/</a>. The latest edition is available at <a href=\"http://www.w3.org/TR/trig/\">http://www.w3.org/TR/trig/</a>",
- "RDF11-TESTCASES": "Markus Lanthaler, Editor. <cite><a href=\"http://www.w3.org/2013/rdf11-testcases/\">RDF 1.1 Test Cases</a></cite>. 6 November 2013. Editor's Draft (work in progress). URL: <a href=\"http://www.w3.org/2013/rdf11-testcases/\">http://www.w3.org/2013/rdf11-testcases/</a>. The latest edition is available at <a href=\"https://dvcs.w3.org/hg/rdf/raw-file/default/rdf11-testcases/index.html\">https://dvcs.w3.org/hg/rdf/raw-file/default/rdf11-testcases/index.html</a>",
- "RDF11-PRIMER": "Guus Schreiber, Yves Raimond. <cite><a href=\"https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-primer/index.html#\">RDF 1.1 Primer</a></cite>. 2013. The latest version is available at <a href=\"http://www.w3.org/TR/rdf11-primer/\">http://www.w3.org/TR/rdf11-primer/</a>.",
- "RDFMS": "Ora Lassila; Ralph R. Swick. <cite><a href=\"http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/\">Resource Description Framework (RDF) Model and Syntax Specification</a></cite>. 22 February 1999. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/\">http://www.w3.org/TR/1999/REC-rdf-syntax-19990222</a>.",
+ "RDF11-TESTCASES": "Markus Lanthaler, Editor. <cite><a href=\"http://www.w3.org/2013/rdf11-testcases/\">RDF 1.1 Test Cases</a></cite>. W3C Editor's Draft (work in progress). URL: <a href=\"http://www.w3.org/2013/rdf11-testcases/\">http://www.w3.org/2013/rdf11-testcases/</a>. The latest edition is available at <a href=\"https://dvcs.w3.org/hg/rdf/raw-file/default/rdf11-testcases/index.html\">https://dvcs.w3.org/hg/rdf/raw-file/default/rdf11-testcases/index.html</a>",
+ "RDF11-PRIMER": "Guus Schreiber, Yves Raimond. <cite><a href=\"https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-primer/index.html\">RDF 1.1 Primer</a></cite>. 2013. The latest version is available at <a href=\"http://www.w3.org/TR/rdf11-primer/\">http://www.w3.org/TR/rdf11-primer/</a>.",
+ "RDF11-NEW": "David Wood. <cite><a href=\"https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-new/index.html\">What’s New in RDF 1.1</a></cite>. W3C Editor's Draft (work in progress). The latest version is available at <a href=\"http://www.w3.org/TR/rdf11-new/\">http://www.w3.org/TR/rdf11-new/</a>.",
+ "RDFMS": "Ora Lassila; Ralph R. Swick. <cite><a href=\"http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/\">Resource Description Framework (RDF) Model and Syntax Specification</a></cite>. 22 February 1999. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/\">http://www.w3.org/TR/1999/REC-rdf-syntax-19990222</a>.",
"LINKED-DATA": "Tim Berners-Lee. <cite><a href=\"http://www.w3.org/DesignIssues/LinkedData.html\">Linked Data</a></cite>. Personal View, imperfect but published. URL: <a href=\"http://www.w3.org/DesignIssues/LinkedData.html\">http://www.w3.org/DesignIssues/LinkedData.html</a>",
"BERNERS-LEE98": "Tim Berners-Lee. <cite><a href=\"http://www.w3.org/DesignIssues/RDFnot.html\">What the Semantic Web can represent</a></cite>. 1998. URI: <a href=\"http://www.w3.org/DesignIssues/RDFnot.html\">http://www.w3.org/DesignIssues/RDFnot.html</a>.",
"HORST04": "Herman J. ter Horst. <cite>Extending the RDFS Entailment Lemma</cite>, in S.A. McIlraith et al. (Eds.), The Semantic Web - ISWC2004, Proceedings of the Third International Semantic Web Conference, Hiroshima, Japan, November 2004, Springer, LNCS 3298, pp. 77-91.",
@@ -21,8 +22,8 @@
"DOAP": "Ed Dumbill. <cite><a href=\"https://github.com/edumbill/doap/wiki\">Description of a Project.</a></cite> Community Specification. URL: <a href=\"https://github.com/edumbill/doap/wiki\">https://github.com/edumbill/doap/wiki</a>",
"RELAXNG": "James Clark and Murata Makoto, editors. <cite><a href=\"http://www.oasis-open.org/committees/relax-ng/spec-20011203.html\">RELAX NG Specification</a></cite>. OASIS Committee Specification, 3 December 2001. Latest version: <a href=\"http://www.oasis-open.org/committees/relax-ng/spec.html\">http://www.oasis-open.org/committees/relax-ng/spec.html</a>.",
"RELAXNG-COMPACT": "James Clark, editor. <cite><a href=\"http://www.oasis-open.org/committees/relax-ng/compact-20021121.html\">RELAX NG Compact Syntax</a></cite>. OASIS Committee Specification, 21 November 2002. URI: <a href=\"http://www.oasis-open.org/committees/relax-ng/compact-20021121.html\">http://www.oasis-open.org/committees/relax-ng/compact-20021121.html</a>.",
- "STRIPEDRDF": "D. Brickley. <cite><a href=\"http://www.w3.org/2001/10/stripes/\">RDF: Understanding the Striped RDF/XML Syntax</a>. W3C, 2001. URI: <a href=\"http://www.w3.org/2001/10/stripes/\">http://www.w3.org/2001/10/stripes/</a>.",
- "IANA-MEDIA-TYPES": "<cite><a href=\"http://www.iana.org/assignments/media-types/\">MIME Media Types</a></cite>. The Internet Assigned Numbers Authority (IANA). The registration for application/rdf+xml is archived at <a href=\"http://www.w3.org/2001/sw/RDFCore/mediatype-registration\">http://www.w3.org/2001/sw/RDFCore/mediatype-registration</a>.",
+ "STRIPEDRDF": "D. Brickley. <cite><a href=\"http://www.w3.org/2001/10/stripes/\">RDF: Understanding the Striped RDF/XML Syntax</a>. W3C, 2001. URI: <a href=\"http://www.w3.org/2001/10/stripes/\">http://www.w3.org/2001/10/stripes/</a>.",
+ "IANA-MEDIA-TYPES": "<cite><a href=\"http://www.iana.org/assignments/media-types/\">MIME Media Types</a></cite>. The Internet Assigned Numbers Authority (IANA). The registration for application/rdf+xml is archived at <a href=\"http://www.w3.org/2001/sw/RDFCore/mediatype-registration\">http://www.w3.org/2001/sw/RDFCore/mediatype-registration</a>.",
"SPARQL11-OVERVIEW": { aliasOf: "sparql11-overview" },
"SPARQL11-ENTAILMENT": { aliasOf: "sparql11-entailment" },
"VOCAB-ORG": { aliasOf: "vocab-org" },
--- a/rdf-concepts/index.html Fri Dec 13 08:05:45 2013 -0500
+++ b/rdf-concepts/index.html Fri Dec 13 08:06:03 2013 -0500
@@ -365,21 +365,19 @@
<ul>
<li>An <a title="IRI">IRI</a>, once minted, should never
- change its intended <a>referent</a>. (See
- <a href="http://www.w3.org/TR/webarch/#URI-persistence">URI
- persistence</a> [[WEBARCH]].)</li>
+ change its intended <a>referent</a>. (See
+ <a href="http://www.w3.org/TR/webarch/#URI-persistence">URI persistence</a>
+ [[WEBARCH]].)</li>
<li><a title="literal">Literals</a>, by design, are constants and
- never change their <a title="literal value">value</a>.</li>
- <li>Some <a title="property">properties</a> may change over time.
- A relationship that holds between two <a title="resource">resources</a>
- at one time may not hold at another time.</li>
- <li><a title="RDF source">RDF sources</a> may change their state
- over time.
- That is, they may provide different <a title="RDF graph">RDF graphs</a>
- at different times.</li>
+ never change their <a title="literal value">value</a>.</li>
+ <li>A relationship that holds between two <a title="resource">resources</a>
+ at one time may not hold at another time.</li>
+ <li><a title="RDF source">RDF sources</a> may change their state over time.
+ That is, they may provide different <a title="RDF graph">RDF graphs</a>
+ at different times.</li>
<li>Some <a title="RDF source">RDF sources</a> may, however, be immutable
- snapshots of another RDF source, archiving its state at some
- point in time.</li>
+ snapshots of another RDF source, archiving its state at some
+ point in time.</li>
</ul>
</section>
@@ -1380,58 +1378,11 @@
<section class="appendix informative" id="changes">
- <h2>Changes between RDF 2004 and RDF 1.1</h2>
- <!--
-
- <p class="issue">The Working Group intends to publish a separate
- Working Group Note entitled
- <em>RDF 1.1 New Features and Migration Guide</em>. This is
- <a href="http://www.w3.org/2011/rdf-wg/track/actions/193">ACTION-193</a>.
- Some or all material in this section may be moved to that document. In the
- meantime, the <a href="#change-log">Change Log</a> is a good indication
- as to what else has changed and why.</p>
- -->
-
- <p>This section discusses changes between the
- <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/">2004
- Recommendation of <em>RDF Concepts and Abstract Syntax</em></a> and
- the RDF 1.1 versions of this specification.</p>
+ <h2>Changes between RDF 1.0 and RDF 1.1</h2>
- <p>Previous versions of RDF used the term
- “<dfn>RDF URI Reference</dfn>” instead of “IRI” and allowed
- additional characters:
- “<code><</code>”, “<code>></code>”,
- “<code>{</code>”, “<code>}</code>”,
- “<code>|</code>”, “<code>\</code>”,
- “<code>^</code>”, “<code>`</code>”,
- ‘<code>“</code>’ (double quote), and “<code> </code>” (space).
- In IRIs, these characters must be percent-encoded as
- described in <a href="http://tools.ietf.org/html/rfc3986#section-2.1">section 2.1</a>
- of [[RFC3986]].</p>
-
- <p>In earlier versions of RDF, <a title="literal">literals</a>
- with a <a>language tag</a> did not have a <a>datatype IRI</a>, and
- <a title="simple literal">simple literals</a> could appear
- directly in the abstract syntax. Simple literals and literals with a
- language tag were collectively known as
- <dfn title="plain literal">plain literals</dfn>.</p>
-
- <p>Earlier versions of RDF permitted
- <a title="language tag">language tags</a> that
- adhered to the generic tag/subtag syntax of language tags,
- but were not well-formed according to [[!BCP47]]. Such
- language tags do not conform to RDF 1.1.</p>
-
- <p>The <code>xsd:string</code> datatype does not
- permit the <code>#x0</code> character, and implementations might not permit
- control codes in the <code>#x1-#x1F</code> range. Earlier versions of
- RDF allowed these characters in
- <a title="simple literal">simple literals</a>, although they
- could never be serialized in a W3C-recommended concrete syntax.
- Currently a literal with type xsd:string containing the #x0 character
- is an ill-typed literal.</p>
-
- <p>RDF 1.1 introduces the notion of <a title="RDF dataset">RDF datasets</a>.</p>
+ <p>A detailed overview of the differences between RDF versions 1.0
+ and 1.1 can be found in
+ <a href="http://www.w3.org/TR/rdf11-new/">What’s New in RDF 1.1</a> [[RDF11-NEW]].</p>
</section>
@@ -1445,7 +1396,10 @@
<a href="http://www.w3.org/TR/2013/CR-rdf11-concepts-20131105/">5 November 2013 Candidate Recommendation (CR)</a>.</p>
<ul>
- <li>2013-12-04: Editorial changes to <a href="#section-Graph-Literal" class="sectionRef"></a> as <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013Nov/0078.html">discussed on the mailing list</a>.</li>
+ <li>2013-12-12: Editorial changes in response to a review by
+ <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013Dec/0084.html">Thomas Baker</a></li>
+ <li>2013-12-12: Replace <a href="#changes" class="sectionRef"></a> with a reference to [[RDF11-NEW]]</li>
+ <li>2013-12-04: Editorial changes to <a href="#section-Graph-Literal" class="sectionRef"></a> as <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013Nov/0078.html">discussed on the mailing list</a></li>
<li>2013-11-06: Editorial changes in response to a <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013Nov/0027.html">review by Guus Schreiber</a></li>
</ul>
</section>
--- a/rdf-dataset/index.html Fri Dec 13 08:05:45 2013 -0500
+++ b/rdf-dataset/index.html Fri Dec 13 08:06:03 2013 -0500
@@ -30,7 +30,7 @@
"DELBRU-ET-AL-2008" : "Renaud Delbru, Axel Polleres, Giovanni Tummarello, Stefan Decker. <cite>Context Dependent Reasoning for Semantic Documents in Sindice.</cite> In Proceedings of the 4th International Workshop on Scalable Semantic Web Knowledge Base Systems (SSWS). Karlsruhe, Germany, 2008.",
-"CARROLL-ET-AL-2005" : "Jeremy Carroll, Pat Hayes, " },
+"NAMED-GRAPH" : "Jeremy Carroll, Pat Hayes, etc" },
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "rdf-datasets",
@@ -40,7 +40,7 @@
// subtitle : "an excellent document",
// if you wish the publication date to be other than today, set this
- publishDate: "2013-09-17",
+ publishDate: "2013-12-04",
// if the specification's copyright date is a range of years, specify
// the start date here:
@@ -65,7 +65,7 @@
// if you want to have extra CSS, append them to this list
// it is recommended that the respec.css stylesheet be kept
- extraCSS: ["http://dvcs.w3.org/hg/rdf/raw-file/default/ReSpec.js/css/respec.css"],
+ //extraCSS: ["http://dvcs.w3.org/hg/rdf/raw-file/default/ReSpec.js/css/respec.css"],
// editors, add as many as you like
// only "name" is required
@@ -134,23 +134,27 @@
<body>
<section id="abstract">
- <p>RDF defines the concept of RDF datasets, a structure composed of a distinguished RDF graph and zero or more named graphs, being pairs comprising an IRI or blank node and an RDF graph. While RDF graphs have a formal model-theoretic semantics that determines what arrangements of the world make an RDF graph true, no agreed formal semantics exists for RDF datasets. This document presents the issues to be addressed when defining a formal semantics for datasets, as they have been discussed in the RDF 1.1 Working Group, and specify several semantics in terms of model theory, each corresponding to a certain design choice for RDF datasets.</p>
+ <p>RDF defines the concept of RDF datasets, a structure composed of a distinguished RDF graph and zero or more named graphs, being pairs comprising an IRI or blank node and an RDF graph. While RDF graphs have a formal model-theoretic semantics that determines what arrangements of the world make an RDF graph true, no agreed formal semantics exists for RDF datasets. This document presents some issues to be addressed when defining a formal semantics for datasets, as they have been discussed in the RDF 1.1 Working Group, and specify several semantics in terms of model theory, each corresponding to a certain design choice for RDF datasets.</p>
+</section>
+
+<section id="sotd">
+ <p>This document is intended to be published as a Working Group note.</p>
</section>
<section id="sec-introduction">
<h2 id="introduction">Introduction</h2>
- <p>The <a href="http://www.w3.org/TR/rdf11-concepts/">Resource Description Framework (RDF)</a> version 1.1 defines the concept of RDF datasets, a notion introduced first by the SPARQL specification [[RDF-SPARQL-QUERY]]. An RDF dataset is defined as a collection of <a title="RDF graph">RDF graphs</a> where all but one are <a title="named graph">named graphs</a> associated with an <a>IRI</a> or <a>blank node</a> (the <a>graph name</a>), and the unnamed default graph [[RDF11-CONCEPTS]]. Given that RDF is a data model equiped with a formal semantics [[RDF11-MT]], it is natural to try and define what the semantics of datasets should be.</p>
+ <p>The <a href="http://www.w3.org/TR/rdf11-concepts/">Resource Description Framework (RDF)</a> version 1.1 defines the concept of RDF datasets, a notion introduced first by the SPARQL specification [[RDF-SPARQL-QUERY]]. An RDF dataset is defined as a collection of <a title="RDF graph">RDF graphs</a> where all but one are <a title="named graph">named graphs</a> associated with an <a>IRI</a> or <a>blank node</a> (the <a>graph name</a>), and the unnamed default graph [[RDF11-CONCEPTS]]. Given that RDF is a data model equipped with a formal semantics [[RDF11-MT]], it is natural to try and define what the semantics of datasets should be.</p>
- <p>The RDF 1.1 Working Group was initially chartered to provide such semantics in its recommendation:</p>
+ <p>The RDF 1.1 Working Group was initially chartered to provide such semantics in its recommendation:</p>
<blockquote cite="http://www.w3.org/2011/01/rdf-wg-charter">
<h5>Required features</h5>
<ul><li id="ng">Standardize a model and semantics for multiple graphs and graphs stores [...]</li></ul>
</blockquote>
- <p>However, discussions within the Working Group revealed that very different assumptions were currently existing among practitioners, who are using RDF datasets with their own intuition of the meaning of the datasets. Defining the semantics of RDF datasets requires an understanding of the two following issues:</p>
+ <p>However, discussions within the Working Group revealed that very different assumptions currently exist among practitioners, who are using RDF datasets with their own intuition of the meaning of datasets. Defining the semantics of RDF datasets requires an understanding of the two following issues:</p>
<ul>
- <li>what the graph names (IRI or blank node) denote;</li>
+ <li>what the graph names (IRI or blank node) denote, or what are the constraints on what the names can possibly denote;</li>
<li>how the triples in the named graph influence the meaning of the dataset.</li>
</ul>
@@ -161,16 +165,20 @@
<li>it denotes a supergraph of the graph inside the pair;</li>
<li>it denotes a container for the RDF graph, that is, a mutable element;</li>
<li>it denotes the information resource that can be obtained by dereferencing the graph name, when it is an IRI and if such resource exists;</li>
- <li>it denotes an arbitrary resource that is constrained to be in a special relationship with the graph inside the pair;</li>
- <li>it denotes an unconstrained resource.</li>
+ <li>it denotes an arbitrary resource that is constrained to be in a special relationship (for instance, <code>ex:hasGraph</code> with the graph inside the pair;</li>
+ <li>it denotes the deductive closure of the graph inside the pair;</li>
+ <li>it denotes an arbitrary resource that is in a special relation with the deductive closure, or with a superset of the graph;</code>
+ <li>it denotes an unconstrained resource;</li>
+ <li>etc.</li>
</ul>
+ <p>Even with an intuitive understanding of what the truth of an RDF dataset should be, the precise model-theoretic formalization can be subject to many variations.</p>
<p>Possible choices for the meaning of the triples in the named graphs include:</p>
<ul>
<li>all the triples in the named graphs and default graphs contribute to the truth of the dataset in the same way triples contribute to the truth of a single graph;</li>
<li>the triples of the named graphs are considered part of the knowledge of the default graph;</li>
- <li>different named graphs indicate different "contexts", or different "worlds", and the triples inside a named graph are assumed to be true in the associated context only; in this case, the default graph can be interpreted as yet another context, or be considered as a "global context" which must hold in all contexts;</li>
- <li>the named graphs are considered as "hypothetical graphs" which bear the same consequences as their RDF graphs, but they do not participate in the truth of the dataset; this is similar to the "context" option above but it allows a graph to contain contradictions without making the dataset contradictory;</li>
+ <li>different named graphs indicate different “contexts”, or different “worlds”, and the triples inside a named graph are assumed to be true in the associated context only; in this case, the default graph can be interpreted as yet another context, or be considered as a “global context” which must hold in all contexts, or again as metadata about the contexts;</li>
+ <li>the named graphs are considered as “hypothetical graphs” which bear the same consequences as their RDF graphs, but they do not participate in the truth of the dataset; this is similar to the “context” option above but it allows a graph to contain contradictions without making the dataset contradictory;</li>
<li>the triples are merely quoted without any indication of what they mean; they do not participate in the truth of a dataset.</li>
</ul>
@@ -183,8 +191,8 @@
<p>We first take a look at existing specifications that could shed a light on how the semantics of datasets should be defined. There are three important documents that closely relate to the issue:</p>
<ul>
- <li>the RDF semantics, as standardised in 2004 [[RDF-MT]] and its revision in 2013 [[RDF11-MT]];</li>
- <li>the article <i>Named Graphs</i> by Carrol et al., which first introduced the term "named graph" and contains a section on formal semantics;</li>
+ <li>the RDF semantics, as standardized in 2004 [[RDF-MT]] and its revision in 2013 [[RDF11-MT]];</li>
+ <li>the article <i>Named Graphs</i> by Carroll et al. [[NAMED-GRAPH]], which first introduced the term “named graph” and contains a section on formal semantics;</li>
<li>the SPARQL specification [[RDF-SPARQL-QUERY]], which defines RDF datasets and how to query them.</li>
</ul>
@@ -193,23 +201,23 @@
<!--<p class="issue">Part of what follows is somewhat subjective.</p>-->
- <p>The first version of RDF semantics defined the meaning of a set of RDF graphs: <q cite="http://www.w3.org/TR/rdf-mt/#entail">a set of graphs can be treated as equivalent to its merge, that is, a single graph, as far as the model theory is concerned</q>. The new version indicates that a set of RDF graphs can be either interpreted as its union or as its merge.</p>
- <p>So, a first intuition could be that an RDF dataset, being presented as a collection of graph, should mean exactly what the set of its named graphs and default graph means. However, this completely leaves out the meaning of graph names, which could be valuable indicators for the truth of a dataset.</p>
- <p>Formally, the semantics of RDF defines a notion of interpretation for a set of triples (i.e., an RDF graph), which then can extend to a set of RDF graphs. A dataset is neither a set of triples nor a set of RDF graphs. It is a set of <em>pairs</em> (name,graph) together with a distinguished RDF graph. Consequently, defining interpretation and entailement for RDF datasets would require at least an extension of the RDF semantics.</p>
+ <p>As described in RDF 1.1 Semantics, a set of RDF graphs can be interpreted as either the union of the graphs or as their merge ([[RDF11-MT]], Technical note, Section 5.2).</p>
+ <p>So, a first intuition could be that an RDF dataset, being presented as a collection of graph, should mean exactly what the set of its named graphs and default graph means. However, this completely leaves out the potential meaning of graph names, which could be valuable indicators for the truth of a dataset.</p>
+ <p>Formally, the semantics of RDF defines a notion of interpretation for a set of triples (i.e., an RDF graph), which then can extend to a set of RDF graphs. A dataset is neither a set of triples nor a set of RDF graphs. It is a set of <em>pairs</em> (name,graph) together with a distinguished RDF graph and the RDF semantics does not itself specify a meaning for these pairs.</p>
<p>Conceptually, it is problematic since one of the reasons for separating triples into distinct (named) graphs is to avoid propagating the knowledge of one graph to the entire triple base. Sometimes, contradicting graphs need to coexist in a store. Sometimes named graphs are not endorsed by the system as a whole, they are merely quoted.</p>
</section>
<section id="sec-named-graph-paper">
<h3 id="named-graph">The Named Graphs paper</h3>
- <p>In Carrol et al., a named graph is simply defined as a pair comprising an IRI and an RDF graph. The notion of RDF interpretation is extended to named graphs by saying that the graph IRI in the pair must denote the pair itself. This non-ambiguously answers the question of what the graph IRI denotes. This can then be used to define a proper dataset semantics, as shown in Section 3.3.</p>
+ <p>In Carroll et al. [[NAMED-GRAPHS]], a named graph is defined as a pair comprising an IRI and an RDF graph. The notion of RDF interpretation is extended to named graphs by saying that the graph IRI in the pair must denote the pair itself. This non-ambiguously answers the question of what the graph IRI denotes. This can then be used to define proper dataset semantics, as shown in Section 3.3. Note that it is deliberate that the graph IRI is forced to denote the pair rather than the RDF graph. This is done in order to differentiate two occurrences of the same RDF graph that could have been published at different times, or authored by different people. A simple reference to the RDF graph would simply identify a mathematical set, which is the same wherever it occurs.</p>
</section>
<section id="sec-sparql">
<h3 id="sparql">The SPARQL specification</h3>
- <p>RDF 1.1 defines the notion of RDF dataset identically to SPARQL, which introduced it first. So, in order to understand the semantics of dataset, it is worth looking at how SPARQL uses datasets. SPARQL defines what are answers to queries posed against a dataset, but it never defines the notions that are key to a model theoretic formal semantics: it neither presents interpretations nor entailment. Still, it is worth noticing that a ASK query that only contains a basic graph pattern without variables yields the same result as asking whether the RDF graph in the query is entailed by the default graph. Based on this observation, one may extrapolate that a ASK query containing no variables and only GRAPH graph patterns would yield the same result as dataset entailment.</p>
- <p>This can be used as a guide for formalizing the semantics of datasets, as can be seen in Section 3.7.</p>
+ <p>RDF 1.1 borrows the notion of RDF dataset from the SPARQL specification [[RDF-SPARQL-QUERY]], with the notable different that RDF 1.1 allows graph names to be blank nodes. So, in order to understand the semantics of dataset, it is worthwhile looking at how SPARQL uses datasets. SPARQL defines what answers to queries posed against a dataset are, but it never defines the notions that are key to a model theoretic formal semantics: it neither presents interpretations nor entailment. Still, it is worth noticing that a ASK query that only contains a basic graph pattern without variables yields the same result as asking whether the RDF graph in the query is entailed by the default graph. Based on this observation, one may extrapolate that a ASK query containing no variables and only <code>GRAPH</code> graph patterns would yield the same result as dataset entailment.</p>
+ <p>This can be used as a guide for formalizing the semantics of datasets, as can be seen in Section 3.7.</p>
</section>
</section>
@@ -219,7 +227,7 @@
<h2 id="formal-definitions">Formal definitions</h2>
- <p>This section presents the different options proposed, together with their formal definitions. We include each time a discussion of the merrits of the choice, and some properties.</p>
+ <p>This section presents the different options proposed, together with their formal definitions. We include each time a discussion of the merits of the choice, and some properties.</p>
<p>Each subsection here describes the option informally, before presenting the formal definitions. As far as the formal part is concerned, one has to be familiar with the definitions given in RDF Semantics. We rely a lot on the notion of interpretation and entailment, which are key in model theory.</p>
<p>All proposed options share some commonalities:</p>
<ul>
@@ -227,18 +235,21 @@
<li>they define notions of interpretation and entailment in function of the corresponding notions in RDF Semantics.</li>
</ul>
- <p>In fact, the dependency on RDF semantics is such that most of the dataset semantics below reuse RDF semantics as a black box. The purpose of a formal semantics for datasets is to determine under what circumstances a dataset can be said to be true or false. The formalisation below indicates that the truth of an RDF dataset can be determined in function of the truth of an RDF graph, no matter how the latter is determined. Therefore, instead of defining a precise definition of RDF graph interpretations and entailment, we use the more abstract notion of <a>entailment regime</a>. In fact, RDF Semantics does not define a single formal semantics, but multiple ones, depending on what standard vocabularies are endorsed by an application. Consequently, we will parameterize most of the definitions below with an unspecified entailment regime <var>E</var>. RDF 1.1 defines the following entailment regimes: simple entailment, D-entailment, RDF-entailment, RDFS-entailment. Additionally, OWL defines two other entailment regimes, based on the OWL 2 direct semantics [[OWL2-DIRECT-SEMANTICS]] and the OWL 2 RDF-based semantics [[OWL2-RDF-BASED-SEMANTICS]].</p>
+ <p>The first item above reflects the indication given in [[RDF11-MT]] with respect to dataset semantics: <q cite="http://www.w3.org/TR/rdf11-mt/#rdf-datasets">a dataset SHOULD be understood to have at least the same content as its default graph</q>.</p>
+ <p>The dependency on RDF semantics is such that most of the dataset semantics below reuse RDF semantics as a black box. More precisely, it is not necessary to be specific about how truth of RDF graphs is defined as long as there is a notion of interpretation that determines the truth of a set of triples. In fact, RDF Semantics does not define a single formal semantics, but multiple ones, depending on what standard vocabularies are endorsed by an application (such as the RDF, RDFS, XSD vocabularies). Consequently, we parameterize most of the definitions below with an unspecified entailment regime <var>E</var>. RDF 1.1 defines the following entailment regimes: simple entailment, D-entailment, RDF-entailment, RDFS-entailment. Additionally, OWL defines two other entailment regimes, based on the OWL 2 direct semantics [[OWL2-DIRECT-SEMANTICS]] and the OWL 2 RDF-based semantics [[OWL2-RDF-BASED-SEMANTICS]].</p>
<p>For an entailment regime <var>E</var>, we will say <var>E</var>-interpretation, <var>E</var>-entailment, <var>E</var>-equivalence, <var>E</var>-consistency to describe the notions of interpretations, entailment, equivalence and consistency associated with the regime <var>E</var>. Similarly, we will use the terms dataset-interpretation, dataset-entailment, dataset-equivalence, dataset-consistency for the corresponding notions in dataset semantics.</p>
<section>
<h3 id="no-meaning">Named graphs have no meaning</h3>
+
<p>The simplest semantics defines an interpretation of a dataset as an RDF interpretation of the default graph. The dataset is true, according to the interpretation, if and only if the default graph is true. In this case, any datasets that have equivalent default graphs are dataset-equivalent.</p>
- <p>This means that the named graphs in a dataset are irrelevent to determining the truth of a dataset. Therefore, arbitrary modifications of the named graphs in a graph store always yield an equivalent dataset, according to this semantics.</p>
+ <p>This means that the named graphs in a dataset are irrelevant to determining the truth of a dataset. Therefore, arbitrary modifications of the named graphs in a graph store always yield a logically equivalent dataset, according to this semantics.</p>
<h4 id="f1" class="formal">Formalization</h4>
<p>Considering an entailment regime <var>E</var>, a dataset-interpretation with respect to <var>E</var> is an <var>E</var>-interpretation. Given an interpretation <var>I</var> and a dataset <var>D</var> having default graph <var>G</var> and named graphs <var>NG</var>, <var>I(D)</var> is true if and only if <var>I(G)</var> is true.</p>
- <h4 id="ex1" class="ex">Examples of entailement and non-entailments</h4>
+ <h4 id="ex1" class="ex">Examples of entailment and non-entailments</h4>
<p>Consider the following dataset:</p>
+
<pre class="example">{ :s :p :o . }
:g1 { :a :b :c }</pre>
<p>does not dataset-entail:</p>
@@ -256,17 +267,17 @@
:g1 :created "2013-09-17"^^xsd:date .}
:g1 { :x :y :z }</pre>
- <h4 id="p1" class="prop">Properties of this dataset semantics</h4>
- <p>Assuming this semantics is convenient since it merely ignores named graphs in a dataset. As a result, datasets can be simply treated as regular RDF graphs by extracting the default graph. Named graphs can still be used to preserve useful information, but it bares no more meaning than a commentary in a program source code.</p>
- <p>The obvious disadvantage is that, since named graphs are completely disregarded, there is no added value in using RDF datasets rather than regular RDF graphs.</p>
+ <h4 id="p1" class="pro">Properties of this dataset semantics</h4>
+ <p>Assuming this semantics is convenient since it merely ignores named graphs in a dataset for any reasoning task. As a result, datasets can be simply treated as regular RDF graphs by extracting the default graph. Named graphs can still be used to preserve useful information, but it bears no more meaning than a commentary in a program source code.</p>
+ <p>The obvious disadvantage is that, since named graphs are completely disregarded in terms of meaning, there is no guarantee that any information intended to be conveyed by the named graphs is preserved by inference.</p>
</section>
<section>
<h3 id="union">Default graph as union or as merge</h3>
- <p>It is sometimes assumed that named graphs are simply a convenient way of sorting the triples but all the triples participte in a united knowledge base that takes the place of the default graph. More precisely, a dataset is considered to be true if all the triples in all the graphs, named or default, are true together. This description allows two formalizations of dataset semantics, depending on how blank nodes spanning several named graphs are treated.</p>
+ <p>It is sometimes assumed that named graphs are simply a convenient way of sorting the triples but all the triples participate in a united knowledge base that takes the place of the default graph. More precisely, a dataset is considered to be true if all the triples in all the graphs, named or default, are true together. This description allows two formalizations of dataset semantics, depending on how blank nodes spanning several named graphs are treated. Indeed, if one blank node appears in several named graphs, it may be intentional, to indicate the existence of only one thing across the graphs, in which case union is appropriate. If the sharing of blank nodes is incidental, merge is also an applicable solution.</p>
<h4 id="f2-1" class="formal">Formalization: first version</h4>
- <p>We define a dataset-interpretation with respect to an entailment regime <var>E</var> as an <var>E</var>-interpretation. Given a dataset-interpretation <var>I</var> and a dataset <var>D</var> having default graph <var>G</var> and named fgraphs <var>NG</var>, <var>I(D)</var> is true if and only if <var>I(G)</var> is true and for all <var>ng</var> in <var>NG</var>, <var>I(ng)</var> is true.</p>
+ <p>We define a dataset-interpretation with respect to an entailment regime <var>E</var> as an <var>E</var>-interpretation. Given a dataset-interpretation <var>I</var> and a dataset <var>D</var> having default graph <var>G</var> and named graphs <var>NG</var>, <var>I(D)</var> is true if and only if <var>I(G)</var> is true and for all <var>ng</var> in <var>NG</var>, <var>I(ng)</var> is true.</p>
<p>This is equivalent to <var>I(D)</var> is true if <var>I(H)</var> is true where <var>H</var> is the <a>merge</a> of all the RDF graphs, named or default, appearing in <var>D</var>.</p>
<h4 id="f2-2" class="formal">Formalization: second version</h4>
@@ -287,21 +298,22 @@
<h4 id="p2" class="prop">Properties of this dataset semantics</h4>
<p>This semantics allows one to partition the triples of an RDF graph into multiple named graphs for easier data management, yet retaining the meaning of the overall RDF graph. Note that this choice of semantics does not impact the way graph names are interpreted: it is possible to further constrain the graph names to denote the RDF graph associated with it, or other possible constraints. The possible interpretations of graph names, and their consequences, are presented in the next sections.</p>
- <p>This semantics is implicitely assumed by existing graph store implementations. The OWLIM RDF database management system implements reasoning techniques over RDF datasets that materialize inferred statements into the database [[citation needed]]. This is done by taking the union of the graphs in the named graphs, applying standard entailment regimes over this RDF graph and putting the inferred triples into the default graph.</p>
- <p>The main drawback of this dataset semantics is that all triples in the named graphs contribute to a global knowledge that must be consistent. In situations where named graphs are used to store RDF graphs obtained from various sources on the open Web, inconsistencies or contradictions can easily occur. Notably, Web crawlers of search engines harvest all RDF documents, and it is known as a fact that the Web contains documents serializing inconsistent RDF graphs as well as documents that are mutually contradicting yet consistent on their own.</p>
+ <p>This semantics is implicitly assumed by existing graph store implementations. The OWLIM RDF database management system implements reasoning techniques over RDF datasets that materialize inferred statements into the database [[citation needed]]. This is done by taking the union of the graphs in the named graphs, applying standard entailment regimes over this RDF graph and putting the inferred triples into the default graph.</p>
+ <p>This dataset semantics makes all triples in the named graphs contribute to a global knowledge, thus making the whole dataset inconsistent whenever two graphs are mutually contradictory. In situations where named graphs are used to store RDF graphs obtained from various sources on the open Web, inconsistencies or contradictions can easily occur. Notably, Web crawlers of search engines harvest all RDF documents, and it is known as a fact that the Web contains documents serializing inconsistent RDF graphs as well as documents that are mutually contradicting yet consistent on their own. In this case, this semantics can be seen as problematic.</p>
</section>
<section>
<h3 id="naming">The graph name denotes the named graph or the graph</h3>
- <p>It is common to use the graph name as a way to identify the RDF graph inside the named graphs, or rather, to identify a particular occurence of the graph. This allows one to describe the graph or the graph source in triples. For instance, one may want to say who is the creator of a particular occurence of a graph. Assuming this semantics for graph names amounts to say that each named graph pair is an assertion that sets the <a>referent</a> of the graph name to be the associated graph.</p>
- <p>Intutively, this semantics can be seen as quoting the RDF graphs inside the named graphs. In this sense, <code>:alice {:bob :is :smart}</code> has to be understood as <q>Alice said: "Bob is smart"</q> which does not entail <q>Alice said: "Bob is intelligent"</q> because Alice did not use the word "intelligent", even though "smart" and "intelligent" can be understood as equivalent.</p>
+ <p>It is common to use the graph name as a way to identify the RDF graph inside the named graphs, or rather, to identify a particular occurrence of the graph. This allows one to describe the graph or the graph source in triples. For instance, one may want to say who the creator of a particular occurrence of a graph is. Assuming this semantics for graph names amounts to say that each named graph pair is an assertion that sets the <a>referent</a> of the graph name to be the associated graph or named graph pair.</p>
+ <p class="issue">The following paragraph refers to speech and asserting, while dataset semantics never refers to such notions. This may be confusing.</p>
+ <p>Intuitively, this semantics can be seen as quoting the RDF graphs inside the named graphs. In this sense, <code>:alice {:bob :is :smart}</code> has to be understood as <q>Alice said: “Bob is smart”</q> which does not entail <q>Alice said: “Bob is intelligent”</q> because Alice did not use the word “intelligent”, even though “smart” and “intelligent” can be understood as equivalent.</p>
<h4 id="f3" class="formal">Formalization</h4>
<p>We reuse the notation presented in [[RDF11-MT]]:</p>
<blockquote>Suppose I is an interpretation and A is a mapping from a set of blank nodes to the universe IR of I. Define the mapping [I+A] to be I on names, and A on blank nodes on the set: [I+A](x)=I(x) when x is a name and [I+A](x)=A(x) when x is a blank node; and extend this mapping to triples and RDF graphs using the rules given above for ground graphs.</blockquote>
<p>A dataset-interpretation <var>I</var> with respect to an entailment regime <var>E</var> is an <var>E</var>-interpretation extended to named graphs and datasets as follows:</p>
<ul><li>if <var>(n,g)</var> is a named graph where the graph name is an IRI, then <var>I(n,g)</var> is true if and only if <var>I(n)</var> = <var>(n,g)</var>.
- <li>if <var>D</var> is a dataset comprising default graph <var>DG</var> and named graphs <var>NG</var>, then <var>I(D)</var> is true if and only if there exists a mapping from bnodes to the universe <var>IR</var> of <var>I</var> such that <var>[I+A](DG)</var> is true and for all named graph <var>(n,g)</var> in <var>NG</var>, <var>[I+A](n)</var> = <var>(n,g)</var>.</li>
+ <li>if <var>D</var> is a dataset comprising default graph <var>DG</var> and named graphs <var>NG</var>, then <var>I(D)</var> is true if and only if there exists a mapping from blank nodes to the universe <var>IR</var> of <var>I</var> such that <var>[I+A](DG)</var> is true and for all named graph <var>(n,g)</var> in <var>NG</var>, <var>[I+A](n)</var> = <var>(n,g)</var>.</li>
</ul>
<h4 id="ex3" class="ex">Examples</h4>
@@ -324,26 +336,26 @@
<pre class="example">{ :age rdfs:range xsd:integer .
:me :age :g1 . } # default graph
:g1 { :s :p :o }</pre>
- <p>The graph name can be used in triples to attached metadata (here <code>:entains</code> is a custom term that does not enforce a formal constraint, so it is up to the implementation to decide how to treat it):</p>
- <pre class="example">{ :g1 :published "2023-08-26"^^xsd:date .
- :g1 :entails :g2 .}
+ <p>The graph name can be used in triples to attached metadata (here <code>:hasNextVersion</code> is a custom term that does not enforce a formal constraint, so it is up to the implementation to decide how to treat it):</p>
+ <pre class="example">{ :g1 :published "2013-08-26"^^xsd:date .
+ :g1 :hasNextVersion :g2 .}
:g1 { :s1 :p1 :o1 .
:s2 :p2 :o2 }
:g2 { :s1 :p1 :o1 }</pre>
<h4 id="p3" class="prop">Properties of this dataset semantics</h4>
- <p>There are important implications with this semantics. First, the presence of blank nodes as graph names can be problematic because a named graph entails an infinity of other named graphs where only the graph name is changed to a different blank node. Second, graph names have to be handled almost like literals. Unlike other IRIs or blank nodes, their denotation is strictly fixed, like literals are. Therefore, any entailment regime that recognizes datatypes and use this semantics has to be able to distinguish graphs from, e.g., integers and strings. Combined with RDFS semantics, it can lead to inconsistencies, as in the last example above.</p>
+ <p>There are important implications with this semantics. In this case, a named graph pair can only entail itself or a graph that is structurally equivalent if the graph name is a blank node. Graph names have to be handled almost like literals. Unlike other IRIs or blank nodes, their denotation is strictly fixed, like literals are. This means that graph IRIs may possibly clash with constraints on datatypes, as in the example above.</p>
<p>A variant of this dataset semantics imposes that the graph name denotes the RDF graph itself, rather than the pair. This means that two occurrences of the same graph in different named graph pairs actually identify the same thing. Thus, the graph names associated with the same RDF graphs are interchangeable in any triple in this case.</p>
</section>
<section>
<h3 id="context">Each named graph defines its own context</h3>
- <p>Named graphs in RDF datasets are sometimes used to delimit a context in which the triples of the named graphs are true. From the truth of these triples, it is possible to infer knowledge that it is convenient to make part of the named graph. An example of such situation occurs when one wants to keep track of the evolution of the data with time. Another example is when one wants to allow different view points to be expressed and reasoned with, without creating a conflict or inconsistency. By having inferences done at the named graph level, one can prevent for instance that triples comming from untrusted parties are influenceing trusted knowledge. Yet it does not disallow reasoning with and drawing conclusions from untrusted information.</p>
- <p>Intutively, this semantics can be seen as interpreting the RDF graphs inside the named graphs. In this sense, <code>:alice {:bob :is :smart}</code> has to be understood as <q>Alice said that Bob is smart</q> which entails <q>Alice said that Bob is intelligent</q> because the two sentences mean the same thing. Neither sentences mean that Alice used these actual words.</p>
+ <p>Named graphs in RDF datasets are sometimes used to delimit a context in which the triples of the named graphs are true. From the truth of these triples according to the graph semantics, follows the truth of the named graph pair. An example of such situation occurs when one wants to keep track of the evolution of facts with time. Another example is when one wants to allow different viewpoints to be expressed and reasoned with, without creating a conflict or inconsistency. By having inferences done at the named graph level, one can prevent for instance that triples coming from untrusted parties are influencing trusted knowledge. Yet it does not disallow reasoning with and drawing conclusions from untrusted information.</p>
+ <p>Intuitively, this semantics can be seen as interpreting the RDF graphs inside the named graphs. In this sense, <code>:alice {:bob :is :smart}</code> has to be understood as <q>Alice said that Bob is smart</q> which entails <q>Alice said that Bob is intelligent</q> because it is what Bob means, whether he used the term “smart”, “intelligent”, or “bright”. Neither sentence implies that Alice used these actual words.</p>
<h4 id="f4" class="formal">Formalization</h4>
<p class="issue">This does not take into account blank nodes as graph names.</p>
- <p>There are several possible formalization of this. One way is to interpret the graph name as denoting a graph that represents all that is true in the context of the named graph. In this case, a dataset-interpretation with respect to an entailment regime <var>E</var> is an <var>E</var>-interpretation such that:</p>
+ <p>There are several possible formalizations of this. One way is to interpret the graph name as denoting a graph, and a named graph pair is true if this graph entails the graph inside the pair. In this case, a dataset-interpretation with respect to an entailment regime <var>E</var> is an <var>E</var>-interpretation such that:</p>
<ul>
<li>for each named graph pair <var>ng</var> = <var>(n,G)</var>, <var>I(ng)</var> is true if <var>I(n)</var> is an RDF graph and <var>E</var>-entails <var>G</var>;</li>
<li>for a dataset <var>D</var> = <var>(DG,NG)</var>, <var>I(D)</var> is true if <var>I(DG)</var> is true and for all named graph <var>ng</var> in <var>NG</var>, <var>I(ng)</var> is true;
@@ -362,7 +374,7 @@
<p>but does not RDFS-dataset-entail:</p>
<pre class="example">{ }
:g2 { :chadHurley rdf:type :GoogleEmployee }</pre>
- <p>With this semantics too, graph names can be used in triples:</p>
+ <p>Graph names used in triples that express metadata do not necessarily generate inconsistency:</p>
<pre class="example">{ :g1 :validAfter "2006"^^xsd:gYear .
:g1 :published "2013-08-26"^^xsd:date .
:g2 :validAt "2005"^^:xsd:gYear .}
@@ -372,34 +384,40 @@
<p>(here, <code>:validAfter</code> and <code>:validAt</code> are custom terms that do not enforce a formal constraint, but may be used internally for, e.g., checking the temporal validity of triples in the named graph).</p>
<h4 id="p4" class="prop">Properties of this dataset semantics</h4>
- <p>This semantics assumes that the truth of named graphs is preserved when replacing the RDF graphs inside named graphs with equivalent graphs. This means in particular, that one can normalise literals and still preserve the truth of a named graph. This means too that standard RDF inferences that can be drawn from the RDF graphs inside named graphs can be added to the graph associated with the graph name without impacting the truth of the RDF dataset.</p>
+ <p>This semantics assumes that the truth of named graphs is preserved when replacing the RDF graphs inside named graphs with equivalent graphs. This means in particular, that one can normalize literals and still preserve the truth of a named graph. This means too that standard RDF inferences that can be drawn from the RDF graphs inside named graphs can be added to the graph associated with the graph name without impacting the truth of the RDF dataset.</p>
<p>While this semantics does not guarantee that reasoning with RDF datasets will preserve the exact triples of an original dataset, it is semantically valid to store both the original and any entailed datasets.</p>
<p>An example implementation of such a context-based semantics is Sindice [[DELBRU-ET-AL-2008]].</p>
- <h4 id="v4" class="other">Variants this dataset semantics</h4>
+ <h4 id="v4" class="other">Variants of this dataset semantics</h4>
<p>There are several variants of this type of dataset-semantics</p>
<ul>
<li>The default graph is interpreted as universal truth, that is, for a named graph <var>(n,G)</var>, <var>I(n)</var> <var>E</var>-entails the default graph.</li>
- <li>The graph name does not denote an RDF graph but a resource associated with an RDF graph. This is similar to saying that the name is interpreted as the intension of the graph, and the actual RDF graph is its extension.</li>
+ <li>The graph name does not denote an RDF graph but a resource associated with an RDF graph.</li>
<li>Each named graph could be associated with a distinct <var>E</var>-interpretation and impose all interpretations to be true for their corresponding graph, in order for the dataset to be true.</li>
</ul>
</section>
- <!--<section>
- <h3>Each named graph defines its own "context"</h3>
- <p>Sometimes, the separation of triples into different named graphs is used to indicate truth in different contexts. Each graph describes a "world".</p>
- <p>In substance, the formalization says that each RDF graph in a dataset is interpreted separately. This models the fact that different RDF graphs may hold in different contexts. This way, graphs that have been put in different "named graph pairs" can contradict with each other without making the dataset inconsistent.</p>
-
- <h4 class="formal">Formalization</h4>
- <p>For any entailment regime <var>E</var>, let <var>K(E)</var> be the set of all <var>E</var>-interpretations. A dataset-interpretation with respect to an entailment regime <var>E</var> is a pair <var>(IG,Con)</var> where IG is an <var>E</var>-interpretation and <var>Con</var> is a partial mapping from to </var>K(E)</var>.</p>
- <p>The truth of a dataset for a dataset-interpretation I = (IG,Con) is defined as follows:</p>
+ <section>
+ <h3 id="boxdataset">Named graph are in a particular relationship with what the graph name dereferences to</h3>
+ <p>In accordance with linked data principles, IRIs may be assumed to reference the document that is obtained by dereferencing it. If the document contains an RDF graph it can be assumed that the graph in the named graph is in a special relationship (such as, equals, entails) with this RDF graph.</p>
+ <p>In such case, the truth of an RDF dataset is dependent on the state of the Web, and the same dataset may entail different statements at different times.</p>
+
+ <h4 id="hbox" class="formal">Formalization</h4>
+ <p>Let <var>d</var> be the function that maps an IRI to an RDF graph that can be obtained from dereferencing the IRI. For an IRI <var>u</var>, <var>d(u)</var> is empty when dereferencing returns an error or a document that does not encode an RDF graph.</p>
+ <p>A dataset-interpretation <var>I</var> with respect to an entailment regime <var>E</var> is an <var>E</var>-interpretation such that:</p>
<ul>
- <li>for a named graph pair ng = (n,G), I(ng) is true if Con(n) is defined Con(n)(G) is true;</li>
- <li>for a dataset D = (DG,G), I(D) is true if IG(G) is true and for all named graph ng in NG, I(ng) is true;
- <li>I(D) is false otherwise.</li>
+ <li>for a named graph pair <var>ng</var> = <var>(n,G)</var>, <var>I(ng)</a> is true if <var>d(n)</var> equals (respectively, is a subgraph of, is entailed by) <var>G</var>;</li>
+ <li>for a dataset <var>D</var> = <var>(DG,NG)</var>, <var>I(D)</var> is true if <var>I(DG)</var> is true and for all named graph <var>ng</var> in <var>NG</var>, <var>I(ng)</var> is true;
+ <li><var>I(D)</var> is false otherwise.</li>
</ul>
- <p>Following standard definitions, we say that a dataset D1 entails a dataset D2 if all dataset-interpretation I that makes D1 true also makes D2 true.</p>
- </section>-->
+
+ <h4 id="ex4" class="ex">Examples</h4>
+ <p>Entailments in this semantics depend not only on the content of a dataset but also on the content of the Web and the ability of a reasoner to accept this content. Moreover, the entailments vary whether the considered relation is “equals”, or “subgraph of”, or “entailed by”.</p>
+ <p>For instance, if the reasoner is offline, then the dereferencing function <var>d</var> in the previous definition always return an empty graph. In this case, if the relation is “equals” or “subgraph of”, only empty named graphs can be true; if the relation is “entails by”, then only named graphs containing axiomatic triples are true. In general, if the relationship is “equals”, named graph do not provide extra entailments.</p>
+
+ <h4 id="pbox" class="prop">Properties of this dataset semantics</h4>
+ <p>The distinguishing characteristic of this dataset semantics is the fact that a single RDF dataset can lead to different entailments, depending on the state of the Web. This can be seen as a feature for systems that need to be in line with what is found online, but is a drawback for systems that must retain consistency even when they go offline.</p>
+ </section>
<!--<section>
<h3>Named graphs as contexts, and the default graph is universal truth</h3>
@@ -416,7 +434,7 @@
<p>This semantics is extending the semantics of RDF rather than simply reusing it.</p>
<h4 id="f5" class="formal">Formalization</h4>
- <p>A quad-interpretration is a tuple <var>(IR,IP,IEXT,IS,IL,LV)</var> where <var>IR</var>, <var>IP</var>, <var>IS</var>, <var>IL</var> and <var>LV</var> are defined as in RDF and <var>IEXT</var> is a mapping from <var>IP</var> into the powerset of <var>IR × IR union IR × IR × IR</var>.</p>
+ <p>A quad-interpretation is a tuple <var>(IR,IP,IEXT,IS,IL,LV)</var> where <var>IR</var>, <var>IP</var>, <var>IS</var>, <var>IL</var> and <var>LV</var> are defined as in RDF and <var>IEXT</var> is a mapping from <var>IP</var> into the powerset of <var>IR × IR union IR × IR × IR</var>.</p>
<p>Since this option modifies the notion of simple-interpretation, which is the basis for all <var>E</var>-interpretations in any entailment regime E, it is not clear how it can be extended to arbitrary entailment regimes. For instance, does the following quad set:</p>
<pre class="example">:a rdf:type :c :x .
@@ -425,16 +443,16 @@
<pre class="example">:a rdf:type :d :x .</pre>
<h4 id="p5" class="prop">Properties of this dataset semantics</h4>
- <p>With this semantics, all inferences that are valid with normal RDF triples are preserved, but it is necessary to extend RDFS in order to accomodate for ternary relations. There are several existing proposal that extends this quad semantics by dealing with a specific "dimension", such as time, uncertainty, provenance. For instance, temporal RDF [[TEMPORAL-RDF]] use the fourth element to denote a time frame, and reasoning can be performed per time frame. Special semantic rules allow one to combine triples in overlapping time frames. Fuzzy RDF [[FUZZY-RDF]] extends the semantics to deal with uncertainty. stRDF [[ST-RDF]] extends temporal RDF to deal with spatial information. Annotated RDF [[ANNOTATED-RDF]] generalizes the previous proposals.</p>
+ <p>With this semantics, all inferences that are valid with normal RDF triples are preserved, but it is necessary to extend RDFS in order to accommodate for ternary relations. There are several existing proposal that extends this quad semantics by dealing with a specific “dimension”, such as time, uncertainty, provenance. For instance, temporal RDF [[TEMPORAL-RDF]] use the fourth element to denote a time frame, and reasoning can be performed per time frame. Special semantic rules allow one to combine triples in overlapping time frames. Fuzzy RDF [[FUZZY-RDF]] extends the semantics to deal with uncertainty. stRDF [[ST-RDF]] extends temporal RDF to deal with spatial information. Annotated RDF [[ANNOTATED-RDF]] generalizes the previous proposals.</p>
</section>
<section>
<h3 id="quote">Quoted graphs</h3>
- <p>Quoted graphs are a way to associate information to a specific RDF graph without constraining the relationship between a graph name and the graph associated with it in a dataset. An RDF graph is "quoted" by using a literal having a lexical form that is a syntactic expression of the graph. For instance:</p>
+ <p>Quoted graphs are a way to associate information to a specific RDF graph without constraining the relationship between a graph name and the graph associated with it in a dataset. An RDF graph is “quoted” by using a literal having a lexical form that is a syntactic expression of the graph. For instance:</p>
<pre class="example">{ :g :quotes ":a :b []"^^:turtle . }
:g { :b rdf:type rdf:Property .
:a :b _:x . }</pre>
- <p>This technique allows one to assume a dataset semantics of contexts (as in Section 3.4) and still preserve an initial version of a graph. However, quoting big graphs may be combursome and would require a custom datatype to be recognized.</p>
+ <p>This technique allows one to assume a dataset semantics of contexts (as in Section 3.4) and still preserve an initial version of a graph. However, quoting big graphs may be cumbersome and would require a custom datatype to be recognized.</p>
</section>
@@ -456,7 +474,7 @@
GRAPH :g2 { :y rdf:type :d }
}</pre>
<p>would answer <code>false</code>.</p>
- <p>This can lead to a classification of dataset semantics in terms of whether they are compatible with SPARQL ASK queries or not. It can be noted that a semantics where each named graph defines its own context is "SPARQL-ASK-compatible", while a semantics where the graph name denotes the graph or named graph is not compatible in this sense.</p>
+ <p>This can lead to a classification of dataset semantics in terms of whether they are compatible with SPARQL ASK queries or not. It can be noted that a semantics where each named graph defines its own context is “SPARQL-ASK-compatible”, while a semantics where the graph name denotes the graph or named graph is not compatible in this sense.</p>
</section>
</section>
@@ -464,7 +482,7 @@
<h2>Declaring the intended semantics</h2>
<p>The RDF Working Group did not define a formal semantics for a multiple graph data model because none of the semantics presented before could obtained consensus. Choosing one or another of the propositions before would have gone against some deployed implementations. Therefore, the Working Group discussed the possibility to define several semantics, among which an implementation could choose, and provide the means to declare which semantics is adopted.</p>
- <p>This was not retained eventually, because of the lack of experience, and potentially the lack of utility, so there is no definite option for this. Nonetheless, for completeness, we describe here possible solutions.</p>
+ <p>This was not retained eventually, because of the lack of experience, so there is no definite option for this. Nonetheless, for completeness, we describe here possible solutions.</p>
<h3 id="using-vocab">Using vocabularies</h3>
<p>A dataset can be described in RDF using vocabularies like voiD [[VOID]] and the SPARQL service description vocabulary [[SPARQL11-SERVICE-DESCRIPTION]]. VoiD is used to describe how a collection of RDF triples is organized in a web site or across web sites, giving information about the size of the datasets, the location of the dump files, the IRI of the query endpoints, and so on. The notion of dataset in voiD is used as a more informal and broader concept than RDF dataset. However, an RDF dataset and the graphs in it can be describe as voiD datasets and the information can be completed with SPARQL service description</p>
@@ -488,8 +506,10 @@
<section class="appendix informative" id="changes">
<h2>Changes</h2>
<ul>
+ <li>2013-12-12: Added the semantics for Sandro's box dataset.</li>
+ <li>2013-12-04: Addressed Pat’s comments.</li>
<li>2013-09-17: All sections revised and document completed. Many improvements.</li>
- <li>2013-01-28: Initial editor's draft.</li>
+ <li>2013-01-28: Initial editor’s draft.</li>
</ul>
</section>
--- a/rdf-mt/index.html Fri Dec 13 08:05:45 2013 -0500
+++ b/rdf-mt/index.html Fri Dec 13 08:06:03 2013 -0500
@@ -505,18 +505,19 @@
<section><h2 id="datatypes">Literals and datatypes</h2>
<p class="changenote"> In the 2004 RDF 1.0 specification, datatype D-entailment was defined as a <a>semantic extension</a> of RDFS-entailment. Here it is defined as a direct extension to basic RDF. This is more in conformity with actual usage, where RDF with datatypes is widely used without the RDFS vocabulary. If there is a need to distinguish this from the 2004 RDF 1.0 terminology, the longer phrasing "simple D-entailment" or "simple datatype entailment" should be used rather than "D-entailment". </p>
-<p> Datatypes are <a title="identify">identified</a> by IRIs. Interpretations will vary according to which IRIs they recognize as denoting datatypes. We describe this using a parameter D on simple interpretations. where D is the set of <dfn>recognize</dfn><strong>d</strong> datatype IRIs. We assume that a recognized IRI <a title="identify">identifies</a> a unique datatype wherever it occurs, and the semantics requires that it refers to this identified datatype. The exact mechanism by which an IRI <a title="identify">identifies</a> a datatype IRI is considered to be external to the semantics. RDF processors which are not able to determine which datatype is identified by an IRI cannot <a>recognize</a> that IRI, and should treat any literals with that IRI as their datatype IRI as unknown names. </p>
-
-<p class="changenote">In the 2004 RDF 1.0 specification, the semantics of datatypes referred to datatype maps. The current treatment subsumes datatype maps into the interpretation mapping on recognized IRIs.The <dfn>datatype map</dfn> corresponding to D is exactly the restriction of a D-interpretation mapping to the set D of recognized datatypes. The 2004 definitions permitted "non-standard" datatype maps which map IRIs to datatypes they do not <a>identify</a> (such as one that maps the IRI '<code>http://www.w3.org/2001/XMLSchema#decimal</code>' to the datatype identified by <code>http://www.w3.org/2001/XMLSchema#gYearMonth</code> ). Semantic extensions based on such non-standard mappings are not sanctioned by this specification.</p>
+<p> Datatypes are <a title="identify">identified</a> by IRIs. Interpretations will vary according to which IRIs are recognized as denoting datatypes. We describe this using a parameter D on simple interpretations, where D is the set of <dfn>recognize</dfn><em><strong>d</strong></em> datatype IRIs. </p>
-<p>RDF literals and datatypes are fully described in <a href="http://www.w3.org/TR/rdf11-concepts/#section-Datatypes"> Section 5</a> of [[!RDF11-CONCEPTS]]. In summary: RDF literals are either language-tagged strings, or datatyped literals which
-combine a string and an IRI <a>identify</a>ing a datatype. A datatype is understood to define a partial mapping, called the <dfn>lexical-to-value mapping</dfn>, from a lexical space (a set of character strings) to values. The function <dfn>L2V</dfn> maps datatypes to their lexical-to-value mapping. A literal with datatype d denotes the value obtained by applying this mapping to the character string sss: L2V(d)(sss). If the literal string is not in the lexical space, so that the lexical-to-value mapping gives no value for the literal string, then the literal has no referent. The <dfn>value space</dfn> of a datatype is the range of the <a>lexical-to-value mapping</a>. Every literal with that type either refers to a value in the value space of the type, or fails to refer at all. An <dfn>ill-typed</dfn> literal is one whose datatype IRI is <a>recognize</a>d, but whose character string is assigned no value by the <a>lexical-to-value mapping</a> for that datatype. </p>
+<p class="changenote">The previous version of this specification defined the parameter D as a <a>datatype map</a> from IRIs to datatypes, i.e. as a restricted kind of interpretation mapping. As the current semantics presumes that a recognized IRI identifies a unique datatype, this IRI-to-datatype mapping is globally unique and externally specified, so we can think of D as either a set of IRIs or as a fixed <a>datatype map</a>. Formally, the <dfn>datatype map</dfn> corresponding to the set D is the restriction of a <a>D-interpretation</a> to the set D. Semantic extensions which are stated in terms of conditions on <a>datatype map</a>s can be interpreted as applying to this mapping. </p>
-<p> RDF processors are not required to <a>recognize</a> any datatype IRIs other than <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-language-tagged-string"><code>rdf:langString</code></a> and <a href="http://www.w3.org/TR/xmlschema11-2/#string"><code>xsd:string</code></a>, but when IRIs listed in <a href="http://www.w3.org/TR/rdf11-concepts/#section-Datatypes">Section 5</a> of [[!RDF11-CONCEPTS]] are <a>recognize</a>d, they MUST be interpreted as described there, and when the IRI <code>rdf:PlainLiteral</code> is <a>recognize</a>d, it MUST be interpreted to refer to the datatype defined in [[!RDF-PLAIN-LITERAL]]. RDF processors MAY recognize other datatype IRIs, but when other datatype IRIs are <a>recognize</a>d, the mapping between a <a>recognize</a>d IRI and the datatype it refers to MUST be specified unambiguously, and MUST be fixed during all RDF transformations or manipulations.</p>
+<p>The exact mechanism by which an IRI <a title="identify">identifies</a> a datatype IRI is considered to be external to the semantics, but the semantics presumes that a recognized IRI <a title="identify">identifies</a> a unique datatype wherever it occurs. RDF processors which are not able to determine which datatype is identified by an IRI cannot <a>recognize</a> that IRI, and should treat any literals with that IRI as their datatype IRI as unknown names. </p>
+
+<p>RDF literals and datatypes are fully described in <a href="http://www.w3.org/TR/rdf11-concepts/#section-Datatypes"> Section 5</a> of [[!RDF11-CONCEPTS]]. In summary: with one exception, RDF literals combine a string and an IRI <a>identify</a>ing a datatype. The exception is <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-language-tagged-string">language-tagged strings</a>, which have two syntactic components, a string and a language tag, and are assigned the type <code>rdf:langString</code>. A datatype is understood to define a partial mapping, called the <dfn>lexical-to-value mapping</dfn>, from a lexical space (a set of character strings) to values. The function <dfn>L2V</dfn> maps datatypes to their lexical-to-value mapping. A literal with datatype d denotes the value obtained by applying this mapping to the character string sss: L2V(d)(sss). If the literal string is not in the lexical space, so that the lexical-to-value mapping gives no value for the literal string, then the literal has no referent. The <dfn>value space</dfn> of a datatype is the range of the <a>lexical-to-value mapping</a>. Every literal with that type either refers to a value in the value space of the type, or fails to refer at all. An <dfn>ill-typed</dfn> literal is one whose datatype IRI is <a>recognize</a>d, but whose character string is assigned no value by the <a>lexical-to-value mapping</a> for that datatype. </p>
+
+<p> RDF processors are not required to <a>recognize</a> any datatype IRIs other than <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-language-tagged-string"><code>rdf:langString</code></a> and <a href="http://www.w3.org/TR/xmlschema11-2/#string"><code>xsd:string</code></a>, but when IRIs listed in <a href="http://www.w3.org/TR/rdf11-concepts/#section-Datatypes">Section 5</a> of [[!RDF11-CONCEPTS]] are <a>recognize</a>d, they MUST be interpreted as described there, and when the IRI <code>rdf:PlainLiteral</code> is <a>recognize</a>d, it MUST be interpreted to refer to the datatype defined in [[!RDF-PLAIN-LITERAL]]. RDF processors MAY recognize other datatype IRIs, but when other datatype IRIs are <a>recognize</a>d, the mapping between the datatype IRI and the datatype it refers to MUST be specified unambiguously, and MUST be fixed during all RDF transformations or manipulations. In practice, this can be achieved by the IRI linking to an external specification of the datatype which describes both the components of the datatype itself and the fact that the IRI identifies the datatype, thereby fixing a value of the <a>datatype map</a> of this IRI.</p>
<p>Literals with <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-language-tagged-string"><code>rdf:langString</code></a> as their datatype are an exceptional case which are given a special treatment. The IRI <code>rdf:langString</code> is classified as a datatype IRI, and interpreted to refer to a datatype, even though no L2V mapping is defined for it. The value space of <code>rdf:langString</code> is the set of all pairs of a string with a language tag. The semantics of literals with this as their type are given below. </p>
-<p>RDF literal syntax allows any IRI to be used in a typed literal, even when it is not <a>recognize</a>d as referring to a datatype. Literals with such an "unknown" datatype IRI, which is not in the set of <a>recognize</a>d datatypes, SHOULD NOT be treated as errors, although RDF applications MAY issue a warning. Such literals SHOULD be treated like IRIs and assumed to denote some thing in the universe IR. RDF processors which fail to <a>recognize</a> a datatype IRI will not be able to detect some entailments which are visible to one which does. For example, the fact that </p><p><code>ex:a ex:p "20.0000"^^xsd:decimal .</code></p><p>entails </p><p><code>ex:a ex:p "20.0"^^xsd:decimal .</code></p><p>will not be visible to a processor which does not <a>recognize</a> the datatype IRI <code>xsd:decimal</code>.</p>
+<p>RDF literal syntax allows any IRI to be used in a typed literal, even when it is not <a>recognize</a>d as referring to a datatype. Literals with such an "unknown" datatype IRI, which is not in the set of <a>recognize</a>d datatypes, SHOULD NOT be treated as errors, although RDF applications MAY issue a warning. Such literals SHOULD be treated like IRIs and assumed to denote some thing in the universe IR. RDF processors which do not <a>recognize</a> a datatype IRI will not be able to detect some entailments which are visible to one which does. For example, the fact that </p><p><code>ex:a ex:p "20.0000"^^xsd:decimal .</code></p><p>entails </p><p><code>ex:a ex:p "20.0"^^xsd:decimal .</code></p><p>will not be visible to a processor which does not <a>recognize</a> the datatype IRI <code>xsd:decimal</code>.</p>
<section id="D_interpretations"><h2>D-interpretations</h2>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/rdf-new/Overview.html Fri Dec 13 08:06:03 2013 -0500
@@ -0,0 +1,623 @@
+<!DOCTYPE html>
+<html lang="en" typeof="bibo:Document " about="" property="dcterms:language" content="en" prefix="bibo: http://purl.org/ontology/bibo/ w3p: http://www.w3.org/2001/02pd/rec54#" xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta charset="utf-8" />
+ <title>What’s New in RDF 1.1</title>
+
+
+
+
+ <style type="text/css">
+ figure { text-align: center; }
+ table td, table th { border: 1px solid #ddd; padding: 0.2em 0.5em; }
+ </style>
+ <style>/*****************************************************************
+ * ReSpec 3 CSS
+ * Robin Berjon - http://berjon.com/
+ *****************************************************************/
+
+/* --- INLINES --- */
+em.rfc2119 {
+ text-transform: lowercase;
+ font-variant: small-caps;
+ font-style: normal;
+ color: #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+ border: none;
+}
+
+dfn {
+ font-weight: bold;
+}
+
+a.internalDFN {
+ color: inherit;
+ border-bottom: 1px solid #99c;
+ text-decoration: none;
+}
+
+a.externalDFN {
+ color: inherit;
+ border-bottom: 1px dotted #ccc;
+ text-decoration: none;
+}
+
+a.bibref {
+ text-decoration: none;
+}
+
+cite .bibref {
+ font-style: normal;
+}
+
+code {
+ color: #ff4500;
+}
+
+/* --- TOC --- */
+.toc a, .tof a {
+ text-decoration: none;
+}
+
+a .secno, a .figno {
+ color: #000;
+}
+
+ul.tof, ol.tof {
+ list-style: none outside none;
+}
+
+.caption {
+ margin-top: 0.5em;
+ font-style: italic;
+}
+
+/* --- TABLE --- */
+table.simple {
+ border-spacing: 0;
+ border-collapse: collapse;
+ border-bottom: 3px solid #005a9c;
+}
+
+.simple th {
+ background: #005a9c;
+ color: #fff;
+ padding: 3px 5px;
+ text-align: left;
+}
+
+.simple th[scope="row"] {
+ background: inherit;
+ color: inherit;
+ border-top: 1px solid #ddd;
+}
+
+.simple td {
+ padding: 3px 10px;
+ border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+ background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+ margin-top: 0;
+}
+
+.section dd > p:last-child {
+ margin-bottom: 0;
+}
+
+.section dd {
+ margin-bottom: 1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+ margin-bottom: 0;
+}
+</style><style>/* --- ISSUES/NOTES --- */
+div.issue-title, div.note-title {
+ padding-right: 1em;
+ min-width: 7.5em;
+ color: #b9ab2d;
+}
+div.issue-title { color: #e05252; }
+div.note-title { color: #2b2; }
+div.issue-title span, div.note-title span {
+ text-transform: uppercase;
+}
+div.note, div.issue {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+.note > p:first-child, .issue > p:first-child { margin-top: 0 }
+.issue, .note {
+ padding: .5em;
+ border-left-width: .5em;
+ border-left-style: solid;
+}
+div.issue, div.note {
+ padding: 1em 1.2em 0.5em;
+ margin: 1em 0;
+ position: relative;
+ clear: both;
+}
+span.note, span.issue { padding: .1em .5em .15em; }
+
+.issue {
+ border-color: #e05252;
+ background: #fbe9e9;
+}
+.note {
+ border-color: #52e052;
+ background: #e9fbe9;
+}
+
+
+</style><link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/W3C-WD" />
+<!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->
+</head>
+
+<body class="h-entry" role="document" id="respecDocument"><div class="head" role="contentinfo" id="respecHeader">
+ <p>
+
+ <a href="http://www.w3.org/"><img width="72" height="48" alt="W3C" src="https://www.w3.org/Icons/w3c_home" /></a>
+
+ </p>
+ <h1 property="dcterms:title" id="title" class="title p-name">What’s New in RDF 1.1</h1>
+
+ <h2 content="2013-12-16T23:00:00.000Z" datatype="xsd:dateTime" property="dcterms:issued" id="w3c-first-public-working-draft-17-december-2013"><abbr title="World Wide Web Consortium">W3C</abbr> First Public Working Draft <time datetime="2013-12-17" class="dt-published">17 December 2013</time></h2>
+ <dl>
+
+ <dt>This version:</dt>
+ <dd><a href="http://www.w3.org/TR/2013/WD-rdf11-new-20131217/" class="u-url">http://www.w3.org/TR/2013/WD-rdf11-new-20131217/</a></dd>
+ <dt>Latest published version:</dt>
+ <dd><a href="http://www.w3.org/TR/rdf11-new/">http://www.w3.org/TR/rdf11-new/</a></dd>
+
+
+ <dt>Latest editor's draft:</dt>
+ <dd><a href="https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-new/index.html">https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-new/index.html</a></dd>
+
+
+
+
+
+
+ <dt>Editor:</dt>
+ <dd inlist="" rel="bibo:editor" class="p-author h-card vcard"><span typeof="foaf:Person"><a href="http://about.me/david_wood" content="David Wood" property="foaf:name" rel="foaf:homepage" class="u-url url p-name fn">David Wood</a>, <a href="http://3roundstones.com/" class="p-org org h-org h-card" rel="foaf:workplaceHomepage">3 Round Stones Inc.</a></span>
+</dd>
+
+
+
+ </dl>
+
+
+
+
+
+ <p class="copyright">
+ <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
+ 2013
+
+ <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
+ (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
+ <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
+ <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>),
+
+ All Rights Reserved.
+
+ <abbr title="World Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
+ <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
+
+ <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
+
+ rules apply.
+ </p>
+
+
+ <hr />
+</div>
+
+<div class="head" role="contentinfo" id="respecHeader">
+ <section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h2 aria-level="1" role="heading" id="h2_abstract">Abstract</h2>
+
+ <p>The Resource Description Framework (RDF) is a language for
+ representing information about resources in the World Wide
+ Web. This document is intended to provide the reader with a summary
+ of changes to RDF introduced in RDF version 1.1.
+ </p>
+ </section><section class="introductory" id="sotd" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h2 aria-level="1" role="heading" id="h2_sotd">Status of This Document</h2>
+
+
+
+ <p>
+ <em>This section describes the status of this document at the time of its publication.
+ Other documents may supersede this document. A list of current <abbr title="World Wide Web Consortium">W3C</abbr> publications and the
+ latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports index</a> at
+ http://www.w3.org/TR/.</em>
+ </p>
+
+ <p>The RDF Working Group expects this document to become a Working
+ Group Note. </p>
+
+ <p>
+ This document was published by the <a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a> as a First Public Working Draft.
+
+
+ If you wish to make comments regarding this document, please send them to
+ <a href="mailto:public-rdf-comments@w3.org">public-rdf-comments@w3.org</a>
+ (<a href="mailto:public-rdf-comments-request@w3.org?subject=subscribe">subscribe</a>,
+ <a href="http://lists.w3.org/Archives/Public/public-rdf-comments/">archives</a>).
+
+
+
+
+ All comments are welcome.
+
+ </p>
+
+
+ <p>
+ Publication as a First Public Working Draft does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr>
+ Membership. This is a draft document and may be updated, replaced or obsoleted by other
+ documents at any time. It is inappropriate to cite this document as other than work in
+ progress.
+ </p>
+
+
+ <p>
+
+ This document was produced by a group operating under the
+ <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/" rel="w3p:patentRules" about="" id="sotd_patent">5 February 2004 <abbr title="World Wide Web Consortium">W3C</abbr> Patent
+ Policy</a>.
+
+
+ The group does not expect this document to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation.
+
+
+
+ <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/46168/status">public list of any patent
+ disclosures</a>
+
+ made in connection with the deliverables of the group; that page also includes
+ instructions for disclosing a patent. An individual who has actual knowledge of a patent
+ which the individual believes contains
+ <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
+ Claim(s)</a> must disclose the information in accordance with
+ <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
+ 6 of the <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+
+
+ </p>
+
+
+
+
+</section><section id="toc"><h2 class="introductory" aria-level="1" role="heading" id="h2_toc">Table of Contents</h2><ul class="toc" role="directory" id="respecContents"><li class="tocline"><a href="#section-introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#section-abstract-syntax" class="tocxref"><span class="secno">2. </span>Abstract Syntax</a><ul class="toc"><li class="tocline"><a href="#identifiers" class="tocxref"><span class="secno">2.1 </span>Identifiers</a></li><li class="tocline"><a href="#literals" class="tocxref"><span class="secno">2.2 </span>Literals</a></li><li class="tocline"><a href="#datasets" class="tocxref"><span class="secno">2.3 </span>Datasets</a></li><li class="tocline"><a href="#datatypes" class="tocxref"><span class="secno">2.4 </span>Datatypes</a></li></ul></li><li class="tocline"><a href="#section-serializations" class="tocxref"><span class="secno">3. </span>New Serialization Formats</a></li><li class="tocline"><a href="#section-semantics" class="tocxref"><span class="secno">4. </span>Semantics</a></li><li class="tocline"><a href="#section-Acknowledgments" class="tocxref"><span class="secno">A. </span>Acknowledgments</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></section>
+
+
+
+</div>
+
+<section id="section-introduction" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
+
+<!--OddPage-->
+<h2 aria-level="1" role="heading" id="h2_section-introduction"><span class="secno">1. </span>Introduction</h2>
+
+ <p>This document is informative in nature. Its
+ purpose is to provide a summary of differences between RDF versions 1.0
+ and 1.1 and to introduce new additions in a very brief manner.
+ </p>
+
+ <p>Readers new to RDF should start with the RDF 1.1 Primer
+ [<cite><a class="bibref" href="#bib-RDF11-PRIMER">RDF11-PRIMER</a></cite>] and then move on to the specifications in which they are
+ most interested. This document is meant to serve as a guide for those
+ already familiar with RDF 1.0 who wish to understand changes in version
+ 1.1.</p>
+
+ <p>Normative specifications of RDF can be found in the
+ following documents: </p>
+ <ul>
+ <li>A document describing the basic concepts underlying RDF, as
+ well as abstract syntax ("RDF Concepts and Abstract Syntax")
+ [<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>]</li>
+ <li>A document describing the formal model-theoretic semantics
+ of RDF ("RDF Semantics") [<cite><a class="bibref" href="#bib-RDF11-MT">RDF11-MT</a></cite>]</li>
+ <li>Specifications of concrete syntaxes for RDF, such as Turtle
+ [<cite><a class="bibref" href="#bib-TURTLE">TURTLE</a></cite>], TriG [<cite><a class="bibref" href="#bib-TRIG">TRIG</a></cite>], N-Triples [<cite><a class="bibref" href="#bib-N-TRIPLES">N-TRIPLES</a></cite>],
+ N-Quads [<cite><a class="bibref" href="#bib-N-QUADS">N-QUADS</a></cite>] and JSON-LD [<cite><a class="bibref" href="#bib-JSON-LD">JSON-LD</a></cite>]. RDFa [<cite><a class="bibref" href="#bib-RDFA-PRIMER">RDFA-PRIMER</a></cite>]
+ is also a concrete syntax for RDF, but it was not defined
+ by the RDF Working Group.</li>
+ <li>An RDF Vocabulary Description Language, RDF Schema
+ [<cite><a class="bibref" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>]</li>
+ </ul>
+
+ <p>The following prefixes are used in this document:</p>
+
+ <table class="simple">
+ <caption>Prefixes and IRIs</caption>
+ <tbody><tr><th>Namespace prefix</th><th>Namespace IRI</th><th>RDF vocabulary</th></tr>
+ <tr><td>rdf</td><td><a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code></a></td><td>The RDF built-in vocabulary [<cite><a class="bibref" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>]</td></tr>
+ <tr><td>xsd</td><td><a href="http://www.w3.org/2001/XMLSchema#"><code>http://www.w3.org/2001/XMLSchema#</code></a></td><td>The
+ RDF-compatible XML Schema datatypes</td></tr>
+ </tbody></table>
+
+</section>
+
+<section id="section-abstract-syntax" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
+
+<!--OddPage-->
+<h2 aria-level="1" role="heading" id="h2_section-abstract-syntax"><span class="secno">2. </span>Abstract Syntax</h2>
+
+ <section id="identifiers" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
+ <h3 aria-level="2" role="heading" id="h3_identifiers"><span class="secno">2.1 </span>Identifiers</h3>
+
+ <p>Identifiers in RDF 1.1 are now IRIs. The following table summarizes specific differences.</p>
+
+ <table class="simple">
+ <caption>Identifiers in RDF 1.0 and 1.1.</caption>
+ <tbody><tr>
+ <th></th>
+ <th>RDF 1.0</th>
+ <th>RDF 1.1</th>
+ </tr>
+ <tr>
+ <td>
+ Identifiers
+ </td>
+ <td>
+ RDF URI References
+ </td>
+ <td>
+ IRIs
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Additional characters
+ </td>
+ <td>
+ "<", ">",
+ "{", "}", "|", "\", "^",
+ "`", ‘"’ (double quote), and " " (space)
+ </td>
+ <td>
+ None; percent-encoding must be used as described in section 2.1 of [<cite><a class="bibref" href="#bib-RFC3986">RFC3986</a></cite>].
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Fragment identifiers
+ </td>
+ <td>
+ Fragment identifiers interpreted in accordance with RDF/XML representation.
+ </td>
+ <td>
+ Full IRIs, including possible fragment identifiers, denote a resource.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Blank nodes
+ </td>
+ <td>
+ RDF 1.0 makes no reference to any internal structure of blank nodes. Given two
+ blank nodes, it is possible to determine whether or not they are the same.
+ </td>
+ <td>
+ Blank node identifiers are local identifiers that are used in some concrete
+ RDF syntaxes or RDF store implementations. They are always locally scoped to
+ the file or RDF store, and are not persistent or portable identifiers for
+ blank nodes. See the section in Concepts and Abstract Syntax regarding
+ Skolemization if blank nodes must be shared between implementations.
+ </td>
+ </tr>
+ </tbody></table>
+
+ </section>
+
+ <section id="literals" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
+ <h3 aria-level="2" role="heading" id="h3_literals"><span class="secno">2.2 </span>Literals</h3>
+
+ <p>The following table summarizes differences in the handling of literals.</p>
+
+ <table class="simple">
+ <caption>Literals in RDF 1.0 and 1.1.</caption>
+ <tbody><tr>
+ <th></th>
+ <th>RDF 1.0</th>
+ <th>RDF 1.1</th>
+ </tr>
+ <tr>
+ <td>
+ Language tags
+ </td>
+ <td>
+ Literals with a language tag did not have a datatype URI.
+ </td>
+ <td>
+ Literals with language tags now have the datatype IRI <code>rdf:langString</code>.
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="2">
+ Simple literals
+ </td>
+ <td>
+ Simple literals could appear directly, e.g. "a literal".
+ </td>
+ <td>
+ Literals all have datatypes; serializations or other implementations
+ might choose to support syntax for simple literals, but only as synonyms
+ for <code>xsd:string</code> literals.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Control codes in the #x0-#x1F range were permitted.
+ </td>
+ <td>
+ The <code>xsd:string</code> datatype does not permit the #x0 character, and implementations
+ might not permit control codes in the #x1-#x1F range. A literal with type
+ <code>xsd:string</code> containing the #x0 character is ill-typed.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Language tags
+ </td>
+ <td>
+ Permitted language tags that adhered to the generic tag/subtag syntax
+ of language tags, but were not well-formed according to [<cite><a class="bibref" href="#bib-BCP47">BCP47</a></cite>].
+ </td>
+ <td>
+ Language tags must be well-formed according to [<cite><a class="bibref" href="#bib-BCP47">BCP47</a></cite>].
+ </td>
+ </tr>
+ </tbody></table>
+
+ <p>Planned updates to DOM version 4 [<cite><a class="bibref" href="#bib-DOM4">DOM4</a></cite>] are not complete as of this writing. The Working
+ Group decided to follow the changes to the DOM in order to support the new datatype <code>rdf:HTML</code>.
+ The unfinished status of DOM version 4 is why both <code>rdf:HTML</code> and <code>rdf:XMLLiteral</code> are non-normative
+ in RDF 1.1 Concepts. RDF 1.1 Concepts and Abstract Syntax clarifies functionality deemed to be
+ useful for those including fragments of XML and HTML content in RDF serialization formats.</p>
+
+ </section>
+
+ <section id="datasets" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
+ <h3 aria-level="2" role="heading" id="h3_datasets"><span class="secno">2.3 </span>Datasets</h3>
+
+ <p>RDF 1.1 introduces the concept of RDF Datasets. An RDF Dataset is a collection of RDF
+ Graphs. The semantics of RDF Datasets are minimally specified as of RDF 1.1.</p>
+
+ <p>RDF Graphs may be named using an IRI or a blank node. RDF Graphs that are so named are
+ called named graphs.</p>
+
+ <p>RDF 1.1 includes three new serialization formats capable of representing multiple graphs.</p>
+
+ </section>
+
+ <section id="datatypes" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
+ <h3 aria-level="2" role="heading" id="h3_datatypes"><span class="secno">2.4 </span>Datatypes</h3>
+
+ <p>A table of RDF-compatible XSD datatypes has been added to RDF 1.1 Concepts and
+ Abstract Syntax. Any XSD datatypes not represented in this table are incompatible
+ with RDF. The following XSD 1.1 datatypes were added to the list of
+ RDF-compatible datatypes:</p>
+
+ <ul>
+ <li><code>xsd:duration</code></li>
+ <li><code>xsd:dayTimeDuration</code></li>
+ <li><code>xsd:yearMonthDuration</code></li>
+ <li><code>xsd:dateTimeStamp</code></li>
+ </ul>
+
+ <p>Support for <code>rdf:XMLLiteral</code> support is now optional. Technically, support for
+ any individual datatype is optional and therefore may not be present in a given
+ implementation. RDF-conformant specifications may require specific datatype maps.</p>
+
+ </section>
+
+</section>
+
+<section id="section-serializations" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
+
+<!--OddPage-->
+<h2 aria-level="1" role="heading" id="h2_section-serializations"><span class="secno">3. </span>New Serialization Formats</h2>
+
+ <p>RDF 1.1 introduces a number of new serialization formats. RDF 1.1 Concepts and
+ Abstract Syntax makes it clear that RDF/XML is no longer the only recommended serialization
+ format; RDF itself should be considered to be the data model (the abstract syntax), not any
+ particular serialization.</p>
+
+ <figure id="fig-rdf-1.0-and-1.1-serialization-formats">
+ <img width="717" height="370" src="serialization-formats.png" />
+ <figcaption>Fig. <span class="figno">1</span> <span class="fig-title">RDF 1.0 and 1.1 serialization formats</span></figcaption>
+ </figure>
+
+</section>
+
+<section id="section-semantics" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
+
+<!--OddPage-->
+<h2 aria-level="1" role="heading" id="h2_section-semantics"><span class="secno">4. </span>Semantics</h2>
+
+ <p>Most of the changes between RDF and RDF 1.1 do not have any effect on
+ implementations of entailment.</p>
+
+ <p>Datatype entailment formally refers to a set of 'recognized' datatypes,
+ replacing datatype maps in RDF 1.0 Semantics, but this does not have any
+ effect on implementation.</p>
+
+ <p>Datatype entailment formally refers to a set of 'recognized' datatype IRIs.
+ The RDF 1.0 Semantics used the concept of a datatype map: in the new semantic
+ description, this is the mapping from recognized IRIs to the datatypes they
+ identify. This change does not have any effect on implementation or semantic
+ entailments.</p>
+
+ <p>RDF entailment has two required datatypes <code>xsd:string</code> and <code>rdf:langString</code>
+ which must be recognized, but this doesn't appreciably add to RDF
+ entailment as these two datatypes replace plain literals.</p>
+
+ <p>One change that does affect entailment is that graphs containing invalid
+ literals (e.g., <code>"a"^^xsd:integer</code>) are immediately inconsistent for
+ recognized datatypes, even in sub-RDFS entailment regimes.</p>
+
+ <p>RDF 1.1 includes RDF Datasets. However, the semantics of RDF Datasets in
+ RDF 1.1 is minimal and entailment per se is only defined on RDF graphs so
+ there are no changes here.</p>
+
+</section>
+
+<section class="appendix" id="section-Acknowledgments" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
+
+<!--OddPage-->
+<h2 aria-level="1" role="heading" id="h2_section-Acknowledgments"><span class="secno">A. </span>Acknowledgments</h2>
+
+ <div class="issue"><div class="issue-title" aria-level="2" role="heading" id="h_issue_1"><span>Issue 1</span></div><p class="">This section does not yet list all those who
+ contributed to this document. It should certainly include reviewers
+ and perhaps current RDF WG members.</p></div>
+
+ <p>The editor gratefully acknowledges the members of the RDF Working
+ Group who contributed to this document, including Richard Cyganiak,
+ Gavin Garothers, Pat Hayes, Sandro Hawke, Gregg Kellogg, Markus
+ Lanthaler, Peter Patel-Schneider, Eric Prud-hommeaux, Guus Schreiber
+ and Manu Sporny.
+
+</p></section>
+
+
+<section id="references" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"></section>
+
+
+
+<section class="appendix" id="references" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<!--OddPage-->
+<h2 aria-level="1" role="heading" id="h2_references"><span class="secno">B. </span>References</h2><section id="normative-references" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h3 aria-level="2" role="heading" id="h3_normative-references"><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-BCP47">[BCP47]</dt><dd rel="dcterms:requires">A. Phillips; M. Davis. <a href="http://tools.ietf.org/html/bcp47"><cite>Tags for Identifying Languages</cite></a>. September 2009. IETF Best Current Practice. URL: <a href="http://tools.ietf.org/html/bcp47">http://tools.ietf.org/html/bcp47</a>
+</dd><dt id="bib-DOM4">[DOM4]</dt><dd rel="dcterms:requires">Anne van Kesteren; Aryeh Gregor; Ms2ger; Alex Russell; Robin Berjon. <a href="http://www.w3.org/TR/dom/"><cite>W3C DOM4</cite></a>. 7 November 2013. W3C Working Draft. URL: <a href="http://www.w3.org/TR/dom/">http://www.w3.org/TR/dom/</a>
+</dd><dt id="bib-JSON-LD">[JSON-LD]</dt><dd rel="dcterms:requires">Manu Sporny, Gregg Kellogg, Markus Lanthaler, Editors. <cite><a href="http://www.w3.org/TR/2013/PR-json-ld-20131105/">JSON-LD 1.0</a>.</cite> 5 November 2013. W3C Proposed Recommendation. URL: <a href="http://www.w3.org/TR/2013/PR-json-ld-20131105/">http://www.w3.org/TR/2013/PR-json-ld-20131105/</a>. The latest edition is available at <a href="http://www.w3.org/TR/json-ld/">http://www.w3.org/TR/json-ld/</a>
+</dd><dt id="bib-N-QUADS">[N-QUADS]</dt><dd rel="dcterms:requires">Gavin Carothers, Editor. <cite><a href="http://www.w3.org/TR/2013/CR-n-quads-20131105/">RDF 1.1 N-Quads</a></cite>. 5 November 2013. W3C Candidate Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2013/CR-n-quads-20131105/">http://www.w3.org/TR/2013/CR-n-quads-20131105/</a>. The latest edition is available at <a href="http://www.w3.org/TR/n-quads/">http://www.w3.org/TR/n-quads/</a>
+</dd><dt id="bib-N-TRIPLES">[N-TRIPLES]</dt><dd rel="dcterms:requires">Gavin Carothers, Editor. <cite><a href="http://www.w3.org/TR/2013/CR-n-triples-20131105/">RDF 1.1 N-Triples</a></cite>. 5 November 2013. W3C Candidate Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2013/CR-n-triples-20131105/">http://www.w3.org/TR/2013/CR-n-triples-20131105/</a>. The latest edition is available at <a href="http://www.w3.org/TR/n-triples/">http://www.w3.org/TR/n-triples/</a>
+</dd><dt id="bib-RDF-SCHEMA">[RDF-SCHEMA]</dt><dd rel="dcterms:requires">Dan Brickley; Ramanathan Guha. <a href="http://www.w3.org/TR/rdf-schema"><cite>RDF Vocabulary Description Language 1.0: RDF Schema</cite></a>. 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/rdf-schema">http://www.w3.org/TR/rdf-schema</a>
+</dd><dt id="bib-RDF11-CONCEPTS">[RDF11-CONCEPTS]</dt><dd rel="dcterms:requires">Richard Cyganiak, David Wood, Markus Lanthaler, Editors. <cite><a href="http://www.w3.org/TR/2013/CR-rdf11-concepts-20131105/">RDF 1.1 Concepts and Abstract Syntax.</a></cite> 5 November 2013. W3C Candidate Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2013/CR-rdf11-concepts-20131105/">http://www.w3.org/TR/2013/CR-rdf11-concepts-20131105/</a>. The latest edition is available at <a href="http://www.w3.org/TR/rdf11-concepts/">http://www.w3.org/TR/rdf11-concepts/</a>
+</dd><dt id="bib-RDF11-MT">[RDF11-MT]</dt><dd rel="dcterms:requires">Patrick J. Hayes, Peter F. Patel-Schneider, Editors. <cite><a href="http://www.w3.org/TR/2013/CR-rdf11-mt-20131105/">RDF 1.1 Semantics.</a></cite> 5 November 2013. W3C Candidate Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2013/CR-rdf11-mt-20131105/">http://www.w3.org/TR/2013/CR-rdf11-mt-20131105/</a>. The latest edition is available at <a href="http://www.w3.org/TR/rdf11-mt/">http://www.w3.org/TR/rdf11-mt/</a>
+</dd><dt id="bib-RDFA-PRIMER">[RDFA-PRIMER]</dt><dd rel="dcterms:requires">Ivan Herman; Ben Adida; Manu Sporny; Mark Birbeck. <a href="http://www.w3.org/TR/rdfa-primer/"><cite>RDFa 1.1 Primer - Second Edition</cite></a>. 22 August 2013. W3C Note. URL: <a href="http://www.w3.org/TR/rdfa-primer/">http://www.w3.org/TR/rdfa-primer/</a>
+</dd><dt id="bib-RFC3986">[RFC3986]</dt><dd rel="dcterms:requires">T. Berners-Lee; R. Fielding; L. Masinter. <a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifier (URI): Generic Syntax (RFC 3986)</cite></a>. January 2005. RFC. URL: <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>
+</dd><dt id="bib-TRIG">[TRIG]</dt><dd rel="dcterms:requires">Gavin Carothers, Andy Seaborne, Editors. <cite><a href="http://www.w3.org/TR/2013/WD-trig-20130919/">TriG: RDF Dataset Language</a></cite>. 19 September 2013. W3C Candidate Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2013/WD-trig-20130919/">http://www.w3.org/TR/2013/WD-trig-20130919/</a>. The latest edition is available at <a href="http://www.w3.org/TR/trig/">http://www.w3.org/TR/trig/</a>
+</dd><dt id="bib-TURTLE">[TURTLE]</dt><dd rel="dcterms:requires">Eric Prud'hommeaux, Gavin Carothers, Editors. <cite><a href="http://www.w3.org/TR/2013/CR-turtle-20130219/">RDF 1.1 Turtle: Terse RDF Triple Language.</a></cite> 19 February 2013. W3C Candidate Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2013/CR-turtle-20130219/">http://www.w3.org/TR/2013/CR-turtle-20130219/</a>. The latest edition is available at <a href="http://www.w3.org/TR/turtle/">http://www.w3.org/TR/turtle/</a>
+</dd></dl></section><section id="informative-references" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h3 aria-level="2" role="heading" id="h3_informative-references"><span class="secno">B.2 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-RDF11-PRIMER">[RDF11-PRIMER]</dt><dd rel="dcterms:references">Guus Schreiber, Yves Raimond. <cite><a href="https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-primer/index.html">RDF 1.1 Primer</a></cite>. 2013. The latest version is available at <a href="http://www.w3.org/TR/rdf11-primer/">http://www.w3.org/TR/rdf11-primer/</a>.
+</dd></dl></section></section></body></html>
\ No newline at end of file
--- a/rdf-new/index.html Fri Dec 13 08:05:45 2013 -0500
+++ b/rdf-new/index.html Fri Dec 13 08:06:03 2013 -0500
@@ -12,6 +12,7 @@
// specification status (e.g. WD, LC, WG-NOTE, etc.). If in doubt use ED.
specStatus: "FPWD",
+ noRecTrack: true,
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "rdf11-new",
@@ -21,7 +22,7 @@
// subtitle : "an excellent document",
// if you wish the publication date to be other than today, set this
- // publishDate: "<li>2013-11-05",
+ publishDate: "2013-12-17",
// if the specification's copyright date is a range of years, specify
@@ -106,7 +107,8 @@
</section>
<section id="sotd">
-
+ <p>The RDF Working Group expects this document to become a Working
+ Group Note. </p>
</section>
</div>
@@ -149,7 +151,9 @@
<caption>Prefixes and IRIs</caption>
<tr><th>Namespace prefix</th><th>Namespace IRI</th><th>RDF vocabulary</th></tr>
<tr><td>rdf</td><td><a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code></a></td><td>The RDF built-in vocabulary [[RDF-SCHEMA]]</td></tr>
- <tr><td>xsd</td><td><a href="http://www.w3.org/2001/XMLSchema#"><code>http://www.w3.org/2001/XMLSchema#</code></a></td><td>The <a>RDF-compatible XSD types</a></td></tr>
+ <tr><td>xsd</td><td><a
+ href="http://www.w3.org/2001/XMLSchema#"><code>http://www.w3.org/2001/XMLSchema#</code></a></td><td>The
+ RDF-compatible XML Schema datatypes</td></tr>
</table>
</section>
--- a/rdf-schema/Overview.html Fri Dec 13 08:05:45 2013 -0500
+++ b/rdf-schema/Overview.html Fri Dec 13 08:06:03 2013 -0500
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en" typeof="bibo:Document w3p:PER" about="" property="dcterms:language" content="en" prefix="bibo: http://purl.org/ontology/bibo/ w3p: http://www.w3.org/2001/02pd/rec54#" xmlns="http://www.w3.org/1999/xhtml">
<head>
- <meta charset="utf-8" />
+ <meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>RDF Schema 1.1</title>
@@ -119,6 +119,38 @@
.section dl.attrs dd, .section dl.eldef dd {
margin-bottom: 0;
}
+</style><style>/* --- EXAMPLES --- */
+div.example-title {
+ min-width: 7.5em;
+ color: #b9ab2d;
+}
+div.example-title span {
+ text-transform: uppercase;
+}
+aside.example, div.example, div.illegal-example {
+ padding: 0.5em;
+ margin: 1em 0;
+ position: relative;
+ clear: both;
+}
+div.illegal-example { color: red }
+div.illegal-example p { color: black }
+aside.example, div.example {
+ padding: .5em;
+ border-left-width: .5em;
+ border-left-style: solid;
+ border-color: #e0cb52;
+ background: #fcfaee;
+}
+
+aside.example div.example {
+ border-left-width: .1em;
+ border-color: #999;
+ background: #fff;
+}
+aside.example div.example div.example-title {
+ color: #999;
+}
</style><style>/* --- ISSUES/NOTES --- */
div.issue-title, div.note-title {
padding-right: 1em;
@@ -161,8 +193,7 @@
</style><link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/W3C-PER" />
<!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->
</head>
-
-<body class="h-entry" role="document" id="respecDocument"><div class="head" role="contentinfo" id="respecHeader">
+ <body class="h-entry" role="document" id="respecDocument"><div class="head" role="contentinfo" id="respecHeader">
<p>
<a href="http://www.w3.org/"><img width="72" height="48" alt="W3C" src="https://www.w3.org/Icons/w3c_home" /></a>
@@ -170,11 +201,11 @@
</p>
<h1 property="dcterms:title" id="title" class="title p-name">RDF Schema 1.1</h1>
- <h2 content="2013-12-03T13:23:18.000Z" datatype="xsd:dateTime" property="dcterms:issued" id="w3c-proposed-edited-recommendation-03-december-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Proposed Edited Recommendation <time datetime="2013-12-03" class="dt-published">03 December 2013</time></h2>
+ <h2 content="2014-01-08T23:00:00.000Z" datatype="xsd:dateTime" property="dcterms:issued" id="w3c-proposed-edited-recommendation-09-january-2014"><abbr title="World Wide Web Consortium">W3C</abbr> Proposed Edited Recommendation <time datetime="2014-01-09" class="dt-published">09 January 2014</time></h2>
<dl>
<dt>This version:</dt>
- <dd><a href="http://www.w3.org/TR/2013/PER-rdf-schema-20131203/" class="u-url">http://www.w3.org/TR/2013/PER-rdf-schema-20131203/</a></dd>
+ <dd><a href="http://www.w3.org/TR/2014/PER-rdf-schema-20140109/" class="u-url">http://www.w3.org/TR/2014/PER-rdf-schema-20140109/</a></dd>
<dt>Latest published version:</dt>
<dd><a href="http://www.w3.org/TR/rdf-schema/">http://www.w3.org/TR/rdf-schema/</a></dd>
@@ -222,7 +253,7 @@
This document is also available in this non-normative format:
- <a href="diff.html" rel="alternate">diff w.r.t. previous recommendation</a>
+ <a href="diff.html" rel="alternate">diff w.r.t. 2004 Recommendation</a>
</p>
@@ -230,7 +261,7 @@
<p class="copyright">
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
- 2004-2013
+ 2004-2014
<a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
(<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
@@ -250,17 +281,13 @@
<hr />
</div>
-
-<div class="head" role="contentinfo">
-
- <section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h2 aria-level="1" role="heading" id="h2_abstract">Abstract</h2>
-
- <p>The Resource Description Framework (RDF) is a language for
- representing information about resources in the World Wide
- Web. RDF Schema provides a data-mdelling vocabulary for RDF data. RDF
- Schema is an extesnion of the basic RDF vocabulary. </p>
-
- </section><section class="introductory" id="sotd" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h2 aria-level="1" role="heading" id="h2_sotd">Status of This Document</h2>
+ <div class="head" role="contentinfo" id="respecHeader">
+ <section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h2 aria-level="1" role="heading" id="h2_abstract">Abstract</h2>
+ <p>The Resource Description Framework (RDF) is a language for
+ representing information about resources in the World Wide Web. RDF
+ Schema provides a data-modelling vocabulary for RDF data. RDF Schema
+ is an extension of the basic RDF vocabulary. </p>
+ </section><section class="introductory" id="sotd" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h2 aria-level="1" role="heading" id="h2_sotd">Status of This Document</h2>
@@ -270,20 +297,14 @@
latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports index</a> at
http://www.w3.org/TR/.</em>
</p>
-
-
- This document is an edited version of the 2004 RDF Schema
- Recommendation. The purpose of this revision is to
- make this document available as part of the RDF 1.1 document
- set. Changes are limited to revised references, terminology
- updates, and adaptations to the introduction. The tile of the
- document was changed from "RDF Vocabulary Description Language 1.0:
- RDF Schema" to
- "RDF Schema 1.1". The technical content
- of the document is unchanged. Details of the chnages
- are listed in the <a href="#PER-changes">Changes</a> section.
-
-
+ This document is an edited version of the 2004 RDF
+ Schema Recommendation. The purpose of this revision is to make this
+ document available as part of the RDF 1.1 document set. Changes are
+ limited to revised references, terminology updates, and adaptations to
+ the introduction. The title of the document was changed from "RDF
+ Vocabulary Description Language 1.0: RDF Schema" to "RDF Schema 1.1".
+ The technical content of the document is unchanged. Details of the changes
+ are listed in the <a href="#PER-changes">Changes</a> section.
<p>
This document was published by the <a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a> as a Proposed Edited Recommendation.
@@ -337,1471 +358,1264 @@
-</section><section id="toc"><h2 class="introductory" aria-level="1" role="heading" id="h2_toc">Table of Contents</h2><ul class="toc" role="directory" id="respecContents"><li class="tocline"><a href="#ch_introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#ch_classes" class="tocxref"><span class="secno">2. </span>Classes</a><ul class="toc"><li class="tocline"><a href="#ch_resource" class="tocxref"><span class="secno">2.1 </span>rdfs:Resource</a></li><li class="tocline"><a href="#ch_class" class="tocxref"><span class="secno">2.2 </span>rdfs:Class</a></li><li class="tocline"><a href="#ch_literal" class="tocxref"><span class="secno">2.3 </span>rdfs:Literal</a></li><li class="tocline"><a href="#ch_datatype" class="tocxref"><span class="secno">2.4 </span>rdfs:Datatype</a></li><li class="tocline"><a href="#ch_langString" class="tocxref"><span class="secno">2.5 </span>rdf:langString</a></li><li class="tocline"><a href="#ch_html" class="tocxref"><span class="secno">2.6 </span>rdf:HTML</a></li><li class="tocline"><a href="#ch_xmlliteral" class="tocxref"><span class="secno">2.7 </span>rdf:XMLLiteral</a></li><li class="tocline"><a href="#ch_property" class="tocxref"><span class="secno">2.8 </span>rdf:Property</a></li></ul></li><li class="tocline"><a href="#ch_properties" class="tocxref"><span class="secno">3. </span>Properties</a><ul class="toc"><li class="tocline"><a href="#ch_range" class="tocxref"><span class="secno">3.1 </span>rdfs:range</a></li><li class="tocline"><a href="#ch_domain" class="tocxref"><span class="secno">3.2 </span>rdfs:domain</a></li><li class="tocline"><a href="#ch_type" class="tocxref"><span class="secno">3.3 </span>rdf:type</a></li><li class="tocline"><a href="#ch_subclassof" class="tocxref"><span class="secno">3.4 </span>rdfs:subClassOf</a></li><li class="tocline"><a href="#ch_subpropertyof" class="tocxref"><span class="secno">3.5 </span>rdfs:subPropertyOf</a></li><li class="tocline"><a href="#ch_label" class="tocxref"><span class="secno">3.6 </span>rdfs:label</a></li><li class="tocline"><a href="#ch_comment" class="tocxref"><span class="secno">3.7 </span>rdfs:comment</a></li></ul></li><li class="tocline"><a href="#ch_domainrange" class="tocxref"><span class="secno">4. </span>Using the Domain and Range vocabulary</a></li><li class="tocline"><a href="#ch_othervocab" class="tocxref"><span class="secno">5. </span>Other vocabulary</a><ul class="toc"><li class="tocline"><a href="#ch_containervocab" class="tocxref"><span class="secno">5.1 </span>Container Classes and Properties</a><ul class="toc"><li class="tocline"><a href="#ch_container" class="tocxref"><span class="secno">5.1.1 </span>rdfs:Container</a></li><li class="tocline"><a href="#ch_bag" class="tocxref"><span class="secno">5.1.2 </span>rdf:Bag</a></li><li class="tocline"><a href="#ch_seq" class="tocxref"><span class="secno">5.1.3 </span>rdf:Seq</a></li><li class="tocline"><a href="#ch_alt" class="tocxref"><span class="secno">5.1.4 </span>rdf:Alt</a></li><li class="tocline"><a href="#ch_containermembershipproperty" class="tocxref"><span class="secno">5.1.5 </span>rdfs:ContainerMembershipProperty</a></li><li class="tocline"><a href="#ch_member" class="tocxref"><span class="secno">5.1.6 </span>rdfs:member</a></li></ul></li><li class="tocline"><a href="#ch_collectionvocab" class="tocxref"><span class="secno">5.2 </span>RDF Collections</a><ul class="toc"><li class="tocline"><a href="#ch_list" class="tocxref"><span class="secno">5.2.1 </span>rdf:List</a></li><li class="tocline"><a href="#ch_first" class="tocxref"><span class="secno">5.2.2 </span>rdf:first</a></li><li class="tocline"><a href="#ch_rest" class="tocxref"><span class="secno">5.2.3 </span>rdf:rest</a></li><li class="tocline"><a href="#ch_nil" class="tocxref"><span class="secno">5.2.4 </span>rdf:nil</a></li></ul></li><li class="tocline"><a href="#ch_reificationvocab" class="tocxref"><span class="secno">5.3 </span>Reification Vocabulary</a><ul class="toc"><li class="tocline"><a href="#ch_statement" class="tocxref"><span class="secno">5.3.1 </span>rdf:Statement</a></li><li class="tocline"><a href="#ch_subject" class="tocxref"><span class="secno">5.3.2 </span>rdf:subject</a></li><li class="tocline"><a href="#ch_predicate" class="tocxref"><span class="secno">5.3.3 </span>rdf:predicate</a></li><li class="tocline"><a href="#ch_object" class="tocxref"><span class="secno">5.3.4 </span>rdf:object</a></li></ul></li><li class="tocline"><a href="#ch_utilvocab" class="tocxref"><span class="secno">5.4 </span>Utility Properties</a><ul class="toc"><li class="tocline"><a href="#ch_seealso" class="tocxref"><span class="secno">5.4.1 </span>rdfs:seeAlso</a></li><li class="tocline"><a href="#ch_isdefinedby" class="tocxref"><span class="secno">5.4.2 </span>rdfs:isDefinedBy</a></li><li class="tocline"><a href="#ch_value" class="tocxref"><span class="secno">5.4.3 </span>rdf:value</a></li></ul></li></ul></li><li class="tocline"><a href="#ch_summary" class="tocxref"><span class="secno">6. </span>RDF Schema summary</a><ul class="toc"><li class="tocline"><a href="#ch_sumclasses" class="tocxref"><span class="secno">6.1 </span>RDF classes</a></li><li class="tocline"><a href="#ch_sumproperties" class="tocxref"><span class="secno">6.2 </span>RDF properties</a></li></ul></li><li class="tocline"><a href="#ch_acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgments</a></li><li class="tocline"><a href="#changes" class="tocxref"><span class="secno">B. </span>Change history</a><ul class="toc"><li class="tocline"><a href="#PER-changes" class="tocxref"><span class="secno">B.1 </span>Changes for Proposed Edited Recommendation in 2013</a></li><li class="tocline"><a href="#2004-changes" class="tocxref"><span class="secno">B.2 </span>Changes history of the 2004 Recommendation</a></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></section>
-
-
-</div>
-
-<section id="ch_introduction" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-
+</section><section id="toc"><h2 class="introductory" aria-level="1" role="heading" id="h2_toc">Table of Contents</h2><ul class="toc" role="directory" id="respecContents"><li class="tocline"><a href="#ch_introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#ch_classes" class="tocxref"><span class="secno">2. </span>Classes</a><ul class="toc"><li class="tocline"><a href="#ch_resource" class="tocxref"><span class="secno">2.1 </span>rdfs:Resource</a></li><li class="tocline"><a href="#ch_class" class="tocxref"><span class="secno">2.2 </span>rdfs:Class</a></li><li class="tocline"><a href="#ch_literal" class="tocxref"><span class="secno">2.3 </span>rdfs:Literal</a></li><li class="tocline"><a href="#ch_datatype" class="tocxref"><span class="secno">2.4 </span>rdfs:Datatype</a></li><li class="tocline"><a href="#ch_langstring" class="tocxref"><span class="secno">2.5 </span>rdf:langString</a></li><li class="tocline"><a href="#ch_html" class="tocxref"><span class="secno">2.6 </span>rdf:HTML</a></li><li class="tocline"><a href="#ch_xmlliteral" class="tocxref"><span class="secno">2.7 </span>rdf:XMLLiteral</a></li><li class="tocline"><a href="#ch_property" class="tocxref"><span class="secno">2.8 </span>rdf:Property</a></li></ul></li><li class="tocline"><a href="#ch_properties" class="tocxref"><span class="secno">3. </span>Properties</a><ul class="toc"><li class="tocline"><a href="#ch_range" class="tocxref"><span class="secno">3.1 </span>rdfs:range</a></li><li class="tocline"><a href="#ch_domain" class="tocxref"><span class="secno">3.2 </span>rdfs:domain</a></li><li class="tocline"><a href="#ch_type" class="tocxref"><span class="secno">3.3 </span>rdf:type</a></li><li class="tocline"><a href="#ch_subclassof" class="tocxref"><span class="secno">3.4 </span>rdfs:subClassOf</a></li><li class="tocline"><a href="#ch_subpropertyof" class="tocxref"><span class="secno">3.5 </span>rdfs:subPropertyOf</a></li><li class="tocline"><a href="#ch_label" class="tocxref"><span class="secno">3.6 </span>rdfs:label</a></li><li class="tocline"><a href="#ch_comment" class="tocxref"><span class="secno">3.7 </span>rdfs:comment</a></li></ul></li><li class="tocline"><a href="#ch_domainrange" class="tocxref"><span class="secno">4. </span>Using the Domain and Range vocabulary</a></li><li class="tocline"><a href="#ch_othervocab" class="tocxref"><span class="secno">5. </span>Other vocabulary</a><ul class="toc"><li class="tocline"><a href="#ch_containervocab" class="tocxref"><span class="secno">5.1 </span>Container Classes and Properties</a><ul class="toc"><li class="tocline"><a href="#ch_container" class="tocxref"><span class="secno">5.1.1 </span>rdfs:Container</a></li><li class="tocline"><a href="#ch_bag" class="tocxref"><span class="secno">5.1.2 </span>rdf:Bag</a></li><li class="tocline"><a href="#ch_seq" class="tocxref"><span class="secno">5.1.3 </span>rdf:Seq</a></li><li class="tocline"><a href="#ch_alt" class="tocxref"><span class="secno">5.1.4 </span>rdf:Alt</a></li><li class="tocline"><a href="#ch_containermembershipproperty" class="tocxref"><span class="secno">5.1.5 </span>rdfs:ContainerMembershipProperty</a></li><li class="tocline"><a href="#ch_member" class="tocxref"><span class="secno">5.1.6 </span>rdfs:member</a></li></ul></li><li class="tocline"><a href="#ch_collectionvocab" class="tocxref"><span class="secno">5.2 </span>RDF Collections</a><ul class="toc"><li class="tocline"><a href="#ch_list" class="tocxref"><span class="secno">5.2.1 </span>rdf:List</a></li><li class="tocline"><a href="#ch_first" class="tocxref"><span class="secno">5.2.2 </span>rdf:first</a></li><li class="tocline"><a href="#ch_rest" class="tocxref"><span class="secno">5.2.3 </span>rdf:rest</a></li><li class="tocline"><a href="#ch_nil" class="tocxref"><span class="secno">5.2.4 </span>rdf:nil</a></li></ul></li><li class="tocline"><a href="#ch_reificationvocab" class="tocxref"><span class="secno">5.3 </span>Reification Vocabulary</a><ul class="toc"><li class="tocline"><a href="#ch_statement" class="tocxref"><span class="secno">5.3.1 </span>rdf:Statement</a></li><li class="tocline"><a href="#ch_subject" class="tocxref"><span class="secno">5.3.2 </span>rdf:subject</a></li><li class="tocline"><a href="#ch_predicate" class="tocxref"><span class="secno">5.3.3 </span>rdf:predicate</a></li><li class="tocline"><a href="#ch_object" class="tocxref"><span class="secno">5.3.4 </span>rdf:object</a></li></ul></li><li class="tocline"><a href="#ch_utilvocab" class="tocxref"><span class="secno">5.4 </span>Utility Properties</a><ul class="toc"><li class="tocline"><a href="#ch_seealso" class="tocxref"><span class="secno">5.4.1 </span>rdfs:seeAlso</a></li><li class="tocline"><a href="#ch_isdefinedby" class="tocxref"><span class="secno">5.4.2 </span>rdfs:isDefinedBy</a></li><li class="tocline"><a href="#ch_value" class="tocxref"><span class="secno">5.4.3 </span>rdf:value</a></li></ul></li></ul></li><li class="tocline"><a href="#ch_summary" class="tocxref"><span class="secno">6. </span>RDF Schema summary</a><ul class="toc"><li class="tocline"><a href="#ch_sumclasses" class="tocxref"><span class="secno">6.1 </span>RDF classes</a></li><li class="tocline"><a href="#ch_sumproperties" class="tocxref"><span class="secno">6.2 </span>RDF properties</a></li></ul></li><li class="tocline"><a href="#ch_acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgments</a></li><li class="tocline"><a href="#changes" class="tocxref"><span class="secno">B. </span>Change history</a><ul class="toc"><li class="tocline"><a href="#PER-changes" class="tocxref"><span class="secno">B.1 </span>Changes for Proposed Edited Recommendation in 2013</a></li><li class="tocline"><a href="#2004-changes" class="tocxref"><span class="secno">B.2 </span>Changes history of the 2004 Recommendation</a></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></section>
+
+ </div>
+ <section id="ch_introduction" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
<!--OddPage-->
<h2 aria-level="1" role="heading" id="h2_ch_introduction"><span class="secno">1. </span>Introduction</h2>
-
-<p>The Resource Description Framework (RDF) is a general-purpose language for
-representing information in the Web.</p>
-
-<p>RDF Schema provides a data-mdelling vocabulary for RDF data.
-It is complemented by several companion documents which
-describe the basic concepts and abstract stntax of RDF
-[<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>], the formal semantics of RDF [<cite><a class="bibref" href="#bib-RDF11-MT">RDF11-MT</a></cite>], and
-various concrete syntaxes for RDF, such as Turtle [<cite><a class="bibref" href="#bib-TURTLE">TURTLE</a></cite>],
-TriG, [<cite><a class="bibref" href="#bib-TRIG">TRIG</a></cite>], and JSON-LD [<cite><a class="bibref" href="#bib-JSON-LD">JSON-LD</a></cite>].
-The RDF Primer [<cite><a class="bibref" href="#bib-RDF11-PRIMER">RDF11-PRIMER</a></cite>] provides an informal introduction and
-examples of the use of the concepts specified in this document.</p>
-
-<p>This document is intended to provide a clear specification of RDF
-Schema to those who find the formal semantics
-specification [<cite><a class="bibref" href="#bib-RDF11-MT">RDF11-MT</a></cite>]
-daunting. Thus, this document duplicates material also specified in the RDF
-Semantics specification . Where there is disagreement between this document
-and the RDF Semantics specification, the RDF Semantics specification should
-be taken to be correct.</p>
-
-
+
+ <p>The Resource Description Framework (RDF) is a general-purpose language
+ for
+ representing information in the Web.</p>
+ <p>RDF Schema provides a data-modelling vocabulary for RDF data.
+ It is complemented by several companion documents which
+ describe the basic concepts and abstract stntax of RDF
+ [<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>], the formal semantics of RDF [<cite><a class="bibref" href="#bib-RDF11-MT">RDF11-MT</a></cite>], and
+ various concrete syntaxes for RDF, such as Turtle [<cite><a class="bibref" href="#bib-TURTLE">TURTLE</a></cite>],
+ TriG, [<cite><a class="bibref" href="#bib-TRIG">TRIG</a></cite>], and JSON-LD [<cite><a class="bibref" href="#bib-JSON-LD">JSON-LD</a></cite>]. The RDF Primer
+ [<cite><a class="bibref" href="#bib-RDF11-PRIMER">RDF11-PRIMER</a></cite>] provides an informal introduction and
+ examples of the use of the concepts specified in this document.</p>
+ <p>This document is intended to provide a clear specification of RDF
+ Schema to those who find the formal semantics
+ specification [<cite><a class="bibref" href="#bib-RDF11-MT">RDF11-MT</a></cite>]
+ daunting. Thus, this document duplicates material also specified in the
+ RDF
+ Semantics specification. Where there is disagreement between this
+ document
+ and the RDF Semantics specification, the RDF Semantics specification
+ should
+ be taken to be correct.</p>
+
<!--
-<p>RDF properties may be thought of as attributes of resources and in
-this sense correspond to traditional attribute-value pairs. RDF
+<p>RDF properties may be thought of as attributes of resources and inthis sense correspond to traditional attribute-value pairs. RDF
properties also represent relationships between resources.</p>
-
-<p>RDF however, provides no mechanisms for describing these properties, nor
-does it provide any mechanisms for describing the relationships between these
-properties and other resources. That is the role of the RDF vocabulary
-description language, RDF Schema. RDF Schema defines classes and properties
+<p>RDF however, provides no mechanisms for describing these properties, nordoes it provide any mechanisms for describing the relationships between these
+properties and other resources. That is the role of the RDF vocabularydescription language, RDF Schema. RDF Schema defines classes and properties
that may be used to describe classes, properties and other resources.</p>
-
-<p>This document does not specify a vocabulary of descriptive properties such
-as "author". Instead it specifies mechanisms that may be used to name and
-describe properties and the classes of resource they describe.</p>
--->
-
-
-<p>
-RDF Schema is a
-<a href="http://www.w3.org/TR/rdf11-mt/#semantic-extensions-and-entailment-regimes">semantic
-extension</a> of RDF. It provides
-mechanisms for describing groups of related resources and the
-relationships between these resources. RDF Schema is written in RDF
-using the terms described in this document.These resources are used to
-determine characteristics of other resources,
-such as the <a href="#ch_domain">domains</a> and
-<a href="#ch_range">ranges</a> of properties.
-</p>
+<p>This document does not specify a vocabulary of descriptive properties suchas "author". Instead it specifies mechanisms that may be used to name and
+describe properties and the classes of resource they describe.</p>-->
-<p>The RDF Schema class and property system is similar to the type
-systems of object-oriented programming languages such as Java. RDF
-Schema differs from many such systems in that instead of defining a class in
-terms of the properties its instances may have, RDF Schema
-describes properties in terms of the classes of
-resource to which they apply. This is the role of the <a href="#ch_domain">domain</a> and <a href="#ch_range">range</a>
-mechanisms described in this specification. For example, we could
-define the <code>eg:author</code>
-property to have a domain of <code>eg:Document</code> and a range of
-<code>eg:Person</code>, whereas a classical object oriented system might
-typically define a class <code>eg:Book</code> with an attribute called
-<code>eg:author</code> of type <code>eg:Person</code>. Using the RDF
-approach, it is easy for others to subsequently define additional
-properties with a domain of eg:<code>Document</code> or a range of
-<code>eg:Person</code>.
-This can be done without the need to re-define the original description of
-these classes. One benefit of the RDF property-centric approach is that it
-allows anyone to extend the description of existing resources, one of the
-architectural principles of the Web [<cite><a class="bibref" href="#bib-BERNERS-LEE98">BERNERS-LEE98</a></cite>].</p>
-
-<p>This specification does not attempt to enumerate all the possible forms of
-representing the meaning of RDF
-classes and properties. Instead, the RDF Schema strategy is
-to acknowledge that there are many techniques through which the meaning of
-classes and properties can be described. Richer vocabulary or 'ontology'
-languages such as OWL [<cite><a class="bibref" href="#bib-OWL2-OVERVIEW">OWL2-OVERVIEW</a></cite>], inference rule
-languages and other formalisms (for example temporal logics) will each
-contribute to our ability to capture meaningful generalizations about data in
-the Web.
-
+ <p>
+ RDF Schema is a <a href="http://www.w3.org/TR/rdf11-mt/#semantic-extensions-and-entailment-regimes">semantic
+ extension</a> of RDF. It provides mechanisms for describing groups of
+ related resources and the relationships between these resources. RDF
+ Schema is written in RDF
+ using the terms described in this document. These resources are used to
+ determine characteristics of other resources, such as the <a href="#ch_domain">domains</a>
+ and <a href="#ch_range">ranges</a> of properties.
+ </p>
+ <p>The RDF Schema class and property system is similar to the type
+ systems of object-oriented programming languages such as Java. RDF
+ Schema differs from many such systems in that instead of defining a
+ class in
+ terms of the properties its instances may have, RDF Schema
+ describes properties in terms of the classes of
+ resource to which they apply. This is the role of the <a href="#ch_domain">domain</a>
+ and <a href="#ch_range">range</a>
+ mechanisms described in this specification. For example, we could
+ define the <code>eg:author</code> property to have a domain of <code>eg:Document</code>
+ and a range of
+ <code>eg:Person</code>, whereas a classical object oriented system might
+ typically define a class <code>eg:Book</code> with an attribute called
+ <code>eg:author</code> of type <code>eg:Person</code>. Using the RDF
+ approach, it is easy for others to subsequently define additional
+ properties with a domain of eg:<code>Document</code> or a range of
+ <code>eg:Person</code>. This can be done without the need to re-define
+ the original description of
+ these classes. One benefit of the RDF property-centric approach is that
+ it
+ allows anyone to extend the description of existing resources, one of
+ the
+ architectural principles of the Web [<cite><a class="bibref" href="#bib-BERNERS-LEE98">BERNERS-LEE98</a></cite>].</p>
+ <p>This specification does not attempt to enumerate all the possible forms
+ of
+ representing the meaning of RDF
+ classes and properties. Instead, the RDF Schema strategy is
+ to acknowledge that there are many techniques through which the meaning
+ of
+ classes and properties can be described. Richer vocabulary or 'ontology'
+ languages such as OWL [<cite><a class="bibref" href="#bib-OWL2-OVERVIEW">OWL2-OVERVIEW</a></cite>], inference rule
+ languages and other formalisms (for example temporal logics) will each
+ contribute to our ability to capture meaningful generalizations about
+ data in
+ the Web.
+
<!--
-RDF vocabulary designers can create and deploy Semantic Web
-applications using the RDF Schema facilities,
-while exploring richer languages that share this
-general approach.
+RDF vocabulary designers can create and deploy Semantic Webapplications using the RDF Schema facilities,
+while exploring richer languages that share thisgeneral approach.
-->
-
</p>
-
-
-<p>The language defined in this specification consists of a collection
-of RDF resources that can be used to describe other RDF
-resources in application-specific RDF
-vocabularies. The core vocabulary is defined in a namespace informally
-called <code>rdfs</code> here. That namespace is identified by the IRI</p>
-
-<blockquote>
-<code>http://www.w3.org/2000/01/rdf-schema#</code>
-</blockquote>
-
-and is conventionally associated with the prefix
-<code>rdfs:</code>. This specification also uses the prefix
-<code>rdf:</code> to refer to the RDF namespace<p></p>
-
-<blockquote>
-<code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code>
-</blockquote>
-
-<p>For convenience and readability, this specification uses an abbreviated
-form to represent IRIs. A name of the form prefix:suffix should be
-interpreted as a IRI consisting of the IRI associated
-with the prefix concatenated with the suffix.</p>
-
-</section>
-
-<section id="ch_classes" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-
-
+ <p>The language defined in this specification consists of a collection of
+ RDF resources that can be used to describe other RDF resources in
+ application-specific RDF vocabularies. The core vocabulary is defined in
+ a namespace informally called <code>rdfs</code> here. That namespace is
+ identified by the IRI</p>
+ <blockquote>
+ <code>http://www.w3.org/2000/01/rdf-schema#</code>
+ </blockquote>
+ and is conventionally associated with the prefix <code>rdfs:</code>. This
+ specification also uses the prefix
+ <code>rdf:</code> to refer to the RDF namespace
+ <p></p>
+ <blockquote>
+ <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code>
+ </blockquote>
+ <p>For convenience and readability, this specification uses an abbreviated
+ form to represent IRIs. A name of the form prefix:suffix should be
+ interpreted as a IRI consisting of the IRI associated
+ with the prefix concatenated with the suffix.</p>
+ </section>
+ <section id="ch_classes" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
<!--OddPage-->
<h2 aria-level="1" role="heading" id="h2_ch_classes"><span class="secno">2. </span>Classes</h2>
-
-<p>Resources may be divided into groups called classes. The members of a
-class are known as <em>instances</em> of the class. Classes are themselves
-resources. They are often identified by <a href="http://www.w3.org/TR/rdf11-concepts/#section-IRIs">IRIs</a> and
-may be described using RDF properties. The <code><a href="#ch_type">rdf:type</a></code> property may be used to state that a
-resource is an instance of a class.</p>
-
-<p>RDF distinguishes between a class and the set of its instances. Associated
-with each class is a set, called the class extension of the class, which is
-the set of the instances of the class. Two classes may have the same set of
-instances but be different classes. For example, the tax office may define
-the class of people living at the same address as the editor of this
-document. The Post Office may define the class of people whose address has
-the same zip code as the address of the author. It is possible for these
-classes to have exactly the same instances, yet to have different properties.
-Only one of the classes has the property that it was defined by the tax
-office, and only the other has the property that it was defined by the Post
-Office.</p>
-
-<p>A class may be a member of its own class extension and may be an instance of itself. </p>
-
-<p>The group of resources that are RDF Schema
-classes is itself a class called <a href="#ch_class"><code>rdfs:Class</code></a>.</p>
-
-<p id="def-subclass">
-If a class C is a <em>subclass</em> of a class C', then all instances of C will
-also be instances of C'.
-The <a href="#ch_subclassof"><code>rdfs:subClassOf</code></a> property
-may be used to state that one class is a subclass of another. The term
-super-class is used as the inverse of subclass. If a class C' is a
-super-class of a class C, then all instances of C are also instances of C'.
-</p>
-
-<p>The RDF Concepts and Abstract Syntax [<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>] specification
-defines the RDF concept of an <a href="http://www.w3.org/TR/rdf11-concepts/#section-Datatypes">RDF
-datatype</a>. All datatypes are classes. The instances of a class that is a
-datatype are the members of the value space of the datatype.</p>
-
-<section id="ch_resource" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_resource"><span class="secno">2.1 </span>rdfs:Resource</h3>
-
-<p>All things described by RDF are called <em>resources</em>, and are
-instances of the class <code>rdfs:Resource</code>. This is the class of
-everything. All other classes are <a href="#def-subclass">subclasses</a> of
-this class. <code>rdfs:Resource</code> is an instance of <a href="#ch_class"><code>rdfs:Class</code></a>.</p>
-
-</section>
-
-<section id="ch_class" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_class"><span class="secno">2.2 </span>rdfs:Class</h3>
-
-<p>This is the class of resources that are RDF classes.
-<code>rdfs:Class</code> is an instance of <code>rdfs:Class.</code></p>
-
-</section>
-
-<section id="ch_literal" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_literal"><span class="secno">2.3 </span>rdfs:Literal</h3>
-
-<p>The class <code>rdfs:Literal</code> is the class of <a href="http://www.w3.org/TR/rdf11-concepts/#section-Graph-Literal">literal</a>
-values such as strings and integers. Property values such as textual
-strings are examples of RDF literals.</p>
-
-<p><code>rdfs:Literal</code> is an instance of <a href="#ch_class"><code>rdfs:Class</code></a>. rdfs:Literal is a <a href="#def-subclass">subclass</a> of <a href="#ch_resource">rdfs:Resource</a>.</p>
-
-</section>
-
-<section id="ch_datatype" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_datatype"><span class="secno">2.4 </span>rdfs:Datatype</h3>
-
-<p><code>rdfs:Datatype</code> is the class of datatypes. All instances of
-<code>rdfs:Datatype</code> correspond to the <a href="http://www.w3.org/TR/rdf11-concepts/#section-Datatypes">RDF
-model of a datatype</a> described in the RDF Concepts specification
-[<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>].
-<code>rdfs:Datatype</code> is
-both an instance of and a <a href="#def-subclass">subclass</a> of <a href="#ch_class"><code>rdfs:Class</code></a>. Each instance of <code>rdfs:Datatype</code> is a <a href="#def-subclass">subclass</a> of rdfs:Literal.</p>
-
-</section>
-
-<section id="ch_langString" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_langString"><span class="secno">2.5 </span>rdf:langString</h3>
-
-<p>The class <code>rdf:langString</code> is the class of <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-language-tagged-string">language-tagged string values</a>. <code>rdf:langString</code> is an instance of
-<code>rdfs:Datatype</code> and a <a href="#def-subclass">subclass</a> of <a href="#ch_literal"><code>rdfs:Literal</code></a>.</p>
-
-</section>
-
-<section id="ch_html" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_html"><span class="secno">2.6 </span>rdf:HTML</h3>
-
-<p>The class <code>rdf:HTML</code> is the class of <a href="http://www.w3.org/TR/rdf11-concepts/#section-html">HTML
-literal values</a>. <code>rdf:HTML</code> is an instance of
-<code>rdfs:Datatype</code> and a <a href="#def-subclass">subclass</a> of <a href="#ch_literal"><code>rdfs:Literal</code></a>.</p>
-
-</section>
-
-<section id="ch_xmlliteral" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_xmlliteral"><span class="secno">2.7 </span>rdf:XMLLiteral</h3>
-
-<p>The class <code>rdf:XMLLiteral</code> is the class of <a href="http://www.w3.org/TR/rdf11-concepts/#section-XMLLiteral">XML
-literal values</a>. <code>rdf:XMLLiteral</code> is an instance of
-<code>rdfs:Datatype</code> and a <a href="#def-subclass">subclass</a> of <a href="#ch_literal"><code>rdfs:Literal</code></a>.</p>
-
-</section>
-<section id="ch_property" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_property"><span class="secno">2.8 </span>rdf:Property</h3>
-
-<p><code>rdf:Property</code> is the class of RDF properties.
-<code>rdf:Property</code> is an instance of <a href="#ch_class"><code>rdfs:Class</code></a>.</p>
-
-</section>
-</section>
-
-<section id="ch_properties" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-
+ <p>Resources may be divided into groups called classes. The members of a
+ class are known as <em>instances</em> of the class. Classes are
+ themselves
+ resources. They are often identified by <a href="http://www.w3.org/TR/rdf11-concepts/#section-IRIs">IRIs</a>
+ and
+ may be described using RDF properties. The <code><a href="#ch_type">rdf:type</a></code>
+ property may be used to state that a
+ resource is an instance of a class.</p>
+ <p>RDF distinguishes between a class and the set of its instances.
+ Associated
+ with each class is a set, called the class extension of the class, which
+ is
+ the set of the instances of the class. Two classes may have the same set
+ of
+ instances but be different classes. For example, the tax office may
+ define
+ the class of people living at the same address as the editor of this
+ document. The Post Office may define the class of people whose address
+ has
+ the same zip code as the address of the author. It is possible for these
+ classes to have exactly the same instances, yet to have different
+ properties.
+ Only one of the classes has the property that it was defined by the tax
+ office, and only the other has the property that it was defined by the
+ Post
+ Office.</p>
+ <p>A class may be a member of its own class extension and may be an
+ instance of itself. </p>
+ <p>The group of resources that are RDF Schema classes is itself a class
+ called <a href="#ch_class"><code>rdfs:Class</code></a>.</p>
+ <p id="def-subclass">
+ If a class C is a <em>subclass</em> of a class C', then all instances
+ of C will
+ also be instances of C'. The <a href="#ch_subclassof"><code>rdfs:subClassOf</code></a>
+ property may be used to state that one class is a subclass of another.
+ The term super-class is used as the inverse of subclass. If a class C'
+ is a super-class of a class C, then all instances of C are also
+ instances of C'.
+ </p>
+ <p>The RDF Concepts and Abstract Syntax [<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>] specification
+ defines the RDF concept of an <a href="http://www.w3.org/TR/rdf11-concepts/#section-Datatypes">RDF
+ datatype</a>. All datatypes are classes. The instances of a class that
+ is a
+ datatype are the members of the value space of the datatype.</p>
+ <section id="ch_resource" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_resource"><span class="secno">2.1 </span>rdfs:Resource</h3>
+ <p>All things described by RDF are called <em>resources</em>, and are
+ instances of the class <code>rdfs:Resource</code>. This is the class
+ of
+ everything. All other classes are <a href="#def-subclass">subclasses</a>
+ of
+ this class. <code>rdfs:Resource</code> is an instance of <a href="#ch_class"><code>rdfs:Class</code></a>.</p>
+ </section>
+ <section id="ch_class" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_class"><span class="secno">2.2 </span>rdfs:Class</h3>
+ <p>This is the class of resources that are RDF classes.
+ <code>rdfs:Class</code> is an instance of <code>rdfs:Class.</code></p>
+ </section>
+ <section id="ch_literal" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_literal"><span class="secno">2.3 </span>rdfs:Literal</h3>
+ <p>The class <code>rdfs:Literal</code> is the class of <a href="http://www.w3.org/TR/rdf11-concepts/#section-Graph-Literal">literal</a>
+ values such as strings and integers. Property values such as textual
+ strings are examples of RDF literals.</p>
+ <p><code>rdfs:Literal</code> is an instance of <a href="#ch_class"><code>rdfs:Class</code></a>.
+ rdfs:Literal is a <a href="#def-subclass">subclass</a> of <a href="#ch_resource">rdfs:Resource</a>.</p>
+ </section>
+ <section id="ch_datatype" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_datatype"><span class="secno">2.4 </span>rdfs:Datatype</h3>
+ <p><code>rdfs:Datatype</code> is the class of datatypes. All instances
+ of
+ <code>rdfs:Datatype</code> correspond to the <a href="http://www.w3.org/TR/rdf11-concepts/#section-Datatypes">RDF
+model
+ of a datatype</a> described in the RDF Concepts specification
+ [<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>].
+ <code>rdfs:Datatype</code> is
+ both an instance of and a <a href="#def-subclass">subclass</a> of <a href="#ch_class"><code>rdfs:Class</code></a>. Each instance of <code>rdfs:Datatype</code>
+ is a <a href="#def-subclass">subclass</a> of rdfs:Literal.</p>
+ </section>
+ <section id="ch_langstring" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_langstring"><span class="secno">2.5 </span>rdf:langString</h3>
+ <p>The class <code>rdf:langString</code> is the class of <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-language-tagged-string">language-tagged
+ string values</a>. <code>rdf:langString</code> is an instance of
+ <code>rdfs:Datatype</code> and a <a href="#def-subclass">subclass</a>
+ of <a href="#ch_literal"><code>rdfs:Literal</code></a>.</p>
+ </section>
+ <section class="informative" id="ch_html" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_html"><span class="secno">2.6 </span>rdf:HTML</h3><p><em>This section is non-normative.</em></p>
+ <p>The class <code>rdf:HTML</code> is the class of <a href="http://www.w3.org/TR/rdf11-concepts/#section-html">HTML
+literal
+ values</a>. <code>rdf:HTML</code> is an instance of
+ <code>rdfs:Datatype</code> and a <a href="#def-subclass">subclass</a>
+ of <a href="#ch_literal"><code>rdfs:Literal</code></a>.</p>
+ </section>
+ <section class="informative" id="ch_xmlliteral" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_xmlliteral"><span class="secno">2.7 </span>rdf:XMLLiteral</h3><p><em>This section is non-normative.</em></p>
+ <p>The class <code>rdf:XMLLiteral</code> is the class of <a href="http://www.w3.org/TR/rdf11-concepts/#section-XMLLiteral">XML
+literal
+ values</a>. <code>rdf:XMLLiteral</code> is an instance of
+ <code>rdfs:Datatype</code> and a <a href="#def-subclass">subclass</a>
+ of <a href="#ch_literal"><code>rdfs:Literal</code></a>.</p>
+ </section>
+ <section id="ch_property" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_property"><span class="secno">2.8 </span>rdf:Property</h3>
+ <p><code>rdf:Property</code> is the class of RDF properties.
+ <code>rdf:Property</code> is an instance of <a href="#ch_class"><code>rdfs:Class</code></a>.</p>
+ </section>
+ </section>
+ <section id="ch_properties" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
<!--OddPage-->
<h2 aria-level="1" role="heading" id="h2_ch_properties"><span class="secno">3. </span>Properties</h2>
-
-<p>The RDF Concepts and Abstract Syntax specification [<cite><a class="bibref" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>]
-describes the concept of an RDF property as a relation between subject
-resources and object resources.</p>
-
-<p id="def-subproperty">
-This specification defines the concept of subproperty.
-The <a href="#ch_subclassof"><code>rdfs:subPropertyOf</code></a> property
-may be used to state that one property is a subproperty of another.
-If a property P is a subproperty of property P', then all pairs of resources which are
-related by P are also related by P'. The term super-property is often
-used as the inverse of subproperty. If a property P' is a super-property
-of a property P, then all pairs of resources which are related by P
-are also related by P'. This specification does not define a top
-property that is the super-property of all properties.
-</p>
-
-<div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_1"><span>Note</span></div><div class="">
-The basic facilities provided by
-<a href="#ch_domain"><code>rdfs:domain</code></a> and
-<a href="#ch_range"><code>rdfs:range</code></a> do not provide any direct
-way to indicate property restrictions that are local to a class. Although
-it is possible to combine use <a href="#ch_domain"><code>rdfs:domain</code></a> and <a href="#ch_range"><code>rdfs:range</code></a>
-with sub-property hierarchies, direct support for such declarations are
-provided by richer Web Ontology languages such as OWL [<cite><a class="bibref" href="#bib-OWL2-OVERVIEW">OWL2-OVERVIEW</a></cite>].
-</div></div>
-
-<section id="ch_range" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_range"><span class="secno">3.1 </span>rdfs:range</h3>
-
-<p><code>rdfs:range</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a> that is used to state that
-the values of a property are instances of one or more classes.</p>
-
-<p>The triple</p>
-
-<blockquote>
- <code>P rdfs:range C</code>
-</blockquote>
- <p>states that P is an instance of the class <a href="#ch_property"><code>rdf:Property</code></a>, that C is an instance of the class <a href="#ch_class"><code>rdfs:Class</code></a> and that the resources denoted by the objects of triples whose predicate is P are instances of the class C.</p>
- <p>Where P has more than one rdfs:range property, then the resources denoted by the objects of triples with predicate P are instances of all the classes stated by the <code>rdfs:range</code> properties.</p>
- <p>The <code>rdfs:range</code> property can be applied to itself. The
-rdfs:range of <code>rdfs:range</code> is the class <a href="#ch_class"><code>rdfs:Class</code></a>. This states that any resource
-that is the value of an <code>rdfs:range</code> property is an instance of <a href="#ch_class"><code>rdfs:Class</code></a>.</p>
- <p>The <code>rdfs:range</code> property is applied to properties. This
-can be represented in RDF using the <a href="#ch_domain"><code>rdfs:domain</code></a> property. The <a href="#ch_domain"><code>rdfs:domain</code></a> of <code>rdfs:range</code> is
-the class <a href="#ch_property"><code>rdf:Property</code></a>. This states
-that any resource with an <code>rdfs:range</code> property is an instance of
-<code><a href="#ch_property">rdf:Property</a></code>.</p>
-
-</section>
-
-<section id="ch_domain" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_domain"><span class="secno">3.2 </span>rdfs:domain</h3>
-
-<p><code>rdfs:domain</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a> that is used to state that
-any resource that has a given property is an instance of one or more
-classes.</p>
- <p>A triple of the form:</p>
-
-<blockquote>
- <code>P rdfs:domain C</code>
-</blockquote>
- <p>states that P is an instance of the class <code><a href="#ch_property">rdf:Property</a></code>, that C is a instance of the class <code><a href="#ch_class">rdfs:Class</a></code> and that the resources denoted by the subjects of triples whose predicate is P are instances of the class C.</p>
- <p>Where a property P has more than one rdfs:domain property, then the resources denoted by subjects of triples with predicate P are instances of all the classes stated by the <code>rdfs:domain</code> properties.</p>
- <p>The <code>rdfs:domain</code> property may be applied to itself. The
-rdfs:domain of <code>rdfs:domain</code> is the class <a href="#ch_property"><code>rdf:Property</code></a>. This states that any
-resource with an <code>rdfs:domain</code> property is an instance of <code><a href="#ch_property">rdf:Property</a></code>.</p>
- <p>The <a href="#ch_range"><code>rdfs:range</code></a> of
-<code>rdfs:domain</code> is the class <code><a href="#ch_class">rdfs:Class</a></code>. This states that any resource that is the value of an <code>rdfs:domain</code> property is an
-instance of <code><a href="#ch_class">rdfs:Class</a></code>.</p>
-
-</section>
-
-<section id="ch_type" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_type"><span class="secno">3.3 </span>rdf:type</h3>
-
-<p><code>rdf:type</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a> that is used to
-state that a resource is an instance of a class.</p>
-
-<p>A triple of the form:</p>
-
-<blockquote>
- <code>R rdf:type C</code>
-</blockquote>
-
-<p>states that C is an instance of <a href="#ch_class"><code>rdfs:Class</code></a> and R is an instance of C.</p>
-
-<p>The <code><a href="#ch_domain">rdfs:domain</a></code> of
-<code>rdf:type</code> is <a href="#ch_resource">rdfs:Resource</a>. The <a href="#ch_range"><code>rdfs:range</code></a> of rdf:type is <a href="#ch_class"><code>rdfs:Class</code></a>.</p>
-
-</section>
-
-<section id="ch_subclassof" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_subclassof"><span class="secno">3.4 </span>rdfs:subClassOf</h3>
-
-<p>The property <code>rdfs:subClassOf</code> is an instance of <code><a href="#ch_property">rdf:Property</a></code> that is used to state that all the instances of one class are instances of another.</p>
- <p>A triple of the form:</p>
- <blockquote>
- <code>C1 rdfs:subClassOf C2</code>
-</blockquote>
-
-<p>states that C1 is an instance of <code><a href="#ch_class">rdfs:Class</a></code>, C2 is an instance of <code><a href="#ch_class">rdfs:Class</a></code> and C1 is a <a href="#def-subclass">subclass</a> of C2. The <code>rdfs:subClassOf</code>
-property is transitive.</p>
-
-<p>The <a href="#ch_domain"><code>rdfs:domain</code></a> of
-<code>rdfs:subClassOf</code> is <code><a href="#ch_class">rdfs:Class</a></code>. The <a href="#ch_range"><code>rdfs:range</code></a> of <code>rdfs:subClassOf</code>
-is <a href="#ch_class"><code>rdfs:Class</code></a>.</p>
-
-</section>
-
-<section id="ch_subpropertyof" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_subpropertyof"><span class="secno">3.5 </span>rdfs:subPropertyOf</h3>
-
-<p>The property <code>rdfs:subPropertyOf</code> is an instance of <code><a href="#ch_property">rdf:Property</a></code> that is used to state that all resources related by one property are also related by another.</p>
- <p>A triple of the form:</p>
- <blockquote>
- <code>P1 rdfs:subPropertyOf P2</code>
-</blockquote>
-
-<p>states that P1 is an instance of <code><a href="#ch_property">rdf:Property</a></code>, P2 is an instance of <code><a href="#ch_property">rdf:Property</a></code> and P1 is a <a href="#def-subproperty">subproperty</a> of P2. The
-<code>rdfs:subPropertyOf</code> property is transitive.</p>
-
-<p>The <a href="#ch_domain"><code>rdfs:domain</code></a> of
-<code>rdfs:subPropertyOf</code> is <code><a href="#ch_property">rdf:Property</a></code>. The <a href="#ch_range"><code>rdfs:range</code></a> of rdfs:subPropertyOf is <a href="#ch_property"><code>rdf:Property</code></a>.</p>
-
-</section>
-
-<section id="ch_label" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_label"><span class="secno">3.6 </span>rdfs:label</h3>
-
-<p><code>rdfs:label</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a> that may be used to provide a human-readable version of a resource's name.</p>
-
-<p>A triple of the form:</p>
-
-<blockquote>
- <code>R rdfs:label L</code>
-</blockquote>
-
-<p>states that L is a human readable label for R.</p>
-
-<p>The <a href="#ch_domain"><code>rdfs:domain</code></a> of
-<code>rdfs:label</code> is <code><a href="#ch_resource">rdfs:Resource</a></code>. The <a href="#ch_range"><code>rdfs:range</code></a> of rdfs:label is <a href="#ch_literal"><code>rdfs:Literal</code></a>.</p>
-
-<p>Multilingual labels are supported using the <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-Graph-Literal">language
-tagging</a> facility of RDF literals.</p>
-
-</section>
-
-<section id="ch_comment" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_comment"><span class="secno">3.7 </span>rdfs:comment</h3>
-
-<p><code>rdfs:comment</code> is an instance of <code><a href="#ch_property">rdf:Property</a></code> that may be used to provide a human-readable description of a resource.</p>
-
-<p>A triple of the form:</p>
-
-<blockquote>
- <code>R rdfs:comment L</code>
-</blockquote>
-
-<p>states that L is a human readable description of R.</p>
-
-<p>The <a href="#ch_domain"><code>rdfs:domain</code></a> of
-<code>rdfs:comment</code> is <code><a href="#ch_resource">rdfs:Resource</a></code>. The <a href="#ch_range"><code>rdfs:range</code></a> of rdfs:comment is <a href="#ch_literal"><code>rdfs:Literal</code></a>.</p>
-
-<p>A textual comment helps clarify the meaning of RDF classes and properties.
-Such in-line documentation complements the use of both formal techniques
-(Ontology and rule languages) and informal (prose documentation, examples,
-test cases). A variety of documentation forms can be combined to indicate the
-intended meaning of the classes and properties described in an RDF
-vocabulary. Since RDF vocabularies are expressed as RDF graphs, vocabularies
-defined in other namespaces may be used to provide richer documentation.</p>
-
-<p>Multilingual documentation is supported through use of the <a href="http://www.w3.org/TR/rdf11-concepts/#section-Graph-Literal">language
-tagging</a> facility of RDF literals.</p>
-
-</section>
-</section>
-
-<section id="ch_domainrange" class="informative" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-
+ <p>The RDF Concepts and Abstract Syntax specification [<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>]
+ describes the concept of an RDF property as a relation between subject
+ resources and object resources.</p>
+ <p id="def-subproperty">
+ This specification defines the concept of subproperty. The <a href="#ch_subclassof"><code>rdfs:subPropertyOf</code></a>
+ property may be used to state that one property is a subproperty of
+ another.
+ If a property P is a subproperty of property P', then all pairs of
+ resources which are related by P are also related by P'. The term
+ super-property is often
+ used as the inverse of subproperty. If a property P' is a super-property
+ of a property P, then all pairs of resources which are related by P are
+ also related by P'. This specification does not define a top
+ property that is the super-property of all properties.
+ </p>
+ <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_1"><span>Note</span></div><p class="">
+ The basic facilities provided by <a href="#ch_domain"><code>rdfs:domain</code></a>
+ and <a href="#ch_range"><code>rdfs:range</code></a> do not provide any
+ direct way to indicate property restrictions that are local to a class.
+ Although it is possible to combine use <a href="#ch_domain"><code>rdfs:domain</code></a>
+ and <a href="#ch_range"><code>rdfs:range</code></a> with sub-property
+ hierarchies, direct support for such declarations are provided by richer
+ Web Ontology languages such as OWL [<cite><a class="bibref" href="#bib-OWL2-OVERVIEW">OWL2-OVERVIEW</a></cite>].
+ </p></div>
+ <section id="ch_range" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_range"><span class="secno">3.1 </span>rdfs:range</h3>
+ <p><code>rdfs:range</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a>
+ that is used to state that
+ the values of a property are instances of one or more classes.</p>
+ <p>The triple</p>
+ <blockquote> <code>P rdfs:range C</code>
+ </blockquote>
+ <p>states that P is an instance of the class <a href="#ch_property"><code>rdf:Property</code></a>,
+ that C is an instance of the class <a href="#ch_class"><code>rdfs:Class</code></a>
+ and that the resources denoted by the objects of triples whose
+ predicate is P are instances of the class C.</p>
+ <p>Where P has more than one rdfs:range property, then the resources
+ denoted by the objects of triples with predicate P are instances of
+ all the classes stated by the <code>rdfs:range</code> properties.</p>
+ <p>The <code>rdfs:range</code> property can be applied to itself. The
+ rdfs:range of <code>rdfs:range</code> is the class <a href="#ch_class"><code>rdfs:Class</code></a>.
+ This states that any resource
+ that is the value of an <code>rdfs:range</code> property is an
+ instance of <a href="#ch_class"><code>rdfs:Class</code></a>.</p>
+ <p>The <code>rdfs:range</code> property is applied to properties. This
+ can be represented in RDF using the <a href="#ch_domain"><code>rdfs:domain</code></a>
+ property. The <a href="#ch_domain"><code>rdfs:domain</code></a> of <code>rdfs:range</code>
+ is
+ the class <a href="#ch_property"><code>rdf:Property</code></a>. This
+ states
+ that any resource with an <code>rdfs:range</code> property is an
+ instance of
+ <code><a href="#ch_property">rdf:Property</a></code>.</p>
+ </section>
+ <section id="ch_domain" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_domain"><span class="secno">3.2 </span>rdfs:domain</h3>
+ <p><code>rdfs:domain</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a>
+ that is used to state that
+ any resource that has a given property is an instance of one or more
+ classes.</p>
+ <p>A triple of the form:</p>
+ <blockquote> <code>P rdfs:domain C</code>
+ </blockquote>
+ <p>states that P is an instance of the class <code><a href="#ch_property">rdf:Property</a></code>,
+ that C is a instance of the class <code><a href="#ch_class">rdfs:Class</a></code>
+ and that the resources denoted by the subjects of triples whose
+ predicate is P are instances of the class C.</p>
+ <p>Where a property P has more than one rdfs:domain property, then the
+ resources denoted by subjects of triples with predicate P are
+ instances of all the classes stated by the <code>rdfs:domain</code>
+ properties.</p>
+ <p>The <code>rdfs:domain</code> property may be applied to itself. The
+ rdfs:domain of <code>rdfs:domain</code> is the class <a href="#ch_property"><code>rdf:Property</code></a>.
+ This states that any
+ resource with an <code>rdfs:domain</code> property is an instance of
+ <code><a href="#ch_property">rdf:Property</a></code>.</p>
+ <p>The <a href="#ch_range"><code>rdfs:range</code></a> of
+ <code>rdfs:domain</code> is the class <code><a href="#ch_class">rdfs:Class</a></code>.
+ This states that any resource that is the value of an <code>rdfs:domain</code>
+ property is an
+ instance of <code><a href="#ch_class">rdfs:Class</a></code>.</p>
+ </section>
+ <section id="ch_type" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_type"><span class="secno">3.3 </span>rdf:type</h3>
+ <p><code>rdf:type</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a>
+ that is used to
+ state that a resource is an instance of a class.</p>
+ <p>A triple of the form:</p>
+ <blockquote> <code>R rdf:type C</code>
+ </blockquote>
+ <p>states that C is an instance of <a href="#ch_class"><code>rdfs:Class</code></a>
+ and R is an instance of C.</p>
+ <p>The <code><a href="#ch_domain">rdfs:domain</a></code> of
+ <code>rdf:type</code> is <a href="#ch_resource">rdfs:Resource</a>.
+ The <a href="#ch_range"><code>rdfs:range</code></a> of rdf:type is <a href="#ch_class"><code>rdfs:Class</code></a>.</p>
+ </section>
+ <section id="ch_subclassof" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_subclassof"><span class="secno">3.4 </span>rdfs:subClassOf</h3>
+ <p>The property <code>rdfs:subClassOf</code> is an instance of <code><a href="#ch_property">rdf:Property</a></code> that is used to state
+ that all the instances of one class are instances of another.</p>
+ <p>A triple of the form:</p>
+ <blockquote> <code>C1 rdfs:subClassOf C2</code>
+ </blockquote>
+ <p>states that C1 is an instance of <code><a href="#ch_class">rdfs:Class</a></code>,
+ C2 is an instance of <code><a href="#ch_class">rdfs:Class</a></code>
+ and C1 is a <a href="#def-subclass">subclass</a> of C2. The <code>rdfs:subClassOf</code>
+ property is transitive.</p>
+ <p>The <a href="#ch_domain"><code>rdfs:domain</code></a> of
+ <code>rdfs:subClassOf</code> is <code><a href="#ch_class">rdfs:Class</a></code>.
+ The <a href="#ch_range"><code>rdfs:range</code></a> of <code>rdfs:subClassOf</code>
+ is <a href="#ch_class"><code>rdfs:Class</code></a>.</p>
+ </section>
+ <section id="ch_subpropertyof" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_subpropertyof"><span class="secno">3.5 </span>rdfs:subPropertyOf</h3>
+ <p>The property <code>rdfs:subPropertyOf</code> is an instance of <code><a href="#ch_property">rdf:Property</a></code> that is used to state
+ that all resources related by one property are also related by
+ another.</p>
+ <p>A triple of the form:</p>
+ <blockquote> <code>P1 rdfs:subPropertyOf P2</code>
+ </blockquote>
+ <p>states that P1 is an instance of <code><a href="#ch_property">rdf:Property</a></code>,
+ P2 is an instance of <code><a href="#ch_property">rdf:Property</a></code>
+ and P1 is a <a href="#def-subproperty">subproperty</a> of P2. The
+ <code>rdfs:subPropertyOf</code> property is transitive.</p>
+ <p>The <a href="#ch_domain"><code>rdfs:domain</code></a> of
+ <code>rdfs:subPropertyOf</code> is <code><a href="#ch_property">rdf:Property</a></code>.
+ The <a href="#ch_range"><code>rdfs:range</code></a> of
+ rdfs:subPropertyOf is <a href="#ch_property"><code>rdf:Property</code></a>.</p>
+ </section>
+ <section id="ch_label" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_label"><span class="secno">3.6 </span>rdfs:label</h3>
+ <p><code>rdfs:label</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a>
+ that may be used to provide a human-readable version of a resource's
+ name.</p>
+ <p>A triple of the form:</p>
+ <blockquote> <code>R rdfs:label L</code>
+ </blockquote>
+ <p>states that L is a human readable label for R.</p>
+ <p>The <a href="#ch_domain"><code>rdfs:domain</code></a> of
+ <code>rdfs:label</code> is <code><a href="#ch_resource">rdfs:Resource</a></code>.
+ The <a href="#ch_range"><code>rdfs:range</code></a> of rdfs:label is
+ <a href="#ch_literal"><code>rdfs:Literal</code></a>.</p>
+ <p>Multilingual labels are supported using the <a href="http://www.w3.org/TR/rdf11-concepts/#section-Graph-Literal">language
+ tagging</a> facility of RDF literals.</p>
+ </section>
+ <section id="ch_comment" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_comment"><span class="secno">3.7 </span>rdfs:comment</h3>
+ <p><code>rdfs:comment</code> is an instance of <code><a href="#ch_property">rdf:Property</a></code>
+ that may be used to provide a human-readable description of a
+ resource.</p>
+ <p>A triple of the form:</p>
+ <blockquote> <code>R rdfs:comment L</code>
+ </blockquote>
+ <p>states that L is a human readable description of R.</p>
+ <p>The <a href="#ch_domain"><code>rdfs:domain</code></a> of
+ <code>rdfs:comment</code> is <code><a href="#ch_resource">rdfs:Resource</a></code>.
+ The <a href="#ch_range"><code>rdfs:range</code></a> of rdfs:comment
+ is <a href="#ch_literal"><code>rdfs:Literal</code></a>.</p>
+ <p>A textual comment helps clarify the meaning of RDF classes and
+ properties.
+ Such in-line documentation complements the use of both formal
+ techniques
+ (Ontology and rule languages) and informal (prose documentation,
+ examples,
+ test cases). A variety of documentation forms can be combined to
+ indicate the
+ intended meaning of the classes and properties described in an RDF
+ vocabulary. Since RDF vocabularies are expressed as RDF graphs,
+ vocabularies
+ defined in other namespaces may be used to provide richer
+ documentation.</p>
+ <p>Multilingual documentation is supported through use of the <a href="http://www.w3.org/TR/rdf11-concepts/#section-Graph-Literal">language
+ tagging</a> facility of RDF literals.</p>
+ </section>
+ </section>
+ <section id="ch_domainrange" class="informative" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
<!--OddPage-->
<h2 aria-level="1" role="heading" id="h2_ch_domainrange"><span class="secno">4. </span>Using the Domain and Range vocabulary</h2><p><em>This section is non-normative.</em></p>
-
-<p>This specification introduces an RDF vocabulary for describing the
-meaningful use of properties and classes in RDF data. For example, an RDF
-vocabulary might describe limitations on the types of values that are
-appropriate for some property, or on the classes to which it makes sense to
-ascribe such properties.</p>
-
-<p>RDF Schema provides a mechanism for describing this information, but does not say whether or how an application should use it. For example, while an RDF vocabulary can assert that an <code>author</code> property is used to
-indicate resources that are instances of the class <code>Person</code>, it
-does not say whether or how an application should act in processing that
-range information. Different applications will use this information in
-different ways. For example, data checking tools might use this to help
-discover errors in some data set, an interactive editor might suggest
-appropriate values, and a reasoning application might use it to infer
-additional information from instance data.</p>
-
-<p>RDF vocabularies can describe relationships between vocabulary items from
-multiple independently developed vocabularies. Since IRIs are used
-to identify classes and properties in the Web, it is possible to create new
-properties that have a <code>domain</code> or <code>range</code> whose value
-is a class defined in another namespace.</p>
-
-</section>
-
-<section id="ch_othervocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-
+ <p>This specification introduces an RDF vocabulary for describing the
+ meaningful use of properties and classes in RDF data. For example, an
+ RDF
+ vocabulary might describe limitations on the types of values that are
+ appropriate for some property, or on the classes to which it makes sense
+ to
+ ascribe such properties.</p>
+ <p>RDF Schema provides a mechanism for describing this information, but
+ does not say whether or how an application should use it. For example,
+ while an RDF vocabulary can assert that an <code>author</code> property
+ is used to
+ indicate resources that are instances of the class <code>Person</code>,
+ it
+ does not say whether or how an application should act in processing that
+ range information. Different applications will use this information in
+ different ways. For example, data checking tools might use this to help
+ discover errors in some data set, an interactive editor might suggest
+ appropriate values, and a reasoning application might use it to infer
+ additional information from instance data.</p>
+ <p>RDF vocabularies can describe relationships between vocabulary items
+ from
+ multiple independently developed vocabularies. Since IRIs are used
+ to identify classes and properties on the Web, it is possible to create
+ new
+ properties that have a <code>domain</code> or <code>range</code> whose
+ value
+ is a class defined in another namespace.</p>
+ </section>
+ <section id="ch_othervocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
<!--OddPage-->
<h2 aria-level="1" role="heading" id="h2_ch_othervocab"><span class="secno">5. </span>Other vocabulary</h2>
-
-<p>Additional classes and properties, including constructs for representing
-containers and RDF statements, and for deploying RDF vocabulary descriptions
-in the World Wide Web are defined in this section.</p>
-
-<section id="ch_containervocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_containervocab"><span class="secno">5.1 </span>Container Classes and Properties</h3>
-
-<p>RDF containers are resources that are used to represent collections. An introduction
-to RDF containers with examples may be found in the <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#containers">RDF
-2004 Primer</a>. The same resource may appear in a container more than
-once. Unlike containment in the physical world, a container may be
-contained in itself.</p>
-
-<p>Three different kinds of container are defined. Whilst the formal
-semantics [<cite><a class="bibref" href="#bib-RDF11-MT">RDF11-MT</a></cite>] of all three classes of container are identical,
-different classes may be used to indicate informally further
-information. An rdf:Bag is used to indicate that the container is
-intended to be unordered. An rdf:Seq is used to indicate that the
-order indicated by the numerical order of the <a href="#ch_containermembershipproperty">container member ship properties</a>
-of the container is intended to be significant. An rdf:Alt container is used
-to indicate that typical processing of the container will be to select one of
-the members.</p>
-
-<p>Just as a hen house may have the property that it is made of wood, that
-does not mean that all the hens it contains are made of wood, a property of a
-container is not necessarily a property of all of its members.</p>
-
-<p>RDF containers are defined by the following classes and properties.</p>
-
-<section id="ch_container" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h4 aria-level="3" role="heading" id="h4_ch_container"><span class="secno">5.1.1 </span>rdfs:Container</h4>
-
-<p>The <code>rdfs:Container</code> class is a super-class of the RDF
-Container classes, i.e. <code><a href="#ch_bag">rdf:Bag</a></code>, <code><a href="#ch_seq">rdf:Seq</a></code>, <code><a href="#ch_alt">rdf:Alt</a></code>.</p>
-
-</section>
-
-<section id="ch_bag" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h4 aria-level="3" role="heading" id="h4_ch_bag"><span class="secno">5.1.2 </span>rdf:Bag</h4>
-
-<p>The <code>rdf:Bag</code> class is the class of RDF 'Bag' containers. It is
-a <a href="#def-subclass">subclass</a> of <code><a href="#ch_container">rdfs:Container</a></code>. Whilst formally it is no
-different from an <code><a href="#ch_seq">rdf:Seq</a></code> or an <code><a href="#ch_alt">rdf:Alt</a></code>, the <code>rdf:Bag</code> class is used
-conventionally to indicate to a human reader that the container is intended
-to be unordered.</p>
-
-</section>
-
-<section id="ch_seq" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h4 aria-level="3" role="heading" id="h4_ch_seq"><span class="secno">5.1.3 </span>rdf:Seq</h4>
-
-<p>The <code>rdf:Seq</code> class is the class of RDF 'Sequence' containers.
-It is a <a href="#def-subclass">subclass</a> of <code><a href="#ch_container">rdfs:Container</a></code>. Whilst formally it is no
-different from an <code><a href="#ch_bag">rdf:Bag</a></code> or an <code><a href="#ch_alt">rdf:Alt</a></code>, the <code>rdf:Seq</code> class is used
-conventionally to indicate to a human reader that the numerical ordering of
-the <a href="#ch_containermembershipproperty">container membership
-properties</a> of the container is intended to be significant.</p>
-
-</section>
-
-<section id="ch_alt" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h4 aria-level="3" role="heading" id="h4_ch_alt"><span class="secno">5.1.4 </span>rdf:Alt</h4>
-
-<p>The <code>rdf:Alt</code> class is the class of RDF 'Alternative'
-containers. It is a <a href="#def-subclass">subclass</a> of <code><a href="#ch_container">rdfs:Container</a></code>. Whilst formally it is no
-different from an <code><a href="#ch_seq">rdf:Seq</a></code> or an <code><a href="#ch_bag">rdf:Bag</a></code>, the <code>rdf:Alt</code> class is used
-conventionally to indicate to a human reader that typical processing will be
-to select one of the members of the container. The first member of the
-container, i.e. the value of the <code><a href="#ch_containermembershipproperty">rdf:_1</a></code> property, is the
-default choice.</p>
-
-</section>
-
-<section id="ch_containermembershipproperty" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h4 aria-level="3" role="heading" id="h4_ch_containermembershipproperty"><span class="secno">5.1.5 </span>rdfs:ContainerMembershipProperty</h4>
-
-<p>The <code>rdfs:ContainerMembershipProperty</code> class has as instances
-the properties <code>rdf:_1, rdf:_2, rdf:_3 ...</code> that are used to state
-that a resource is a member of a container.
-<code>rdfs:ContainerMembershipProperty</code> is a <a href="#def-subclass">subclass</a> of <a href="#ch_property"><code>rdf:Property</code></a>. Each instance of
-<code>rdfs:ContainerMembershipProperty</code> is an <a href="#ch_subpropertyof"><code>rdfs:subPropertyOf</code></a> the <code><a href="#ch_member">rdfs:member</a></code> property.</p>
-
-<p>Given a container C, a triple of the form:</p>
-
-<blockquote>
- <code>C rdf:_nnn O</code>
-</blockquote>
-
-<p>where nnn is the decimal representation of an integer greater than 0 with
-no leading zeros, states that O is a member of the container C.</p>
-
-<p>Container membership properties may be applied to resources other than containers.</p>
-
-</section>
-
-<section id="ch_member" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h4 aria-level="3" role="heading" id="h4_ch_member"><span class="secno">5.1.6 </span>rdfs:member</h4>
-
-<p><code>rdfs:member</code> is an instance of <code><a href="#ch_property">rdf:Property</a></code> that is a super-property of all
-the container membership properties i.e. each container membership property
-has an <a href="#ch_subpropertyof"><code>rdfs:subPropertyOf</code></a>
-relationship to the property <code>rdfs:member</code>.</p>
-
-<p>The <a href="#ch_domain"><code>rdfs:domain</code></a> of
-<code>rdfs:member</code> is <code><a href="#ch_resource">rdfs:Resource</a></code>. The <a href="#ch_range"><code>rdfs:range</code></a> of <code>rdfs:member</code> is
-<code><a href="#ch_resource">rdfs:Resource</a></code>.</p>
-
-</section>
-</section>
-
-<section id="ch_collectionvocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_collectionvocab"><span class="secno">5.2 </span>RDF Collections</h3>
-
-<p>RDF containers are open in the sense that the core RDF specifications
-define no mechanism to state that there are no more members. The RDF
-Collection vocabulary of classes and properties can describe a closed
-collection, i.e. one that can have no more members. The reader is referred to
-the <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#collections">collections</a>
-section of the RDF 2004 primer for an informal introduction to collections with
-examples.</p>
-
-<p>A collection is represented as a list of items, a representation that
-will be familiar to those with experience of Lisp and similar
-programming languages. There is a <a href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/#section-Syntax-parsetype-Collection">shorthand notation</a> in the RDF/XML syntax specification for representing collections.</p>
-
-<div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_2"><span>Note</span></div><div class="">
-RDFS does not require that there be only one
-first element of a list-like structure, or even that a list-like structure
-have a first element.
-</div></div>
-
-<section id="ch_list" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h4 aria-level="3" role="heading" id="h4_ch_list"><span class="secno">5.2.1 </span>rdf:List</h4>
-
-<p><code>rdf:List</code> is an instance of <a href="#ch_class"><code>rdfs:Class</code></a>
-that can be used to build descriptions of lists and other list-like structures.
-</p>
-
-</section>
-
-<section id="ch_first" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h4 aria-level="3" role="heading" id="h4_ch_first"><span class="secno">5.2.2 </span>rdf:first</h4>
-
-<p><code>rdf:first</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a> that can be used to
-build descriptions of lists and other list-like structures.
-</p>
-
-<p>A triple of the form:</p>
-
-<blockquote>
- <code>L rdf:first O</code>
-</blockquote>
-
-<p>states that there is a first-element relationship between L and O.</p>
-
-<p>
-The <a href="#ch_domain"><code>rdfs:domain</code></a> of
-<code>rdf:first</code> is <code><a href="#ch_list">rdf:List</a></code>.
-The <a href="#ch_range"><code>rdfs:range</code></a> of
-<code>rdf:first</code> is <code><a href="#ch_resource">rdfs:Resource</a></code>.
-</p>
-
-</section>
-
-<section id="ch_rest" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h4 aria-level="3" role="heading" id="h4_ch_rest"><span class="secno">5.2.3 </span>rdf:rest</h4>
-
-<p><code>rdf:rest</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a> that can be used to
-build descriptions of lists and other list-like structures.
-</p>
-
-<p>A triple of the form:</p>
-
-<blockquote>
- <code>L rdf:rest O</code>
-</blockquote>
-
-<p>states that there is a rest-of-list relationship between L and O.</p>
-
-<p>
-The <a href="#ch_domain"><code>rdfs:domain</code></a> of
-<code>rdf:rest</code> is <code><a href="#ch_list">rdf:List</a></code>.
-The <a href="#ch_range"><code>rdfs:range</code></a> of
-<code>rdf:rest</code> is <code><a href="#ch_list">rdf:List</a></code>.
-
-</p>
-
-</section>
-
-<section id="ch_nil" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h4 aria-level="3" role="heading" id="h4_ch_nil"><span class="secno">5.2.4 </span>rdf:nil</h4>
-
-<p>The resource <code>rdf:nil</code> is an instance of <code><a href="#ch_list">rdf:List</a></code> that can be used to represent an
-empty list or other list-like structure.</p>
-
-<p>A triple of the form:</p>
+ <p>Additional classes and properties, including constructs for
+ representing
+ containers and RDF statements, and for deploying RDF vocabulary
+ descriptions
+ in the World Wide Web, are defined in this section.</p>
+ <section class="informative" id="ch_containervocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_containervocab"><span class="secno">5.1 </span>Container Classes and Properties</h3><p><em>This section is non-normative.</em></p>
+ <p>RDF containers are resources that are used to represent collections.
+ The same resource may appear in a container more than
+ once. Unlike containment in the physical world, a container may be
+ contained in itself.</p>
+ <p>Three different kinds of container are defined. Whilst the formal
+ semantics [<cite><a class="bibref" href="#bib-RDF11-MT">RDF11-MT</a></cite>] of all three classes of container are
+ identical,
+ different classes may be used to indicate informally further
+ information. An rdf:Bag is used to indicate that the container is
+ intended to be unordered. An rdf:Seq is used to indicate that the
+ order indicated by the numerical order of the <a href="#ch_containermembershipproperty">container
+ membership properties</a>
+ of the container is intended to be significant. An rdf:Alt container
+ is used
+ to indicate that typical processing of the container will be to select
+ one of
+ the members.</p>
+ <p>Just as a hen house may have the property that it is made of wood,
+ that
+ does not mean that all the hens it contains are made of wood, a
+ property of a
+ container is not necessarily a property of all of its members.</p>
+ <p>RDF containers are defined by the following classes and properties.</p>
+ <section id="ch_container" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h4 aria-level="3" role="heading" id="h4_ch_container"><span class="secno">5.1.1 </span>rdfs:Container</h4>
+ <p>The <code>rdfs:Container</code> class is a super-class of the RDF
+ Container classes, i.e. <code><a href="#ch_bag">rdf:Bag</a></code>,
+ <code><a href="#ch_seq">rdf:Seq</a></code>, <code><a href="#ch_alt">rdf:Alt</a></code>.</p>
+ </section>
+ <section id="ch_bag" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h4 aria-level="3" role="heading" id="h4_ch_bag"><span class="secno">5.1.2 </span>rdf:Bag</h4>
+ <p>The <code>rdf:Bag</code> class is the class of RDF 'Bag'
+ containers. It is
+ a <a href="#def-subclass">subclass</a> of <code><a href="#ch_container">rdfs:Container</a></code>.
+ Whilst formally it is no
+ different from an <code><a href="#ch_seq">rdf:Seq</a></code> or an
+ <code><a href="#ch_alt">rdf:Alt</a></code>, the <code>rdf:Bag</code>
+ class is used
+ conventionally to indicate to a human reader that the container is
+ intended
+ to be unordered.</p>
+ </section>
+ <section id="ch_seq" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h4 aria-level="3" role="heading" id="h4_ch_seq"><span class="secno">5.1.3 </span>rdf:Seq</h4>
+ <p>The <code>rdf:Seq</code> class is the class of RDF 'Sequence'
+ containers.
+ It is a <a href="#def-subclass">subclass</a> of <code><a href="#ch_container">rdfs:Container</a></code>.
+ Whilst formally it is no
+ different from an <code><a href="#ch_bag">rdf:Bag</a></code> or an
+ <code><a href="#ch_alt">rdf:Alt</a></code>, the <code>rdf:Seq</code>
+ class is used
+ conventionally to indicate to a human reader that the numerical
+ ordering of
+ the <a href="#ch_containermembershipproperty">container membership
+ properties</a> of the container is intended to be significant.</p>
+ </section>
+ <section id="ch_alt" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h4 aria-level="3" role="heading" id="h4_ch_alt"><span class="secno">5.1.4 </span>rdf:Alt</h4>
+ <p>The <code>rdf:Alt</code> class is the class of RDF 'Alternative'
+ containers. It is a <a href="#def-subclass">subclass</a> of <code><a href="#ch_container">rdfs:Container</a></code>. Whilst formally
+ it is no
+ different from an <code><a href="#ch_seq">rdf:Seq</a></code> or an
+ <code><a href="#ch_bag">rdf:Bag</a></code>, the <code>rdf:Alt</code>
+ class is used
+ conventionally to indicate to a human reader that typical processing
+ will be
+ to select one of the members of the container. The first member of
+ the
+ container, i.e. the value of the <code><a href="#ch_containermembershipproperty">rdf:_1</a></code>
+ property, is the
+ default choice.</p>
+ </section>
+ <section id="ch_containermembershipproperty" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h4 aria-level="3" role="heading" id="h4_ch_containermembershipproperty"><span class="secno">5.1.5 </span>rdfs:ContainerMembershipProperty</h4>
+ <p>The <code>rdfs:ContainerMembershipProperty</code> class has as
+ instances
+ the properties <code>rdf:_1, rdf:_2, rdf:_3 ...</code> that are
+ used to state
+ that a resource is a member of a container.
+ <code>rdfs:ContainerMembershipProperty</code> is a <a href="#def-subclass">subclass</a>
+ of <a href="#ch_property"><code>rdf:Property</code></a>. Each
+ instance of
+ <code>rdfs:ContainerMembershipProperty</code> is an <a href="#ch_subpropertyof"><code>rdfs:subPropertyOf</code></a>
+ the <code><a href="#ch_member">rdfs:member</a></code> property.</p>
+ <p>Given a container C, a triple of the form:</p>
+ <blockquote> <code>C rdf:_nnn O</code>
+ </blockquote>
+ <p>where <code>nnn</code> is the decimal representation of an integer
+ greater than 0 with
+ no leading zeros, states that O is a member of the container C.</p>
+ <p>Container membership properties may be applied to resources other
+ than containers.</p>
+ </section>
+ <section id="ch_member" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h4 aria-level="3" role="heading" id="h4_ch_member"><span class="secno">5.1.6 </span>rdfs:member</h4>
+ <p><code>rdfs:member</code> is an instance of <code><a href="#ch_property">rdf:Property</a></code>
+ that is a super-property of all
+ the container membership properties i.e. each container membership
+ property
+ has an <a href="#ch_subpropertyof"><code>rdfs:subPropertyOf</code></a>
+ relationship to the property <code>rdfs:member</code>.</p>
+ <p>The <a href="#ch_domain"><code>rdfs:domain</code></a> of
+ <code>rdfs:member</code> is <code><a href="#ch_resource">rdfs:Resource</a></code>.
+ The <a href="#ch_range"><code>rdfs:range</code></a> of <code>rdfs:member</code>
+ is
+ <code><a href="#ch_resource">rdfs:Resource</a></code>.</p>
+ </section>
+ </section>
+ <section class="informative" id="ch_collectionvocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_collectionvocab"><span class="secno">5.2 </span>RDF Collections</h3><p><em>This section is non-normative.</em></p>
+ <p>RDF containers are open in the sense that the core RDF specifications
+ define no mechanism to state that there are no more members. The RDF
+ Collection vocabulary of classes and properties can describe a closed
+ collection, i.e. one that can have no more members.</p>
+ <p>A collection is represented as a list of items, a representation that
+ will be familiar to those with experience of Lisp and similar
+ programming languages. There is a <a href="http://www.w3.org/TR/turtle/#collections">shorthand
+ notation</a> in the Turtle syntax specification for representing
+ collections.</p>
+ <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_2"><span>Note</span></div><p class="">
+ RDFS does not require that there be only one first element of a
+ list-like structure, or even that a list-like structure have a first
+ element.
+ </p></div>
+ <section id="ch_list" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h4 aria-level="3" role="heading" id="h4_ch_list"><span class="secno">5.2.1 </span>rdf:List</h4>
+ <p><code>rdf:List</code> is an instance of <a href="#ch_class"><code>rdfs:Class</code></a>
+ that can be used to build descriptions of lists and other list-like
+ structures.
+ </p>
+ </section>
+ <section id="ch_first" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h4 aria-level="3" role="heading" id="h4_ch_first"><span class="secno">5.2.2 </span>rdf:first</h4>
+ <p><code>rdf:first</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a>
+ that can be used to build descriptions of lists and other list-like
+ structures.
+ </p>
+ <p>A triple of the form:</p>
+ <blockquote> <code>L rdf:first O</code>
+ </blockquote>
+ <p>states that there is a first-element relationship between L and O.</p>
+ <p>
+ The <a href="#ch_domain"><code>rdfs:domain</code></a> of <code>rdf:first</code>
+ is <code><a href="#ch_list">rdf:List</a></code>. The <a href="#ch_range"><code>rdfs:range</code></a>
+ of <code>rdf:first</code> is <code><a href="#ch_resource">rdfs:Resource</a></code>.
+ </p>
+ </section>
+ <section id="ch_rest" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h4 aria-level="3" role="heading" id="h4_ch_rest"><span class="secno">5.2.3 </span>rdf:rest</h4>
+ <p><code>rdf:rest</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a>
+ that can be used to build descriptions of lists and other list-like
+ structures.
+ </p>
+ <p>A triple of the form:</p>
+ <blockquote> <code>L rdf:rest O</code>
+ </blockquote>
+ <p>states that there is a rest-of-list relationship between L and O.</p>
+ <p>
+ The <a href="#ch_domain"><code>rdfs:domain</code></a> of <code>rdf:rest</code>
+ is <code><a href="#ch_list">rdf:List</a></code>. The <a href="#ch_range"><code>rdfs:range</code></a>
+ of <code>rdf:rest</code> is <code><a href="#ch_list">rdf:List</a></code>.
+ </p>
+ </section>
+ <section id="ch_nil" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h4 aria-level="3" role="heading" id="h4_ch_nil"><span class="secno">5.2.4 </span>rdf:nil</h4>
+ <p>The resource <code>rdf:nil</code> is an instance of <code><a href="#ch_list">rdf:List</a></code>
+ that can be used to represent an empty list or other list-like
+ structure.</p>
+ <p>A triple of the form:</p>
+ <blockquote> <code>L rdf:rest rdf:nil</code>
+ </blockquote>
+ <p>states that L is an instance of <code><a href="#ch_list">rdf:List</a></code>
+ that has one item; that item can be indicated using the <code><a href="#ch_first">rdf:first</a></code>
+ property.</p>
+ </section>
+ </section>
+ <section class="informative" id="ch_reificationvocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">>
+ <h3 aria-level="2" role="heading" id="h3_ch_reificationvocab"><span class="secno">5.3 </span>Reification Vocabulary</h3><p><em>This section is non-normative.</em></p>
+
+<!--
+<p>The 1999 RDF Model and Syntax Specification [[RDFMS]] defined a vocabulary for describing RDF statements without stating them.
+The 2004 RDF specification did not assign a normative formal semantics to this vocabulary. However, an intended meaning of
+this vocabulary (which generally clarifies the intent of the RDFMS definition) is described here.
+An informal introduction to the reification vocabulary, with examples, may be found in the <a
+href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#reification">RDF2004 primer</a>.
+</p>-->
-<blockquote>
- <code>L rdf:rest rdf:nil</code>
-</blockquote>
-
-<p>states that L is an instance of <code><a href="#ch_list">rdf:List</a></code> that has one item; that item can be
-indicated using the <code><a href="#ch_first">rdf:first</a></code> property.</p>
-
-</section>
-</section>
-
-<section id="ch_reificationvocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_reificationvocab"><span class="secno">5.3 </span>Reification Vocabulary</h3>
-
-
-<!--
-<p>The 1999 RDF Model and Syntax Specification [[RDFMS]] defined a
-vocabulary for describing RDF statements without stating them.
-The 2004 RDF specification did not assign a normative
-formal semantics to this vocabulary. However, an intended meaning of
-this vocabulary (which generally clarifies the intent of the
-RDFMS definition) is described here.
-An informal introduction to the reification vocabulary, with examples,
-may be found in the <a
-href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#reification">RDF
-2004 primer</a>.
-</p>
--->
-
-
-<section id="ch_statement" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h4 aria-level="3" role="heading" id="h4_ch_statement"><span class="secno">5.3.1 </span>rdf:Statement</h4>
-
-<p><code>rdf:Statement</code> is an instance of
-<code><a href="#ch_class">rdfs:Class.</a></code>
-It is intended to represent the class of RDF statements. An RDF statement is the
-statement made by a token of an RDF triple.
-The subject of an RDF statement is the instance of
-<code><a href="#ch_resource">rdfs:Resource</a></code>
-identified by the subject of the triple. The predicate of an RDF
-statement is the instance of <code><a href="#ch_property">rdf:Property</a></code>
-identified by the predicate
-of the triple. The object of an RDF statement is the instance of
-<code><a href="#ch_resource">rdfs:Resource</a></code>
-identified by the object of the triple.
-<code>rdf:Statement</code>
-is in the domain of the properties
-<code><a href="#ch_predicate">rdf:predicate</a></code>,
-<code><a href="#ch_subject">rdf:subject</a></code>
-and
-<code><a href="#ch_object">rdf:object</a></code>.
-Different individual <code>rdf:Statement</code>
-instances may have the same values for their
-<code><a href="#ch_predicate">rdf:predicate</a></code>,
-<code><a href="#ch_subject">rdf:subject</a></code>
-and <code><a href="#ch_object">rdf:object</a></code> properties.
-</p>
-
-</section>
-
-<section id="ch_subject" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h4 aria-level="3" role="heading" id="h4_ch_subject"><span class="secno">5.3.2 </span>rdf:subject</h4>
-
-<p><code>rdf:subject</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a> that is used to state the
-subject of a statement.</p>
-
-<p>A triple of the form:</p>
-
-<blockquote>
- <code>S rdf:subject R</code>
-</blockquote>
-
-<p>states that S is an instance of <code><a href="#ch_statement">rdf:Statement</a></code> and that the subject of S is
-R.</p>
-
-<p class="schemacomment">The <a href="#ch_domain"><code>rdfs:domain</code></a> of <code>rdf:subject</code> is
-<code><a href="#ch_statement">rdf:Statement</a></code>. The <a href="#ch_range"><code>rdfs:range</code></a> of <code>rdf:subject</code> is
-<code><a href="#ch_resource">rdfs:Resource</a></code>.</p>
-
-</section>
-
-<section id="ch_predicate" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h4 aria-level="3" role="heading" id="h4_ch_predicate"><span class="secno">5.3.3 </span>rdf:predicate</h4>
-
-<p>rdf:predicate is an instance of <a href="#ch_property"><code>rdf:Property</code></a> that is used to state the
-predicate of a statement.</p>
-
-<p>A triple of the form:</p>
-
-<blockquote>
- <code>S rdf:predicate P</code>
-</blockquote>
-
-<p>states that S is an instance of <code><a href="#ch_statement">rdf:Statement</a></code>, that P is an instance of
-<code><a href="#ch_property">rdf:Property</a></code> and that the predicate
-of S is P.</p>
-
-<p>The <a href="#ch_domain"><code>rdfs:domain</code></a> of
-<code>rdf:predicate</code> is <code><a href="#ch_statement">rdf:Statement</a></code> and the <a href="#ch_range"><code>rdfs:range</code></a> is <a href="#ch_resource"><code>rdfs:Resource</code></a>.</p>
-
-</section>
-
-<section id="ch_object" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h4 aria-level="3" role="heading" id="h4_ch_object"><span class="secno">5.3.4 </span>rdf:object</h4>
-
-<p>rdf:object is an instance of <a href="#ch_property"><code>rdf:Property</code></a> that is used to state the
-object of a statement.</p>
-
-<p>A triple of the form:</p>
-
-<blockquote>
- <code>S rdf:object O</code>
-</blockquote>
-
-<p>states that S is an instance of <code><a href="#ch_statement">rdf:Statement</a></code> and that the object of S is
-O.</p>
-
-<p>The <a href="#ch_domain"><code>rdfs:domain</code></a> of
-<code>rdf:object</code> is <code><a href="#ch_statement">rdf:Statement</a></code>. The <a href="#ch_range"><code>rdfs:range</code></a> of <code>rdf:object</code> is
-<code><a href="#ch_resource">rdfs:Resource</a></code>.</p>
-
-</section>
-</section>
-
-<section id="ch_utilvocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-
-<h3 aria-level="2" role="heading" id="h3_ch_utilvocab"><span class="secno">5.4 </span>Utility Properties</h3>
-
-<p>The following utility classes and properties are defined in the RDF core
-namespaces.</p>
-
-<section id="ch_seealso" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-
-<h4 aria-level="3" role="heading" id="h4_ch_seealso"><span class="secno">5.4.1 </span>rdfs:seeAlso</h4>
-
-<p><code>rdfs:seeAlso</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a> that is used to indicate a
-resource that might provide additional information about the subject
-resource.</p>
-
-<p>A triple of the form:</p>
-
-<blockquote>
- <code>S rdfs:seeAlso O</code>
-</blockquote>
-
-<p>states that the resource O may provide additional information about S. It
-may be possible to retrieve representations of O from the Web, but this is
-not required. When such representations may be retrieved, no constraints are
-placed on the format of those representations.</p>
-
-<p>The <code><a href="#ch_domain">rdfs:domain</a></code> of
-<code>rdfs:seeAlso</code> is <code><a href="#ch_resource">rdfs:Resource</a></code>. The <code><a href="#ch_range">rdfs:range</a></code> of <code>rdfs:seeAlso</code> is
-<code><a href="#ch_resource">rdfs:Resource</a></code>.</p>
-
-</section>
-
-<section id="ch_isdefinedby" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-
-<h4 aria-level="3" role="heading" id="h4_ch_isdefinedby"><span class="secno">5.4.2 </span>rdfs:isDefinedBy</h4>
-
-<p><code>rdfs:isDefinedBy</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a> that is used to indicate a
-resource defining the subject resource. This property may be used to indicate
-an RDF vocabulary in which a resource is described.</p>
-
-<p>A triple of the form:</p>
-
-<blockquote>
- <code>S rdfs:isDefinedBy O</code>
-</blockquote>
-
-<p>states that the resource O defines S. It may be possible to retrieve
-representations of O from the Web, but this is not required. When such
-representations may be retrieved, no constraints are placed on the format of
-those representations. <code>rdfs:isDefinedBy</code> is a <a href="#def-subproperty">subproperty</a> of <code><a href="#ch_seealso">rdfs:seeAlso</a></code>.</p>
-
-<p>The <code><a href="#ch_domain">rdfs:domain</a></code> of
-<code>rdfs:isDefinedBy</code> is <code><a href="#ch_resource">rdfs:Resource</a></code>. The <code><a href="#ch_range">rdfs:range</a></code> of <code>rdfs:isDefinedBy</code> is
-<code><a href="#ch_resource">rdfs:Resource</a></code>.</p>
-
-</section>
-
-<section id="ch_value" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-
-<h4 aria-level="3" role="heading" id="h4_ch_value"><span class="secno">5.4.3 </span>rdf:value</h4>
-
-<p><code>rdf:value</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a> that may be used in
-describing structured values.</p>
-
-<p>rdf:value has no meaning on its own. It is provided as a piece of
-vocabulary that may be used in idioms such as illustrated in <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example21">example
-21</a> of the RDF 1.0 primer. Despite
-the lack of formal specification of the meaning of this property, there is
-value in defining it to encourage the use of a common idiom in examples of
-this kind.</p>
-
-<p>The <code><a href="#ch_domain">rdfs:domain</a></code> of
-<code>rdf:value</code> is <code><a href="#ch_resource">rdfs:Resource</a></code>. The <code><a href="#ch_range">rdfs:range</a></code> of <code>rdf:value</code> is <code><a href="#ch_resource">rdfs:Resource</a></code>.</p>
-
-</section>
-</section>
-</section>
-
-<section id="ch_summary" class="informative" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-
-
+ <section id="ch_statement" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h4 aria-level="3" role="heading" id="h4_ch_statement"><span class="secno">5.3.1 </span>rdf:Statement</h4>
+ <p><code>rdf:Statement</code> is an instance of <code><a href="#ch_class">rdfs:Class.</a></code>
+ It is intended to represent the class of RDF statements. An RDF
+ statement is the statement made by a token of an RDF triple. The
+ subject of an RDF statement is the instance of <code><a href="#ch_resource">rdfs:Resource</a></code>
+ identified by the subject of the triple. The predicate of an RDF
+ statement is the instance of <code><a href="#ch_property">rdf:Property</a></code>
+ identified by the predicate of the triple. The object of an RDF
+ statement is the instance of <code><a href="#ch_resource">rdfs:Resource</a></code>
+ identified by the object of the triple.
+ <code>rdf:Statement</code> is in the domain of the properties <code><a href="#ch_predicate">rdf:predicate</a></code>, <code><a href="#ch_subject">rdf:subject</a></code>
+ and <code><a href="#ch_object">rdf:object</a></code>. Different
+ individual <code>rdf:Statement</code> instances may have the same
+ values for their <code><a href="#ch_predicate">rdf:predicate</a></code>,
+ <code><a href="#ch_subject">rdf:subject</a></code>
+ and <code><a href="#ch_object">rdf:object</a></code> properties.
+ </p>
+ </section>
+ <section id="ch_subject" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h4 aria-level="3" role="heading" id="h4_ch_subject"><span class="secno">5.3.2 </span>rdf:subject</h4>
+ <p><code>rdf:subject</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a>
+ that is used to state the
+ subject of a statement.</p>
+ <p>A triple of the form:</p>
+ <blockquote> <code>S rdf:subject R</code>
+ </blockquote>
+ <p>states that S is an instance of <code><a href="#ch_statement">rdf:Statement</a></code>
+ and that the subject of S is
+ R.</p>
+ <p class="schemacomment">The <a href="#ch_domain"><code>rdfs:domain</code></a>
+ of <code>rdf:subject</code> is
+ <code><a href="#ch_statement">rdf:Statement</a></code>. The <a href="#ch_range"><code>rdfs:range</code></a>
+ of <code>rdf:subject</code> is
+ <code><a href="#ch_resource">rdfs:Resource</a></code>.</p>
+ </section>
+ <section id="ch_predicate" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h4 aria-level="3" role="heading" id="h4_ch_predicate"><span class="secno">5.3.3 </span>rdf:predicate</h4>
+ <p>rdf:predicate is an instance of <a href="#ch_property"><code>rdf:Property</code></a>
+ that is used to state the
+ predicate of a statement.</p>
+ <p>A triple of the form:</p>
+ <blockquote> <code>S rdf:predicate P</code>
+ </blockquote>
+ <p>states that S is an instance of <code><a href="#ch_statement">rdf:Statement</a></code>,
+ that P is an instance of
+ <code><a href="#ch_property">rdf:Property</a></code> and that the
+ predicate
+ of S is P.</p>
+ <p>The <a href="#ch_domain"><code>rdfs:domain</code></a> of
+ <code>rdf:predicate</code> is <code><a href="#ch_statement">rdf:Statement</a></code>
+ and the <a href="#ch_range"><code>rdfs:range</code></a> is <a href="#ch_resource"><code>rdfs:Resource</code></a>.</p>
+ </section>
+ <section id="ch_object" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h4 aria-level="3" role="heading" id="h4_ch_object"><span class="secno">5.3.4 </span>rdf:object</h4>
+ <p>rdf:object is an instance of <a href="#ch_property"><code>rdf:Property</code></a>
+ that is used to state the
+ object of a statement.</p>
+ <p>A triple of the form:</p>
+ <blockquote> <code>S rdf:object O</code>
+ </blockquote>
+ <p>states that S is an instance of <code><a href="#ch_statement">rdf:Statement</a></code>
+ and that the object of S is
+ O.</p>
+ <p>The <a href="#ch_domain"><code>rdfs:domain</code></a> of
+ <code>rdf:object</code> is <code><a href="#ch_statement">rdf:Statement</a></code>.
+ The <a href="#ch_range"><code>rdfs:range</code></a> of <code>rdf:object</code>
+ is
+ <code><a href="#ch_resource">rdfs:Resource</a></code>.</p>
+ </section>
+ </section>
+ <section id="ch_utilvocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_utilvocab"><span class="secno">5.4 </span>Utility Properties</h3>
+ <p>The following utility classes and properties are defined in the RDF
+ core
+ namespaces.</p>
+ <section id="ch_seealso" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h4 aria-level="3" role="heading" id="h4_ch_seealso"><span class="secno">5.4.1 </span>rdfs:seeAlso</h4>
+ <p><code>rdfs:seeAlso</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a>
+ that is used to indicate a
+ resource that might provide additional information about the subject
+ resource.</p>
+ <p>A triple of the form:</p>
+ <blockquote> <code>S rdfs:seeAlso O</code>
+ </blockquote>
+ <p>states that the resource O may provide additional information about
+ S. It
+ may be possible to retrieve representations of O from the Web, but
+ this is
+ not required. When such representations may be retrieved, no
+ constraints are
+ placed on the format of those representations.</p>
+ <p>The <code><a href="#ch_domain">rdfs:domain</a></code> of
+ <code>rdfs:seeAlso</code> is <code><a href="#ch_resource">rdfs:Resource</a></code>.
+ The <code><a href="#ch_range">rdfs:range</a></code> of <code>rdfs:seeAlso</code>
+ is
+ <code><a href="#ch_resource">rdfs:Resource</a></code>.</p>
+ </section>
+ <section id="ch_isdefinedby" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h4 aria-level="3" role="heading" id="h4_ch_isdefinedby"><span class="secno">5.4.2 </span>rdfs:isDefinedBy</h4>
+ <p><code>rdfs:isDefinedBy</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a>
+ that is used to indicate a
+ resource defining the subject resource. This property may be used to
+ indicate
+ an RDF vocabulary in which a resource is described.</p>
+ <p>A triple of the form:</p>
+ <blockquote> <code>S rdfs:isDefinedBy O</code>
+ </blockquote>
+ <p>states that the resource O defines S. It may be possible to
+ retrieve
+ representations of O from the Web, but this is not required. When
+ such
+ representations may be retrieved, no constraints are placed on the
+ format of
+ those representations. <code>rdfs:isDefinedBy</code> is a <a href="#def-subproperty">subproperty</a>
+ of <code><a href="#ch_seealso">rdfs:seeAlso</a></code>.</p>
+ <p>The <code><a href="#ch_domain">rdfs:domain</a></code> of
+ <code>rdfs:isDefinedBy</code> is <code><a href="#ch_resource">rdfs:Resource</a></code>.
+ The <code><a href="#ch_range">rdfs:range</a></code> of <code>rdfs:isDefinedBy</code>
+ is
+ <code><a href="#ch_resource">rdfs:Resource</a></code>.</p>
+ </section>
+ <section id="ch_value" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h4 aria-level="3" role="heading" id="h4_ch_value"><span class="secno">5.4.3 </span>rdf:value</h4>
+ <p><code>rdf:value</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a>
+ that may be used in
+ describing structured values.</p>
+ <p>rdf:value has no meaning on its own. It is provided as a piece of
+ vocabulary that may be used in idioms such as illustrated
+ in example below:</p>
+ <div class="example"><div class="example-title"><span>Example 1</span></div><pre class="example"><http://www.example.com/2002/04/products#item10245>
+ <http://www.example.org/terms/weight> [
+ rdf:value 2.4 ;
+ <http://www.example.org/terms/units> <http://www.example.org/units/kilograms>
+ ] .</pre></div>
+ Despite
+ the lack of formal specification of the meaning of this property,
+ there is
+ value in defining it to encourage the use of a common idiom in
+ examples of
+ this kind.<p></p>
+ <p>The <code><a href="#ch_domain">rdfs:domain</a></code> of
+ <code>rdf:value</code> is <code><a href="#ch_resource">rdfs:Resource</a></code>.
+ The <code><a href="#ch_range">rdfs:range</a></code> of <code>rdf:value</code>
+ is <code><a href="#ch_resource">rdfs:Resource</a></code>.</p>
+ </section>
+ </section>
+ </section>
+ <section id="ch_summary" class="informative" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
<!--OddPage-->
<h2 aria-level="1" role="heading" id="h2_ch_summary"><span class="secno">6. </span>RDF Schema summary</h2><p><em>This section is non-normative.</em></p>
-
-<p>This table presents an overview of the vocabulary of RDF, drawing together
-vocabulary originally defined in the RDF Model and Syntax
-specification [<cite><a class="bibref" href="#bib-RDFMS">RDFMS</a></cite>] with
-classes and properties that originate with RDF Schema.</p>
-
-<section id="ch_sumclasses" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-
-<h3 aria-level="2" role="heading" id="h3_ch_sumclasses"><span class="secno">6.1 </span>RDF classes</h3>
-
-<table border="1">
- <tbody>
- <tr>
- <th>Class name</th>
- <th>comment</th>
- </tr>
- <tr>
- <td>rdfs:Resource</td>
- <td>The class resource, everything.</td>
- </tr>
- <tr>
- <td>rdfs:Literal</td>
- <td>The class of literal values, e.g. textual strings and integers.</td>
- </tr>
- <tr>
- <td>rdf:langString</td>
- <td>The class of language-tagged string literal values.</td>
- </tr>
- <tr>
- <td>rdf:HTML</td>
- <td>The class of HTML literal values.</td>
- </tr>
- <tr>
- <td>rdf:XMLLiteral</td>
- <td>The class of XML literal values.</td>
- </tr>
- <tr>
- <td>rdfs:Class</td>
- <td>The class of classes.</td>
- </tr>
- <tr>
- <td>rdf:Property</td>
- <td>The class of RDF properties.</td>
- </tr>
- <tr>
- <td>rdfs:Datatype</td>
- <td>The class of RDF datatypes.</td>
- </tr>
- <tr>
- <td>rdf:Statement</td>
- <td>The class of RDF statements.</td>
- </tr>
- <tr>
- <td>rdf:Bag</td>
- <td>The class of unordered containers.</td>
- </tr>
- <tr>
- <td>rdf:Seq</td>
- <td>The class of ordered containers.</td>
- </tr>
- <tr>
- <td>rdf:Alt</td>
- <td>The class of containers of alternatives.</td>
- </tr>
- <tr>
- <td>rdfs:Container</td>
- <td>The class of RDF containers.</td>
- </tr>
- <tr>
- <td>rdfs:ContainerMembershipProperty</td>
- <td>The class of container membership properties, rdf:_1, rdf:_2, ...,
- all of which are sub-properties of 'member'.</td>
- </tr>
- <tr>
- <td>rdf:List</td>
- <td>The class of RDF Lists.</td>
- </tr>
- </tbody>
-</table>
-
-</section>
-
-<section id="ch_sumproperties" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-
-<h3 aria-level="2" role="heading" id="h3_ch_sumproperties"><span class="secno">6.2 </span>RDF properties</h3>
+ <p>The tables in this section provide an overview of the RDF Schema vocabulary.</p>
+
+<!-- of RDF, drawing together
+ vocabulary originally defined in the RDF Model and Syntax
+ specification [[RDFMS]] with
+ classes and properties that originate with RDF Schema.
+ -->
-<table border="1">
- <tbody>
- <tr>
- <th>Property name</th>
- <th>comment</th>
- <th>domain</th>
- <th>range</th>
- </tr>
- <tr>
- <td>rdf:type</td>
- <td>The subject is an instance of a class.</td>
- <td>rdfs:Resource</td>
- <td>rdfs:Class</td>
- </tr>
- <tr>
- <td>rdfs:subClassOf</td>
- <td>The subject is a subclass of a class.</td>
- <td>rdfs:Class</td>
- <td>rdfs:Class</td>
- </tr>
- <tr>
- <td>rdfs:subPropertyOf</td>
- <td>The subject is a subproperty of a property.</td>
- <td>rdf:Property</td>
- <td>rdf:Property</td>
- </tr>
- <tr>
- <td>rdfs:domain</td>
- <td>A domain of the subject property.</td>
- <td>rdf:Property</td>
- <td>rdfs:Class</td>
- </tr>
- <tr>
- <td>rdfs:range</td>
- <td>A range of the subject property.</td>
- <td>rdf:Property</td>
- <td>rdfs:Class</td>
- </tr>
- <tr>
- <td>rdfs:label</td>
- <td>A human-readable name for the subject.</td>
- <td>rdfs:Resource</td>
- <td>rdfs:Literal</td>
- </tr>
- <tr>
- <td>rdfs:comment</td>
- <td>A description of the subject resource.</td>
- <td>rdfs:Resource</td>
- <td>rdfs:Literal</td>
- </tr>
- <tr>
- <td>rdfs:member</td>
- <td>A member of the subject resource.</td>
- <td>rdfs:Resource</td>
- <td>rdfs:Resource</td>
- </tr>
- <tr>
- <td>rdf:first</td>
- <td>The first item in the subject RDF list.</td>
- <td>rdf:List</td>
- <td>rdfs:Resource</td>
- </tr>
- <tr>
- <td>rdf:rest</td>
- <td>The rest of the subject RDF list after the first item.</td>
- <td>rdf:List</td>
- <td>rdf:List</td>
- </tr>
- <tr>
- <td>rdfs:seeAlso</td>
- <td>Further information about the subject resource.</td>
- <td>rdfs:Resource</td>
- <td>rdfs:Resource</td>
- </tr>
- <tr>
- <td>rdfs:isDefinedBy</td>
- <td>The definition of the subject resource.</td>
- <td>rdfs:Resource</td>
- <td>rdfs:Resource</td>
- </tr>
- <tr>
- <td>rdf:value</td>
- <td>Idiomatic property used for structured values (see the RDF Primer for <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example16">an
- example</a> of its usage).</td>
- <td>rdfs:Resource</td>
- <td>rdfs:Resource</td>
- </tr>
- <tr>
- <td>rdf:subject</td>
- <td>The subject of the subject RDF statement.</td>
- <td>rdf:Statement</td>
- <td>rdfs:Resource</td>
- </tr>
- <tr>
- <td>rdf:predicate</td>
- <td>The predicate of the subject RDF statement.</td>
- <td>rdf:Statement</td>
- <td>rdfs:Resource</td>
- </tr>
- <tr>
- <td>rdf:object</td>
- <td>The object of the subject RDF statement.</td>
- <td>rdf:Statement</td>
- <td>rdfs:Resource</td>
- </tr>
- </tbody>
-</table>
-
-<p>In addition to these classes and properties, RDF also uses properties
-called <code>rdf:_1</code>, <code>rdf:_2</code>, <code>rdf:_3</code>... etc.,
-each of which is both a sub-property of <code>rdfs:member</code> and an
-instance of the class <code>rdfs:ContainerMembershipProperty</code>. There is
-also an instance of <code>rdf:List</code> called <code>rdf:nil</code> that is
-an empty <code>rdf:List</code>.</p>
-
-</section>
-</section>
-
-<section id="ch_acknowledgements" class="appendix informative" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-
-
+ <section id="ch_sumclasses" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_sumclasses"><span class="secno">6.1 </span>RDF classes</h3>
+ <table border="1">
+ <tbody>
+ <tr>
+ <th>Class name</th>
+ <th>comment</th>
+ </tr>
+ <tr>
+ <td><a href="#ch_resource">rdfs:Resource</a></td>
+ <td>The class resource, everything.</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_literal">rdfs:Literal</a></td>
+ <td>The class of literal values, e.g. textual strings and
+ integers.</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_langstring">rdf:langString</a></td>
+ <td>The class of language-tagged string literal values.</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_html">rdf:HTML</a></td>
+ <td>The class of HTML literal values.</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_xmlliteral">rdf:XMLLiteral</a></td>
+ <td>The class of XML literal values.</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_class">rdfs:Class</a></td>
+ <td>The class of classes.</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_property">rdf:Property</a></td>
+ <td>The class of RDF properties.</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_datatype">rdfs:Datatype</a></td>
+ <td>The class of RDF datatypes.</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_statement">rdf:Statement</a></td>
+ <td>The class of RDF statements.</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_bag">rdf:Bag</a></td>
+ <td>The class of unordered containers.</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_seq">rdf:Seq</a></td>
+ <td>The class of ordered containers.</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_alt">rdf:Alt</a></td>
+ <td>The class of containers of alternatives.</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_container">rdfs:Container</a></td>
+ <td>The class of RDF containers.</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_containermembershipproperty">rdfs:ContainerMembershipProperty</a></td>
+ <td>The class of container membership properties, rdf:_1, rdf:_2,
+ ..., all of which are sub-properties of 'member'.</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_list">rdf:List</a></td>
+ <td>The class of RDF Lists.</td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+ <section id="ch_sumproperties" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_ch_sumproperties"><span class="secno">6.2 </span>RDF properties</h3>
+ <table border="1">
+ <tbody>
+ <tr>
+ <th>Property name</th>
+ <th>comment</th>
+ <th>domain</th>
+ <th>range</th>
+ </tr> <tr>
+ <td><a href="#ch_type">rdf:type</a></td>
+ <td>The subject is an instance of a class.</td>
+ <td>rdfs:Resource</td>
+ <td>rdfs:Class</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_subclassof">rdfs:subClassOf</a></td>
+ <td>The subject is a subclass of a class.</td>
+ <td>rdfs:Class</td>
+ <td>rdfs:Class</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_subpropertyof">rdfs:subPropertyOf</a></td>
+ <td>The subject is a subproperty of a property.</td>
+ <td>rdf:Property</td>
+ <td>rdf:Property</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_domain">rdfs:domain</a></td>
+ <td>A domain of the subject property.</td>
+ <td>rdf:Property</td>
+ <td>rdfs:Class</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_range">rdfs:range</a></td>
+ <td>A range of the subject property.</td>
+ <td>rdf:Property</td>
+ <td>rdfs:Class</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_label">rdfs:label</a></td>
+ <td>A human-readable name for the subject.</td>
+ <td>rdfs:Resource</td>
+ <td>rdfs:Literal</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_comment">rdfs:comment</a></td>
+ <td>A description of the subject resource.</td>
+ <td>rdfs:Resource</td>
+ <td>rdfs:Literal</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_member">rdfs:member</a></td>
+ <td>A member of the subject resource.</td>
+ <td>rdfs:Resource</td>
+ <td>rdfs:Resource</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_first">rdf:first</a></td>
+ <td>The first item in the subject RDF list.</td>
+ <td>rdf:List</td>
+ <td>rdfs:Resource</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_rest">rdf:rest</a></td>
+ <td>The rest of the subject RDF list after the first item.</td>
+ <td>rdf:List</td>
+ <td>rdf:List</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_seealso">rdfs:seeAlso</a></td>
+ <td>Further information about the subject resource.</td>
+ <td>rdfs:Resource</td>
+ <td>rdfs:Resource</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_isdefinedby">rdfs:isDefinedBy</a></td>
+ <td>The definition of the subject resource.</td>
+ <td>rdfs:Resource</td>
+ <td>rdfs:Resource</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_value">rdf:value</a></td>
+ <td>Idiomatic property used for structured values.</td>
+ <td>rdfs:Resource</td>
+ <td>rdfs:Resource</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_subject">rdf:subject</a></td>
+ <td>The subject of the subject RDF statement.</td>
+ <td>rdf:Statement</td>
+ <td>rdfs:Resource</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_predicate">rdf:predicate</a></td>
+ <td>The predicate of the subject RDF statement.</td>
+ <td>rdf:Statement</td>
+ <td>rdfs:Resource</td>
+ </tr>
+ <tr>
+ <td><a href="#ch_object">rdf:object</a></td>
+ <td>The object of the subject RDF statement.</td>
+ <td>rdf:Statement</td>
+ <td>rdfs:Resource</td>
+ </tr>
+ </tbody>
+ </table>
+ <p>In addition to these classes and properties, RDF also uses properties
+ called <code>rdf:_1</code>, <code>rdf:_2</code>, <code>rdf:_3</code>...
+ etc.,
+ each of which is both a sub-property of <code>rdfs:member</code> and
+ an
+ instance of the class <code>rdfs:ContainerMembershipProperty</code>.
+ There is
+ also an instance of <code>rdf:List</code> called <code>rdf:nil</code>
+ that is
+ an empty <code>rdf:List</code>.</p>
+ </section>
+ </section>
+ <section id="ch_acknowledgements" class="appendix informative" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
<!--OddPage-->
<h2 aria-level="1" role="heading" id="h2_ch_acknowledgements"><span class="secno">A. </span>Acknowledgments</h2><p><em>This section is non-normative.</em></p>
-
-<p>The RDF Schema design was originally produced by the RDF Schema Working
-Group (1997-2000). The current specification is largely an editorial
-clarification of that design, and has benefited greatly from the hard work of
-the <a href="http://www.w3.org/2001/sw/RDFCore/">RDF Core Working Group</a>
-<a href="http://www.w3.org/2001/sw/RDFCore/#Membership">members</a>, and from
-implementation feedback from many members of the <a href="http://www.w3.org/RDF/Interest/">RDF Interest Group</a>. In
-2013-2014 Guus Schreiber edited this document on behalf of the <a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a>
-to bring it in line with the RDF 1.1 specifications. </p>
-
-<p>David Singer of IBM was the chair of the original RDF Schema group
-throughout most of the development of this specification; we thank David for
-his efforts and thank IBM for supporting him and us in this endeavor.
-Particular thanks are also due to Andrew Layman for his editorial work on
-early versions of this specification.</p>
-
-<p>The original RDF Schema Working Group membership included:</p>
-
-<p>Nick Arnett (Verity), Dan Brickley (ILRT / University of Bristol), Walter
-Chang (Adobe), Sailesh Chutani (Oracle), Ron Daniel (DATAFUSION), Charles
-Frankston (Microsoft), Joe Lapp (webMethods Inc.), Patrick Gannon
-(CommerceNet), RV Guha (Epinions, previously of Netscape Communications), Tom
-Hill (Apple Computer), Renato Iannella (DSTC), Sandeep Jain (Oracle), Kevin
-Jones, (InterMind), Emiko Kezuka (Digital Vision Laboratories), Ora Lassila
-(Nokia Research Center), Andrew Layman (Microsoft), John McCarthy (Lawrence
-Berkeley National Laboratory), Michael Mealling (Network Solutions), Norbert
-Mikula (DataChannel), Eric Miller (OCLC), Frank Olken (Lawrence Berkeley
-National Laboratory), Sri Raghavan (Digital/Compaq), Lisa Rein (webMethods
-Inc.), Tsuyoshi Sakata (Digital Vision Laboratories), Leon Shklar (Pencom Web
-Works), David Singer (IBM), Wei (William) Song (SISU), Neel Sundaresan (IBM),
-Ralph Swick (<abbr title="World Wide Web Consortium">W3C</abbr>), Naohiko Uramoto (IBM), Charles Wicksteed (Reuters Ltd.),
-Misha Wolf (Reuters Ltd.)</p>
-
-</section>
-
-<section id="changes" class="appendix informative" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-
-
+ <p>The RDF Schema design was originally produced by the RDF Schema Working
+ Group (1997-2000). The current specification is largely an editorial
+ clarification of that design, and has benefited greatly from the hard
+ work of
+ the <a href="http://www.w3.org/2001/sw/RDFCore/">RDF Core Working Group</a>
+ <a href="http://www.w3.org/2001/sw/RDFCore/#Membership">members</a>, and
+ from
+ implementation feedback from many members of the <a href="http://www.w3.org/RDF/Interest/">RDF
+ Interest Group</a>. In
+ 2013-2014 Guus Schreiber edited this document on behalf of the <a href="http://www.w3.org/2011/rdf-wg/">RDF
+ Working Group</a>
+ to bring it in line with the RDF 1.1 specifications. </p>
+ <p>David Singer of IBM was the chair of the original RDF Schema group
+ throughout most of the development of this specification; we thank David
+ for
+ his efforts and thank IBM for supporting him and us in this endeavor.
+ Particular thanks are also due to Andrew Layman for his editorial work
+ on
+ early versions of this specification.</p>
+ <p>The original RDF Schema Working Group membership included:</p>
+ <p>Nick Arnett (Verity), Dan Brickley (ILRT / University of Bristol),
+ Walter
+ Chang (Adobe), Sailesh Chutani (Oracle), Ron Daniel (DATAFUSION),
+ Charles
+ Frankston (Microsoft), Joe Lapp (webMethods Inc.), Patrick Gannon
+ (CommerceNet), RV Guha (Epinions, previously of Netscape
+ Communications), Tom
+ Hill (Apple Computer), Renato Iannella (DSTC), Sandeep Jain (Oracle),
+ Kevin
+ Jones, (InterMind), Emiko Kezuka (Digital Vision Laboratories), Ora
+ Lassila
+ (Nokia Research Center), Andrew Layman (Microsoft), John McCarthy
+ (Lawrence
+ Berkeley National Laboratory), Michael Mealling (Network Solutions),
+ Norbert
+ Mikula (DataChannel), Eric Miller (OCLC), Frank Olken (Lawrence Berkeley
+ National Laboratory), Sri Raghavan (Digital/Compaq), Lisa Rein
+ (webMethods
+ Inc.), Tsuyoshi Sakata (Digital Vision Laboratories), Leon Shklar
+ (Pencom Web
+ Works), David Singer (IBM), Wei (William) Song (SISU), Neel Sundaresan
+ (IBM),
+ Ralph Swick (<abbr title="World Wide Web Consortium">W3C</abbr>), Naohiko Uramoto (IBM), Charles Wicksteed (Reuters
+ Ltd.),
+ Misha Wolf (Reuters Ltd.)</p>
+ </section>
+ <section id="changes" class="appendix informative" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
<!--OddPage-->
<h2 aria-level="1" role="heading" id="h2_changes"><span class="secno">B. </span>Change history</h2><p><em>This section is non-normative.</em></p>
-
-<section id="PER-changes" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-
-<h3 aria-level="2" role="heading" id="h3_PER-changes"><span class="secno">B.1 </span>Changes for Proposed Edited Recommendation in 2013</h3>
-
-<ul>
- <li>Conversion to ResPec, inclduing formatting of examples and notes.</li>
- <li>Refereces and anchors to RDF 1.0 documents where appropriate replaced by
- references and anchors to RDF 1.1 documents.</li>
- <li>Replaced the term "URI Reference" with the term "IRI". </li>
- <li>Removed discussion about distinction between plain and typed
- literals, as this distinction is absent in RDF 1.1 and has no technical
- bearing on RDF Schema.</li>
- <li>Fixed incorrect pointer to RDF Primer example 16 to example
- 21.</li>
- <li>Removed the introductory paragraph of Sec. <a href="#ch_reificationvocab">"Reification Vocabulary"</a>, as
- this discussion is not related to the technical content and is
- irrelevant and confusing now. </li>
- <li>Update of affiliation of the editors. </li>
- <li>Added RDF WG to the Acknowledgements section.</li>
- <li>Renamed the document from "RDF Vocabulary Description Language
- 1.0: RDF Schema" to "RDF Schema 1.1", as the term Vocabulary
- Description Language has led to confusion.</li>
- <li>Three paragraphs of the Introduction were left out. These
- paragraphs described the things that RDF Schema does not do and are
- now much less relevant than in 2004. </li>
- <li>Added the datatypes <code>rdf:langString</code> and
- <code>rdf:HTML</code>. </li>
- <li>Removed Appendix "RDF Schema in RDF/XML". It was informative,
- but now out of date, in terms of content and in terms of syntax.</li>
-</ul>
-
-</section>
-
-<section id="2004-changes" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-
-<h3 aria-level="2" role="heading" id="h3_2004-changes"><span class="secno">B.2 </span>Changes history of the 2004 Recommendation</h3>
-
-<p>The following is an outline of the main changes made to the 2004 specification, latest first,
-since the Last Call Working Draft of <a href="http://www.w3.org/TR/2003/WD-rdf-schema-20030123/">23
-January 2003</a>. See the <a href="http://www.w3.org/2001/sw/RDFCore/20030123-issues/#schema">Last Call issue tracking
-document</a> for details of the specific issues raised regarding this specification.
-</p>
-
-<ul>
-<li>Amended Appendix A to note that the RDF/XML description of RDF and RDFS
-terms is not directly published at the RDFS namespace, but split between the 'rdf:' and 'rdfs:' namespace documents.
-Also removed the pre-REC warning that the WG might choose to change the namespace URI prior to Recommendation.</li>
-<li>Amended rdfs:range specification for rdf:predicate for consistency with the Semantics document (previously rdf:Property; now, rdfs:Resource)</li>
-<li>Removed reference to RDF mimetypes doc, as the IETF draft has expired and is 404 missing on their site.</li>
-<li>Reification vocabulary redescribed (<a href="http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003Aug/0161.html">details</a>).</li>
-<li>Reworded rdfs:comment for rdfs:member, changing "container" to "resource"</li>
-<li>Reworded lead-in to Appendix A per <a href="http://lists.w3.org/Archives/Public/www-rdf-comments/2003JulSep/0170.html">0170.html</a>.
-</li>
-<li>OWL references now go to OWL specs rather than WebOnt homepage. Fixed minor typos per <a href="http://lists.w3.org/Archives/Public/www-rdf-comments/2003JanMar/0373.html">0373.html</a>)</li>
-<li>Reworded rdf:nil to tone down the imperative style.</li>
-<li>Added note to Properties section warning about over-use of sub-property,
-and referencing OWL, an editorial suggestion from Bijan Parsia. (<a href="http://lists.w3.org/Archives/Public/www-rdf-comments/2003AprJun/0177.html">details</a>).
-</li>
-<li>Regarding <a href="http://www.w3.org/2001/sw/RDFCore/20030123-issues/#pfps-12">pfps-12</a>, <a href="http://lists.w3.org/Archives/Public/www-rdf-comments/2003AprJun/0277.html">discussion</a>
-led to rdf:first/rest/List/nil rewritten per Peter Patel-Schneider's suggestion.</li>
-<li>Change to description of subProperty and subClass, to match <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210/#change">changes to RDF
-Semantics</a>. See
-<a href="http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003Jul/0161.html">discussion</a>
-for details.</li>
-<li>Edits <a href="http://lists.w3.org/Archives/Public/www-rdf-comments/2003AprJun/0099.html">closing</a>
-'what is rdf schema' issue by clarifying that RDFS is a semantic extension of RDF, as defined
-in the RDF Semantics document. This closes rdfcore last call issue pfps-24.</li>
-</ul>
-
-</section>
-</section>
-
-
+ <section id="PER-changes" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_PER-changes"><span class="secno">B.1 </span>Changes for Proposed Edited Recommendation in 2013</h3>
+ <ul>
+ <li>Conversion to ResPec, inclduing formatting of examples and notes.</li>
+ <li>Refereces and anchors to RDF 1.0 documents where appropriate
+ replaced by references and anchors to RDF 1.1 documents.</li>
+ <li>Replaced the term "URI Reference" with the term "IRI". </li>
+ <li>Removed discussion about distinction between plain and typed
+ literals, as this distinction is absent in RDF 1.1 and has no
+ technical bearing on RDF Schema.</li>
+ <li>Fixed incorrect pointer to RDF Primer example 16 to example 21.</li>
+ <li>Removed the introductory paragraph of Sec. <a href="#ch_reificationvocab">"Reification
+ Vocabulary"</a>, as this discussion is not related to the
+ technical content and is irrelevant and confusing now. </li>
+ <li>Update of affiliation of the editors. </li>
+ <li>Added RDF WG to the Acknowledgements section.</li>
+ <li>Renamed the document from "RDF Vocabulary Description Language
+ 1.0: RDF Schema" to "RDF Schema 1.1", as the term Vocabulary
+ Description Language has led to confusion.</li>
+ <li>Three paragraphs of the Introduction were left out. These
+ paragraphs described the things that RDF Schema does not do and are
+ now much less relevant than in 2004. </li>
+ <li>Added the datatypes <code>rdf:langString</code> and <code>rdf:HTML</code>.
+ </li>
+ <li>Removed Appendix "RDF Schema in RDF/XML". It was informative, but
+ now out of date, in terms of content and in terms of
+ syntax.</li>
+ <li>Marked <code>rdf:HTML</code> and <code>rdf:XMLLiteral</code>
+ as non-normative.</li>
+ <li>Removed references to 2004 Primer from Secs. 5.1, 5.2
+ and 5.4.3. In the latter case the example referred to was
+ moved into this document for readability purposes. </li>
+ </ul>
+ </section>
+ <section id="2004-changes" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+ <h3 aria-level="2" role="heading" id="h3_2004-changes"><span class="secno">B.2 </span>Changes history of the 2004 Recommendation</h3>
+ <p>The following is an outline of the main changes made to the 2004
+ specification, latest first, since the Last Call Working Draft of <a href="http://www.w3.org/TR/2003/WD-rdf-schema-20030123/">23 January
+ 2003</a>. See the <a href="http://www.w3.org/2001/sw/RDFCore/20030123-issues/#schema">Last
+ Call issue tracking document</a> for details of the specific issues
+ raised regarding this specification.
+ </p>
+ <ul>
+ <li>Amended Appendix A to note that the RDF/XML description of RDF and
+ RDFS terms is not directly published at the RDFS namespace, but
+ split between the 'rdf:' and 'rdfs:' namespace documents. Also
+ removed the pre-REC warning that the WG might choose to change the
+ namespace URI prior to Recommendation.</li>
+ <li>Amended rdfs:range specification for rdf:predicate for consistency
+ with the Semantics document (previously rdf:Property; now,
+ rdfs:Resource)</li>
+ <li>Removed reference to RDF mimetypes doc, as the IETF draft has
+ expired and is 404 missing on their site.</li>
+ <li>Reification vocabulary redescribed (<a href="http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003Aug/0161.html">details</a>).</li>
+ <li>Reworded rdfs:comment for rdfs:member, changing "container" to
+ "resource"</li>
+ <li>Reworded lead-in to Appendix A per <a href="http://lists.w3.org/Archives/Public/www-rdf-comments/2003JulSep/0170.html">0170.html</a>.
+ </li>
+ <li>OWL references now go to OWL specs rather than WebOnt homepage.
+ Fixed minor typos per <a href="http://lists.w3.org/Archives/Public/www-rdf-comments/2003JanMar/0373.html">0373.html</a>)</li>
+ <li>Reworded rdf:nil to tone down the imperative style.</li>
+ <li>Added note to Properties section warning about over-use of
+ sub-property,
+ and referencing OWL, an editorial suggestion from Bijan Parsia. (<a href="http://lists.w3.org/Archives/Public/www-rdf-comments/2003AprJun/0177.html">details</a>).
+ </li>
+ <li>Regarding <a href="http://www.w3.org/2001/sw/RDFCore/20030123-issues/#pfps-12">pfps-12</a>,
+ <a href="http://lists.w3.org/Archives/Public/www-rdf-comments/2003AprJun/0277.html">discussion</a>
+ led to rdf:first/rest/List/nil rewritten per Peter Patel-Schneider's
+ suggestion.</li>
+ <li>Change to description of subProperty and subClass, to match <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210/#change">changes
+ to RDF Semantics</a>. See
+ <a href="http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003Jul/0161.html">discussion</a>
+ for details.</li>
+ <li>Edits <a href="http://lists.w3.org/Archives/Public/www-rdf-comments/2003AprJun/0099.html">closing</a>
+ 'what is rdf schema' issue by clarifying that RDFS is a semantic
+ extension of RDF, as defined in the RDF Semantics document. This
+ closes rdfcore last call issue pfps-24.</li>
+ </ul>
+ </section>
+ </section>
+
<!--
-
<section class="appendix informative" id="ch_appendix_rdfs">
-
<h2>RDF Schema as RDF/XML</h2>
-
<p class="issue">
-Update of the RDFS namespace document required!?
-</p>
-
+Update of the RDFS namespace document required!?</p>
<p>
-An RDFS description of the <a href="http://www.w3.org/TR/rdf11-mt/#rdf-interpretations">RDF vocabulary</a>
-and <a href="http://www.w3.org/TR/rdf11-mt/#rdfs-interpretations">RDFS vocabulary</a> is given here in RDF/XML syntax.
-It includes statements describing RDF resources originally introduced by
-the 1999 RDF Model and Syntax specification [[RDFMS]], as well as definitions for
+An RDFS description of the <a href="http://www.w3.org/TR/rdf11-mt/#rdf-interpretations">RDF vocabulary</a> and <a href="http://www.w3.org/TR/rdf11-mt/#rdfs-interpretations">RDFS vocabulary</a> is given here in RDF/XML syntax.
+It includes statements describing RDF resources originally introduced bythe 1999 RDF Model and Syntax specification [[RDFMS]], as well as definitions for
resources introduced in the RDF Schema vocabulary.</p>
-
-<p>
-This material is also available as <a href="rdfs-namespace">a separate
-RDF/XML document</a>. It does not necessarily match the content
-published at the <a
-href="http://www.w3.org/1999/02/22-rdf-syntax-ns#">RDF namespace
-URI</a> or the <a href="http://www.w3.org/2000/01/rdf-schema#">RDFS
-namespace URI</a>, which may evolve over time.
-</p>
-
+<p>This material is also available as <a href="rdfs-namespace">a separate
+RDF/XML document</a>. It does not necessarily match the contentpublished at the <a
+href="http://www.w3.org/1999/02/22-rdf-syntax-ns#">RDF namespaceURI</a> or the <a href="http://www.w3.org/2000/01/rdf-schema#">RDFS
+namespace URI</a>, which may evolve over time.</p>
<table cellpadding="5" border="1" width="95%" summary="RDF Schema in RDF">
- <tbody>
- <tr>
- <td>
- <pre>
-<rdf:RDF
- xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
- xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
- xmlns:owl="http://www.w3.org/2002/07/owl#">
-
+ <tbody> <tr>
+ <td> <pre>
+<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:owl="http://www.w3.org/2002/07/owl#">
<owl:Ontology rdf:about="http://www.w3.org/2000/01/rdf-schema#"/>
-
<rdfs:Class rdf:about="http://www.w3.org/2000/01/rdf-schema#Resource">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>Resource</rdfs:label>
- <rdfs:comment>The class resource, everything.</rdfs:comment>
-</rdfs:Class>
-
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/> <rdfs:label>Resource</rdfs:label>
+ <rdfs:comment>The class resource, everything.</rdfs:comment></rdfs:Class>
<rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#type">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>type</rdfs:label>
- <rdfs:comment>The subject is an instance of a class.</rdfs:comment>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Class"/>
- <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
-</rdf:Property>
-
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/> <rdfs:label>type</rdfs:label>
+ <rdfs:comment>The subject is an instance of a class.</rdfs:comment> <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Class"/>
+ <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/></rdf:Property>
<rdfs:Class rdf:about="http://www.w3.org/2000/01/rdf-schema#Class">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>Class</rdfs:label>
- <rdfs:comment>The class of classes.</rdfs:comment>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/> <rdfs:label>Class</rdfs:label>
+ <rdfs:comment>The class of classes.</rdfs:comment> <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
</rdfs:Class>
-
-<rdf:Property rdf:about="http://www.w3.org/2000/01/rdf-schema#subClassOf">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>subClassOf</rdfs:label>
- <rdfs:comment>The subject is a subclass of a class.</rdfs:comment>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Class"/>
- <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Class"/>
-</rdf:Property>
-
-<rdf:Property rdf:about="http://www.w3.org/2000/01/rdf-schema#subPropertyOf">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>subPropertyOf</rdfs:label>
- <rdfs:comment>The subject is a subproperty of a property.</rdfs:comment>
- <rdfs:range rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
- <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
+<rdf:Property rdf:about="http://www.w3.org/2000/01/rdf-schema#subClassOf"> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
+ <rdfs:label>subClassOf</rdfs:label> <rdfs:comment>The subject is a subclass of a class.</rdfs:comment>
+ <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Class"/> <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Class"/>
</rdf:Property>
-
-<rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>Property</rdfs:label>
- <rdfs:comment>The class of RDF properties.</rdfs:comment>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
-</rdfs:Class>
-
+<rdf:Property rdf:about="http://www.w3.org/2000/01/rdf-schema#subPropertyOf"> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
+ <rdfs:label>subPropertyOf</rdfs:label> <rdfs:comment>The subject is a subproperty of a property.</rdfs:comment>
+ <rdfs:range rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
+</rdf:Property>
+<rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>Property</rdfs:label> <rdfs:comment>The class of RDF properties.</rdfs:comment>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/></rdfs:Class>
<rdf:Property rdf:about="http://www.w3.org/2000/01/rdf-schema#comment">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>comment</rdfs:label>
- <rdfs:comment>A description of the subject resource.</rdfs:comment>
- <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
-</rdf:Property>
-
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/> <rdfs:label>comment</rdfs:label>
+ <rdfs:comment>A description of the subject resource.</rdfs:comment> <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+ <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/></rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/2000/01/rdf-schema#label">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>label</rdfs:label>
- <rdfs:comment>A human-readable name for the subject.</rdfs:comment>
- <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
-</rdf:Property>
-
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/> <rdfs:label>label</rdfs:label>
+ <rdfs:comment>A human-readable name for the subject.</rdfs:comment> <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+ <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/></rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/2000/01/rdf-schema#domain">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>domain</rdfs:label>
- <rdfs:comment>A domain of the subject property.</rdfs:comment>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Class"/>
- <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
-</rdf:Property>
-
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/> <rdfs:label>domain</rdfs:label>
+ <rdfs:comment>A domain of the subject property.</rdfs:comment> <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Class"/>
+ <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/></rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/2000/01/rdf-schema#range">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>range</rdfs:label>
- <rdfs:comment>A range of the subject property.</rdfs:comment>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Class"/>
- <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
-</rdf:Property>
-
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/> <rdfs:label>range</rdfs:label>
+ <rdfs:comment>A range of the subject property.</rdfs:comment> <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Class"/>
+ <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/></rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/2000/01/rdf-schema#seeAlso">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>seeAlso</rdfs:label>
- <rdfs:comment>Further information about the subject resource.</rdfs:comment>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
- <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
-</rdf:Property>
-
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/> <rdfs:label>seeAlso</rdfs:label>
+ <rdfs:comment>Further information about the subject resource.</rdfs:comment> <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+ <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/></rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/2000/01/rdf-schema#isDefinedBy">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:subPropertyOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#seeAlso"/>
- <rdfs:label>isDefinedBy</rdfs:label>
- <rdfs:comment>The defininition of the subject resource.</rdfs:comment>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
- <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/> <rdfs:subPropertyOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#seeAlso"/>
+ <rdfs:label>isDefinedBy</rdfs:label> <rdfs:comment>The defininition of the subject resource.</rdfs:comment>
+ <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/> <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
</rdf:Property>
-
-<rdfs:Class rdf:about="http://www.w3.org/2000/01/rdf-schema#Literal">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>Literal</rdfs:label>
- <rdfs:comment>The class of literal values, eg. textual strings and integers.</rdfs:comment>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
-</rdfs:Class>
-
+<rdfs:Class rdf:about="http://www.w3.org/2000/01/rdf-schema#Literal"> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
+ <rdfs:label>Literal</rdfs:label> <rdfs:comment>The class of literal values, eg. textual strings and integers.</rdfs:comment>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/></rdfs:Class>
<rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>Statement</rdfs:label>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
- <rdfs:comment>The class of RDF statements.</rdfs:comment>
-</rdfs:Class>
-
-<rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#subject">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>subject</rdfs:label>
- <rdfs:comment>The subject of the subject RDF statement.</rdfs:comment>
- <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
-</rdf:Property>
-
-<rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#predicate">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>predicate</rdfs:label>
- <rdfs:comment>The predicate of the subject RDF statement.</rdfs:comment>
- <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
-</rdf:Property>
-
-<rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#object">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>object</rdfs:label>
- <rdfs:comment>The object of the subject RDF statement.</rdfs:comment>
- <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
-</rdf:Property>
-
-<rdfs:Class rdf:about="http://www.w3.org/2000/01/rdf-schema#Container">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>Container</rdfs:label>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
- <rdfs:comment>The class of RDF containers.</rdfs:comment>
-</rdfs:Class>
-
-<rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Bag">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>Bag</rdfs:label>
- <rdfs:comment>The class of unordered containers.</rdfs:comment>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Container"/>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/> <rdfs:label>Statement</rdfs:label>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/> <rdfs:comment>The class of RDF statements.</rdfs:comment>
</rdfs:Class>
-
-<rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Seq">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>Seq</rdfs:label>
- <rdfs:comment>The class of ordered containers.</rdfs:comment>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Container"/>
-</rdfs:Class>
-
-<rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Alt">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>Alt</rdfs:label>
- <rdfs:comment>The class of containers of alternatives.</rdfs:comment>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Container"/>
+<rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#subject"> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>subject</rdfs:label> <rdfs:comment>The subject of the subject RDF statement.</rdfs:comment>
+ <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/> <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+</rdf:Property>
+<rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#predicate"> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>predicate</rdfs:label> <rdfs:comment>The predicate of the subject RDF statement.</rdfs:comment>
+ <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/> <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+</rdf:Property>
+<rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#object"> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>object</rdfs:label> <rdfs:comment>The object of the subject RDF statement.</rdfs:comment>
+ <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/> <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+</rdf:Property>
+<rdfs:Class rdf:about="http://www.w3.org/2000/01/rdf-schema#Container"> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
+ <rdfs:label>Container</rdfs:label> <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+ <rdfs:comment>The class of RDF containers.</rdfs:comment></rdfs:Class>
+<rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Bag">
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/> <rdfs:label>Bag</rdfs:label>
+ <rdfs:comment>The class of unordered containers.</rdfs:comment> <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Container"/>
</rdfs:Class>
-
-<rdfs:Class rdf:about="http://www.w3.org/2000/01/rdf-schema#ContainerMembershipProperty">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>ContainerMembershipProperty</rdfs:label>
- <rdfs:comment>The class of container membership properties, rdf:_1, rdf:_2, ...,
- all of which are sub-properties of 'member'.</rdfs:comment>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
+<rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Seq"> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>Seq</rdfs:label> <rdfs:comment>The class of ordered containers.</rdfs:comment>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Container"/></rdfs:Class>
+<rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Alt">
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/> <rdfs:label>Alt</rdfs:label>
+ <rdfs:comment>The class of containers of alternatives.</rdfs:comment> <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Container"/>
</rdfs:Class>
-
-<rdf:Property rdf:about="http://www.w3.org/2000/01/rdf-schema#member">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>member</rdfs:label>
- <rdfs:comment>A member of the subject resource.</rdfs:comment>
- <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+<rdfs:Class rdf:about="http://www.w3.org/2000/01/rdf-schema#ContainerMembershipProperty"> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
+ <rdfs:label>ContainerMembershipProperty</rdfs:label> <rdfs:comment>The class of container membership properties, rdf:_1, rdf:_2, ...,
+ all of which are sub-properties of 'member'.</rdfs:comment> <rdfs:subClassOf rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
+</rdfs:Class>
+<rdf:Property rdf:about="http://www.w3.org/2000/01/rdf-schema#member"> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
+ <rdfs:label>member</rdfs:label> <rdfs:comment>A member of the subject resource.</rdfs:comment>
+ <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/> <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
</rdf:Property>
-
-<rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#value">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>value</rdfs:label>
- <rdfs:comment>Idiomatic property used for structured values.</rdfs:comment>
- <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+<rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#value"> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>value</rdfs:label> <rdfs:comment>Idiomatic property used for structured values.</rdfs:comment>
+ <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/> <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
</rdf:Property>
-
-<rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#List">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>List</rdfs:label>
- <rdfs:comment>The class of RDF Lists.</rdfs:comment>
+<rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#List"> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>List</rdfs:label> <rdfs:comment>The class of RDF Lists.</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/></rdfs:Class>
-
-<rdf:List rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#nil">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>nil</rdfs:label>
- <rdfs:comment>The empty list, with no items in it. If the rest of a list is nil then the list has no more items in it.</rdfs:comment>
+<rdf:List rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#nil"> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>nil</rdfs:label> <rdfs:comment>The empty list, with no items in it. If the rest of a list is nil then the list has no more items in it.</rdfs:comment>
</rdf:List>
-
-<rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#first">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>first</rdfs:label>
- <rdfs:comment>The first item in the subject RDF list.</rdfs:comment>
- <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#List"/>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
-</rdf:Property>
-
-<rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#rest">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>rest</rdfs:label>
- <rdfs:comment>The rest of the subject RDF list after the first item.</rdfs:comment>
- <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#List"/>
- <rdfs:range rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#List"/>
+<rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#first"> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>first</rdfs:label> <rdfs:comment>The first item in the subject RDF list.</rdfs:comment>
+ <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#List"/> <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
</rdf:Property>
-
-<rdfs:Class rdf:about="http://www.w3.org/2000/01/rdf-schema#Datatype">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>Datatype</rdfs:label>
- <rdfs:comment>The class of RDF datatypes.</rdfs:comment>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Class"/>
-</rdfs:Class>
-
-<rdfs:Datatype rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral">
- <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>XMLLiteral</rdfs:label>
- <rdfs:comment>The class of XML literal values.</rdfs:comment>
+<rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#rest"> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>rest</rdfs:label> <rdfs:comment>The rest of the subject RDF list after the first item.</rdfs:comment>
+ <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#List"/> <rdfs:range rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#List"/>
+</rdf:Property>
+<rdfs:Class rdf:about="http://www.w3.org/2000/01/rdf-schema#Datatype"> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
+ <rdfs:label>Datatype</rdfs:label> <rdfs:comment>The class of RDF datatypes.</rdfs:comment>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Class"/></rdfs:Class>
+ <rdfs:Datatype rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral">
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/> <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>XMLLiteral</rdfs:label> <rdfs:comment>The class of XML literal values.</rdfs:comment>
</rdfs:Datatype>
-
-<rdf:Description rdf:about="http://www.w3.org/2000/01/rdf-schema#">
- <rdfs:seeAlso rdf:resource="http://www.w3.org/2000/01/rdf-schema-more"/>
+<rdf:Description rdf:about="http://www.w3.org/2000/01/rdf-schema#"> <rdfs:seeAlso rdf:resource="http://www.w3.org/2000/01/rdf-schema-more"/>
</rdf:Description>
-
</rdf:RDF>
-
- </pre>
- </td>
- </tr>
- </tbody>
-</table>
-<hr />
-
+ </pre> </td>
+ </tr> </tbody>
+</table><hr />
</section>
-->
-
-
+
<section class="appendix" id="references" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<!--OddPage-->
@@ -1812,7 +1626,5 @@
</dd><dt id="bib-TURTLE">[TURTLE]</dt><dd rel="dcterms:requires">Eric Prud'hommeaux, Gavin Carothers, Editors. <cite><a href="http://www.w3.org/TR/2013/CR-turtle-20130219/">RDF 1.1 Turtle: Terse RDF Triple Language.</a></cite> 19 February 2013. W3C Candidate Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2013/CR-turtle-20130219/">http://www.w3.org/TR/2013/CR-turtle-20130219/</a>. The latest edition is available at <a href="http://www.w3.org/TR/turtle/">http://www.w3.org/TR/turtle/</a>
</dd></dl></section><section id="informative-references" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h3 aria-level="2" role="heading" id="h3_informative-references"><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-BERNERS-LEE98">[BERNERS-LEE98]</dt><dd rel="dcterms:references">Tim Berners-Lee. <cite><a href="http://www.w3.org/DesignIssues/RDFnot.html">What the Semantic Web can represent</a></cite>. 1998. URI: <a href="http://www.w3.org/DesignIssues/RDFnot.html">http://www.w3.org/DesignIssues/RDFnot.html</a>.
</dd><dt id="bib-OWL2-OVERVIEW">[OWL2-OVERVIEW]</dt><dd rel="dcterms:references">W3C OWL Working Group. <a href="http://www.w3.org/TR/owl2-overview/"><cite>OWL 2 Web Ontology Language Document Overview (Second Edition)</cite></a>. 11 December 2012. W3C Recommendation. URL: <a href="http://www.w3.org/TR/owl2-overview/">http://www.w3.org/TR/owl2-overview/</a>
-</dd><dt id="bib-RDF-CONCEPTS">[RDF-CONCEPTS]</dt><dd rel="dcterms:references">Graham Klyne; Jeremy Carroll. <a href="http://www.w3.org/TR/rdf-concepts/"><cite>Resource Description Framework (RDF): Concepts and Abstract Syntax</cite></a>. 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/rdf-concepts/">http://www.w3.org/TR/rdf-concepts/</a>
-</dd><dt id="bib-RDF11-PRIMER">[RDF11-PRIMER]</dt><dd rel="dcterms:references">Guus Schreiber, Yves Raimond, editors. <cite><a href="https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-primer/index.html#">RDF 1.1 Primer</a></cite>. 2013. The latest version is available at <a href="http://www.w3.org/TR/rdf11-primer/">http://www.w3.org/TR/rdf11-primer/</a>.
-</dd><dt id="bib-RDFMS">[RDFMS]</dt><dd rel="dcterms:references">Ora Lassila; Ralph R. Swick. <cite><a href="http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/">Resource Description Framework (RDF) Model and Syntax Specification</a></cite>. 22 February 1999. W3C Recommendation. URL: <a href="http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/">http://www.w3.org/TR/1999/REC-rdf-syntax-19990222</a>.
+</dd><dt id="bib-RDF11-PRIMER">[RDF11-PRIMER]</dt><dd rel="dcterms:references">Guus Schreiber, Yves Raimond. <cite><a href="https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-primer/index.html">RDF 1.1 Primer</a></cite>. 2013. The latest version is available at <a href="http://www.w3.org/TR/rdf11-primer/">http://www.w3.org/TR/rdf11-primer/</a>.
</dd></dl></section></section></body></html>
\ No newline at end of file
--- a/rdf-schema/diff.html Fri Dec 13 08:05:45 2013 -0500
+++ b/rdf-schema/diff.html Fri Dec 13 08:06:03 2013 -0500
@@ -1,6 +1,6 @@
<html lang="en" typeof="bibo:Document w3p:PER" about="" property="dcterms:language" content="en" prefix="bibo: http://purl.org/ontology/bibo/ w3p: http://www.w3.org/2001/02pd/rec54#" xmlns="http://www.w3.org/1999/xhtml">
<head>
-<meta charset="utf-8" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>RDF Schema 1.1</title>
<style type="text/css">
@@ -126,6 +126,43 @@
<style type="text/css">
/*<![CDATA[*/
+/* --- EXAMPLES --- */
+div.example-title {
+ min-width: 7.5em;
+ color: #b9ab2d;
+}
+div.example-title span {
+ text-transform: uppercase;
+}
+aside.example, div.example, div.illegal-example {
+ padding: 0.5em;
+ margin: 1em 0;
+ position: relative;
+ clear: both;
+}
+div.illegal-example { color: red }
+div.illegal-example p { color: black }
+aside.example, div.example {
+ padding: .5em;
+ border-left-width: .5em;
+ border-left-style: solid;
+ border-color: #e0cb52;
+ background: #fcfaee;
+}
+
+aside.example div.example {
+ border-left-width: .1em;
+ border-color: #999;
+ background: #fff;
+}
+aside.example div.example div.example-title {
+ color: #999;
+}
+/*]]>*/
+</style>
+
+<style type="text/css">
+/*<![CDATA[*/
/* --- ISSUES/NOTES --- */
div.issue-title, div.note-title {
padding-right: 1em;
@@ -207,7 +244,7 @@
<ins class="diff-new">1.1
</ins>
</h1>
-<h2 content="2013-12-03T13:23:18.000Z" datatype="xsd:dateTime" property="dcterms:issued" id="w3c-proposed-edited-recommendation-03-december-2013">
+<h2 content="2014-01-08T23:00:00.000Z" datatype="xsd:dateTime" property="dcterms:issued" id="w3c-proposed-edited-recommendation-09-january-2014">
<abbr title="World Wide Web Consortium">
W3C
</abbr>
@@ -219,10 +256,10 @@
February
2004
</del>
-<time datetime="2013-12-03" class="dt-published">
-<ins class="diff-chg">03
-December
-2013
+<time datetime="2014-01-09" class="dt-published">
+<ins class="diff-chg">09
+January
+2014
</ins></time>
</h2>
<dl>
@@ -236,8 +273,8 @@
<dd>
<del class="diff-old">http://www.w3.org/TR/2004/REC-rdf-schema-20040210/
</del>
-<a href="http://www.w3.org/TR/2013/PER-rdf-schema-20131203/" class="u-url">
-<ins class="diff-chg">http://www.w3.org/TR/2013/PER-rdf-schema-20131203/
+<a href="http://www.w3.org/TR/2014/PER-rdf-schema-20140109/" class="u-url">
+<ins class="diff-chg">http://www.w3.org/TR/2014/PER-rdf-schema-20140109/
</ins>
</a>
</dd>
@@ -362,8 +399,8 @@
</ins><a href="diff.html" rel="alternate"><ins class="diff-chg">
diff
w.r.t.
-previous
-recommendation
+2004
+Recommendation
</ins></a>
</p>
<p class="copyright">
@@ -374,7 +411,7 @@
2004
</del>
<ins class="diff-chg">©
-2004-2013
+2004-2014
</ins>
<a href="http://www.w3.org/">
<abbr title="World Wide Web Consortium">
@@ -435,7 +472,7 @@
</p>
<hr />
</div>
-<div class="head" role="contentinfo">
+<div class="head" role="contentinfo" id="respecHeader">
<section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h2 aria-level="1" role="heading" id="h2_abstract">
Abstract
@@ -469,12 +506,12 @@
how
to
use
-RDF
-to
+</del>
+RDF
+<del class="diff-old">to
describe
-</del>
-RDF
-<del class="diff-old">vocabularies.
+RDF
+vocabularies.
This
specification
defines
@@ -483,7 +520,7 @@
provides
</ins>
a
-<ins class="diff-new">data-mdelling
+<ins class="diff-new">data-modelling
</ins>
vocabulary
for
@@ -505,7 +542,7 @@
Schema
is
an
-extesnion
+extension
of
</ins>
the
@@ -684,7 +721,7 @@
</del>
<ins class="diff-chg">introduction.
The
-tile
+title
</ins>
of
the
@@ -769,7 +806,7 @@
Details
of
the
-chnages
+changes
are
listed
in
@@ -1188,7 +1225,7 @@
</del>
</li>
<li class="tocline">
-<a href="#ch_langString" class="tocxref">
+<a href="#ch_langstring" class="tocxref">
<span class="secno">
2.5
<del class="diff-old">rdf:XMLLiteral
@@ -1719,16 +1756,17 @@
<ins class="diff-chg">C.
</ins></span><ins class="diff-chg">
References
-</ins></a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno"><ins class="diff-chg">
-C.1
+</ins>
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#normative-references" class="tocxref">
+<span class="secno">
+<ins class="diff-chg">C.1
</ins></span><ins class="diff-chg">
Normative
references
-</ins>
-</a>
-</li>
-<li class="tocline">
-<a href="#informative-references" class="tocxref">
+</ins></a></li><li class="tocline"><a href="#informative-references" class="tocxref">
<span class="secno">
<ins class="diff-new">C.2
</ins></span><ins class="diff-new">
@@ -1797,14 +1835,14 @@
referred
to
the
-</del>
-RDF
-<del class="diff-old">schema
+RDF
+schema
chapter
in
the
-RDF
-Primer
+</del>
+RDF
+<del class="diff-old">Primer
[
RDF-PRIMER
]
@@ -1832,7 +1870,7 @@
<ins class="diff-chg">Schema
provides
a
-data-mdelling
+data-modelling
</ins>
vocabulary
<del class="diff-old">description
@@ -2027,8 +2065,11 @@
the
RDF
Semantics
-specification
+<del class="diff-old">specification
.
+</del>
+<ins class="diff-chg">specification.
+</ins>
Where
there
is
@@ -2181,12 +2222,12 @@
extension
<del class="diff-old">(as
defined
-in
+</del>
+</a>
+<del class="diff-old">in
[
RDF-SEMANTICS
-</del>
-</a>
-<del class="diff-old">])
+])
</del>
of
RDF.
@@ -2222,11 +2263,8 @@
described
in
this
-<del class="diff-old">document.
+document.
These
-</del>
-<ins class="diff-chg">document.These
-</ins>
resources
are
used
@@ -3401,8 +3439,8 @@
rdfs:Literal.
</p>
</section>
-<section id="ch_langString" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_langString">
+<section id="ch_langstring" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<h3 aria-level="2" role="heading" id="h3_ch_langstring">
<span class="secno">
<ins class="diff-chg">2.5
</ins></span><ins class="diff-chg">
@@ -3437,14 +3475,19 @@
subclass
</ins></a><ins class="diff-chg">
of
-</ins><a href="#ch_literal">
-<code>
-<ins class="diff-new">rdfs:Literal
-</ins></code></a>.</p></section><section id="ch_html" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h3 aria-level="2" role="heading" id="h3_ch_html"><span class="secno"><ins class="diff-new">
+</ins><a href="#ch_literal"><code><ins class="diff-chg">
+rdfs:Literal
+</ins></code></a>.</p></section><section class="informative" id="ch_html" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h3 aria-level="2" role="heading" id="h3_ch_html"><span class="secno"><ins class="diff-chg">
2.6
-</ins></span><ins class="diff-new">
+</ins></span><ins class="diff-chg">
rdf:HTML
-</ins></h3><p><ins class="diff-new">
+</ins></h3><p>
+<em>
+<ins class="diff-new">This
+section
+is
+non-normative.
+</ins></em></p><p><ins class="diff-new">
The
class
</ins><code><ins class="diff-new">
@@ -3479,12 +3522,19 @@
<ins class="diff-chg">of
</ins><a href="#ch_literal"><code><ins class="diff-chg">
rdfs:Literal
-</ins></code></a>.</p></section><section id="ch_xmlliteral" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h3 aria-level="2" role="heading" id="h3_ch_xmlliteral"><span class="secno"><ins class="diff-chg">
+</ins></code></a>.</p></section><section class="informative" id="ch_xmlliteral" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h3 aria-level="2" role="heading" id="h3_ch_xmlliteral"><span class="secno"><ins class="diff-chg">
2.7
</ins></span>
rdf:XMLLiteral
</h3>
<p>
+<em>
+<ins class="diff-chg">This
+section
+is
+non-normative.
+</ins></em></p>
+<p>
The
class
<code>
@@ -3572,9 +3622,12 @@
Syntax
specification
[
+<del class="diff-old">RDF-CONCEPTS
+</del>
<cite>
-<a class="bibref" href="#bib-RDF-CONCEPTS">
-RDF-CONCEPTS
+<a class="bibref" href="#bib-RDF11-CONCEPTS">
+<ins class="diff-chg">RDF11-CONCEPTS
+</ins>
</a>
</cite>
]
@@ -3709,7 +3762,7 @@
</del>
</span>
</div>
-<div class="">
+<p class="">
The
basic
facilities
@@ -3785,11 +3838,12 @@
OWL2-OVERVIEW
</ins>
</a>
-<del class="diff-old">].
-</del>
</cite>
-<ins class="diff-chg">].
-</ins></div></div><section id="ch_range" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h3 aria-level="2" role="heading" id="h3_ch_range">
+].
+</p>
+</div>
+<section id="ch_range" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<h3 aria-level="2" role="heading" id="h3_ch_range">
<span class="secno">
3.1
</span>
@@ -4723,7 +4777,7 @@
supported
using
the
-<a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-Graph-Literal">
+<a href="http://www.w3.org/TR/rdf11-concepts/#section-Graph-Literal">
language
tagging
</a>
@@ -5142,7 +5196,10 @@
classes
and
properties
-in
+<del class="diff-old">in
+</del>
+<ins class="diff-chg">on
+</ins>
the
Web,
it
@@ -5204,14 +5261,17 @@
the
World
Wide
-Web
+<del class="diff-old">Web
+</del>
+<ins class="diff-chg">Web,
+</ins>
are
defined
in
this
section.
</p>
-<section id="ch_containervocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<section class="informative" id="ch_containervocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_ch_containervocab">
<span class="secno">
5.1
@@ -5222,6 +5282,12 @@
Properties
</h3>
<p>
+<em>
+<ins class="diff-new">This
+section
+is
+non-normative.
+</ins></em></p><p>
RDF
containers
are
@@ -5232,7 +5298,7 @@
to
represent
collections.
-An
+<del class="diff-old">An
introduction
to
RDF
@@ -5244,16 +5310,12 @@
found
in
the
-<a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#containers">
-RDF
-<ins class="diff-new">2004
-</ins>
+RDF
Primer
-<del class="diff-old">[
+[
RDF-PRIMER
].
</del>
-</a>.
The
same
resource
@@ -5351,8 +5413,11 @@
the
<a href="#ch_containermembershipproperty">
container
-member
+<del class="diff-old">member
ship
+</del>
+<ins class="diff-chg">membership
+</ins>
properties
</a>
of
@@ -5841,7 +5906,9 @@
</blockquote>
<p>
where
+<code>
nnn
+</code>
is
the
decimal
@@ -5967,7 +6034,7 @@
</p>
</section>
</section>
-<section id="ch_collectionvocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<section class="informative" id="ch_collectionvocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_ch_collectionvocab">
<span class="secno">
5.2
@@ -5976,6 +6043,12 @@
Collections
</h3>
<p>
+<em>
+<ins class="diff-new">This
+section
+is
+non-normative.
+</ins></em></p><p>
RDF
containers
are
@@ -6020,21 +6093,17 @@
no
more
members.
-The
+<del class="diff-old">The
reader
is
referred
to
the
-<a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#collections">
collections
-</a>
section
of
the
RDF
-<ins class="diff-new">2004
-</ins>
primer
for
an
@@ -6044,6 +6113,7 @@
collections
with
examples.
+</del>
</p>
<p>
A
@@ -6074,13 +6144,16 @@
There
is
a
-<a href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/#section-Syntax-parsetype-Collection">
+<a href="http://www.w3.org/TR/turtle/#collections">
shorthand
notation
</a>
in
the
-RDF/XML
+<del class="diff-old">RDF/XML
+</del>
+<ins class="diff-chg">Turtle
+</ins>
syntax
specification
<del class="diff-old">[
@@ -6099,7 +6172,7 @@
</del>
</span>
</div>
-<div class="">
+<p class="">
RDFS
does
not
@@ -6125,7 +6198,7 @@
a
first
element.
-</div>
+</p>
</div>
<section id="ch_list" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ch_list">
@@ -6437,14 +6510,16 @@
</p>
</section>
</section>
-<section id="ch_reificationvocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-<h3 aria-level="2" role="heading" id="h3_ch_reificationvocab">
+<section class="informative" id="ch_reificationvocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<ins class="diff-chg">>
+</ins><h3 aria-level="2" role="heading" id="h3_ch_reificationvocab">
<span class="secno">
5.3
</span>
Reification
Vocabulary
</h3>
+<p>
<del class="diff-old">The
original
RDF
@@ -6519,8 +6594,13 @@
RDFMS
]
definition)
-is
-described
+</del>
+<em>
+<ins class="diff-chg">This
+section
+</ins>
+is
+<del class="diff-old">described
here.
An
informal
@@ -6542,6 +6622,9 @@
RDF-PRIMER
].
</del>
+<ins class="diff-chg">non-normative.
+</ins></em>
+</p>
<section id="ch_statement" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ch_statement">
<span class="secno">
@@ -7388,24 +7471,27 @@
as
illustrated
in
-<a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example21">
example
<del class="diff-old">16
-</del>
-<ins class="diff-chg">21
-</ins>
-</a>
-of
-the
-RDF
-<del class="diff-old">primer
+of
+the
+RDF
+primer
[
RDF-PRIMER
].
</del>
-<ins class="diff-chg">1.0
-primer.
-</ins>
+<ins class="diff-chg">below:
+</ins></p><div class="example"><div class="example-title"><span><ins class="diff-chg">
+Example
+1
+</ins></span></div><pre class="example"><ins class="diff-chg">
+<http://www.example.com/2002/04/products#item10245>
+ <http://www.example.org/terms/weight> [
+ rdf:value 2.4 ;
+ <http://www.example.org/terms/units> <http://www.example.org/units/kilograms>
+ ] .
+</ins></pre></div>
Despite
the
lack
@@ -7437,6 +7523,7 @@
of
this
kind.
+<p>
</p>
<p>
The
@@ -7488,19 +7575,26 @@
</h2>
<p>
<em>
-<ins class="diff-new">This
-section
+This
+<del class="diff-old">table
+presents
+</del>
+<ins class="diff-chg">section
is
non-normative.
-</ins></em></p><p>
-This
-table
-presents
+</ins></em></p><p><ins class="diff-chg">
+The
+tables
+in
+this
+section
+provide
+</ins>
an
overview
of
the
-vocabulary
+<del class="diff-old">vocabulary
of
RDF,
drawing
@@ -7515,12 +7609,6 @@
and
Syntax
specification
-<ins class="diff-new">[
-</ins><cite><a class="bibref" href="#bib-RDFMS"><ins class="diff-new">
-RDFMS
-</ins></a></cite><ins class="diff-new">
-]
-</ins>
with
classes
and
@@ -7528,8 +7616,13 @@
that
originate
with
-RDF
-Schema.
+</del>
+RDF
+<del class="diff-old">Schema.
+</del>
+<ins class="diff-chg">Schema
+vocabulary.
+</ins>
</p>
<section id="ch_sumclasses" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_ch_sumclasses">
@@ -7552,7 +7645,9 @@
</tr>
<tr>
<td>
+<a href="#ch_resource">
rdfs:Resource
+</a>
</td>
<td>
The
@@ -7563,7 +7658,9 @@
</tr>
<tr>
<td>
+<a href="#ch_literal">
rdfs:Literal
+</a>
</td>
<td>
The
@@ -7580,8 +7677,9 @@
</tr>
<tr>
<td>
+<a href="#ch_langstring">
<ins class="diff-new">rdf:langString
-</ins></td><td><ins class="diff-new">
+</ins></a></td><td><ins class="diff-new">
The
class
of
@@ -7589,17 +7687,18 @@
string
literal
values.
-</ins></td></tr><tr><td><ins class="diff-new">
+</ins></td></tr><tr><td><a href="#ch_html"><ins class="diff-new">
rdf:HTML
-</ins></td><td><ins class="diff-new">
+</ins></a></td><td><ins class="diff-new">
The
class
of
HTML
literal
values.
-</ins></td></tr><tr><td>
+</ins></td></tr><tr><td><a href="#ch_xmlliteral">
rdf:XMLLiteral
+</a>
</td>
<td>
The
@@ -7615,7 +7714,9 @@
</tr>
<tr>
<td>
+<a href="#ch_class">
rdfs:Class
+</a>
</td>
<td>
The
@@ -7626,7 +7727,9 @@
</tr>
<tr>
<td>
+<a href="#ch_property">
rdf:Property
+</a>
</td>
<td>
The
@@ -7638,7 +7741,9 @@
</tr>
<tr>
<td>
+<a href="#ch_datatype">
rdfs:Datatype
+</a>
</td>
<td>
The
@@ -7650,7 +7755,9 @@
</tr>
<tr>
<td>
+<a href="#ch_statement">
rdf:Statement
+</a>
</td>
<td>
The
@@ -7662,7 +7769,9 @@
</tr>
<tr>
<td>
+<a href="#ch_bag">
rdf:Bag
+</a>
</td>
<td>
The
@@ -7674,7 +7783,9 @@
</tr>
<tr>
<td>
+<a href="#ch_seq">
rdf:Seq
+</a>
</td>
<td>
The
@@ -7686,7 +7797,9 @@
</tr>
<tr>
<td>
+<a href="#ch_alt">
rdf:Alt
+</a>
</td>
<td>
The
@@ -7699,7 +7812,9 @@
</tr>
<tr>
<td>
+<a href="#ch_container">
rdfs:Container
+</a>
</td>
<td>
The
@@ -7711,7 +7826,9 @@
</tr>
<tr>
<td>
+<a href="#ch_containermembershipproperty">
rdfs:ContainerMembershipProperty
+</a>
</td>
<td>
The
@@ -7734,7 +7851,9 @@
</tr>
<tr>
<td>
+<a href="#ch_list">
rdf:List
+</a>
</td>
<td>
The
@@ -7774,7 +7893,9 @@
</tr>
<tr>
<td>
+<a href="#ch_type">
rdf:type
+</a>
</td>
<td>
The
@@ -7795,7 +7916,9 @@
</tr>
<tr>
<td>
+<a href="#ch_subclassof">
rdfs:subClassOf
+</a>
</td>
<td>
The
@@ -7816,7 +7939,9 @@
</tr>
<tr>
<td>
+<a href="#ch_subpropertyof">
rdfs:subPropertyOf
+</a>
</td>
<td>
The
@@ -7837,7 +7962,9 @@
</tr>
<tr>
<td>
+<a href="#ch_domain">
rdfs:domain
+</a>
</td>
<td>
A
@@ -7856,7 +7983,9 @@
</tr>
<tr>
<td>
+<a href="#ch_range">
rdfs:range
+</a>
</td>
<td>
A
@@ -7875,7 +8004,9 @@
</tr>
<tr>
<td>
+<a href="#ch_label">
rdfs:label
+</a>
</td>
<td>
A
@@ -7894,7 +8025,9 @@
</tr>
<tr>
<td>
+<a href="#ch_comment">
rdfs:comment
+</a>
</td>
<td>
A
@@ -7913,7 +8046,9 @@
</tr>
<tr>
<td>
+<a href="#ch_member">
rdfs:member
+</a>
</td>
<td>
A
@@ -7932,7 +8067,9 @@
</tr>
<tr>
<td>
+<a href="#ch_first">
rdf:first
+</a>
</td>
<td>
The
@@ -7953,7 +8090,9 @@
</tr>
<tr>
<td>
+<a href="#ch_rest">
rdf:rest
+</a>
</td>
<td>
The
@@ -7977,7 +8116,9 @@
</tr>
<tr>
<td>
+<a href="#ch_seealso">
rdfs:seeAlso
+</a>
</td>
<td>
Further
@@ -7996,7 +8137,9 @@
</tr>
<tr>
<td>
+<a href="#ch_isdefinedby">
rdfs:isDefinedBy
+</a>
</td>
<td>
The
@@ -8015,7 +8158,9 @@
</tr>
<tr>
<td>
+<a href="#ch_value">
rdf:value
+</a>
</td>
<td>
Idiomatic
@@ -8023,19 +8168,20 @@
used
for
structured
-values
+<del class="diff-old">values
(see
the
RDF
Primer
for
-<a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example16">
an
example
-</a>
of
its
usage).
+</del>
+<ins class="diff-chg">values.
+</ins>
</td>
<td>
rdfs:Resource
@@ -8046,7 +8192,9 @@
</tr>
<tr>
<td>
+<a href="#ch_subject">
rdf:subject
+</a>
</td>
<td>
The
@@ -8066,7 +8214,9 @@
</tr>
<tr>
<td>
+<a href="#ch_predicate">
rdf:predicate
+</a>
</td>
<td>
The
@@ -8086,7 +8236,9 @@
</tr>
<tr>
<td>
+<a href="#ch_object">
rdf:object
+</a>
</td>
<td>
The
@@ -8958,6 +9110,45 @@
terms
of
syntax.
+</ins></li><li><ins class="diff-chg">
+Marked
+</ins><code><ins class="diff-chg">
+rdf:HTML
+</ins></code><ins class="diff-chg">
+and
+</ins><code><ins class="diff-chg">
+rdf:XMLLiteral
+</ins></code><ins class="diff-chg">
+as
+non-normative.
+</ins></li><li><ins class="diff-chg">
+Removed
+references
+to
+2004
+Primer
+from
+Secs.
+5.1,
+5.2
+and
+5.4.3.
+In
+the
+latter
+case
+the
+example
+referred
+to
+was
+moved
+into
+this
+document
+for
+readability
+purposes.
</ins></li></ul></section><section id="2004-changes" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h3 aria-level="2" role="heading" id="h3_2004-changes">
<span class="secno">
<ins class="diff-chg">B.2
@@ -9551,8 +9742,7 @@
<rdfs:comment>The class of literal values, eg. textual strings and integers.</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
</rdfs:Class>
-</del>
-<del class="diff-old"><rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement">
+<rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement">
<rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
<rdfs:label>Statement</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
@@ -9565,6 +9755,39 @@
<rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
</rdf:Property>
+<rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#predicate">
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>predicate</rdfs:label>
+ <rdfs:comment>The predicate of the subject RDF statement.</rdfs:comment>
+ <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
+ <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+</rdf:Property>
+<rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#object">
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>object</rdfs:label>
+ <rdfs:comment>The object of the subject RDF statement.</rdfs:comment>
+ <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
+ <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+</rdf:Property>
+<rdfs:Class rdf:about="http://www.w3.org/2000/01/rdf-schema#Container">
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
+ <rdfs:label>Container</rdfs:label>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+ <rdfs:comment>The class of RDF containers.</rdfs:comment>
+</rdfs:Class>
+<rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Bag">
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>Bag</rdfs:label>
+ <rdfs:comment>The class of unordered containers.</rdfs:comment>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Container"/>
+</rdfs:Class>
+</del>
+<del class="diff-old"><rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Seq">
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>Seq</rdfs:label>
+ <rdfs:comment>The class of ordered containers.</rdfs:comment>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Container"/>
+</rdfs:Class>
</del>
</dd>
<dt id="bib-RDF11-MT">
@@ -9578,26 +9801,25 @@
Patel-Schneider,
Editors.
</ins><cite>
-<del class="diff-old"><rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#predicate">
+<del class="diff-old"><rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Alt">
<rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>predicate</rdfs:label>
- <rdfs:comment>The predicate of the subject RDF statement.</rdfs:comment>
- <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
-</rdf:Property>
+ <rdfs:label>Alt</rdfs:label>
+ <rdfs:comment>The class of containers of alternatives.</rdfs:comment>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Container"/>
+</rdfs:Class>
</del>
<a href="http://www.w3.org/TR/2013/CR-rdf11-mt-20131105/">
<ins class="diff-chg">RDF
1.1
Semantics.
</ins></a>
-<del class="diff-old"><rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#object">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>object</rdfs:label>
- <rdfs:comment>The object of the subject RDF statement.</rdfs:comment>
- <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
-</rdf:Property>
+<del class="diff-old"><rdfs:Class rdf:about="http://www.w3.org/2000/01/rdf-schema#ContainerMembershipProperty">
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
+ <rdfs:label>ContainerMembershipProperty</rdfs:label>
+ <rdfs:comment>The class of container membership properties, rdf:_1, rdf:_2, ...,
+ all of which are sub-properties of 'member'.</rdfs:comment>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
+</rdfs:Class>
</del>
</cite>
<ins class="diff-chg">5
@@ -9622,12 +9844,13 @@
</ins><a href="http://www.w3.org/TR/rdf11-mt/"><ins class="diff-chg">
http://www.w3.org/TR/rdf11-mt/
</ins></a>
-<del class="diff-old"><rdfs:Class rdf:about="http://www.w3.org/2000/01/rdf-schema#Container">
+<del class="diff-old"><rdf:Property rdf:about="http://www.w3.org/2000/01/rdf-schema#member">
<rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>Container</rdfs:label>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
- <rdfs:comment>The class of RDF containers.</rdfs:comment>
-</rdfs:Class>
+ <rdfs:label>member</rdfs:label>
+ <rdfs:comment>A member of the subject resource.</rdfs:comment>
+ <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+ <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+</rdf:Property>
</del>
</dd>
<dt id="bib-TRIG">
@@ -9639,12 +9862,13 @@
Seaborne,
Editors.
</ins><cite>
-<del class="diff-old"><rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Bag">
+<del class="diff-old"><rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#value">
<rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>Bag</rdfs:label>
- <rdfs:comment>The class of unordered containers.</rdfs:comment>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Container"/>
-</rdfs:Class>
+ <rdfs:label>value</rdfs:label>
+ <rdfs:comment>Idiomatic property used for structured values.</rdfs:comment>
+ <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+ <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+</rdf:Property>
</del>
<a href="http://www.w3.org/TR/2013/WD-trig-20130919/">
<ins class="diff-chg">TriG:
@@ -9652,12 +9876,7 @@
Dataset
Language
</ins></a>
-<del class="diff-old"><rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Seq">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>Seq</rdfs:label>
- <rdfs:comment>The class of ordered containers.</rdfs:comment>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Container"/>
-</rdfs:Class>
+<del class="diff-old"><!-- the following are new additions, Nov 2002 -->
</del>
</cite>.
<ins class="diff-chg">19
@@ -9682,12 +9901,11 @@
</ins><a href="http://www.w3.org/TR/trig/"><ins class="diff-chg">
http://www.w3.org/TR/trig/
</ins></a>
-<del class="diff-old"><rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Alt">
+<del class="diff-old"><rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#List">
<rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>Alt</rdfs:label>
- <rdfs:comment>The class of containers of alternatives.</rdfs:comment>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Container"/>
-</rdfs:Class>
+ <rdfs:label>List</rdfs:label>
+ <rdfs:comment>The class of RDF Lists.</rdfs:comment>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/></rdfs:Class>
</del>
</dd>
<dt id="bib-TURTLE">
@@ -9699,13 +9917,11 @@
Carothers,
Editors.
</ins><cite>
-<del class="diff-old"><rdfs:Class rdf:about="http://www.w3.org/2000/01/rdf-schema#ContainerMembershipProperty">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>ContainerMembershipProperty</rdfs:label>
- <rdfs:comment>The class of container membership properties, rdf:_1, rdf:_2, ...,
- all of which are sub-properties of 'member'.</rdfs:comment>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
-</rdfs:Class>
+<del class="diff-old"><rdf:List rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#nil">
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>nil</rdfs:label>
+ <rdfs:comment>The empty list, with no items in it. If the rest of a list is nil then the list has no more items in it.</rdfs:comment>
+</rdf:List>
</del>
<a href="http://www.w3.org/TR/2013/CR-turtle-20130219/">
<ins class="diff-chg">RDF
@@ -9716,11 +9932,11 @@
Triple
Language.
</ins></a>
-<del class="diff-old"><rdf:Property rdf:about="http://www.w3.org/2000/01/rdf-schema#member">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>member</rdfs:label>
- <rdfs:comment>A member of the subject resource.</rdfs:comment>
- <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+<del class="diff-old"><rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#first">
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>first</rdfs:label>
+ <rdfs:comment>The first item in the subject RDF list.</rdfs:comment>
+ <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#List"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
</rdf:Property>
</del>
@@ -9747,12 +9963,12 @@
</ins><a href="http://www.w3.org/TR/turtle/"><ins class="diff-chg">
http://www.w3.org/TR/turtle/
</ins></a>
-<del class="diff-old"><rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#value">
+<del class="diff-old"><rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#rest">
<rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>value</rdfs:label>
- <rdfs:comment>Idiomatic property used for structured values.</rdfs:comment>
- <rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
+ <rdfs:label>rest</rdfs:label>
+ <rdfs:comment>The rest of the subject RDF list after the first item.</rdfs:comment>
+ <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#List"/>
+ <rdfs:range rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#List"/>
</rdf:Property>
</del>
</dd>
@@ -9760,7 +9976,19 @@
</section>
<section id="informative-references" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_informative-references">
-<del class="diff-old"><!-- the following are new additions, Nov 2002 -->
+<del class="diff-old"><rdfs:Class rdf:about="http://www.w3.org/2000/01/rdf-schema#Datatype">
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
+ <rdfs:label>Datatype</rdfs:label>
+ <rdfs:comment>The class of RDF datatypes.</rdfs:comment>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Class"/>
+</rdfs:Class>
+
+<rdfs:Datatype rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral">
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
+ <rdfs:label>XMLLiteral</rdfs:label>
+ <rdfs:comment>The class of XML literal values.</rdfs:comment>
+</rdfs:Datatype>
</del>
<span class="secno">
<ins class="diff-chg">C.2
@@ -9773,11 +10001,9 @@
Tim
Berners-Lee.
</ins><cite>
-<del class="diff-old"><rdfs:Class rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#List">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>List</rdfs:label>
- <rdfs:comment>The class of RDF Lists.</rdfs:comment>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/></rdfs:Class>
+<del class="diff-old"><rdf:Description rdf:about="http://www.w3.org/2000/01/rdf-schema#">
+ <rdfs:seeAlso rdf:resource="http://www.w3.org/2000/01/rdf-schema-more"/>
+</rdf:Description>
</del>
<a href="http://www.w3.org/DesignIssues/RDFnot.html">
<ins class="diff-chg">What
@@ -9787,11 +10013,7 @@
can
represent
</ins></a>
-<del class="diff-old"><rdf:List rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#nil">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>nil</rdfs:label>
- <rdfs:comment>The empty list, with no items in it. If the rest of a list is nil then the list has no more items in it.</rdfs:comment>
-</rdf:List>
+<del class="diff-old"></rdf:RDF>
</del>
</cite>.
<ins class="diff-chg">1998.
@@ -9806,14 +10028,6 @@
Working
Group.
</ins><a href="http://www.w3.org/TR/owl2-overview/">
-<del class="diff-old"><rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#first">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>first</rdfs:label>
- <rdfs:comment>The first item in the subject RDF list.</rdfs:comment>
- <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#List"/>
- <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
-</rdf:Property>
-</del>
<cite>
<ins class="diff-chg">OWL
2
@@ -9825,14 +10039,6 @@
(Second
Edition)
</ins></cite>
-<del class="diff-old"><rdf:Property rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#rest">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>rest</rdfs:label>
- <rdfs:comment>The rest of the subject RDF list after the first item.</rdfs:comment>
- <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#List"/>
- <rdfs:range rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#List"/>
-</rdf:Property>
-</del>
</a>.
<ins class="diff-chg">11
December
@@ -9843,55 +10049,6 @@
</ins><a href="http://www.w3.org/TR/owl2-overview/"><ins class="diff-chg">
http://www.w3.org/TR/owl2-overview/
</ins></a>
-<del class="diff-old"><rdfs:Class rdf:about="http://www.w3.org/2000/01/rdf-schema#Datatype">
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
- <rdfs:label>Datatype</rdfs:label>
- <rdfs:comment>The class of RDF datatypes.</rdfs:comment>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Class"/>
-</rdfs:Class>
-
-<rdfs:Datatype rdf:about="http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral">
- <rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
- <rdfs:label>XMLLiteral</rdfs:label>
- <rdfs:comment>The class of XML literal values.</rdfs:comment>
-</rdfs:Datatype>
-</del>
-</dd>
-<dt id="bib-RDF-CONCEPTS">
-<ins class="diff-chg">[RDF-CONCEPTS]
-</ins></dt><dd rel="dcterms:references"><ins class="diff-chg">
-Graham
-Klyne;
-Jeremy
-Carroll.
-</ins><a href="http://www.w3.org/TR/rdf-concepts/">
-<del class="diff-old"><rdf:Description rdf:about="http://www.w3.org/2000/01/rdf-schema#">
- <rdfs:seeAlso rdf:resource="http://www.w3.org/2000/01/rdf-schema-more"/>
-</rdf:Description>
-</del>
-<cite>
-<ins class="diff-chg">Resource
-Description
-Framework
-(RDF):
-Concepts
-and
-Abstract
-Syntax
-</ins></cite>
-<del class="diff-old"></rdf:RDF>
-</del>
-</a>.
-<ins class="diff-chg">10
-February
-2004.
-W3C
-Recommendation.
-URL:
-</ins><a href="http://www.w3.org/TR/rdf-concepts/"><ins class="diff-chg">
-http://www.w3.org/TR/rdf-concepts/
-</ins></a>
</dd>
<dt id="bib-RDF11-PRIMER">
<ins class="diff-chg">[RDF11-PRIMER]
@@ -9899,14 +10056,14 @@
Guus
Schreiber,
Yves
-Raimond,
-editors.
+Raimond.
</ins><cite>
-<a href="https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-primer/index.html#">
-<ins class="diff-chg">RDF
+<a href="https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-primer/index.html">
+<ins class="diff-new">RDF
1.1
Primer
-</ins></a>
+</ins>
+</a>
</cite>.
<ins class="diff-chg">2013.
The
@@ -9917,35 +10074,6 @@
at
</ins><a href="http://www.w3.org/TR/rdf11-primer/"><ins class="diff-chg">
http://www.w3.org/TR/rdf11-primer/
-</ins></a>.</dd><dt id="bib-RDFMS"><ins class="diff-chg">
-[RDFMS]
-</ins></dt><dd rel="dcterms:references"><ins class="diff-chg">
-Ora
-Lassila;
-Ralph
-R.
-Swick.
-</ins><cite>
-<a href="http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/">
-<ins class="diff-new">Resource
-Description
-Framework
-(RDF)
-Model
-and
-Syntax
-Specification
-</ins>
-</a>
-</cite>.
-<ins class="diff-chg">22
-February
-1999.
-W3C
-Recommendation.
-URL:
-</ins><a href="http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/"><ins class="diff-chg">
-http://www.w3.org/TR/1999/REC-rdf-syntax-19990222
</ins></a>.</dd></dl></section></section>
</body>
</html>
--- a/rdf-schema/index.html Fri Dec 13 08:05:45 2013 -0500
+++ b/rdf-schema/index.html Fri Dec 13 08:06:03 2013 -0500
@@ -122,9 +122,6 @@
</div>
<section id="ch_introduction">
<h2>Introduction</h2>
-
- <p class="issue">Check status of rdf:HTML and rdf:XMLLiteral before
- publication</p>
<p>The Resource Description Framework (RDF) is a general-purpose language
for
@@ -311,7 +308,7 @@
<code>rdfs:Datatype</code> and a <a href="#def-subclass">subclass</a>
of <a href="#ch_literal"><code>rdfs:Literal</code></a>.</p>
</section>
- <section id="ch_html">
+ <section id="ch_html" class="informative">
<h3>rdf:HTML</h3>
<p>The class <code>rdf:HTML</code> is the class of <a href="http://www.w3.org/TR/rdf11-concepts/#section-html">HTML
literal
@@ -319,7 +316,7 @@
<code>rdfs:Datatype</code> and a <a href="#def-subclass">subclass</a>
of <a href="#ch_literal"><code>rdfs:Literal</code></a>.</p>
</section>
- <section id="ch_xmlliteral">
+ <section id="ch_xmlliteral" class="informative">
<h3>rdf:XMLLiteral</h3>
<p>The class <code>rdf:XMLLiteral</code> is the class of <a href="http://www.w3.org/TR/rdf11-concepts/#section-XMLLiteral">XML
literal
@@ -350,7 +347,7 @@
also related by P'. This specification does not define a top
property that is the super-property of all properties.
</p>
- <div class="note">
+ <p class="note">
The basic facilities provided by <a href="#ch_domain"><code>rdfs:domain</code></a>
and <a href="#ch_range"><code>rdfs:range</code></a> do not provide any
direct way to indicate property restrictions that are local to a class.
@@ -358,7 +355,7 @@
and <a href="#ch_range"><code>rdfs:range</code></a> with sub-property
hierarchies, direct support for such declarations are provided by richer
Web Ontology languages such as OWL [[OWL2-OVERVIEW]].
- </div>
+ </p>
<section id="ch_range">
<h3>rdfs:range</h3>
<p><code>rdfs:range</code> is an instance of <a href="#ch_property"><code>rdf:Property</code></a>
@@ -553,10 +550,7 @@
<section id="ch_containervocab" class="informative">
<h3>Container Classes and Properties</h3>
<p>RDF containers are resources that are used to represent collections.
- An introduction
- to RDF containers with examples may be found in the <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#containers">RDF
-2004
- Primer</a>. The same resource may appear in a container more than
+ The same resource may appear in a container more than
once. Unlike containment in the physical world, a container may be
contained in itself.</p>
<p>Three different kinds of container are defined. Whilst the formal
@@ -669,22 +663,17 @@
<p>RDF containers are open in the sense that the core RDF specifications
define no mechanism to state that there are no more members. The RDF
Collection vocabulary of classes and properties can describe a closed
- collection, i.e. one that can have no more members. The reader is
- referred to
- the <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#collections">collections</a>
- section of the RDF 2004 primer for an informal introduction to
- collections with
- examples.</p>
+ collection, i.e. one that can have no more members.</p>
<p>A collection is represented as a list of items, a representation that
will be familiar to those with experience of Lisp and similar
programming languages. There is a <a href="http://www.w3.org/TR/turtle/#collections">shorthand
notation</a> in the Turtle syntax specification for representing
collections.</p>
- <div class="note">
+ <p class="note">
RDFS does not require that there be only one first element of a
list-like structure, or even that a list-like structure have a first
element.
- </div>
+ </p>
<section id="ch_list">
<h4>rdf:List</h4>
<p><code>rdf:List</code> is an instance of <a href="#ch_class"><code>rdfs:Class</code></a>
@@ -875,8 +864,16 @@
that may be used in
describing structured values.</p>
<p>rdf:value has no meaning on its own. It is provided as a piece of
- vocabulary that may be used in idioms such as illustrated in <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example21">example
- 21</a> of the RDF 1.0 primer. Despite
+ vocabulary that may be used in idioms such as illustrated
+ in example below:</p>
+ <pre class="example">
+<http://www.example.com/2002/04/products#item10245>
+ <http://www.example.org/terms/weight> [
+ rdf:value 2.4 ;
+ <http://www.example.org/terms/units> <http://www.example.org/units/kilograms>
+ ] .
+ </pre>
+ Despite
the lack of formal specification of the meaning of this property,
there is
value in defining it to encourage the use of a common idiom in
@@ -1164,7 +1161,13 @@
<li>Added the datatypes <code>rdf:langString</code> and <code>rdf:HTML</code>.
</li>
<li>Removed Appendix "RDF Schema in RDF/XML". It was informative, but
- now out of date, in terms of content and in terms of syntax.</li>
+ now out of date, in terms of content and in terms of
+ syntax.</li>
+ <li>Marked <code>rdf:HTML</code> and <code>rdf:XMLLiteral</code>
+ as non-normative.</li>
+ <li>Removed references to 2004 Primer from Secs. 5.1, 5.2
+ and 5.4.3. In the latter case the example referred to was
+ moved into this document for readability purposes. </li>
</ul>
</section>
<section id="2004-changes">
--- a/rdf-turtle/index.html Fri Dec 13 08:05:45 2013 -0500
+++ b/rdf-turtle/index.html Fri Dec 13 08:06:03 2013 -0500
@@ -123,26 +123,7 @@
.separated tbody tr td.r { text-align: right; padding: .5em; }
.grammar td { font-family: monospace; vertical-align: top; }
.grammar-literal { color: gray;}
- .atrisk {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #ffc;
-}
-
-/* .atrisk::before */
-.atrisktext
-{
- /* content: "Feature At Risk"; */
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #f00;
- background: #fff;
- padding: 3px 1em;
-}
-.grammar_comment { color: #A52A2A; font-style: italic; }
+ .grammar_comment { color: #A52A2A; font-style: italic; }
</style>
</head>
@@ -266,15 +247,15 @@
<a href="../rdf-concepts/index.html#dfn-iri">IRIs</a> may be written as relative or absolute IRIs or prefixed names.
Relative and absolute IRIs are enclosed in '<' and '>' and may contain <a href="#numeric">numeric escape sequences</a> (described below). For example <code><http://example.org/#green-goblin></code>.
</p>
- <p>Relative IRIs like <code><#green-goblin></code> are resolved relative to the current base IRI. A new base IRI can be defined using the '<code>@base</code>' directive. Specifics of this operation are defined in <a href="#sec-iri-references" class="sectionRef"></a> </p>
+ <p>Relative IRIs like <code><#green-goblin></code> are resolved relative to the current base IRI. A new base IRI can be defined using the '<code>@base</code>' or '<code>BASE</code>' directive. Specifics of this operation are defined in <a href="#sec-iri-references" class="sectionRef"></a> </p>
<p>
The token '<code>a</code>' in the predicate position of a Turtle triple represents the IRI <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</code> .
</p>
<p>
A <em id="prefixed-name">prefixed name</em> is a prefix label and a local part, separated by a colon ":".
- A prefixed name is turned into an IRI by concatenating the IRI associated with the prefix and the local part. The '<code>@prefix</code>' directive associates a prefix label with an IRI.
- Subsequent '<code>@prefix</code>' directives may re-map the same prefix label. </p>
+ A prefixed name is turned into an IRI by concatenating the IRI associated with the prefix and the local part. The '<code>@prefix</code>' or '<code>PREFIX</code>' directive associates a prefix label with an IRI.
+ Subsequent '<code>@prefix</code>' or '<code>PREFIX</code>' directives may re-map the same prefix label. </p>
<p>
To write <code>http://www.perceive.net/schemas/relationship/enemyOf</code> using a prefixed name: </p>
@@ -309,9 +290,15 @@
@base <http://one.example/> .
<subject2> <predicate2> <object2> . # relative IRIs, e.g. http://one.example/subject2
+BASE <http://one.example/>
+<subject2> <predicate2> <object2> . # relative IRIs, e.g. http://one.example/subject2
+
@prefix p: <http://two.example/> .
p:subject3 p:predicate3 p:object3 . # prefixed name, e.g. http://two.example/subject3
+PREFIX p: <http://two.example/>
+p:subject3 p:predicate3 p:object3 . # prefixed name, e.g. http://two.example/subject3
+
@prefix p: <path/> . # prefix p: now stands for http://one.example/path/
p:subject4 p:predicate4 p:object4 . # prefixed name, e.g. http://one.example/path/subject4
@@ -322,6 +309,9 @@
<http://伝言.example/?user=أكرم&channel=R%26D> a :subject8 . # a multi-script subject IRI .
</script></pre>
+ <div class="note">
+ <p>The '<code>@prefix</code>' and '<code>@base</code>' directives require a trailing '<code>.</code>' after the IRI, the equalivent '<code>PREFIX</code>' and '<code>BASE</code>' must not have a trailing '<code>.</code>' after the IRI part of the directive.
+ </div>
</section>
@@ -542,7 +532,7 @@
<p>An example of an RDF collection of two literals.</p>
<pre class="example"><script type="text/turtle">
-@prefix : <http://example.org/stuff/1.0/> .
+PREFIX : <http://example.org/stuff/1.0/>
:a :b ( "apple" "banana" ) .
</script></pre>
<p>which is short for (<a href="examples/example2.ttl">example2.ttl</a>):</p>
@@ -576,7 +566,7 @@
<p>RDF collections can be nested and can involve other syntactic forms:</p>
- <pre class="example untested"><script type="text/turtle">@prefix : <http://example.org/stuff/1.0/> .
+ <pre class="example untested"><script type="text/turtle">PREFIX : <http://example.org/stuff/1.0/>
(1 [:p :q] ( 2 ) ) :p2 :q2 .</script></pre>
<p>is syntactic sugar for:</p><pre class="example untested"><script type="text/turtle">@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@@ -603,7 +593,7 @@
<li>SPARQL permits variables (<code>?</code><em>name</em> or <code>$</code><em>name</em>) in any part of the triple of the form.</li>
<li>Turtle allows <a href="#grammar-production-directive">prefix and base declarations</a> anywhere outside of a triple. In SPARQL, they are only allowed in the <a href="http://www.w3.org/TR/sparql11-query/#rPrologue">Prologue</a> (at the start of the SPARQL query).</li>
- <li>SPARQL uses case insensitive keywords, except for '<code>a</code>'. Turtle's prefix and base declarations are case sensitive.</li>
+ <li>SPARQL uses case insensitive keywords, except for '<code>a</code>'. Turtle's <code>@prefix</code> and <code>@base</code> declarations are case sensitive, the SPARQL dervied <code>PREFIX</code> and <code>BASE</code> are case insensitive.</li>
<li>'<code>true</code>' and '<code>false</code>' are case insensitive in SPARQL and case sensitive in Turtle. <code>TrUe</code> is not a valid boolean value in Turtle.</li>
</ol>
@@ -674,11 +664,11 @@
Characters additionally allowed in IRI references are treated in the same way that unreserved characters are treated in URI references, per section 6.5 of <a href="http://www.ietf.org/rfc/rfc3987.txt" class="norm">Internationalized Resource Identifiers (IRIs)</a> [<a href="#rfc3987">RFC3987</a>].
</p>
<p>
- The <code>@base</code> directive defines the Base IRI used to resolve relative IRIs per RFC3986 section 5.1.1, "Base URI Embedded in Content".
+ The <code>@base</code> or <code>BASE</code> directive defines the Base IRI used to resolve relative IRIs per RFC3986 section 5.1.1, "Base URI Embedded in Content".
Section 5.1.2, "Base URI from the Encapsulating Entity" defines how the In-Scope Base IRI may come from an encapsulating document, such as a SOAP envelope with an xml:base directive or a mime multipart document with a Content-Location header.
The "Retrieval URI" identified in 5.1.3, Base "URI from the Retrieval URI", is the URL from which a particular Turtle document was retrieved.
If none of the above specifies the Base URI, the default Base URI (section 5.1.4, "Default Base URI") is used.
- Each <code>@base</code> directive sets a new In-Scope Base URI, relative to the previous one.
+ Each <code>@base</code> or <code>BASE</code> directive sets a new In-Scope Base URI, relative to the previous one.
</p>
</section>
@@ -813,7 +803,7 @@
</thead>
<tbody>
<tr>
- <td class="r"><span style="font-weight:bold;">IRI</span>s, used as <a href="#grammar-production-IRIref">RDF terms</a> or as in <a href="#grammar-production-prefixID">@prefix</a> or <a href="#grammar-production-base">@base</a> declarations</td>
+ <td class="r"><span style="font-weight:bold;">IRI</span>s, used as <a href="#grammar-production-IRIref">RDF terms</a> or as in <a href="#grammar-production-prefixID">@prefix</a>, <a href="#grammar-production-sparqlPrefix">PREFIX</a>, <a href="#grammar-production-base">@base</a>, or <a href="#grammar-production-sparqlBase">BASE</a> declarations</td>
<td style="background-color: green; border:1px solid black;">yes</td>
<td>no</td>
<td>no</td>
@@ -837,13 +827,6 @@
</section>
<section id="sec-grammar-grammar">
<h3>Grammar</h3>
- <div class="atrisk"><p class="atrisktext">Feature At Risk</p>
- <p>The RDF Working Group proposes to make the following changes to align Turtle with SPARQL.</p>
- <ul>
- <li>The addition of <a href="#grammar-production-sparqlPrefix">sparqlPrefix</a> and <a href="#grammar-production-sparqlBase">sparqlBase</a> which allow for using SPARQL style <code>BASE</code> and <code>PREFIX</code> directives in a Turtle document.</li>
- </ul>
- <p>Feedback, both positive and negative, is invited by sending email to mailing list <a href="mailto:public-rdf-comments@w3.org">public-rdf-comments@w3.org</a> (<a href="mailto:public-rdf-comments-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-rdf-comments/">archives</a>).</p>
- </div>
<p>The <abbr title="Extended Backus–Naur Form">EBNF</abbr> used here is defined in XML 1.0
[[!EBNF-NOTATION]]. Production labels consisting of a number and a final 's', e.g. [<a href="http://www.w3.org/TR/sparql11-query/#rRDFLiteral"><span class="prodNo">60s</span></a>], reference the production with that number in the <a href="http://www.w3.org/TR/sparql11-query/#sparqlGrammar">SPARQL Query Language for RDF grammar</a> [[RDF-SPARQL-QUERY]].
</p>
@@ -1136,12 +1119,12 @@
<dd>No widely deployed applications are known to use this media type. It may be used by some web services and clients consuming their data.</dd>
<dt>Additional information:</dt>
<dt>Magic number(s):</dt>
- <dd>Turtle documents may have the strings '@prefix' or '@base' (case dependent) near the beginning of the document.</dd>
+ <dd>Turtle documents may have the strings '@prefix' or '@base' (case dependent) or the strings 'PREFIX' or 'BASE' (case independent) near the beginning of the document.</dd>
<dt>File extension(s):</dt>
<dd>".ttl"</dd>
<dt>Base URI:</dt>
- <dd>The Turtle '@base <IRIref>' term can change the current base URI for relative IRIrefs in the query language that are used sequentially later in the document.</dd>
+ <dd>The Turtle '@base <IRIref>' or 'BASE <IRIref>' term can change the current base URI for relative IRIrefs in the query language that are used sequentially later in the document.</dd>
<dt>Macintosh file type code(s):</dt>
<dd>"TEXT"</dd>
<dt>Person & email address to contact for further information:</dt>
@@ -1184,19 +1167,29 @@
</section>
<section id="sec-changelog" class="appendix">
- <h2>Changes since the last publication of this document</h2>
-
+ <h2>Change Log</h2>
+ <section>
+ <h2>Changes from Candidate Recommendation 19 February 2013 to this version</h2>
<ul>
+ <li>The addition of <a href="#grammar-production-sparqlPrefix">sparqlPrefix</a> and <a href="#grammar-production-sparqlBase">sparqlBase</a> which allow for using SPARQL style <code>BASE</code> and <code>PREFIX</code> directives in a Turtle document. No longer at risk.</li>
+ </ul>
+ </section>
+ <section>
+ <h3>Changes in Working Drafts to Candidate Recommendation</h3>
+ <ul>
<li>Renaming for STRING_* productions to STRING_LITERAL_QUOTE sytle names rather than numbers
<li>Local part of prefix names can now include ":"
- <li>Turtle in HTML
- <li>Renaming of grammar tokens and rules around IRIs
- <li>Reserved character escape sequences
- <li>String escape sequences limited to strings
- <li>Numeric escape sequences limited to IRIs and Strings
- <li>Support top-level blank-predicate-object lists
- <li>Whitespace required between @prefix and prefix label
- </ul>
+ <li>Turtle in HTML
+ <li>Renaming of grammar tokens and rules around IRIs
+ <li>Reserved character escape sequences
+ <li>String escape sequences limited to strings
+ <li>Numeric escape sequences limited to IRIs and Strings
+ <li>Support top-level blank-predicate-object lists
+ <li>Whitespace required between @prefix and prefix label
+ </ul>
+ </section>
+ <section>
+ <h3>Other changes</h3>
<p>Other changes since the Team Submission
<a href="http://www.w3.org/TeamSubmission/2008/SUBM-turtle-20080114">W3C Turtle Submission 2008-01-14</a>
@@ -1220,6 +1213,7 @@
<li>explicitly allowed re-use of the same prefix.</li>
<li>Added <a href="#sec-parsing">parsing rules</a>.</li>
</ul>
+ </section>
</section>
--- a/rdf-turtle/n-triples.html Fri Dec 13 08:05:45 2013 -0500
+++ b/rdf-turtle/n-triples.html Fri Dec 13 08:06:03 2013 -0500
@@ -76,9 +76,7 @@
wgPatentURI: "http://www.w3.org/2004/01/pp-impl/46168/status",
// doRDFa: true,
testSuiteURI: "http://www.w3.org/2013/N-TriplesTests/",
- implementationReportURI: "https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/reports/n-triples.html"
-
-
+ implementationReportURI: "https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/reports-nt/index.html"
};
</script>
<style type="text/css">
@@ -232,10 +230,12 @@
<li><code>HEX</code> MUST use only uppercase letters (<code>[A-F]</code>).</li>
<li>Characters MUST NOT be represented by <code>UCHAR</code>.</li>
<li>Within <a href="#grammar-production-STRING_LITERAL_QUOTE">STRING_LITERAL_QUOTE</a>,
- only characters not allowed directly in
- <a href="#grammar-production-STRING_LITERAL_QUOTE">STRING_LITERAL_QUOTE</a> (<code>U+0022</code>, <code>U+005C</code>, <code>U+000A</code>, <code>U+000D</code>)
-should use <code>ECHAR</code>.
- For all other characters, <code>ECHAR</code> MUST NOT be used.</li>
+ only the characters
+ <code>U+0022</code>, <code>U+005C</code>, <code>U+000A</code>, <code>U+000D</code>
+ are encoded using <code>ECHAR</code>.
+ <code>ECHAR</code> MUST NOT be used for characters that are
+ allowed directly in
+ <a href="#grammar-production-STRING_LITERAL_QUOTE">STRING_LITERAL_QUOTE</a>. </li>
</ul>
</section>
@@ -330,7 +330,8 @@
<section id="section-ack" class="informative">
<h2>Acknowledgements</h2>
- <p>The editor of the RDF 1.1 edition acknowledges valuable contributions from Gregg Kellogg, Eric Prud'hommeaux, Dave Beckett, David Robillard, Gregory Williams, Pat Hayes, Richard Cyganiak, Henry S. Thompson, and David Booth.</p>
+ <p>The editor of the RDF 1.1 edition acknowledges valuable contributions from Gregg Kellogg, Eric Prud'hommeaux, Dave Beckett, David Robillard, Gregory Williams, Pat Hayes, Richard Cyganiak, Henry S. Thompson,
+Peter Ansell and David Booth.</p>
<p>This specification is a product of extended deliberations by the
<a href="http://www.w3.org/2000/09/dbwg/details?group=46168&public=1">members of the RDF Working Group</a>.
It draws upon the earlier specification in <a href="http://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#ntriples">RDF Test Cases</a>, edited by Dave Beckett.</p>
@@ -339,7 +340,7 @@
<section id="sec-changes" class="appendix">
<h2>Changes to this document<h2>
<h3>Changes since last publication as Last Call Working Draft</h3>
- <p>No substitutive changes.</p>
+ <p>The text for "Canonical N-Triples" has been made into a separate section.</p>
<h3>Changes since original publication as Note</h3>
<ul>
<li>Section defines <a href="#dfn-canonical-n-triples-document">canonical N-Triples document</a>.
--- a/rdf11-testcases/index.html Fri Dec 13 08:05:45 2013 -0500
+++ b/rdf11-testcases/index.html Fri Dec 13 08:06:03 2013 -0500
@@ -11,7 +11,7 @@
localBiblio: localBibliography,
// specification status (e.g. WD, LC, WG-NOTE, etc.). If in doubt use ED.
- specStatus: "unofficial",
+ specStatus: "ED",
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "rdf11-testcases",
--- a/trig/index.html Fri Dec 13 08:05:45 2013 -0500
+++ b/trig/index.html Fri Dec 13 08:06:03 2013 -0500
@@ -881,14 +881,50 @@
<section id="sec-changes" class="appendix">
<h2>Changes since the last publication of this document</h2>
- <ul>
- <li>The "Features at risk" (uses of <code>GRAPH</code>, default
- graph triple with enclosing
- <code>{</code>...<code>}</code>)
- have been accepted by the Working Group and been incorporated into
- the document.
- </li>
- </ul>
+ <p>A bug in the grammar in rule 4g has been corrected.</p>
+
+ <table class="grammar">
+ <tbody class="grammar-productions">
+ <tr>
+ <td>[4g]</td>
+ <td><code>triples2</code></td>
+ <td>::=</td>
+ <td><a href='#grammar-production-blankNodePropertyList'>blankNodePropertyList</a>
+ <a href='#grammar-production-predicateObjectList'>predicateObjectList</a>?
+ '<code class='grammar-literal'>.</code>'
+ <code>| </code>
+ <a href='#grammar-production-collection'>collection</a>
+ <a href='#grammar-production-predicateObjectList'>predicateObjectList</a>
+ '<code class='grammar-literal'>.</code>'
+ </td>
+ </tr>
+ </tbody>
+ </table>
+
+ <p>The old rule was:</p>
+
+ <table class="grammar">
+ <tbody class="grammar-productions">
+ <tr>
+ <td>[4g]</td>
+ <td><code>triples2</code></td>
+ <td>::=</td>
+ <td>(<a href="#grammar-production-blankNodePropertyList">blankNodePropertyList</a> <code>| </code> <a href="#grammar-production-collection">collection</a>) <a href="#grammar-production-predicateObjectList">predicateObjectList</a>?
+ '<code class="grammar-literal">.</code>'
+ </td>
+ </tr>
+ </tbody>
+ </table>
+
+ <p>The effect of this change is to not allow as a TriG document:</p>
+ <pre>
+ (1 2 3) .
+ </pre>
+ and
+ <pre>
+ () .
+ </pre>
+ <p> which are not legal Turtle documents.</p>
</section>
</body>
</html>
--- a/trig/trig-bnf.html Fri Dec 13 08:05:45 2013 -0500
+++ b/trig/trig-bnf.html Fri Dec 13 08:06:03 2013 -0500
@@ -18,11 +18,19 @@
<td>::=</td>
<td><a href='#grammar-production-labelOrSubject'>labelOrSubject</a> (<a href='#grammar-production-wrappedGraph'>wrappedGraph</a> <code>| </code> <a href='#grammar-production-predicateObjectList'>predicateObjectList</a> '<code class='grammar-literal'>.</code>')</td>
</tr>
- <tr id="grammar-production-triples2" data-grammar-original="[4g] triples2 ::=( blankNodePropertyList | collection ) predicateObjectList? '.'" data-grammar-expression="(',', [('|', [('id', 'blankNodePropertyList'), ('id', 'collection')]), ('?', ('id', 'predicateObjectList')), ("'", '.')])" >
+<tr id="grammar-production-triples2" data-grammar-original="[4g] triples2 ::= blankNodePropertyList predicateObjectList? '.' | collection predicateObjectList '.' " data-grammar-expression="" >
<td>[4g]</td>
<td><code>triples2</code></td>
<td>::=</td>
- <td>(<a href='#grammar-production-blankNodePropertyList'>blankNodePropertyList</a> <code>| </code> <a href='#grammar-production-collection'>collection</a>) <a href='#grammar-production-predicateObjectList'>predicateObjectList</a>? '<code class='grammar-literal'>.</code>'</td>
+
+ <td><a href='#grammar-production-blankNodePropertyList'>blankNodePropertyList</a>
+ <a href='#grammar-production-predicateObjectList'>predicateObjectList</a>?
+ '<code class='grammar-literal'>.</code>'
+ <code>| </code>
+ <a href='#grammar-production-collection'>collection</a>
+ <a href='#grammar-production-predicateObjectList'>predicateObjectList</a>
+ '<code class='grammar-literal'>.</code>'
+ </td>
</tr>
<tr id="grammar-production-wrappedGraph" data-grammar-original="[5g] wrappedGraph ::='{' triplesBlock? '}'" data-grammar-expression="(',', [("'", '{'), ('?', ('id', 'triplesBlock')), ("'", '}')])" >
<td>[5g]</td>
--- a/trig/trig.bnf Fri Dec 13 08:05:45 2013 -0500
+++ b/trig/trig.bnf Fri Dec 13 08:06:03 2013 -0500
@@ -9,7 +9,8 @@
labelOrSubject ( wrappedGraph | predicateObjectList '.' )
[4g] triples2 ::=
- ( blankNodePropertyList | collection ) predicateObjectList? '.'
+ blankNodePropertyList predicateObjectList? '.' |
+ collection predicateObjectList '.'
[5g] wrappedGraph ::=
'{' triplesBlock? '}'