--- a/rdf-dataset/index.html Wed Feb 19 08:00:12 2014 -0800
+++ b/rdf-dataset/index.html Wed Feb 19 17:58:04 2014 +0100
@@ -424,7 +424,7 @@
<pre class="example">:a rdf:type :d :x .</pre>
<h4 id="p5" class="prop">Properties of this dataset semantics</h4>
- <p>With this semantics, all inferences that are valid with normal RDF triples are preserved, but it is necessary to extend RDFS in order to accommodate for ternary relations. There are several existing proposal that extends this quad semantics by dealing with a specific “dimension”, such as time, uncertainty, provenance. For instance, temporal RDF [[TEMPORAL-RDF]] use the fourth element to denote a time frame, and reasoning can be performed per time frame. Special semantic rules allow one to combine triples in overlapping time frames. Fuzzy RDF [[FUZZY-RDF]] extends the semantics to deal with uncertainty. stRDF [[ST-RDF]] extends temporal RDF to deal with spatial information. Annotated RDF [[ANNOTATED-RDF]] generalizes the previous proposals.</p>
+ <p>With this semantics, all inferences that are valid with normal RDF triples are preserved, but it is necessary to extend RDFS in order to accommodate for ternary relations. There are several existing proposals that extend this quad semantics by dealing with a specific “dimension”, such as time, uncertainty, provenance. For instance, temporal RDF [[TEMPORAL-RDF]] uses the fourth element to denote a time frame and thus allow reasoning to be performed per time frame. Special semantic rules allow one to combine triples in overlapping time frames. Fuzzy RDF [[FUZZY-RDF]] extends the semantics to deal with uncertainty. stRDF [[ST-RDF]] extends temporal RDF to deal with spatial information. Annotated RDF [[ANNOTATED-RDF]] generalizes the previous proposals.</p>
</section>
<section>
@@ -481,7 +481,7 @@
<p>Communication of the intended semantics could be performed in various ways, from having the author tell the consumers directly, to inventing a protocol for this. Use of the HTTP protocol and content negotiation could be a possible way too. Special syntactic markers in the concrete serialization of datasets could convey the intended meaning. All of those are solutions that do not follow current practices.</p>
</section>
-<section class="appendix informative" id="section-acknowledgements">
+<section class="appendix" id="section-acknowledgements">
<h2>Acknowledgements</h2>
@@ -493,7 +493,7 @@
</section>
-<section class="appendix informative" id="changes">
+<section class="appendix" id="changes">
<h2>Changes since the first public working draft of 17 December 2013</h2>
<ul>
<li>2014-02-19: Updated references to [[SPARQL11-QUERY]].</li>