typos.
authorPat Hayes <phayes@ihmc.us>
Mon, 17 Jun 2013 03:27:54 -0500
changeset 855 3a3d50dd41d5
parent 854 7ff926d07b49
child 856 5784e3c47db2
typos.
rdf-mt/index.html
--- a/rdf-mt/index.html	Mon Jun 17 02:36:45 2013 -0500
+++ b/rdf-mt/index.html	Mon Jun 17 03:27:54 2013 -0500
@@ -623,7 +623,7 @@
     </tr>
   </table>
 
-<p>RDF imposes no particular normative meanings on the rest of the RDF vocabulary.  Appendix D describes the intended uses of some of this vocabulary.</p>
+<p>RDF imposes no particular normative meanings on the rest of the RDF vocabulary.  <a>Appendix D</a> describes the intended uses of some of this vocabulary.</p>
 
 
 <p>The datatype IRIs <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-language-tagged-string"><code>rdf:langString</code></a> and <a href="http://www.w3.org/TR/xmlschema11-2/#string"><code>xsd:string</code></a> MUST be <a>recognize</a>d by all RDF interpretations. </p>
@@ -652,7 +652,7 @@
       <th ><strong>then S RDF entails, recognizing D</strong></th>
     </tr>
     <tr > 
-      <td class="othertable">rdfD1</td>
+      <td class="othertable"><dfn>rdfD1</dfn></td>
       <td class="othertable">   xxx aaa <code>"</code>sss<code>"^^</code>ddd <code>.</code> <br/>
           for ddd in D</td>
       <td class="othertable">xxx aaa _:nnn <code>.</code><br/>
@@ -936,7 +936,7 @@
 </table>
 
 <p>RDFS does not partition the universe into disjoint categories of classes, properties and individuals. Anything in the universe can be used as a class or as a property, or both, while retaining its status as an individual which may be in classes and have properties. Thus, RDFS permits classes which contain other classes, classes of properties, properties of classes, etc. As the axiomatic triples above illustrate, it also permits classes which contain themselves and properties which apply to themselves. A property of a class is not necessarily a property of its members, nor vice versa. </p>
-<section class="informative">
+<section>
 <h4>A note on rdfs:Literal</h3>
 <p>The class <code>rdfs:Literal</code> is not the class of literals, but rather that of literal values, which may also be referred to by IRIs. For example, LV does not contain the literal <code>"foodle"^^xsd:string</code> but it does contain the string "foodle".</p>
 
@@ -1074,7 +1074,7 @@
 
 <section class="appendix" class="informative"><h3  id="entailment_rules">Entailment rules (Informative)</h3>
 
-<p>This section is based on work described more fully in [[HORST04]], [[HORST05]], which should be consulted for technical details and proofs. </p>
+<p>(<em>This section is based on work described more fully in </em>[[HORST04]]<em>, </em>[[HORST05]]<em>, which should be consulted for technical details and proofs.</em>) </p>
 <p> The RDF and RDFS entailment patterns listed in the above tables can be viewed as left-to-right rules which add the entailed conclusion to a graph. These rule sets can be used to check RDF (or RDFS) entailment between graphs S and E, by the following sequence of operations:</p>
 <p>1. Add to S all the RDF (or RDF and RDFS) axiomatic triples except those containing the container membership property IRIs <code>rdf:_1, rdf:_2, ...</code>.<br/>
 2. For every container membership property IRI which occurs in E, add the RDF (or RDF and RDFS) axiomatic triples which contain that IRI.<br/>