--- a/model/working-copy/prov-dm-constraints.html Wed Feb 15 11:20:56 2012 +0000
+++ b/model/working-copy/prov-dm-constraints.html Wed Feb 15 11:54:34 2012 +0000
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<html><head>
- <title>PROV-DM Part II: Constraints of the PROV Data Model</title>
+ <title>PROV-DM Part II: Constraints of the Provenance Data Model</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<!--
=== NOTA BENE ===
@@ -1618,7 +1618,7 @@
</section>
-
+<!--
<section id="resource-section">
<h2>Resources, URIs, Entities, Identifiers, and Scope</h2>
@@ -1711,6 +1711,7 @@
</section>
+-->
<!--
<li>For use, generation, and derivation event, the first argument is the 'effect' (i.e. most recent item) and the second argument is the 'cause' (i.e. least recent item). This order is
@@ -1718,13 +1719,20 @@
-->
<section>
-<h3>From Scruffy to Proper ...</h3>
+<h3>From "Scruffy" to "Proper" ...</h3>
<div class='note'>
Now that all constraints have been defined, it's time to revisit provenance nicknamed scuffy, and see what it actuall means, and how it can be made more proper.
+<p>
+What does a provenance description such as the following, actually mean? Why is it "scruffy"?
+<pre>
+wasAssociatedWith(tr:WD-prov-dm-20111215,ex:Simon)
+</pre>
+What do we need to add to make it "proper"?
</div>
</section>
+<!--
<section>
<h3>Stuff to Keep, Maybe?</h3>
@@ -1744,6 +1752,7 @@
</section>
+-->
<section class="appendix">
<h2>Acknowledgements</h2>