HTML syntax fixes for validation.
authorDavid Wood <dwood@zepheira.com>
Wed, 03 Jul 2013 12:29:00 -0400
changeset 899 0aa948ea4fbf
parent 895 5c32143aec58
child 900 60dd129e1f73
HTML syntax fixes for validation.
rdf-concepts/index.html
--- a/rdf-concepts/index.html	Wed Jul 03 11:05:44 2013 -0400
+++ b/rdf-concepts/index.html	Wed Jul 03 12:29:00 2013 -0400
@@ -8,7 +8,7 @@
 .figure a[href]:hover { background: transparent; }
 table td, table th { border: 1px solid #ddd; padding: 0.2em 0.5em; }
     </style>
-    <script src='../ReSpec.js/js/respec.js' class='remove'></script>
+    <script src="http://www.w3.org/Tools/respec/respec-w3c-common" class="remove"></script>
     <script class='remove'>
       var respecConfig = {
           // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
@@ -149,7 +149,7 @@
 
     <ul>
       <li>serialization syntaxes for storing and exchanging RDF
-      (e.g., <a href="http://www.w3.org/TR/turtle/">Turtle</a> [[TURTLE-TR]]
+      (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>
 
@@ -255,7 +255,7 @@
     by means of a specification or other document that explains
     what is denoted. For example, the
     <a href="http://www.w3.org/TR/vocab-org/">Organization Ontology
-    document</a> [[VOCAB-ORG]] specifies the intended referents
+    document</a> [[vocab-org]] specifies the intended referents
     of various IRIs that start with
     <code>http://www.w3.org/ns/org#</code>.</li>
 
@@ -296,7 +296,8 @@
     Some namespace IRIs are associated by convention with a short name
     known as a <dfn>namespace prefix</dfn>. Some examples:
 
-    <table rules="all" summary="Some example namespace prefixes and IRIs">
+    <table class="simple">
+			<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>
@@ -304,8 +305,8 @@
     </table>
 
     <p>In some serialization formats it is common to abbreviate <a title="IRI">IRIs</a>
-    that start with <a title="namespace IRI">namespace IRIs</a> by using the
-    associated <a>namespace prefix</a> in order to assist readability. For example, the IRI
+    that start with <a title="namespace IRI">namespace IRIs</a> by using a
+    <a>namespace prefix</a> in order to assist readability. For example, the IRI
     <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code>
     would be abbreviated as <code>rdf:XMLLiteral</code>.
     Note however that these abbreviations are <em>not</em> valid IRIs,
@@ -452,12 +453,12 @@
 
     <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-TR]], RDFa [[RDFA-PRIMER]], JSON-LD [[JSON-LD]],
-    RDF/XML [[RDF-SYNTAX-GRAMMAR]], or N-Triples [[N-TRIPLES]].  
+    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>
 
-    <p>A <a>concrete RDF syntax<a> may offer
+    <p>A <a>concrete RDF syntax</a> may offer
     many different ways to encode the same <a>RDF graph</a> or
     <a>RDF dataset</a>, for example through the use of
     <a title="namespace prefix">namespace prefixes</a>,
@@ -530,7 +531,7 @@
 <section id="section-IRIs">
     <h3>IRIs</h3>
 
-    <p>An <dfn title="IRI"><acronym title="Internationalized Resource Identifier">IRI</acronym></dfn>
+    <p>An <dfn title="IRI"><abbr title="Internationalized Resource Identifier">IRI</abbr></dfn>
     (Internationalized Resource Identifier) within an RDF graph
     is a Unicode string [[!UNICODE]] that conforms to the syntax
     defined in RFC 3987 [[!RFC3987]].</p>
@@ -548,7 +549,7 @@
     <div class="note" id="note-iris">
     <p><strong>URIs and IRIs:</strong>
     IRIs are a generalization of
-    <dfn title="URI"><acronym title="Uniform Resource Identifier">URI</acronym>s</dfn> [[RFC3986]] that permits a much wider range of Unicode characters.
+    <dfn title="URI"><abbr title="Uniform Resource Identifier">URI</abbr>s</dfn> [[RFC3986]] that permits a much 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
@@ -741,7 +742,7 @@
     if needed.</p>
 
     <p>Systems that want Skolem IRIs to be recognizable outside of the system
-    boundaries SHOULD use a well-known IRI [[WELL-KNOWN]] with the registered
+    boundaries SHOULD use a well-known IRI [[RFC5785]] with the registered
     name <code>genid</code>. This is an IRI that uses the HTTP or HTTPS scheme,
     or another scheme that has been specified to use well-known IRIs; and whose
     path component starts with <code>/.well-known/genid/</code>.
@@ -751,7 +752,7 @@
 
     <pre>http://example.com/.well-known/genid/d26a2d0e98334696f4ad70a677abc1f6</pre>
 
-    <p class="note">RFC 5785 [[WELL-KNOWN]] only specifies well-known URIs,
+    <p class="note">RFC 5785 [[RFC5785]] only specifies well-known URIs,
     not IRIs. For the purpose of this document, a well-known IRI is any
     IRI that results in a well-known URI after IRI-to-URI mapping [[!RFC3987]].</p>
 </section>
@@ -832,10 +833,10 @@
 <section id="section-dataset-isomorphism">
 		<h3>RDF Dataset Comparison</h3>
 
-    <p id="section-graph-equality">Two <a title="RDF Dataset">RDF datasets</a>
+    <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
+		<var>DG2</var> and named graph <var>NG2</var>) are
 		<dfn title="dataset isomorphism">dataset-isomorphic</dfn> if and only if:</p>
 		<ol>
 		  <li><var>DG1</var> and <var>DG2</var> are graph-isomorphic;</li>
@@ -925,32 +926,33 @@
     <p>The <a title="literal">literals</a> that can be defined using this
     datatype are:</p>
 
-    <table rules="all" summary="This table lists the literals of type xsd:boolean.">
+    <table class="simple">
+			<caption>This table lists the literals of type xsd:boolean.</caption>
       <tr>
         <th>Literal</th>
         <th>Value</th>
       </tr>
       <tr>
-        <td align="center">&lt;“<code>true</code>”, <code>xsd:boolean</code>&gt;</td>
-        <td align="center"><em><strong>true</strong></em></td>
+        <td>&lt;“<code>true</code>”, <code>xsd:boolean</code>&gt;</td>
+        <td><em><strong>true</strong></em></td>
       </tr>
       <tr>
-        <td align="center">&lt;“<code>false</code>”, <code>xsd:boolean</code>&gt;</td>
-        <td align="center"><em><strong>false</strong></em></td>
+        <td>&lt;“<code>false</code>”, <code>xsd:boolean</code>&gt;</td>
+        <td><em><strong>false</strong></em></td>
       </tr>
       <tr>
-        <td align="center">&lt;“<code>1</code>”, <code>xsd:boolean</code>&gt;</td>
-        <td align="center"><em><strong>true</strong></em></td>
+        <td>&lt;“<code>1</code>”, <code>xsd:boolean</code>&gt;</td>
+        <td><em><strong>true</strong></em></td>
       </tr>
       <tr>
-        <td align="center">&lt;“<code>0</code>”, <code>xsd:boolean</code>&gt;</td>
-        <td align="center"><em><strong>false</strong></em></td>
+        <td>&lt;“<code>0</code>”, <code>xsd:boolean</code>&gt;</td>
+        <td><em><strong>false</strong></em></td>
       </tr>
     </table>
 
 
-<section id="xsd-datatypes" name="xsd-datatypes">
-    <h3>The XML Schema Built-in Datatypes</h3>
+<section id="xsd-datatypes">
+    <h3 name="xsd-datatypes">The XML Schema Built-in Datatypes</h3>
 
     <p><a title="IRI">IRIs</a> of the form
     <code>http://www.w3.org/2001/XMLSchema#<em>xxx</em></code>,
@@ -965,7 +967,8 @@
 		datatypes are the only safe datatypes for transferring binary
 		information.</p>
  
-    <table rules="all" summary="A list of the RDF-compatible XSD types, with short descriptions">
+    <table class="simple">
+			<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>
@@ -1116,13 +1119,12 @@
     <code><dfn>rdf:XMLLiteral</dfn></code>, which is defined as follows:</p>
    
     <dl>
-      <dt id="XMLLiteral-uri">An IRI denoting
-      this datatype</a></dt>
+      <dt id="XMLLiteral-uri">An IRI denoting this <a>datatype</a></dt>
 
       <dd>is
       <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code>.</dd>
 
-      <dt id="XMLLiteral-lexical-space">The lexical space</a></dt>
+      <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> 
@@ -1131,7 +1133,7 @@
       <a href="http://www.w3.org/TR/1999/REC-xml-names-19990114/">XML Namespaces</a>
       [[!XML-NAMES]].</dd>
 
-      <dt id="XMLLiteral-value-space">The value space</a></dt>
+      <dt id="XMLLiteral-value-space">The <a>value space</a></dt>
 
       <dd>is a set of DOM
       <a href="http://www.w3.org/TR/dom/#interface-documentfragment"><code>DocumentFragment</code></a>
@@ -1142,7 +1144,7 @@
       <code><em>A</em>.<a href="http://www.w3.org/TR/dom/#dom-node-isequalnode">isEqualNode</a>(<em>B</em>)</code>
       returns <code>true</code>.</dd>
 
-      <dt id="XMLLiteral-mapping">The lexical-to-value mapping</a></dt>
+      <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 
@@ -1154,7 +1156,7 @@
       <li>Return <code>domfrag.<a href="http://www.w3.org/TR/dom/#dom-node-normalize">normalize</a>()</code></li>
       </ul></dd>
 
-      <dt id="XMLLiteral-canonical">The canonical mapping</a></dt>
+      <dt id="XMLLiteral-canonical">The <a>canonical mapping</a></dt>
       <dd>defines a
       <a href="http://www.w3.org/TR/xmlschema11-2/#dt-canonical-mapping">canonical lexical form</a>
       [[!XMLSCHEMA11-2]] for each member of the value space.
@@ -1321,7 +1323,7 @@
     Massimo Marchiori, Tim Berners-Lee, Dave Reynolds and Dan Connolly.</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>.
+    <a href="http://www.w3.org/2000/09/dbwg/details?group=46168&amp;public=1">members of the RDF Working Group</a>.
     It draws upon two earlier specifications,
     <em><a href="http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/">RDF Model and Syntax</a></em>, edited by Ora Lassilla and Ralph Swick,
     and <em><a href="http://www.w3.org/TR/2000/CR-rdf-schema-20000327/">RDF Schema</a></em>, edited by Dan Brickley and R. V. Guha, which were produced by
@@ -1388,7 +1390,7 @@
 <section class="appendix informative" id="change-log">
   <h2>Change Log</h2>
 
-<section class="appendix" id="changes-wd3">
+<section class="appendix" id="changes-wd4">
   <h3>Changes from 15 January 2013 WD to this version</h3>
 
   <p>This section lists changes from the