--- a/ReSpec.js/bibref/biblio.js Mon May 28 15:39:12 2012 +0100
+++ b/ReSpec.js/bibref/biblio.js Mon May 28 17:28:54 2012 +0100
@@ -438,7 +438,7 @@
"RDF-UML" : "Walter W. Chang. <a href=\"http://www.w3.org/TR/1998/NOTE-rdf-uml-19980804\"><cite>A Discussion of the Relationship Between RDF-Schema and UML.</cite></a> 4 August 1998. W3C Note. URL: <a href=\"http://www.w3.org/TR/1998/NOTE-rdf-uml-19980804\">http://www.w3.org/TR/1998/NOTE-rdf-uml-19980804</a> ",
"RDFA-CORE" : "Shane McCarron; et al. <a href=\"http://www.w3.org/TR/2012/PR-rdfa-core-20120508/\"><cite>RDFa Core 1.1: Syntax and processing rules for embedding RDF through attributes.</cite></a> 8 May 2012. W3C Proposed Recommendation. URL: <a href=\"http://www.w3.org/TR/2012/PR-rdfa-core-20120508/\">http://www.w3.org/TR/2012/PR-rdfa-core-20120508/</a> ",
"RDFA-LITE" : "Manu Sporny. <a href=\"http://www.w3.org/TR/2012/PR-rdfa-lite-20120508/\"><cite>RDFa Lite 1.1.</cite></a> 8 May 2012. W3C Proposed Recommendation. URL: <a href=\"http://www.w3.org/TR/2012/PR-rdfa-lite-20120508/\">http://www.w3.org/TR/2012/PR-rdfa-lite-20120508/</a> ",
- "RDFA-PRIMER" : "Ben Adida, Ivan Herman, Manu Sporny. <a href=\"http://www.w3.org/TR/2011/WD-rdfa-primer-20111208\"><cite>RDFa Primer.</cite></a> 08 December 2011. W3C Working Draft. URL: <a href=\"http://www.w3.org/TR/2011/WD-rdfa-primer-20111208\">http://www.w3.org/TR/2011/WD-rdfa-primer-20111208</a> ",
+ "RDFA-PRIMER" : "Ben Adida, Ivan Herman, Manu Sporny. <a href=\"http://www.w3.org/TR/2012/WD-rdfa-primer-20120508/\"><cite>RDFa 1.1 Primer.</cite></a> 08 May 2012. W3C Working Draft. URL: <a href=\"http://www.w3.org/TR/2012/WD-rdfa-primer-20120508/">http://www.w3.org/TR/2012/WD-rdfa-primer-20120508/</a> ",
"RDFA-SYNTAX" : "Ben Adida, et al. <a href=\"http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014\"><cite>RDFa in XHTML: Syntax and Processing.</cite></a> 14 October 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014\">http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014</a> ",
"RDFCAL" : "Dan Connolly; Libby Miller. <a href=\"http://www.w3.org/TR/2005/NOTE-rdfcal-20050929\"><cite>RDF Calendar - an application of the Resource Description Framework to iCalendar Data.</cite></a> 29 September 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-rdfcal-20050929\">http://www.w3.org/TR/2005/NOTE-rdfcal-20050929</a> ",
"RDFTM-SURVEY" : "Fabio Vitali; et al. <a href=\"http://www.w3.org/TR/2006/NOTE-rdftm-survey-20060210\"><cite>A Survey of RDF/Topic Maps Interoperability Proposals.</cite></a> 10 February 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-rdftm-survey-20060210\">http://www.w3.org/TR/2006/NOTE-rdftm-survey-20060210</a> ",
--- a/rdf-concepts/index.html Mon May 28 15:39:12 2012 +0100
+++ b/rdf-concepts/index.html Mon May 28 17:28:54 2012 +0100
@@ -184,8 +184,8 @@
<p>Any <a>IRI</a> and <a>literal</a> <dfn title="denote">denotes</dfn>
some thing in the universe of discourse. These things are called
<dfn title="resource">resources</dfn>. Anything can be a resource,
- including physical things, documents, and abstract concepts; the term
- is synonymous with “entity”.
+ including physical things, documents, abstract concepts, numbers
+ and strings; the term is synonymous with “entity”.
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">value</a>. Literals have
@@ -210,8 +210,11 @@
(logical AND) of the <a title="RDF statement">statements</a>
corresponding to all the triples it contains.</p>
- <p><a title="RDF statement">Statements</a> involving
- <a title="blank node">blank nodes</a> say that something with the given
+ <p>Unlike <a title="IRI">IRIs</a> and <a title="literal">literals</a>,
+ <a title="blank node">blank nodes</a> do not denote specific
+ <a title="resource">resources</a>.
+ <a title="RDF statement">Statements</a> involving
+ blank nodes say that something with the given
relationships exists, without explicitly naming it.</p>
</section>
@@ -585,17 +588,23 @@
<a title="literal">literals</a>.
Otherwise, this set of blank nodes is arbitrary.</p>
- <p>RDF 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.</p>
+ <p>Given two blank nodes, it is
+ possible to determine whether or not they are the same.
+ Besides that, RDF makes no reference to any internal structure
+ of blank nodes.</p>
- <p class="note">Some concrete syntaxes for RDF use
- <dfn title="blank node identifier">blank node identifiers</dfn>
- to allow several statements to use the same
- blank node. A blank node identifier is a local identifier that can be
- distinguished from IRIs and literals. Such blank node identifiers are
- <em>not</em> part of the RDF abstract syntax, but are entirely
- dependent on the particular concrete syntax used.</p>
+ <p class="note" id="note-bnode-id">
+ <dfn title="blank node identifier">Blank node identifiers</dfn>
+ are local identifiers that are used in some
+ <a title="concrete RDF syntax">concrete RDF syntaxes</a>
+ or RDF store implementations.
+ They are always locally scoped to the file or RDF store,
+ and are <em>not</em> persistent or portable identifiers
+ for blank nodes. Blank node identifiers are <em>not</em>
+ part of the RDF abstract syntax, but are entirely dependent
+ 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.</p>
</section>
@@ -1148,7 +1157,14 @@
<p>Likewise, RDF graphs embedded in non-RDF representations
with mechanism such as RDFa [[RDFA-PRIMER]]
should use fragment identifiers consistently with the semantics
- imposed by the host language.</p>
+ imposed by the host language.
+ For example, if the fragment <code>#chapter1</code> identifies
+ a document section
+ in an HTML+RDFa representation, then <code>#chapter1</code>
+ should be taken
+ to denote that same section in any RDFa-encoded statements
+ in the document.
+ </p>
</section>