--- a/rdf-spaces/index.html Fri May 11 14:20:33 2012 -0400
+++ b/rdf-spaces/index.html Sun May 13 12:49:34 2012 -0400
@@ -251,11 +251,14 @@
sections include more scenarios (not involving the Example
Foundation's federated phonebook) which illustrate the use case.
Each section also links to an appendix where a detailed solution is
- provided.
+ provided. </p>
- <section id="uc-reloads">
- <h2>Minimizing Reloads</h2>
+ <section id="uc-start">
+ <h2>Baseline</h2>
+ <p>@@@Old text -- not a use case. Merge this with above into the
+ "baseline" system to which we want to add stuff.</p>
+
<p>An obvious drawback of version 1 is that for any data change in
a division database to show through to the users, the harvester
must be re-run, to again fetch and merge all the data. HTTP
@@ -278,56 +281,79 @@
it can replace just the ones coming from a given source.</p>
<p>For a discussion of how this use case could be addressed, see
- <a href="#example-reloads" class="sectionRef"></a></p>
+ <a href="#example-start" class="sectionRef"></a></p>
</section>
- <section>
+ <section id="uc-web">
<h2>Showing Provenance</h2>
- <p>@@@ the released db shows which dept supplies each part of the information </p>
+ <p>@@@ the released db shows which division supplies each part of the information </p>
+
+ <p>For a discussion of how this use case could be addressed, see
+ <a href="#example-web" class="sectionRef"></a></p>
+
</section>
- <section>
+ <section id="uc-process">
<h2>Maintaining Derived Data</h2>
<p>@@@ namefill is needed, and its results need their own provenance</p>
- </section>
-
- <section>
- <h2>Distributed Harvesting</h2>
-
- <p>@@@ divisions gather from departments who might gather from
- individuals </p>
+ <p>For a discussion of how this use case could be addressed, see
+ <a href="#example-process" class="sectionRef"></a></p>
</section>
- <section>
+ <section id="uc-reported">
+ <h2>Distributed Harvesting</h2>
+
+ <p>@@@ divisions gather from departments who might gather from
+ individuals; we want end-users to see that provenance. </p>
+
+ <p>For a discussion of how this use case could be addressed, see
+ <a href="#example-reported" class="sectionRef"></a></p>
+
+ </section>
+
+
+ <section id="uc-untrusted">
<h2>Loading Untrusted Datasets</h2>
<p>@@@ what if one of the divisions gives you bad quads? It
better not mess up provenance. Maybe suggest GSP-style name
- mangling...?</p>
+ mangling...? Put "renaming datasets" in Concepts somewhere as a
+ standard thing?</p>
+
+ <p>For a discussion of how this use case could be addressed, see
+ <a href="#example-untrusted" class="sectionRef"></a></p>
</section>
- <section>
+ <section id="uc-transtime">
<h2>Showing Revision History</h2>
<p>@@@ we want to be able to see all the changes, for auditing, to
see what the DB said about anyone at any point in time.
(transaction time)</p>
+
+ <p>For a discussion of how this use case could be addressed, see
+ <a href="#example-transtime" class="sectionRef"></a></p>
+
</section>
- <section>
+ <section id="uc-validtime">
<h2>Expressing Past or Future States</h2>
<p>@@@ we want to be able to express when someone started and stopped having a particular role various ways, which might not be the time we put this into the db.
</p>
+
+ <p>For a discussion of how this use case could be addressed, see
+ <a href="#example-validtime" class="sectionRef"></a></p>
+
</section>
@@ -911,6 +937,8 @@
document-scope for now. This is <a href="http://www.w3.org/2011/rdf-wg/track/issues/21">Issue-21</a>.</li>
<li>Can blank node labels be used as space names?
Assuming not, for now.</li>
+ <li>Can we provide a way to say a graph is in multiple spaces without repeating it? Something like [GRAPH] g1, g2, DEFAULT { ... } (where default is a keyword stand-in for the default graph</li>
+ <li>Can we allow allow people to re-use subject, like: g1 { ... }; :lastModified .... ? </li>
</ul>
</div>
@@ -950,13 +978,69 @@
</div>
- <section id="example-reloads">
- <h2>How to Minimize Reloads</h2>
+ <section id="example-start">
+ <h2>Showing Triples (v1)</h2>
- <p>To address the needs described in <a href="#uc-reloads"
- class="sectionRef"></a> ... @@@ </p>
+ <p>@@@ Shows the baseline in <a href="#uc-start" class="sectionRef"></a></p>
</section>
+
+
+ <section id="example-web">
+ <h2>Showing Web Provenance (v2)</h2>
+
+ <p>@@@ Shows how to address<a href="#uc-web" class="sectionRef"></a></p>
+
+ </section>
+
+
+
+ <section id="example-process">
+ <h2>Showing Process Provenance(v3)</h2>
+
+ <p>@@@ Shows how to address <a href="#uc-process" class="sectionRef"></a></p>
+
+ </section>
+
+
+
+ <section id="example-reported">
+ <h2>Showing Reported Provenance (v4)</h2>
+
+ <p>@@@ Shows how to address <a href="#uc-reported" class="sectionRef"></a></p>
+
+ </section>
+
+
+
+ <section id="example-untrusted">
+ <h2>Showing Untrusted Quads(v5)</h2>
+
+ <p>@@@ Show how to address <a href="#uc-untrusted" class="sectionRef"></a></p>
+
+ </section>
+
+
+
+ <section id="example-transtime">
+ <h2>Showing Change History (v6)</h2>
+
+ <p>@@@ Show how to address <a href="#uc-transtime" class="sectionRef"></a></p>
+
+ </section>
+
+
+
+ <section id="example-validtime">
+ <h2>Showing Past and Future States (v7)</h2>
+
+ <p>@@@ Shows how to address <a href="#uc-validtime" class="sectionRef"></a></p>
+
+ </section>
+
+
+
+
</section>
@@ -1118,6 +1202,7 @@
<section class="appendix informative" id="changes">
<h2>Changes</h2>
<ul>
+ <li>2012-05-13: Fill in the example's skeleton, add a few issues/ideas on trig</li>
<li>2012-05-11: Rewriting and reorganizing Concepts; some more work on Usecases and Example; removed the Detailed Example since it needs to be so re-written; renamed 'reflection' to 'folding'; reworked the Semanics</li>
<li>2012-05-10: Wrote a short intro. Started writing the Use Cases section for real. Added grammar for N-Quads and Trig. Did a first draft of the semantics.</li>
<li>2012-05-09: Renamed "layers" as "spaces"; some word-smithing in Concepts and the Abstract; removed "Turtle in HTML" as a dataset syntax; added some text about trig and nquads; added a note about change-over-time; added an appendix with a reflection vocabulary</li>