Fix references and some ReSpec issues
authorMarkus Lanthaler <>
Mon, 21 Oct 2013 20:01:29 +0200
changeset 1154 735b58f87355
parent 1153 33f93931bd5d
child 1155 9ef6020b1be2
Fix references and some ReSpec issues
--- a/rdf-concepts/index.html	Mon Oct 21 19:25:30 2013 +0200
+++ b/rdf-concepts/index.html	Mon Oct 21 20:01:29 2013 +0200
@@ -53,10 +53,6 @@
           // necessary.
           prevRecShortname: "rdf-concepts",
-          // if you want to have extra CSS, append them to this list
-          // it is recommended that the respec.css stylesheet be kept
-          extraCSS:             ["//"],
           // editors, add as many as you like
           // only "name" is required
           editors:  [
@@ -207,7 +203,7 @@
     <a title="literal value">literal value</a>. Literals have
     <a title="datatype">datatypes</a> that define the range of possible
     values, such as strings, numbers, and dates. A special kind of literals,
-    <a>language-tagged strings</a>, denote plain-text strings in a
+    <a title="language-tagged string">language-tagged strings</a>, denote plain-text strings in a
     natural language.</p>
     <p>Asserting an <a>RDF triple</a> says that <em>some relationship,
@@ -361,7 +357,7 @@
     can be reflected in the following ways:</p>
-      <li>An <a>IRI</a>, once <a title="minting">minted</a>, should never
+      <li>An <a>IRI</a>, once minted, should never
       change its intended <a>referent</a>. (See
       <a href="">URI
       persistence</a> [[WEBARCH]].)</li>
@@ -386,7 +382,7 @@
     <h3>Working with Multiple RDF Graphs</h3>
     <p>As RDF graphs are sets of triples, they can be
-    <a title="merge">combined</a> easily, supporting the use of data from
+    combined easily, supporting the use of data from
     multiple sources. Nevertheless, it is sometimes desirable to work
     with multiple RDF graphs while keeping their contents separate.
     <a title="RDF dataset">RDF datasets</a> support this requirement.</p>
@@ -735,7 +731,7 @@
     <p>In situations where stronger identification is needed, systems MAY
     systematically replace some or all of the blank nodes in an RDF graph
     with <a title="IRI">IRIs</a>.  Systems wishing to do this SHOULD
-    <a title="minting">mint</a> a new, globally
+    mint a new, globally
     unique IRI (a <dfn>Skolem IRI</dfn>) for each blank node so replaced.</p>
     <p>This transformation does not appreciably change the meaning of an
@@ -1169,7 +1165,7 @@
       <li>Return <code>domfrag.<a href="">normalize</a>()</code></li>
-      <dt id="XMLLiteral-canonical">The <a>canonical mapping</a></dt>
+      <dt id="XMLLiteral-canonical">The canonical mapping</dt>
       <dd>defines a
       <a href="">canonical lexical form</a>
       [[!XMLSCHEMA11-2]] for each member of the value space.
@@ -1326,7 +1322,7 @@
       <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
+      <a title="literal">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