--- a/rdf-concepts/index.html Wed Oct 30 18:32:37 2013 +0100
+++ b/rdf-concepts/index.html Wed Oct 30 18:55:12 2013 +0100
@@ -1,13 +1,8 @@
<!DOCTYPE html>
<html lang="en">
<head>
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+ <meta 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; }
- </style>
<script src="../local-biblio.js" class="remove"></script>
<script src="https://www.w3.org/Tools/respec/respec-w3c-common" class="remove"></script>
<script class='remove'>
@@ -108,42 +103,43 @@
// from the dcterms, foaf, and bibo. The parameter defaults to false.
doRDFa: "1.1",
};
-
</script>
+ <style type="text/css">
+ figure { text-align: center; }
+ table td, table th { border: 1px solid #ddd; padding: 0.2em 0.5em; }
+ </style>
</head>
<body>
<div class="head">
-
-<section id="abstract">
+ <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
- (a data model) which serves to link all RDF-based languages and
- specifications. The abstract syntax has two key data structures:
- RDF graphs are sets of subject-predicate-object triples,
- where the elements may be IRIs, blank nodes, or datatyped literals. They
- are used to express descriptions of resources. RDF datasets are used
- to organize collections of RDF graphs, and comprise a default graph
- and zero or more named graphs.
- This document also introduces key concepts and terminology, and discusses
- datatyping and the handling of fragment identifiers in IRIs within
- RDF graphs.</p>
-</section>
+ <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
+ (a data model) which serves to link all RDF-based languages and
+ specifications. The abstract syntax has two key data structures:
+ RDF graphs are sets of subject-predicate-object triples,
+ where the elements may be IRIs, blank nodes, or datatyped literals. They
+ are used to express descriptions of resources. RDF datasets are used
+ to organize collections of RDF graphs, and comprise a default graph
+ and zero or more named graphs.
+ This document also introduces key concepts and terminology, and discusses
+ datatyping and the handling of fragment identifiers in IRIs within
+ RDF graphs.</p>
+ </section>
-<section id="sotd">
-
- <p>The following features are at risk and may be removed:</p>
+ <section id="sotd">
- <ul>
- <li><a href="#at-risk-html">The <code>rdf:HTML</code> datatype may be made non-normative</li>
- <li><a href="#at-risk-xmlliteral">The <code>rdf:XMLLiteral</code> datatype may be made non-normative</li>
- </ul>
+ <p>The following features are at risk and may be changed from normative to non-normative:</p>
-</section>
+ <ul>
+ <li><a href="#at-risk-html">The <code>rdf:HTML</code> datatype may be made non-normative</li>
+ <li><a href="#at-risk-xmlliteral">The <code>rdf:XMLLiteral</code> datatype may be made non-normative</li>
+ </ul>
+ </section>
</div>
<section id="section-Introduction" class="informative">
@@ -182,9 +178,10 @@
directed-arc diagram, in which each triple is represented as a
node-arc-node link.</p>
- <div class="figure">
+ <figure>
<a href="rdf-graph.svg"><img src="rdf-graph.svg" alt="An RDF graph with two nodes (Subject and Object) and a triple connecting them (Predicate)" /></a>
- </div>
+ <figcaption>An RDF graph with two nodes (Subject and Object) and a triple connecting them (Predicate)</figcaption>
+ </figure>
<p>There can be three kinds of <a title="node">nodes</a> in an
<a>RDF graph</a>: <a title="IRI">IRIs</a>, <a title="literal">literals</a>,
@@ -195,7 +192,7 @@
<section id="resources-and-statements">
<h3>Resources and Statements</h3>
- <p>Any <a>IRI</a> or <a>literal</a> <dfn title="denote">denotes</dfn>
+ <p>Any <a title="IRI">IRI</a> or <a>literal</a> <dfn title="denote">denotes</dfn>
something in the world (the "universe of discourse").
These things are called
<dfn title="resource">resources</dfn>. Anything can be a resource,
@@ -215,7 +212,7 @@
<a title="resource">resources</a> <a title="denote">denoted</a> by
the <a>subject</a> and <a>object</a></em>. This statement corresponding
to an RDF triple is known as an <dfn>RDF statement</dfn>.
- The predicate itself is an <a>IRI</a> and denotes a <dfn>property</dfn>,
+ The predicate itself is an <a title="IRI">IRI</a> and denotes a <dfn>property</dfn>,
that is, a <a>resource</a> that can be thought of as a binary relation.
(Relations that involve more than two entities can only be
<a href="http://www.w3.org/TR/swbp-n-aryRelations/">indirectly
@@ -233,7 +230,7 @@
<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>
+ <p>The <a>resource</a> <a title="denote">denoted</a> by an <a title="IRI">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
@@ -241,7 +238,7 @@
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
+ <p>Guidelines for determining the <a>referent</a> of an <a title="IRI">IRI</a> are
provided in other documents, like
<em><a href="http://www.w3.org/TR/webarch/">Architecture of the
World Wide Web, Volume One</a></em> [[WEBARCH]] and
@@ -256,7 +253,7 @@
<li>By social convention, the
<a href="http://www.w3.org/TR/webarch/#uri-ownership">IRI owner</a>
[[WEBARCH]] gets to say what the intended (or usual)
- referent of an <a>IRI</a> is. Applications and users need not
+ referent of an <a title="IRI">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>
@@ -361,7 +358,7 @@
can be reflected in the following ways:</p>
<ul>
- <li>An <a>IRI</a>, once minted, should never
+ <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>
@@ -393,7 +390,7 @@
<p>An <a>RDF dataset</a> is a collection of
<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
+ an associated <a title="IRI">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>.
The remaining graph does not have an associated IRI, and is called
@@ -507,11 +504,11 @@
<ul>
<li>the <dfn>subject</dfn>, which is an
- <a>IRI</a> or a <a>blank node</a></li>
+ <a title="IRI">IRI</a> or a <a>blank node</a></li>
- <li>the <dfn>predicate</dfn>, which is an <a>IRI</a></li>
+ <li>the <dfn>predicate</dfn>, which is an <a title="IRI">IRI</a></li>
- <li>the <dfn>object</dfn>, which is an <a>IRI</a>,
+ <li>the <dfn>object</dfn>, which is an <a title="IRI">IRI</a>,
a <a>literal</a> or a <a>blank node</a></li>
</ul>
@@ -622,7 +619,7 @@
<ul>
<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>IRI</a> identifying a
+ <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>
</ul>
@@ -811,7 +808,7 @@
<li>Exactly one <dfn>default graph</dfn>, being an <a>RDF graph</a>.
The default graph does not have a name and MAY be empty.</li>
<li>Zero or more <dfn title="named graph">named graphs</dfn>.
- Each named graph is a pair consisting of an <a>IRI</a> or a blank node
+ Each named graph is a pair consisting of an <a title="IRI">IRI</a> or a blank node
(the <dfn>graph name</dfn>), and an <a>RDF graph</a>.
Graph names are unique within an RDF dataset.</li>
</ul>
@@ -1246,7 +1243,7 @@
reject such RDF as either a syntactic or semantic error.<p>
<p>Other specifications
- MAY impose additional constraints on <a>datatype IRIs</a>,
+ MAY impose additional constraints on <a title="datatype IRI">datatype IRIs</a>,
for example, require support for certain datatypes.</p>
<p class="note" id="note-custom-datatypes">The Web Ontology Language
@@ -1283,7 +1280,7 @@
<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
- full <a>IRI</a> <code><foo#bar></code> in the <a>RDF graph</a>.
+ full <a title="IRI">IRI</a> <code><foo#bar></code> in the <a>RDF graph</a>.
Since IRIs in RDF graphs can denote anything, this can be
something external to the representation, or even external
to the web.</p>
@@ -1298,7 +1295,7 @@
with these constraints. For example, in an HTML+RDFa document [[HTML-RDFA]],
the fragment <code>chapter1</code> may identify a document section
via the semantics of HTML's <code>@name</code> or <code>@id</code>
- attributes. The <a>IRI</a> <code><#chapter1></code> should
+ 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
@@ -1312,7 +1309,7 @@
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>IRI</a>
+ 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>
@@ -1454,6 +1451,7 @@
<em>RDF 1.1 Concepts and Abstract Syntax</em>.</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