Skip to content

Commit 39805f4

Browse files
committed
Fixes some HTML markup issues.
1 parent c9e69c1 commit 39805f4

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

spec/index.html

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -887,7 +887,7 @@ <h2>D-interpretations</h2>
887887

888888
<p>The special datatypes
889889
<a data-cite="RDF12-CONCEPTS#dfn-language-tagged-string"><code>rdf:langString</code></a> and
890-
<a data-cite="RDF12-CONCEPTS#dfn-directional-language-tagged-string"><code>rdf:dirLangString</code>
890+
<a data-cite="RDF12-CONCEPTS#dfn-directional-language-tagged-string"><code>rdf:dirLangString</code></a>
891891
have no <a>ill-typed</a> literals.
892892
Any syntactically legal literal with one of these types will denote a value in every
893893
D-interpretation where D includes <code>rdf:langString</code> or <code>rdf:dirLangString</code>.
@@ -1034,7 +1034,7 @@ <h2>RDF Interpretations</h2>
10341034

10351035
<p>The datatype IRIs
10361036
<a data-cite="RDF12-CONCEPTS#dfn-language-tagged-string"><code>rdf:langString</code></a>,
1037-
<a data-cite="RDF12-CONCEPTS#dfn-directional-language-tagged string"><code>rdf:dirLangString</code>,
1037+
<a data-cite="RDF12-CONCEPTS#dfn-directional-language-tagged string"><code>rdf:dirLangString</code></a>,
10381038
and <a data-cite="XMLSCHEMA11-2#string"><code>xsd:string</code></a>
10391039
MUST be <a>recognized</a> by all RDF interpretations.</p>
10401040

@@ -1557,11 +1557,11 @@ <h4>Patterns of RDFS entailment (Informative)</h4>
15571557

15581558
<p>As an example of a RDFS entailment involving triple terms using the entailment pattern rdfs14, the following graph &mdash;</p>
15591559

1560-
<p><code>ex:a ex:b <<( ex:c ex:d <<(ex:e ex:f ex:g)>> )>> .</code></p>
1560+
<p><code>ex:a ex:b &lt;&lt;( ex:c ex:d &lt;&lt;(ex:e ex:f ex:g)>> )>> .</code></p>
15611561

15621562
<p>&mdash; RDFS entails &mdash;</p>
15631563

1564-
<p><code>ex:a ex:b <<( ex:c ex:d _:b1 )>> .<br/>
1564+
<p><code>ex:a ex:b &lt;&lt;( ex:c ex:d _:b1 )>> .<br/>
15651565
ex:a ex:b _:b2 .<br/>
15661566
_:b1 rdf:type rdfs:Proposition .<br/>
15671567
_:b2 rdf:type rdfs:Proposition .</code></p>
@@ -1622,7 +1622,7 @@ <h2>RDF Datasets</h2>
16221622
<tr>
16231623
<td class="semantictable">
16241624
<p>An <a>RDF dataset</a>
1625-
is a set:</p>
1625+
is a set:<br/>
16261626
{ G, (&lt;u<sub>1</sub>&gt;, G<sub>1</sub>), (&lt;u<sub>2</sub>&gt;, G<sub>2</sub>), . .
16271627
. (&lt;u<sub>n</sub>&gt;, G<sub>n</sub>) }<br>
16281628
where n&ge;0 and G and each G<sub>i</sub> are graphs, and each &lt;u<sub>i</sub>&gt; is an IRI. Each
@@ -1814,6 +1814,7 @@ <h2>Entailment rules (Informative)</h2>
18141814
The complete entailment pattern for generalized RDF with [=symmetric RDF triples=],
18151815
considering that, according to the semantics, the denotation of triple terms should
18161816
be of type <code>rdfs:Proposition</code>, is the following:
1817+
</p>
18171818
<table>
18181819
<caption>RDFS-T entailment pattern.</caption>
18191820
<tbody>
@@ -1832,7 +1833,6 @@ <h2>Entailment rules (Informative)</h2>
18321833
</tr>
18331834
</tbody>
18341835
</table>
1835-
</p>
18361836

18371837
<p class="issue" data-number="76">We don't have a completeness proof for the RDFS entailment rules (yet).</p>
18381838

0 commit comments

Comments
 (0)