--- a/rdf-dataset/index.html Tue Sep 17 10:00:27 2013 +0200
+++ b/rdf-dataset/index.html Tue Sep 17 10:44:53 2013 +0200
@@ -17,13 +17,34 @@
margin-left: 1em
}
</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.
specStatus: "ED",
- // the specification's short name, as in http://www.w3.org/TR/short-name/
+ localBiblio:{
+"RDF11-CONCEPTS": "Richard Cyganiak, David Wood. <cite><a href=\"http://www.w3.org/TR/2013/WD-rdf11-concepts-20130723/\">RDF 1.1 Concepts and Abstract Syntax.</a></cite> 23 July 2013. W3C Last Call Working Draft. URL: <a href=\"http://www.w3.org/TR/2013/WD-rdf11-concepts-20130723/\">http://www.w3.org/TR/2013/WD-rdf11-concepts-20130723/</a>. The latest edition is available at <a href=\"http://www.w3.org/TR/rdf11-concepts/\">http://www.w3.org/TR/rdf11-concepts/</a>",
+
+"RDF11-MT" : "Patrick J. Hayes; Peter F. Patel-Schneider. <a href=\"http://www.w3.org/TR/2013/WD-rdf11-mt-20130723/\"><cite>RDF 1.1 Semantics</cite></a>. 23 July 2013. W3C Last Call Working Draft. URL: <a href=\"http://www.w3.org/TR/2013/WD-rdf11-mt-20130723/\">http://www.w3.org/TR/2013/WD-rdf11-mt-20130723/</a>. The latest edition is available at <a href=\"http://www.w3.org/TR/rdf11-mt/\">http://www.w3.org/TR/rdf11-mt/</a>",
+
+"VOID" : "Keith Alexander, Richard Cyganiak, Michael Hausenblas, Jun Zhao. <cite><a href=\"http://www.w3.org/TR/2011/NOTE-void-20110303/\">Describing Linked Datasets with the VoID Vocabulary.</a></cite> 03 March 2011. W3C Interest Group Note. URL: <a href=\"http://www.w3.org/TR/2011/NOTE-void-20110303/\">http://www.w3.org/TR/2011/NOTE-void-20110303/</a>. The latest edition is available at <a href=\"http://www.w3.org/TR/void/\">http://www.w3.org/TR/void/</a>",
+
+"SPARQL11-ENTAILMENT-REGIMES" : "Birte Glimm, Chimezie Ogbuji. <cite><a href=\"http://www.w3.org/TR/2013/REC-sparql11-entailment-20130321/\"><cite>SPARQL 1.1 Entailment Regimes.</a></cite> 21 March 2013. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2013/REC-sparql11-entailment-20130321/\">http://www.w3.org/TR/2013/REC-sparql11-entailment-20130321/</a>. The latest edition is available at <a href=\"http://www.w3.org/TR/sparql11-entailment/\">http://www.w3.org/TR/sparql11-entailment/</a>",
+
+"SPARQL11-SERVICE-DESCRIPTION" : "Gregory Todd Williams. <cite><a href=\"http://www.w3.org/TR/2013/REC-sparql11-service-description-20130321/\"><cite>SPARQL 1.1 Entailment Regimes.</a></cite> 21 March 2013. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2013/REC-sparql11-service-description-20130321/\">http://www.w3.org/TR/2013/REC-sparql11-service-description-20130321/</a>. The latest edition is available at <a href=\"http://www.w3.org/TR/sparql11-service-description/\">http://www.w3.org/TR/sparql11-service-description/</a>",
+
+"TEMPORAL-RDF" : "Claudio Gutiérrez, Carlos A. Hurtado, Alejandro A. Vaisman. <cite>Temporal RDF.</cite> In The Semantic Web: Research and Applications, Second European Semantic Web Conference, ESWC 2005, Heraklion, Crete, Greece, May 29 - June 1, 2005, Proceedings. Springer, LNCS 3532, pp. 93-107",
+
+"FUZZY-RDF" : "Umberto Straccia. <cite>A Minimal Deductive System for General Fuzzy RDF.</cite> In Web Reasoning and Rule Systems, Third International Conference, RR 2009, Chantilly, VA, USA, October 25-26, 2009, Proceedings. Springer, LNCS 5837, pp. 166-181",
+
+"ST-RDF" : "Manolis Koubarakis, Kostis Kyzirakos. <cite>Modeling and Querying Metadata in the Semantic Sensor Web: The Model stRDF and the Query Language stSPARQL.</cite> In The Semantic Web: Research and Applications, 7th Extended Semantic Web Conference, ESWC 2010, Heraklion, Crete, Greece, May 30 - June 3, 2010, Proceedings, Part I. Springer, LNCS 6088, pp. 425-439.",
+
+"ANNOTATED-RDF" : "Octavian Udrea, Diego Reforgiato Recupero, V. S. Subrahmanian. <cite>Annotated RDF.</cite> In The Semantic Web: Research and Applications, 3rd European Semantic Web Conference, ESWC 2006, Budva, Montenegro, June 11-14, 2006, Proceedings. Springer, LNCS 4011, pp. 487-501",
+
+"DELBRU-ET-AL-2008" : "Renaud Delbru, Axel Polleres, Giovanni Tummarello, Stefan Decker. <cite>Context Dependent Reasoning for Semantic Documents in Sindice.</cite> In Proceedings of the 4th International Workshop on Scalable Semantic Web Knowledge Base Systems (SSWS). Karlsruhe, Germany, 2008." },
+
+ // the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "rdf-datasets",
// if your specification has a subtitle that goes below the main
@@ -350,7 +371,7 @@
<h4 class="prop">Properties of this dataset semantics</h4>
<p>This semantics assumes that the truth of named graphs is preserved when replacing the RDF graphs inside named graphs with equivalent graphs. This means in particular, that one can normalise literals and still preserve the truth of a named graph. This means too that standard RDF inferences that can be drawn from the RDF graphs inside named graphs can be added to the graph associated with the graph name without impacting the truth of the RDF dataset.</p>
<p>While this semantics does not guarantee that reasoning with RDF datasets will preserve the exact triples of an original dataset, it is semantically valid to store both the original and any entailed datasets.</p>
- <p>An example implementation of such a context-based semantics is Sindice [[Delbru-et-al]].</p>
+ <p>An example implementation of such a context-based semantics is Sindice [[DELBRU-ET-AL-2008]].</p>
<h4 class="other">Variants this dataset semantics</h4>
<p>There are several variants of this type of dataset-semantics</p>
@@ -401,7 +422,7 @@
<pre class="example">:a rdf:type :d :x .</pre>
<h4 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 accomodate 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 extends the semantics to deal with uncertainty. stRDF extends temporal RDF to deal with spatial information. 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 accomodate 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>
</section>
<section>
@@ -416,7 +437,7 @@
<section>
<h3>Relationship with SPARQL entailment regime</h3>
- <p>There is a strong relationship between SPARQL ASK queries with an entailment regime [[SPARQL-ENTAILMENT-REGIME]] and inferences in the regime. If an ASK query does not contain variables and its WHERE clause only contains a basic graph pattern, then the query can be seen as an RDF graph. If such a graph query <var>Q</var> returns <code>true</code> when issued against an RDF graph <var>G</var> with entailment regime <var>E</var>, then <var>G</var> <var>E</var>-entails <var>Q</var>. If it returns <code>false</code>, then <var>G</var> does not <var>E</var>-entail <var>Q</var>.</p>
+ <p>There is a strong relationship between SPARQL ASK queries with an entailment regime [[SPARQL11-ENTAILMENT-REGIMES]] and inferences in the regime. If an ASK query does not contain variables and its WHERE clause only contains a basic graph pattern, then the query can be seen as an RDF graph. If such a graph query <var>Q</var> returns <code>true</code> when issued against an RDF graph <var>G</var> with entailment regime <var>E</var>, then <var>G</var> <var>E</var>-entails <var>Q</var>. If it returns <code>false</code>, then <var>G</var> does not <var>E</var>-entail <var>Q</var>.</p>
<p>A dataset semantics can also be compared to what ASK queries return when they do not contain variables but may contain basic graph patterns or graph graph patterns. For instance, consider the dataset:</p>
<pre class="example">{ }
:g1 { :x rdf:type :c .
@@ -443,7 +464,7 @@
<p>This was not retained eventually, because of the lack of experience, and potentially the lack of utility, so there is no definite option for this. Nonetheless, for completeness, we describe here possible solutions.</p>
<h3>Using vocabularies</h3>
- <p>A dataset can be described in RDF using vocabularies like voiD [[VOID]] and the SPARQL service description vocabulary [[SPARQL-SERVICE-DESCRIPTION]]. VoiD is used to describe how a collection of RDF triples is organized in a web site or across web sites, giving information about the size of the datasets, the location of the dump files, the IRI of the query endpoints, and so on. The notion of dataset in voiD is used as a more informal and broader concept than RDF dataset. However, an RDF dataset and the graphs in it can be describe as voiD datasets and the information can be completed with SPARQL service description</p>
+ <p>A dataset can be described in RDF using vocabularies like voiD [[VOID]] and the SPARQL service description vocabulary [[SPARQL11-SERVICE-DESCRIPTION]]. VoiD is used to describe how a collection of RDF triples is organized in a web site or across web sites, giving information about the size of the datasets, the location of the dump files, the IRI of the query endpoints, and so on. The notion of dataset in voiD is used as a more informal and broader concept than RDF dataset. However, an RDF dataset and the graphs in it can be describe as voiD datasets and the information can be completed with SPARQL service description</p>
<pre class="example">@prefix er: <http://www.w3.org/ns/entailment> .
@prefix sd: <http://www.w3.org/ns/sparql-service-description#> .
[] a sd:Dataset;
@@ -459,7 +480,6 @@
</section>
<section id="references">
-<p>@@@ tbd</p>
</section>
<section class="appendix informative" id="changes">