--- a/rdf-concepts/index.html Wed Nov 06 17:21:18 2013 +0100
+++ b/rdf-concepts/index.html Wed Nov 06 17:46:00 2013 +0100
@@ -164,8 +164,7 @@
<li>serialization syntaxes for storing and exchanging RDF
(e.g., <a href="http://www.w3.org/TR/turtle/">Turtle</a> [[TURTLE]]
- and <a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF/XML</a>
- [[RDF-SYNTAX-GRAMMAR]]),</li>
+ and <a href="http://www.w3.org/TR/json-ld/">JSON-LD</a> [[JSON-LD]]),</li>
<li>the <a href="http://www.w3.org/TR/rdf-sparql-query/">SPARQL
Query Language</a> [[RDF-SPARQL-QUERY]],</li>
@@ -204,7 +203,7 @@
<dfn title="resource">resources</dfn>. Anything can be a resource,
including physical things, documents, abstract concepts, numbers
and strings; the term is synonymous with "entity" as it is used in
- the RDF Semantics specification [[RDF11-MT]].
+ the RDF Semantics specification [[RDF11-MT]].
The resource denoted by an IRI is called its <a>referent</a>, and the
resource denoted by a literal is called its
<a title="literal value">literal value</a>. Literals have
@@ -464,10 +463,9 @@
<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]], RDFa [[RDFA-PRIMER]], JSON-LD [[JSON-LD]],
- RDF/XML [[RDF-SYNTAX-GRAMMAR]], or N-Triples [[N-TRIPLES]].
- RDF documents enable the exchange of RDF graphs and RDF datasets
- between systems.</p>
+ such as Turtle [[TURTLE]], RDFa [[RDFA-PRIMER]], JSON-LD [[JSON-LD]], or
+ TriG [[TRIG]]. RDF documents enable the exchange of RDF graphs and RDF
+ datasets between systems.</p>
<p>A <a>concrete RDF syntax</a> may offer
many different ways to encode the same <a>RDF graph</a> or
@@ -561,7 +559,7 @@
<p><strong>URIs and IRIs:</strong>
IRIs are a generalization of
<dfn title="URI"><abbr title="Uniform Resource Identifier">URI</abbr>s</dfn>
- [[RFC3986]] that permits a wider range of Unicode characters.
+ [[RFC3986]] that permits a wider range of Unicode characters.
Every absolute URI and URL is an IRI, but not every IRI is an URI.
When IRIs are used in operations that are only
defined for URIs, they must first be converted according to
@@ -626,8 +624,8 @@
<li>a <dfn>lexical form</dfn>, being a Unicode [[!UNICODE]] string,
which SHOULD be in Normal Form C [[!NFC]],</li>
<li>a <dfn>datatype IRI</dfn>, being an <a title="IRI">IRI</a> identifying a
- datatype that determines how the lexical form maps to a
- <a>literal value</a>.</li>
+ datatype that determines how the lexical form maps to a
+ <a>literal value</a>.</li>
</ul>
<p>A literal is a <dfn>language-tagged string</dfn> if and only if its
@@ -871,8 +869,7 @@
<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
+ <p>Web 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
@@ -1236,10 +1233,10 @@
</ol>
<p class="note">Semantic extensions of RDF might choose to
- recognize other datatype IRIs
+ recognize other datatype IRIs
and require them to refer to a fixed datatype. See the RDF
- Semantics specification [[RDF11-MT]] for more information on
- semantic extensions.</p>
+ Semantics specification [[RDF11-MT]] for more information on
+ semantic extensions.</p>
<p>RDF processors are not required to recognize datatype IRIs.
Any literal typed with an unrecognized IRI is treated just like
@@ -1267,9 +1264,9 @@
<section id="section-fragID" class="informative">
- <h2>Fragment Identifiers</h2>
+ <h2>Fragment Identifiers</h2>
- <p>RDF uses <a title="IRI">IRIs</a>, which may include
+ <p>RDF uses <a title="IRI">IRIs</a>, which may include
<dfn>fragment identifiers</dfn>, as resource identifiers.
The semantics of fragment identifiers is
<a href="http://tools.ietf.org/html/rfc3986#section-3.5">defined in
@@ -1279,10 +1276,10 @@
of representations that might result from a retrieval action
on the primary resource.</p>
- <p>This section discusses the handling of fragment identifiers
+ <p>This section discusses the handling of fragment identifiers
in representations that encode <a title="RDF graph">RDF graphs</a>.</p>
- <p>In RDF-bearing representations of a primary resource
+ <p>In RDF-bearing representations of a primary resource
<code><foo></code>,
the secondary resource identified by a fragment <code>bar</code>
is the <a>resource</a> <a title="denote">denoted</a> by the
@@ -1291,11 +1288,11 @@
something external to the representation, or even external
to the web.</p>
- <p>In this way, the RDF-bearing representation acts as an intermediary
+ <p>In this way, the RDF-bearing representation acts as an intermediary
between the web-accessible primary resource, and some set of possibly
non-web or abstract entities that the <a>RDF graph</a> may describe.</p>
- <p>In cases where other specifications constrain the semantics of
+ <p>In cases where other specifications constrain the semantics of
fragment identifiers in RDF-bearing representations, the encoded
<a>RDF graph</a> should use fragment identifiers in a way that is consistent
with these constraints. For example, in an HTML+RDFa document [[HTML-RDFA]],
@@ -1304,21 +1301,14 @@
attributes. The <a title="IRI">IRI</a> <code><#chapter1></code> should
then be taken to <a>denote</a> that same section in any RDFa-encoded
<a title="RDF triple">triples</a> within the same document.
- Similarly, if the <code>@xml:id</code> attribute [[XML-ID]] is used
- in an RDF/XML document, then the corresponding IRI
- should be taken to denote an XML element.</p>
-
- <p>Primary resources may have multiple representations that are
- made available via
+ Similarly, fragment identifiers should be used consistently in resources
+ with multiple representations that are made available via
<a href="http://www.w3.org/TR/webarch/#frag-coneg">content negotiation</a>
- [[WEBARCH]]. Fragments in RDF-bearing representations
- should be used in a way that is consistent with the semantics imposed by any
- non-RDF representations. For example, if the fragment
- <code>chapter1</code> identifies a document section in an
- HTML representation of the primary resource, then the <a title="IRI">IRI</a>
- <code><#chapter1></code>
- should be taken to <a>denote</a> that same section in all RDF-bearing
- representations of the same primary resource.</p>
+ [[WEBARCH]]. For example, if the fragment <code>chapter1</code> identifies a
+ document section in an HTML representation of the primary resource, then the
+ <a title="IRI">IRI</a> <code><#chapter1></code> should be taken to
+ <a>denote</a> that same section in all RDF-bearing representations of the
+ same primary resource.</p>
</section>
<section id="section-generalized-rdf" class="informative">
@@ -1377,9 +1367,9 @@
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>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>.
@@ -1396,72 +1386,83 @@
<!--
<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>
+ 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>
+ <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>
<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>
+ “<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>
+ 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>
+ <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>
+ 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>
</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>
+<section class="appendix" id="changes-cr">
+ <h3>Changes from 5 November 2013 CR</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>
+ <a href="http://www.w3.org/TR/2013/CR-rdf11-concepts-20131105/">5 November 2013 Candidate Recommendation (CR)</a>.</p>
+
+ <ul>
+ <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>
+
+<section class="appendix" id="changes-wd5">
+ <h3>Changes from 23 July 2013 LC</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>.</p>
<ul>
<li>2013-10-30: Mark <code>rdf:rdf:HTML</code> and <code>rdf:XMLLiteral</code> as at risk.</li>
- <li>2013010-21: Added Markus Lanthaler as editor. Minor editorial updates (e.g. repair of broken links). Updates to sections 1.2, 1.3, 3.1, 3.2, 3.3, 4.1 and 5.4 to address <a href="http://lists.w3.org/Archives/Public/public-rdf-comments/2013Oct/0057.html">comments from Michael Schneider</a> (<a href="http://www.w3.org/2011/rdf-wg/track/issues/161">ISSUE-161</a>)</li>
- <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>2013010-21: Added Markus Lanthaler as editor. Minor editorial updates (e.g. repair of broken links). Updates to sections 1.2, 1.3, 3.1, 3.2, 3.3, 4.1 and 5.4 to address <a href="http://lists.w3.org/Archives/Public/public-rdf-comments/2013Oct/0057.html">comments from Michael Schneider</a> (<a href="http://www.w3.org/2011/rdf-wg/track/issues/161">ISSUE-161</a>)</li>
+ <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
@@ -1470,11 +1471,10 @@
</section>
<section class="appendix" id="changes-wd4">
- <h3>Changes from 15 January 2013 WD to this version</h3>
+ <h3>Changes from 15 January 2013 WD</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 (LC)</a> to the Last Call Working Draft of
- <em>RDF 1.1 Concepts and Abstract Syntax</em>.</p>
+ <a href="http://www.w3.org/TR/2013/WD-rdf11-concepts-20130115/">15 January 2013 Working Draft (LC)</a>.</p>
<ul>
<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>
@@ -1502,11 +1502,10 @@
</section>
<section class="appendix" id="changes-wd3">
- <h3>Changes from 05 June 2012 WD to this version</h3>
+ <h3>Changes from 05 June 2012 WD</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
- <em>RDF 1.1 Concepts and Abstract Syntax</em>.</p>
+ <a href="http://www.w3.org/TR/2012/WD-rdf11-concepts-20120605/">05 June 2012 Working Draft (WD)</a>.</p>
<ul>
<li>2013-01-14: Editorial changes in response to <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2012Nov/0354.html">reviews from Antoine Zimmermann</a> <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2012Nov/0360.html">and Peter Patel-Schneider</a></li>
@@ -1532,12 +1531,10 @@
<section class="appendix" id="changes-wd2">
- <h3>Changes from FPWD to 05 June 2012 WD</h3>
+ <h3>Changes from FPWD</h3>
<p>This section lists changes from the
- <a href="http://www.w3.org/TR/2011/WD-rdf11-concepts-20110830/">First Public Working Draft (FPWD)</a>
- to the <a href="http://www.w3.org/TR/2012/WD-rdf11-concepts-20120605/">05 June 2012 Working Draft (WD)</a> of
- <em>RDF 1.1 Concepts and Abstract Syntax</em>.</p>
+ <a href="http://www.w3.org/TR/2011/WD-rdf11-concepts-20110830/">First Public Working Draft (FPWD)</a>.</p>
<ul>
<li>2012-05-31: Update <a href="#section-Acknowledgments">Acknowledgements</a> for RDF 1.1; added RDFa 1.1 markup</li>
@@ -1567,13 +1564,10 @@
</section>
<section class="appendix" id="changes-fpwd">
- <h3>Changes from RDF 2004 to FPWD</h3>
+ <h3>Changes from RDF 2004</h3>
<p>This section lists changes from the
- <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/">2004 Recommendation of
- <em>RDF Concepts and Abstract Syntax</em></a> to the
- <a href="http://www.w3.org/TR/2011/WD-rdf11-concepts-20110830/">First Public Working Draft (FPWD) of
- <em>RDF 1.1 Concepts and Abstract Syntax</em></a>.</p>
+ <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/">2004 Recommendation of <em>RDF Concepts and Abstract Syntax</em></a>.</p>
<ul>
<li>2011-08-13: Updated Turtle reference to Turtle FPWD</li>