fixed a few typoes, decided to make the partial-graph thing not an explicit issue for now; it doesn't really stand out against the rest of this stuff.
--- a/rdf-spaces/index.html Tue May 15 07:47:32 2012 -0400
+++ b/rdf-spaces/index.html Tue May 15 08:45:40 2012 -0400
@@ -733,7 +733,7 @@
formally stated in <a href="#semantics" class="sectionRef"></a>,
and the semantics of OWL, where { ?a owl:sameAs ?b } means that
the terms ?a and ?b both denote the same thing, the second dataset
- above entails the first, and includes only additional information
+ above entails the first and includes only additional information
that is known to be true. (Slight caveat: the new information is
only true if the assumptions of the name-generation function are
correct, that the name is previously unused and this naming agent
@@ -754,7 +754,7 @@
addressing the use case described in <a href="#uc-untrusted"
class="sectionRef"></a> and is illustrated in <a
href="#example-untrusted" class="sectionRef"></a>. It uses quads
- to addresses some—perhaps all—of the need for quints
+ to address some—perhaps all—of the need for quints
or nested graphs.</p>
<p>More precisely:</p>
@@ -869,10 +869,9 @@
class="sectionRef"></a>.
</p>
- <p class="issue">Do the named graphs in a dataset include all the
- triples in the spaces with those names, or only some of them? Aka
- partial-graph or complete-graph semantics. Assuming partial, but
- maybe we can say something about how things SHOULD be done?</p>
+ <p>@@@ explain why we use partial-graph semantics, and how in most
+ applications its bad to drop information, but sometimes it's
+ necessary, and sometimes you only have incomplete information.</p>
</section>