--- a/rdf-concepts/index.html Wed Oct 16 12:03:59 2013 -0400
+++ b/rdf-concepts/index.html Wed Oct 16 12:56:23 2013 -0400
@@ -4,24 +4,24 @@
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>RDF 1.1 Concepts and Abstract Syntax</title>
<style type="text/css">
-.figure { text-align: center; }
-.figure a[href]:hover { background: transparent; }
-table td, table th { border: 1px solid #ddd; padding: 0.2em 0.5em; }
+ .figure { text-align: center; }
+ .figure a[href]:hover { background: transparent; }
+ table td, table th { border: 1px solid #ddd; padding: 0.2em 0.5em; }
</style>
<script src="https://www.w3.org/Tools/respec/respec-w3c-common" class="remove"></script>
<script class='remove'>
var respecConfig = {
// specification status (e.g. WD, LC, WG-NOTE, etc.). If in doubt use ED.
- specStatus: "ED",
-
-localBiblio:{
-"RDF11-MT" : "Patrick J. Hayes; Peter F. Patel-Schneider. <a href=\"http://www.w3.org/TR/2013/WD-rdf11-mt-20130723/\"><cite>RDF 1.1 Semantics</cite></a>. 23 July 2013. W3C Last Call Working Draft. URL: <a href=\"http://www.w3.org/TR/2013/WD-rdf11-mt-20130723/\">http://www.w3.org/TR/2013/WD-rdf11-mt-20130723/</a>. The latest edition is available at <a href=\"http://www.w3.org/TR/rdf11-mt/\">http://www.w3.org/TR/rdf11-mt/</a>",
+ specStatus: "CR",
-"TURTLE-CR":"Eric Prud'hommeaux, Gavin Carothers. <cite><a href=\"http://www.w3.org/TR/2013/CR-turtle-20130219/\">Turtle; Terse RDF Triple Language</a></cite> 19 February 2013. W3C Candidate Recommendation. 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>",
+ localBiblio:{
+ "RDF11-MT" : "Patrick J. Hayes; Peter F. Patel-Schneider. <a href=\"http://www.w3.org/TR/2013/WD-rdf11-mt-20130723/\"><cite>RDF 1.1 Semantics</cite></a>. 23 July 2013. W3C Last Call Working Draft. URL: <a href=\"http://www.w3.org/TR/2013/WD-rdf11-mt-20130723/\">http://www.w3.org/TR/2013/WD-rdf11-mt-20130723/</a>. The latest edition is available at <a href=\"http://www.w3.org/TR/rdf11-mt/\">http://www.w3.org/TR/rdf11-mt/</a>",
-"N-TRIPLES" : "Gavin Carothers. <a href=\"http://www.w3.org/TR/2013/NOTE-n-triples-20130409/\"><cite>N-Triples</cite></a>. 9 April 2013. W3C Working Group Note. URL: <a href=\"http://www.w3.org/TR/2013/NOTE-n-triples-20130409/\">http://www.w3.org/TR/2013/NOTE-n-triples-20130409/</a>. The latest edition is available at <a href=\"http://www.w3.org/TR/n-triples/\">http://www.w3.org/TR/n-triples/</a>"
-},
-
+ "TURTLE-CR":"Eric Prud'hommeaux, Gavin Carothers. <cite><a href=\"http://www.w3.org/TR/2013/CR-turtle-20130219/\">Turtle; Terse RDF Triple Language</a></cite> 19 February 2013. W3C Candidate Recommendation. 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>",
+
+ "N-TRIPLES" : "Gavin Carothers. <a href=\"http://www.w3.org/TR/2013/NOTE-n-triples-20130409/\"><cite>N-Triples</cite></a>. 9 April 2013. W3C Working Group Note. URL: <a href=\"http://www.w3.org/TR/2013/NOTE-n-triples-20130409/\">http://www.w3.org/TR/2013/NOTE-n-triples-20130409/</a>. The latest edition is available at <a href=\"http://www.w3.org/TR/n-triples/\">http://www.w3.org/TR/n-triples/</a>"
+ },
+
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "rdf11-concepts",
@@ -30,7 +30,8 @@
// subtitle : "an excellent document",
// if you wish the publication date to be other than today, set this
- // publishDate: "2013-07-23",
+ publishDate: "2013-11-05",
+ crEnd: "2013-11-26",
// if the specification's copyright date is a range of years, specify
// the start date here:
@@ -38,8 +39,8 @@
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
- previousPublishDate: "2013-01-15",
- previousMaturity: "WD",
+ previousPublishDate: "2013-07-23",
+ previousMaturity: "LC",
// if there a publicly available Editor's Draft, this is the link
edDraftURI: "https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-concepts/index.html",
@@ -66,20 +67,24 @@
company: "3 Round Stones", companyURL: "http://3roundstones.com/",
},
],
- otherLinks: [ {
- key: "Previous Editors",
- data: [{
- value: "Graham Klyne",
- href: "http://www.ninebynine.org/"
- }, {
- value: "Jeremy J. Carroll"
- }, {
- value: "Brian McBride"
- }
- }
- ],
- // authors, add as many as you like.
+ otherLinks: [
+ {
+ key: "Previous Editors",
+ data: [
+ {
+ value: "Graham Klyne",
+ href: "http://www.ninebynine.org/"
+ }, {
+ value: "Jeremy J. Carroll"
+ }, {
+ value: "Brian McBride"
+ }
+ ]
+ }
+ ],
+
+ // authors, add as many as you like.
// This is optional, uncomment if you have authors as well as editors.
// only "name" is required. Same format as editors.
@@ -87,16 +92,16 @@
// { name: "Your Name", url: "http://example.org/",
// company: "Your Company", companyURL: "http://example.com/" },
//],
-
+
// name of the WG
wg: "RDF Working Group",
-
+
// URI of the public WG page
wgURI: "http://www.w3.org/2011/rdf-wg/",
-
+
// name (with the @w3c.org) of the public mailing to which comments are due
wgPublicList: "public-rdf-comments",
-
+
// URI of the patent status for this WG, for Rec-track documents
// !!!! IMPORTANT !!!!
// This is important for Rec-track documents, do not copy a patent URI from a random
@@ -107,7 +112,7 @@
// if this parameter is set to true, ReSpec.js will embed various RDFa attributes
// throughout the generated specification. The triples generated use vocabulary items
// from the dcterms, foaf, and bibo. The parameter defaults to false.
- // doRDFa: "1.1",
+ doRDFa: "1.1",
};
</script>
@@ -116,9 +121,9 @@
<body>
<div class="head">
-
+
<section id="abstract">
-
+
<p>The Resource Description Framework (RDF) is a framework for
representing information in the Web.</p>
<p>RDF 1.1 Concepts and Abstract Syntax defines an abstract syntax
@@ -134,6 +139,10 @@
RDF graphs.</p>
</section>
+<section id="sotd">
+
+</section>
+
</div>
<section id="section-Introduction" class="informative">
@@ -149,7 +158,7 @@
<ul>
<li>the <a href="http://www.w3.org/TR/rdf11-mt/">formal
model-theoretic semantics for RDF and RDFS</a> [[!RDF11-MT]].</li>
-
+
<li>serialization syntaxes for storing and exchanging RDF
(e.g., <a href="http://www.w3.org/TR/turtle/">Turtle</a> [[TURTLE-CR]]
and <a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF/XML</a>
@@ -222,13 +231,13 @@
<section id="referents">
<h3>The Referent of an IRI</h3>
- <p>The <a>resource</a> <a title="denote">denoted</a> by an <a>IRI</a>
- is also called its <dfn>referent</dfn>. For some IRIs with particular
- meanings, such as those identifying XSD datatypes, the referent is
- fixed by this specification. For all other IRIs, what exactly is
- denoted by any given IRI is not defined by this specification. Other
- specifications may fix IRI referents, or apply other constraints on
- what may be the referent of any IRI.</p>
+ <p>The <a>resource</a> <a title="denote">denoted</a> by an <a>IRI</a>
+ is also called its <dfn>referent</dfn>. For some IRIs with particular
+ meanings, such as those identifying XSD datatypes, the referent is
+ fixed by this specification. For all other IRIs, what exactly is
+ denoted by any given IRI is not defined by this specification. Other
+ specifications may fix IRI referents, or apply other constraints on
+ what may be the referent of any IRI.</p>
<p>Guidelines for determining the <a>referent</a> of an <a>IRI</a> are
provided in other documents, like
@@ -240,15 +249,15 @@
<ul>
<li>IRIs have global scope: Two different appearances of an IRI
- <a>denote</a> the same <a>resource</a>.</li>
-
+ <a>denote</a> the same <a>resource</a>.</li>
+
<li>By social convention, the
<a href="http://www.w3.org/TR/webarch/#uri-ownership">IRI owner</a>
[[WEBARCH]] gets to say what what the intended (or usual)
- referent of an <a>IRI</a> is. Applications and users need not
- abide by this intended denotation, but there may be a loss of
- interoperability with other applications and users if they do
- not do so.</li>
+ referent of an <a>IRI</a> is. Applications and users need not
+ abide by this intended denotation, but there may be a loss of
+ interoperability with other applications and users if they do
+ not do so.</li>
<li>The IRI owner can establish the intended <a>referent</a>
by means of a specification or other document that explains
@@ -269,15 +278,15 @@
</ul>
<p>Perhaps the most important characteristic of <a title="IRI">IRIs</a>
- in web architecture is that they can be
+ in web architecture is that they can be
<a href="http://www.w3.org/TR/webarch/#uri-dereference">dereferenced</a>,
and hence serve as starting points for interactions with a remote server.
This specification is not concerned with such interactions.
It does not define an interaction model. It only treats IRIs as globally
unique identifiers in a graph data model that describes resources.
- However, those interactions are critical to the concept of
- <em><a href="http://www.w3.org/DesignIssues/LinkedData.html">Linked Data</a></em> [[LINKED-DATA]],
- which makes use of the RDF data model and serialization formats.</p>
+ However, those interactions are critical to the concept of
+ <em><a href="http://www.w3.org/DesignIssues/LinkedData.html">Linked Data</a></em> [[LINKED-DATA]],
+ which makes use of the RDF data model and serialization formats.</p>
</section>
<section id="vocabularies">
@@ -296,7 +305,7 @@
known as a <dfn>namespace prefix</dfn>. Some examples:
<table class="simple">
- <caption>Some example namespace prefixes and IRIs</caption>
+ <caption>Some example namespace 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>rdfs</td><td><a href="http://www.w3.org/2000/01/rdf-schema#"><code>http://www.w3.org/2000/01/rdf-schema#</code></a></td><td>The RDF Schema vocabulary [[RDF-SCHEMA]]</td></tr>
@@ -384,7 +393,7 @@
<a title="RDF graph">RDF graphs</a>. All but one of these graphs have
an associated <a>IRI</a> or blank node. They are called
<a title="named graph">named graphs</a>, and the IRI or blank node
- is called the <a>graph name</a>.
+ is called the <a>graph name</a>.
The remaining graph does not have an associated IRI, and is called
the <a>default graph</a> of the RDF dataset.</p>
@@ -401,8 +410,8 @@
simple <dfn>logical expression</dfn>, or claim about the world.
An <a>RDF graph</a> is the conjunction (logical <em>AND</em>) of
its triples. The precise details of this meaning of RDF triples and graphs are
- the subject of the RDF Semantics specification [[RDF-MT]], which yields the
- following relationships between <a>RDF graph</a>s:</p>
+ the subject of the RDF Semantics specification [[RDF-MT]], which yields the
+ following relationships between <a>RDF graph</a>s:</p>
<dl>
<dt><dfn>Entailment</dfn></dt>
@@ -426,17 +435,17 @@
</dl>
<p>An <dfn>entailment regime</dfn> [[RDF-MT]] is a specification that
- defines precise conditions that make these relationships hold.
+ defines precise conditions that make these relationships hold.
RDF itself recognizes only some basic cases of entailment, equivalence
and inconsistency. Other specifications, such as
<a href="http://www.w3.org/TR/rdf-schema/">RDF Schema</a> [[RDF-SCHEMA]]
and <a href="http://www.w3.org/TR/owl2-overview/">OWL 2</a>
[[OWL2-OVERVIEW]], add more powerful entailment regimes,
as do some domain-specific <a title="RDF vocabulary">vocabularies</a>.
- </p>
+ </p>
<p>This specification does not constrain how implementations
- use the logical relationships defined by
+ use the logical relationships defined by
<a title="entailment regime">entailment regimes</a>.
Implementations may or may not detect
<a title="inconsistency">inconsistencies</a>, and may make all,
@@ -451,7 +460,7 @@
<p>An <dfn>RDF document</dfn> is a document that encodes an
<a>RDF graph</a> or <a>RDF dataset</a> in a <dfn>concrete RDF syntax</dfn>,
such as Turtle [[TURTLE-CR]], RDFa [[RDFA-PRIMER]], JSON-LD [[JSON-LD]],
- RDF/XML [[RDF-SYNTAX-GRAMMAR]], or N-Triples [[N-TRIPLES]].
+ RDF/XML [[RDF-SYNTAX-GRAMMAR]], or N-Triples [[N-TRIPLES]].
RDF documents enable the exchange of RDF graphs and RDF datasets
between systems.</p>
@@ -506,7 +515,7 @@
<p>An RDF triple is conventionally written in the order subject,
predicate, object.</p>
-
+
<p>The set of <dfn title="node">nodes</dfn> of an <a>RDF graph</a>
is the set of subjects and objects of triples in the graph.
It is possible for a predicate IRI to also occur as a node in
@@ -624,17 +633,17 @@
The language tag MUST be well-formed according to
<a href="http://tools.ietf.org/html/bcp47#section-2.2.9">section 2.2.9</a>
of [[!BCP47]]. Lexical representations of language tags MAY be converted to
- lower case. The value space of language tags is always in lower case.</li>
- <li>A badly formed language tag MUST be treated as a syntax error.</li>
+ lower case. The value space of language tags is always in lower case.</li>
+ <li>A badly formed language tag MUST be treated as a syntax error.</li>
</ul>
- <p class="note" id="note-language-tag-regex">
- Implementors might wish to note that language tags conform to the
- regular expression <code>’@’ [a-zA-Z]{1,8} (’-’
- [a-zA-Z0-9]{1,8})*</code>
- before normalizing to lowercase.</p>
+ <p class="note" id="note-language-tag-regex">
+ Implementors might wish to note that language tags conform to the
+ regular expression <code>’@’ [a-zA-Z]{1,8} (’-’
+ [a-zA-Z0-9]{1,8})*</code>
+ before normalizing to lowercase.</p>
- <p>Multiple literals may have the same lexical form.</p>
+ <p>Multiple literals may have the same lexical form.</p>
<p>Concrete syntaxes MAY support <dfn title="simple literal">simple
literals</dfn>, consisting of only a <a>lexical form</a>
@@ -644,31 +653,31 @@
<a title="literal">literals</a> with the <a>datatype IRI</a>
<code>http://www.w3.org/2001/XMLSchema#string</code>.</p>
- <p><dfn>Literal term equality</dfn>: Two literals are term-equal
- (the same RDF literal) if and only if the two <a title="lexical form">lexical forms</a>, the
- two <a title="datatype IRI">datatype IRIs</a>, and the two <a title="language tag">language tags</a> (if any) compare equal,
- character by character.</p>
-
- <p>Two literals can have the same value without being the same
- <a title="RDF Term">RDF term</a>. For example:
-
- <pre>
- "1"^^xs:integer
- "01"^^xs:integer
- </pre>
-
- <p>denote the same value, but are not the same literal
- <a title="RDF Term">RDF terms</a> and are not term-equals.</p>
-
- <p>The <dfn>literal value</dfn> associated with a <a>literal</a> is:</p>
+ <p><dfn>Literal term equality</dfn>: Two literals are term-equal
+ (the same RDF literal) if and only if the two <a title="lexical form">lexical forms</a>, the
+ two <a title="datatype IRI">datatype IRIs</a>, and the two <a title="language tag">language tags</a> (if any) compare equal,
+ character by character.</p>
+
+ <p>Two literals can have the same value without being the same
+ <a title="RDF Term">RDF term</a>. For example:
+
+ <pre>
+ "1"^^xs:integer
+ "01"^^xs:integer
+ </pre>
+
+ <p>denote the same value, but are not the same literal
+ <a title="RDF Term">RDF terms</a> and are not term-equals.</p>
+
+ <p>The <dfn>literal value</dfn> associated with a <a>literal</a> is:</p>
<ol>
<li><strong>If the literal is a <a>language-tagged string</a>,</strong>
then the literal value is a pair consisting of its <a>lexical form</a>
and its <a>language tag</a>, in that order.</li>
<li><strong>If the literal's <a>datatype IRI</a> is not
- <a title="recognized datatype IRIs">recognized</a> by an
- implementation,</strong> then the literal value
+ <a title="recognized datatype IRIs">recognized</a> by an
+ implementation,</strong> then the literal value
is not defined by this specification.</li>
<li>Let <var>d</var> be the <a>referent</a> of the
datatype IRI in the set of <a>recognized datatype IRIs</a>.
@@ -676,14 +685,14 @@
<a>lexical space</a> of <var>d</var>,</strong> then the literal value
is the result of applying the <a>lexical-to-value mapping</a>
of <var>d</var> to the <a>lexical form</a>.</li>
- <li><strong>Otherwise</strong>, the literal is ill-typed,
- and no literal value can be associated with the literal. Such a case
- produces a semantic inconsistency but is not <em>syntactically</em>
- ill-formed and implementations MUST accept ill-typed literals and produce
- RDF graphs from them. Implementations MAY produce warnings when
- encountering ill-typed literals.</li>
+ <li><strong>Otherwise</strong>, the literal is ill-typed,
+ and no literal value can be associated with the literal. Such a case
+ produces a semantic inconsistency but is not <em>syntactically</em>
+ ill-formed and implementations MUST accept ill-typed literals and produce
+ RDF graphs from them. Implementations MAY produce warnings when
+ encountering ill-typed literals.</li>
</ol>
-
+
</section>
@@ -691,9 +700,9 @@
<h2>Blank Nodes</h2>
<p><dfn title="blank node">Blank nodes</dfn> are disjoint from
- <a title="IRI">IRIs</a> and <a title="literal">literals</a>. Otherwise,
- the set of possible blank nodes is arbitrary. RDF makes no reference to
- any internal structure of blank nodes.</p>
+ <a title="IRI">IRIs</a> and <a title="literal">literals</a>. Otherwise,
+ the set of possible blank nodes is arbitrary. RDF makes no reference to
+ any internal structure of blank nodes.</p>
<p class="note" id="note-bnode-id">
<dfn title="blank node identifier">Blank node identifiers</dfn>
@@ -707,9 +716,9 @@
on the concrete syntax or implementation. The syntactic restrictions
on blank node identifiers, if any, therefore also depend on
the concrete RDF syntax or implementation. Implementations that handle blank node
- identifiers in concrete syntaxes need to be careful not to create the
- same blank node from multiple occurences of the same blank node identifier
- except in situations where this is supported by the syntax.</p>
+ identifiers in concrete syntaxes need to be careful not to create the
+ same blank node from multiple occurences of the same blank node identifier
+ except in situations where this is supported by the syntax.</p>
</section>
@@ -761,8 +770,8 @@
<p id="section-graph-equality">Two
<a title="RDF graph">RDF graphs</a> <var>G</var> and <var>G'</var> are
<dfn title="graph isomorphism">isomorphic</dfn> (that is, they have an identical
- form) if there is a bijection <var>M</var> between the sets of nodes of the two
- graphs, such that:</p>
+ form) if there is a bijection <var>M</var> between the sets of nodes of the two
+ graphs, such that:</p>
<ol>
<li><var>M</var> maps blank nodes to blank nodes.</li>
@@ -779,7 +788,7 @@
<p>See also: <a>IRI equality</a>, <a>literal term equality</a>.</p>
- <p>With this definition, <var>M</var> shows how each blank node
+ <p>With this definition, <var>M</var> shows how each blank node
in <var>G</var> can be replaced with
a new blank node to give <var>G'</var>. Graph isomorphism
is needed to support the RDF Test Cases [[RDF-TESTCASES]] specification.</p>
@@ -828,42 +837,42 @@
</div>
<section id="section-dataset-isomorphism">
- <h3>RDF Dataset Comparison</h3>
-
- <p id="section-dataset-equality">Two <a title="RDF Dataset">RDF datasets</a>
- (the RDF dataset <var>D1</var> with default graph <var>DG1</var> and named
- graph <var>NG1</var> and the RDF dataset <var>D2</var> with default graph
- <var>DG2</var> and named graph <var>NG2</var>)
- are <dfn title="dataset isomorphism">dataset-isomorphic</dfn> if and only if
- there is a bijection <var>M</var> between the nodes, triples and graphs in
- <var>D1</var> and those in <var>D2</var> such that:</p>
+ <h3>RDF Dataset Comparison</h3>
- <ol>
- <li><var>M</var> maps blank nodes to blank nodes;</li>
- <li><var>M</var> is the identity map on literals and URIs;</li>
- <li>For every triple <s p o>, <var>M</var>(<s, p, o>)=
- <<var>M(s)</var>, <var>M(p)</var>, <var>M(o)</var>>;</li>
- <li>For every graph <var>G</var>={t1, ...1n},
- <var>M(G)</var>={<var>M(t1)</var>, ..., <var>M(Tn)</var>};</li>
- <li><var>DG2</var> = <var>M(DG1)</var>; and</li>
- <li><n, G> is in <var>NG1</var> if and only if
- <<var>M(n)</var>, <var>M(G)</var>> is in <var>NG2</var>.
- </ol>
-
+ <p id="section-dataset-equality">Two <a title="RDF Dataset">RDF datasets</a>
+ (the RDF dataset <var>D1</var> with default graph <var>DG1</var> and named
+ graph <var>NG1</var> and the RDF dataset <var>D2</var> with default graph
+ <var>DG2</var> and named graph <var>NG2</var>)
+ are <dfn title="dataset isomorphism">dataset-isomorphic</dfn> if and only if
+ there is a bijection <var>M</var> between the nodes, triples and graphs in
+ <var>D1</var> and those in <var>D2</var> such that:</p>
+
+ <ol>
+ <li><var>M</var> maps blank nodes to blank nodes;</li>
+ <li><var>M</var> is the identity map on literals and URIs;</li>
+ <li>For every triple <s p o>, <var>M</var>(<s, p, o>)=
+ <<var>M(s)</var>, <var>M(p)</var>, <var>M(o)</var>>;</li>
+ <li>For every graph <var>G</var>={t1, ...1n},
+ <var>M(G)</var>={<var>M(t1)</var>, ..., <var>M(Tn)</var>};</li>
+ <li><var>DG2</var> = <var>M(DG1)</var>; and</li>
+ <li><n, G> is in <var>NG1</var> if and only if
+ <<var>M(n)</var>, <var>M(G)</var>> is in <var>NG2</var>.
+ </ol>
+
</section>
<section id="section-dataset-conneg" class="informative">
- <h3>Content Negotiation of RDF Datasets</h3>
-
- <p>Primary resources may have multiple representations that are
- made available via
- <a href="http://www.w3.org/TR/webarch/#frag-coneg">content negotiation</a>
- [[WEBARCH]]. A representation may be returned in an RDF serialization
- format that supports the expression of both <a title="RDF Dataset">RDF datasets</a> and
- <a title="RDF graph">RDF graphs</a>. If an <a title="RDF Dataset">RDF dataset</a>
- is returned and the consumer is expecting an <a title="RDF graph">RDF graph</a>,
- the consumer is expected to use the <a title="RDF Dataset">RDF dataset's</a> default graph.</p>
-
+ <h3>Content Negotiation of RDF Datasets</h3>
+
+ <p>Primary resources may have multiple representations that are
+ made available via
+ <a href="http://www.w3.org/TR/webarch/#frag-coneg">content negotiation</a>
+ [[WEBARCH]]. A representation may be returned in an RDF serialization
+ format that supports the expression of both <a title="RDF Dataset">RDF datasets</a> and
+ <a title="RDF graph">RDF graphs</a>. If an <a title="RDF Dataset">RDF dataset</a>
+ is returned and the consumer is expecting an <a title="RDF graph">RDF graph</a>,
+ the consumer is expected to use the <a title="RDF Dataset">RDF dataset's</a> default graph.</p>
+
</section>
</section>
@@ -929,7 +938,7 @@
datatype are:</p>
<table class="simple">
- <caption>This table lists the literals of type xsd:boolean.</caption>
+ <caption>This table lists the literals of type xsd:boolean.</caption>
<tr>
<th>Literal</th>
<th>Value</th>
@@ -965,12 +974,12 @@
listed in the following table are the
<dfn>RDF-compatible XSD types</dfn>. Their use is RECOMMENDED.</p>
- <p>Readers might note that the xsd:hexBinary and xsd:base64Binary
- datatypes are the only safe datatypes for transferring binary
- information.</p>
-
+ <p>Readers might note that the xsd:hexBinary and xsd:base64Binary
+ datatypes are the only safe datatypes for transferring binary
+ information.</p>
+
<table class="simple">
- <caption>A list of the RDF-compatible XSD types, with short descriptions"</caption>
+ <caption>A list of the RDF-compatible XSD types, with short descriptions"</caption>
<tr><th></th><th>Datatype</th><th>Value space (informative)</th></tr>
<tr><th rowspan="4">Core types</th><td><a href="http://www.w3.org/TR/xmlschema11-2/#string"><code>xsd:string</code></a></td><td>Character strings (but not all Unicode character strings)</td></tr>
@@ -1033,20 +1042,20 @@
<div class="note">
<ul>
- <li><a href="http://www.w3.org/TR/xmlschema11-2/#QName"><code>xsd:QName</code></a>
+ <li><a href="http://www.w3.org/TR/xmlschema11-2/#QName"><code>xsd:QName</code></a>
and
- <a href="http://www.w3.org/TR/xmlschema11-2/#ENTITY"><code>xsd:ENTITY</code></a>
+ <a href="http://www.w3.org/TR/xmlschema11-2/#ENTITY"><code>xsd:ENTITY</code></a>
require an enclosing XML document context.</li>
- <li><a href="http://www.w3.org/TR/xmlschema11-2/#ID"><code>xsd:ID</code></a>
+ <li><a href="http://www.w3.org/TR/xmlschema11-2/#ID"><code>xsd:ID</code></a>
and
<a href="http://www.w3.org/TR/xmlschema11-2/#IDREF"><code>xsd:IDREF</code></a>
are for cross references within an XML document.</li>
- <li><a href="http://www.w3.org/TR/xmlschema11-2/#NOTATION"><code>xsd:NOTATION</code></a>
+ <li><a href="http://www.w3.org/TR/xmlschema11-2/#NOTATION"><code>xsd:NOTATION</code></a>
is not intended for direct use.</li>
- <li><a href="http://www.w3.org/TR/xmlschema11-2/#IDREFS"><code>xsd:IDREFS</code></a>,
- <a href="http://www.w3.org/TR/xmlschema11-2/#ENTITIES"><code>xsd:ENTITIES</code></a>
+ <li><a href="http://www.w3.org/TR/xmlschema11-2/#IDREFS"><code>xsd:IDREFS</code></a>,
+ <a href="http://www.w3.org/TR/xmlschema11-2/#ENTITIES"><code>xsd:ENTITIES</code></a>
and
- <a href="http://www.w3.org/TR/xmlschema11-2/#NMTOKENS"><code>xsd:NMTOKENS</code></a>
+ <a href="http://www.w3.org/TR/xmlschema11-2/#NMTOKENS"><code>xsd:NMTOKENS</code></a>
are sequence-valued datatypes which do not fit the RDF <a>datatype</a>
model.</li>
</ul>
@@ -1083,7 +1092,7 @@
<dt>The lexical-to-value mapping</dt>
<dd>
- <p>Each member of the lexical space is associated with the result
+ <p>Each member of the lexical space is associated with the result
of applying the following algorithm:</p>
<ul>
<li>Let <code>domnodes</code> be the list of
@@ -1105,7 +1114,7 @@
XML namespaces (<code>xmlns</code>) desired in the HTML content
must be included explicitly in the HTML literal. Relative URLs
in attributes such as <code>href</code> do not have a well-defined
- base URL and are best avoided.
+ base URL and are best avoided.
RDF applications may use additional equivalence relations,
such as that which relates an <code>xsd:string</code> with an
<code>rdf:HTML</code> literal corresponding to a single text node
@@ -1119,7 +1128,7 @@
Such content is indicated in an <a>RDF graph</a> using a <a>literal</a>
whose <a>datatype</a> is a special built-in datatype
<code><dfn>rdf:XMLLiteral</dfn></code>, which is defined as follows:</p>
-
+
<dl>
<dt id="XMLLiteral-uri">An IRI denoting this <a>datatype</a></dt>
@@ -1128,8 +1137,8 @@
<dt id="XMLLiteral-lexical-space">The <a>lexical space</a></dt>
- <dd>is the set of all strings which are well-balanced, self-contained
- <a href="http://www.w3.org/TR/2000/REC-xml-20001006#NT-content">XML content</a>
+ <dd>is the set of all strings which are well-balanced, self-contained
+ <a href="http://www.w3.org/TR/2000/REC-xml-20001006#NT-content">XML content</a>
[[!XML10]]; and for which embedding between an arbitrary
XML start tag and an end tag yields a document conforming to
<a href="http://www.w3.org/TR/1999/REC-xml-names-19990114/">XML Namespaces</a>
@@ -1149,7 +1158,7 @@
<dt id="XMLLiteral-mapping">The <a>lexical-to-value mapping</a></dt>
<dd>
- <p>Each member of the lexical space is associated with the result
+ <p>Each member of the lexical space is associated with the result
of applying the following algorithm:</p>
<ul>
<li>Let <code>domfrag</code> be a DOM
@@ -1164,7 +1173,7 @@
[[!XMLSCHEMA11-2]] for each member of the value space.
The <code>rdf:XMLLiteral</code> canonical mapping is the
<a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/#def-exclusive-XML-canonicalization-method">exclusive
- XML canonicalization method</a> (<em>with comments, with empty
+ XML canonicalization method</a> (<em>with comments, with empty
<a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/#def-InclusiveNamespaces-PrefixList">
InclusiveNamespaces PrefixList</a></em>) [[!XML-EXC-C14N]].
@@ -1184,46 +1193,46 @@
<h3>Datatype IRIs</h3>
<p>Datatypes are identified by <a title="IRI">IRIs</a>. If
- <var>D</var> is a set of IRIs which are used to refer to
- datatypes, then the elements of <var>D</var> are called <dfn>recognized
- datatype IRIs</dfn>. Recognized IRIs have fixed
- <a href="#referents">referents</a>, which MUST satisfy these
- conditions:
+ <var>D</var> is a set of IRIs which are used to refer to
+ datatypes, then the elements of <var>D</var> are called <dfn>recognized
+ datatype IRIs</dfn>. Recognized IRIs have fixed
+ <a href="#referents">referents</a>, which MUST satisfy these
+ conditions:
- <ol>
- <li>If the IRI
- <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code>
- is recognized then it refers to the datatype
- <code>rdf:XMLLiteral</code>;</li>
- <li>If the IRI
- <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#HTML</code>
- is recognized then it refers to the datatype <code>rdf:HTML</code>;</li>
- <li>If any IRI of the form
- <code>http://www.w3.org/2001/XMLSchema#xxx</code>
- is recognized then it refers to the RDF-compatible XSD type
- named <code>xsd:xxx</code>, for every XSD type listed in
- <a href="#xsd-datatypes">section 5.1</a>.</li>
- </ol>
+ <ol>
+ <li>If the IRI
+ <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code>
+ is recognized then it refers to the datatype
+ <code>rdf:XMLLiteral</code>;</li>
+ <li>If the IRI
+ <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#HTML</code>
+ is recognized then it refers to the datatype <code>rdf:HTML</code>;</li>
+ <li>If any IRI of the form
+ <code>http://www.w3.org/2001/XMLSchema#xxx</code>
+ is recognized then it refers to the RDF-compatible XSD type
+ named <code>xsd:xxx</code>, for every XSD type listed in
+ <a href="#xsd-datatypes">section 5.1</a>.</li>
+ </ol>
- <p>Semantic extensions of RDF MAY recognize other datatype IRIs
- and require them to refer to a fixed datatype.</p>
+ <p>Semantic extensions of RDF MAY recognize other datatype IRIs
+ and require them to refer to a fixed datatype.</p>
- <p>RDF processors are not required to recognize datatype IRIs.
- Any literal typed with an unrecognized IRI is treated just like
- an unknown IRI, i.e. as referring to an unknown thing. Applications
- MAY give a warning message if they are unable to determine the
- referent of an IRI used in a typed literal, but they SHOULD NOT
- reject such RDF as either a syntactic or semantic error.<p>
+ <p>RDF processors are not required to recognize datatype IRIs.
+ Any literal typed with an unrecognized IRI is treated just like
+ an unknown IRI, i.e. as referring to an unknown thing. Applications
+ MAY give a warning message if they are unable to determine the
+ referent of an IRI used in a typed literal, but they SHOULD NOT
+ reject such RDF as either a syntactic or semantic error.<p>
<p>Other specifications
MAY impose additional constraints on <a>datatype IRIs</a>,
for example, require support for certain datatypes.</p>
<p class="note" id="note-custom-datatypes">The Web Ontology Language
- [[OWL2-OVERVIEW]] offers facilities for formally defining
+ [[OWL2-OVERVIEW]] offers facilities for formally defining
<a href="http://www.w3.org/TR/owl2-syntax/#Datatype_Definitions">custom
- datatypes</a> that can be used with RDF. Furthermore, a practice for
- identifying
+ datatypes</a> that can be used with RDF. Furthermore, a practice for
+ identifying
<a href="http://www.w3.org/TR/swbp-xsch-datatypes/#sec-userDefined">
user-defined simple XML Schema datatypes</a>
is suggested in [[SWBP-XSCH-DATATYPES]]. RDF implementations
@@ -1291,32 +1300,32 @@
<section id="section-generalized-rdf" class="informative">
<h2>Generalized RDF Triples, Graphs, and Datasets</h2>
- <p>It is sometimes convenient to loosen the requirements
+ <p>It is sometimes convenient to loosen the requirements
on <a>RDF triple</a>s. For example, the completeness
of the RDFS entailment rules is easier to show with a
generalization of RDF triples.</p>
-
- <p>A <dfn title="generalized RDF triple">generalized RDF
- triple</dfn> is a triple having a subject, a predicate,
- and object, where each can be an <a title="iri">IRI</a>, a
- <a title="blank node">blank node</a> or a
- <a>literal</a>. A
- <dfn title="generalized RDF graph">generalized RDF graph</dfn>
- is a set of generalized RDF triples. A
- <dfn title="generalized RDF dataset">generalized RDF dataset</dfn>
- comprises a distinguished generalized RDF graph, and zero
- or more pairs each associating an IRI, a blank node or a literal
- to a generalized RDF graph.</p>
-
- <p>Generalized RDF triples, graphs, and datasets differ
- from normative RDF <a title="RDF triple">triples</a>,
- <a title="RDF graph">graphs</a>, and
- <a title="RDF dataset">datasets</a> only
- by allowing <a title="IRI">IRIs</a>,
- <a title="blank node">blank nodes</a> and
- <a>literals</a> to appear
- in any position, i.e., as subject, predicate, object or graph names.</p>
+ <p>A <dfn title="generalized RDF triple">generalized RDF
+ triple</dfn> is a triple having a subject, a predicate,
+ and object, where each can be an <a title="iri">IRI</a>, a
+ <a title="blank node">blank node</a> or a
+ <a>literal</a>. A
+ <dfn title="generalized RDF graph">generalized RDF graph</dfn>
+ is a set of generalized RDF triples. A
+ <dfn title="generalized RDF dataset">generalized RDF dataset</dfn>
+ comprises a distinguished generalized RDF graph, and zero
+ or more pairs each associating an IRI, a blank node or a literal
+ to a generalized RDF graph.</p>
+
+
+ <p>Generalized RDF triples, graphs, and datasets differ
+ from normative RDF <a title="RDF triple">triples</a>,
+ <a title="RDF graph">graphs</a>, and
+ <a title="RDF dataset">datasets</a> only
+ by allowing <a title="IRI">IRIs</a>,
+ <a title="blank node">blank nodes</a> and
+ <a>literals</a> to appear
+ in any position, i.e., as subject, predicate, object or graph names.</p>
<p class="note" id="note-generalized-rdf"> Any users of
generalized RDF triples, graphs or datasets need to be
@@ -1332,7 +1341,7 @@
<h2>Acknowledgments</h2>
<p>The RDF 1.1 editors acknowledge valuable contributions from
- Thomas Baker, Dan Brickley, Gavin Carothers, Jeremy Carroll,
+ Thomas Baker, Dan Brickley, Gavin Carothers, Jeremy Carroll,
Pierre-Antoine Champin, Dan Connolly, Tim Berners-Lee,
John Cowan, Martin J. Dürst, Alex Hall, Steve Harris, Pat Hayes,
Ivan Herman, Peter F. Patel-Schneider, Addison Phillips,
@@ -1341,9 +1350,13 @@
<p>The RDF 2004 editors acknowledge valuable contributions from
Frank Manola, Pat Hayes, Dan Brickley, Jos de Roo, Sergey Melnik,
- Dave Beckett, Patrick Stickler, Peter F. Patel-Schneider, Jerome Euzenat,
+ Dave Beckett, Patrick Stickler, Peter F. Patel-Schneider, Jerome Euzenat,
Massimo Marchiori, Tim Berners-Lee, Dave Reynolds and Dan Connolly.</p>
+ <p>Editors of the 2004 version of this specification were Graham Klyne
+ and Jeremy J. Carroll. Brian McBride served as series editor for
+ the 2004 RDF specifications.</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 two earlier specifications,
@@ -1367,7 +1380,7 @@
as to what else has changed and why.</p>
-->
- <p>This section discusses changes between the
+ <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>
@@ -1403,46 +1416,59 @@
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>
-
+ Currently a literal with type xsd:string containing the #x0 character
+ is an ill-typed literal.</p>
+
</section>
<section class="appendix informative" id="change-log">
<h2>Change Log</h2>
+<section class="appendix" id="changes-wd5">
+ <h3>Changes from 23 July 2013 LC to this version</h3>
+
+ <p>This section lists changes from the
+ <a href="http://www.w3.org/TR/2013/WD-rdf11-concepts-20130723/">23 July 2013 Last Call Working Draft (LC)</a> to this Candidate Recommendation of
+ <em>RDF 1.1 Concepts and Abstract Syntax</em>.</p>
+
+ <ul>
+ <li>2013-10-16: Fixed ReSpec issue regarding previous editor attributions
+ and added previous editors to acknowledgements to address <a
+ href="http://www.w3.org/2011/rdf-wg/track/issues/150">ISSUE-150</a>.</li>
+ <li>2013-10-16: Update to Section 7 in accordance with <a href="http://www.w3.org/2011/rdf-wg/track/issues/147">ISSUE-147</a> (<a href="https://www.w3.org/2011/rdf-wg/track/actions/309">ACTION-309</a>, <a href="https://www.w3.org/2013/meeting/rdf-wg/2013-10-09#line0258">assignment of action</a>)</li>
+ <li>2013-09-10: Update to Section 7 in accordance with <a href="http://www.w3.org/2011/rdf-wg/track/issues/139">ISSUE-139</a> (<a href="https://www.w3.org/2013/meeting/rdf-wg/2013-09-04#resolution_3">resolution</a>)</li>
+ <li>2013-08-26: Update to Section 4.1 to satisfy <a
+ href="https://www.w3.org/2011/rdf-wg/track/actions/283">ACTION-283</a> and <a href="http://www.w3.org/2011/rdf-wg/track/issues/140">ISSUE-140</a> (<a href="https://www.w3.org/2013/meeting/rdf-wg/2013-08-21#resolution_7">resolution</a>)</li>
+ </ul>
+</section>
+
<section class="appendix" id="changes-wd4">
<h3>Changes from 15 January 2013 WD to this version</h3>
<p>This section lists changes from the
- <a href="http://www.w3.org/TR/2013/WD-rdf11-concepts-20130115/">15 January 2013 Working Draft (WD)</a> to this Editor's Draft of
+ <a href="http://www.w3.org/TR/2013/WD-rdf11-concepts-20130115/">15 January 2013 Working Draft (LC)</a> to the Last Call Working Draft of
<em>RDF 1.1 Concepts and Abstract Syntax</em>.</p>
<ul>
- <li>2013-10-16: Update to Section 7 in accordance with <a href="http://www.w3.org/2011/rdf-wg/track/issues/147">ISSUE-147</a> (<a href="https://www.w3.org/2011/rdf-wg/track/actions/309">ACTION-309</a>, <a href="https://www.w3.org/2013/meeting/rdf-wg/2013-10-09#line0258">assignment of action</a>)</li>
- <li>2013-09-10: Update to Section 7 in accordance with <a href="http://www.w3.org/2011/rdf-wg/track/issues/139">ISSUE-139</a> (<a href="https://www.w3.org/2013/meeting/rdf-wg/2013-09-04#resolution_3">resolution</a>)</li>
- <li>2013-08-26: Update to Section 4.1 to satisfy <a
- href="https://www.w3.org/2011/rdf-wg/track/actions/283">ACTION-283</a> and <a href="http://www.w3.org/2011/rdf-wg/track/issues/140">ISSUE-140</a> (<a
- href="https://www.w3.org/2013/meeting/rdf-wg/2013-08-21#resolution_7">resolution</a>)</li>
- <li>2013-07-15: Editorial change to the first paragraph of Section 1.7 in an attempt to clarify the relationship to RDF-MT following the <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jul/0003.html">review by Markus Lanthaler</a> and <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jul/0164.html">suggested changes by Peter Patel-Schneider</a></li>
- <li>2013-07-03: Editorial changes in response to <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jul/0003.html">a review by Markus Lanthaler</a> and a <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jul/0026.html">related request</a></li>
- <li>2013-06-27: Added informative section on generalized RDF triples, graphs, and
- datasets.</li>
- <li>2013-06-27: Added caution on the use of graph names as blank nodes.</li>
- <li>2013-06-19: Noted that RDF Dataset graph names may be blank nodes (<a
- href="https://www.w3.org/2011/rdf-wg/track/actions/274">ACTION-274</a>, <a
- href="https://www.w3.org/2013/meeting/rdf-wg/2013-06-12#resolution_1">resolution</a>)</li>
- <li>2013-06-19: Changes in response to <a
- href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013May/0221.html">a
- review by Peter Patel-Schneider</a></li>
- <li>2013-06-05: Minor change to note to specify the value space and lexical space of language tags (<a href="http://www.w3.org/2011/rdf-wg/track/actions/265">ACTION-265</a>, <a href="https://www.w3.org/2013/meeting/rdf-wg/2013-05-22#resolution_3">resolution</a>)</li>
- <li>2013-05-08: Minor change to note that a badly formed language tag is a syntax error (<a href="http://www.w3.org/2011/rdf-wg/track/actions/262">ACTION-262</a>)</li>
- <li>2013-05-08: Migrated language related to datatype maps to recognized datatype IRIs (<a href="http://www.w3.org/2011/rdf-wg/track/issues/118">ISSUE-118</a>)</li>
- <li>2013-05-08: Editorial changes in response to <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013May/0058.html">a discussion of literal equality</a></li>
- <li>2013-05-08: Editorial changes in response to <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013May/0075.html">a review by Sandro Hawke</a></li>
+ <li>2013-07-15: Editorial change to the first paragraph of Section 1.7 in an attempt to clarify the relationship to RDF-MT following the <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jul/0003.html">review by Markus Lanthaler</a> and <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jul/0164.html">suggested changes by Peter Patel-Schneider</a></li>
+ <li>2013-07-03: Editorial changes in response to <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jul/0003.html">a review by Markus Lanthaler</a> and a <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jul/0026.html">related request</a></li>
+ <li>2013-06-27: Added informative section on generalized RDF triples, graphs, and
+ datasets.</li>
+ <li>2013-06-27: Added caution on the use of graph names as blank nodes.</li>
+ <li>2013-06-19: Noted that RDF Dataset graph names may be blank nodes (<a
+ href="https://www.w3.org/2011/rdf-wg/track/actions/274">ACTION-274</a>, <a
+ href="https://www.w3.org/2013/meeting/rdf-wg/2013-06-12#resolution_1">resolution</a>)</li>
+ <li>2013-06-19: Changes in response to <a
+ href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013May/0221.html">a
+ review by Peter Patel-Schneider</a></li>
+ <li>2013-06-05: Minor change to note to specify the value space and lexical space of language tags (<a href="http://www.w3.org/2011/rdf-wg/track/actions/265">ACTION-265</a>, <a href="https://www.w3.org/2013/meeting/rdf-wg/2013-05-22#resolution_3">resolution</a>)</li>
+ <li>2013-05-08: Minor change to note that a badly formed language tag is a syntax error (<a href="http://www.w3.org/2011/rdf-wg/track/actions/262">ACTION-262</a>)</li>
+ <li>2013-05-08: Migrated language related to datatype maps to recognized datatype IRIs (<a href="http://www.w3.org/2011/rdf-wg/track/issues/118">ISSUE-118</a>)</li>
+ <li>2013-05-08: Editorial changes in response to <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013May/0058.html">a discussion of literal equality</a></li>
+ <li>2013-05-08: Editorial changes in response to <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013May/0075.html">a review by Sandro Hawke</a></li>
<li>2013-05-07: Revised the definition of blank nodes (<a href="http://www.w3.org/2011/rdf-wg/track/issues/107">ISSUE-107</a>)</li>
- <li>2013-05-07: Defined the consequence of a literal being ill-typed (<a href="http://www.w3.org/2011/rdf-wg/track/issues/109">ISSUE-109</a>)</li>
+ <li>2013-05-07: Defined the consequence of a literal being ill-typed (<a href="http://www.w3.org/2011/rdf-wg/track/issues/109">ISSUE-109</a>)</li>
<li>2013-05-07: Clarified the existence of null control characters in xsd:strings (<a href="http://www.w3.org/2011/rdf-wg/track/issues/126">ISSUE-126</a>)</li>
<li>2013-05-07: Added a definition of RDF Dataset isomorphism (<a href="http://www.w3.org/2011/rdf-wg/track/issues/111">ISSUE-111</a>)</li>
<li>2013-05-07: Addressed content negotiation as it relates to graphs and datasets (<a href="http://www.w3.org/2011/rdf-wg/track/issues/105">ISSUE-105</a>)</li>
@@ -1453,7 +1479,7 @@
<h3>Changes from 05 June 2012 WD to this version</h3>
<p>This section lists changes from the
- <a href="http://www.w3.org/TR/2012/WD-rdf11-concepts-20120605/">05 June 2012 Working Draft (WD)</a> to this Editor's Draft of
+ <a href="http://www.w3.org/TR/2012/WD-rdf11-concepts-20120605/">05 June 2012 Working Draft (WD)</a> to this Editor's Draft of
<em>RDF 1.1 Concepts and Abstract Syntax</em>.</p>
<ul>