--- a/model/ProvenanceModel.html Fri Nov 25 12:04:34 2011 +0000
+++ b/model/ProvenanceModel.html Fri Nov 25 12:51:39 2011 +0000
@@ -572,6 +572,9 @@
<section class="informative" id="prov-dm-example">
<h2>Example</h2>
+<div class='issue'> There is a suggestion that a better example should be adopted for this document. Possibly, several shorter examples. This is <a href="http://www.w3.org/2011/prov/track/issues/132">ISSUE-132</a></div>
+
+
To illustrate PROV-DM, this section presents an example encoded according to PROV-ASN. For more detailed explanations of how PROV-DM should be used, and for more examples, we refer the reader to the Provenance Primer [[PROV-PRIMER]].
@@ -938,7 +941,7 @@
<p> An activity record, written <span class="name">activity(id, rl, st, et, [ attr1=val1, ...])</span> in PROV-ASN, contains:</p>
<ul>
<li><em>id</em>: an identifier <span class="name">id</span> identifying an activity;</li>
-<li><em>recipeLink</em>: an OPTIONAL <a href="#record-RecipeLink">recipe link</a> <span class="name">rl</span>, which consists of a domain specific description of the activity;</li>
+<li><em>recipeLink</em>: an OPTIONAL <a href="#record-RecipeLink">recipe link</a> <span class="name">rl</span>, which consists of a domain specific specification of the activity;</li>
<li><em>startTime</em>: an OPTIONAL time <span class="name">st</span> indicating the start of the activity;</li>
<li><em>endTime</em>: an OPTIONAL time <span class="name">et</span> indicating the end of the activity;</li>
<li><em>attributes</em>: a set of attribute-value pairs <span class="name">[ attr1=val1, ...]</span>, representing other attributes of this activity that hold for its whole duration.</li>
@@ -2165,7 +2168,7 @@
<span class="nonterminal">recordContainer</span> :=
<span class="name">container</span>
<span class="name">(</span>
-{ <span class="nonterminal">namespaceDeclarations</span> }
+<span class="nonterminal">namespaceDeclarations</span>
<span class="name">,</span>
{ <span class="nonterminal">identifier</span> }
<span class="name">,</span>
@@ -2185,7 +2188,8 @@
<p>
The following container </p>
<pre class="codeexample">
-container([x http://example.org/], [acc1,acc2]
+container(x: http://example.org/,
+ [acc1,acc2]
account(acc1,http://example.org/asserter1,...)
account(acc2,http://example.org/asserter1,...))
</pre>
@@ -2407,6 +2411,8 @@
inter-operable manner). Is this what we intend?
</div>
+<div class='issue'> Simplify the references to recipe link. This is <a href="http://www.w3.org/2011/prov/track/issues/131">ISSUE-131</a></div>
+
</section>
@@ -2614,7 +2620,7 @@
</ul>
</div>
-<p>We note that the previous constraint is not really an inference <em>rule<æm>, since there is nothing that we can actually infer. Instead, this constraint should simply be seen as part of the definition of the traceability record. </p>
+<p>We note that the previous constraint is not really an inference <em>rule</em>, since there is nothing that we can actually infer. Instead, this constraint should simply be seen as part of the definition of the traceability record. </p>
</section>
@@ -3008,7 +3014,7 @@
<section id="resource-section">
<h2>Resources, URIs, Entities, Identifiers, and Scope</h2>
-<p>This specification introduces the notion of an identifiable entity in the world. In PROV-DM, an entity record is a representation of such an identifiable entity. An entity record includes an identifier identifying this entity. Identifiers are URIs (TBC). </p>
+<p>This specification introduces the notion of an identifiable entity in the world. In PROV-DM, an entity record is a representation of such an identifiable entity. An entity record includes an identifier identifying this entity. Identifiers are qualified names, which can be mapped to IRIs. </p>
<p>The term 'resource' is used in a general sense
for whatever might be identified by a URI [[!RFC3986]]. On the Web, a URI denotes a resource, without any expectation that the resource is accessed. </p>
@@ -3021,51 +3027,64 @@
</p>
<pre>
-account(acc1,
- http://example.org/asserter1,
-
- entity(urn:example:0, [ prov:type="Document", ex:path="http://example.org/crime.txt" ])
- entity(urn:example:1, [ prov:type="Document", ex:path="http://example.org/crime.txt", ex:version="2.1", ex:content="...", ex:date="2011-10-07" ])
- entity(urn:example:2, [ prov:type="Document", ex:author="John" ])
- ...)
+container (app: urn:example:,
+ cr: http://example.org/crime/,
+ [acc1],
+ account(acc1,
+ http://example.org/asserter1,
+
+ entity(app:0, [ prov:type="Document", cr:path="http://example.org/crime.txt" ])
+ entity(app:1, [ prov:type="Document", cr:path="http://example.org/crime.txt", cr:version="2.1", cr:content="...", cr:date="2011-10-07" ])
+ entity(app:2, [ prov:type="Document", cr:author="John" ])
+ ...))
</pre>
<p>Each entity record contains an idenfier that identifies the entity it represents.
-In this example, three identifiers were minted using the URN syntax with "example" namespace.</p>
+In this example, three identifiers were minted, and their prefix uses the URN syntax with "example" namespace.</p>
<p>Given that the report is a resource denoted by the URI <span class="name">http://example.org/crime.txt</span>, we could simply use this URI as the identifier of an entity. This would avoid us minting new URIs. Hence, the report URI would play a double role: as a URI it denotes a resource accessible at that URI, and as a PROV-DM identifier, it identifies a specific characterization of this report. A given identifier identifies a single entity within the scope of an account. Hence, below, all entities records have been given the same identifier but appear in the scope of different accounts. </p>
<pre>
-account(acc2,
- http://example.org/asserter1,
-
- entity(http://example.org/crime.txt, [ prov:type="Document", ex:path="http://example.org/crime.txt" ])
- ...)
-
-account(acc3,
- http://example.org/asserter1,
-
- entity(http://example.org/crime.txt, [ prov:type="Document", ex:path="http://example.org/crime.txt", ex:version="2.1", ex:content="...", ex:date="2011-10-07" ])
- ...)
-
-account(acc4,
- http://example.org/asserter1,
- entity(http://example.org/crime.txt, [ prov:type="Document", ex:author="John" ])
- ...)
+container (app: http://example.org/,
+ cr: http://example.org/crime/,
+ [acc2, acc3, acc4],
+
+ account(acc2,
+ http://example.org/asserter1,
+
+ entity(app:crime.txt, [ prov:type="Document", cr:path="http://example.org/crime.txt" ])
+ ...)
+
+ account(acc3,
+ http://example.org/asserter1,
+
+ entity(app:crime.txt, [ prov:type="Document", cr:path="http://example.org/crime.txt", cr:version="2.1", cr:content="...", cr:date="2011-10-07" ])
+ ...)
+
+ account(acc4,
+ http://example.org/asserter1,
+ entity(app:crime.txt, [ prov:type="Document", cr:author="John" ])
+ ...))
</pre>
-<p>In this case, the URI <span class="name">http://example.org/crime.txt</span> still denotes the same resource; however, it identifies a different entity in each account. </p>
-
-<p> Alternatively, if we need to assert the existence of two different characterizations of the report within the same account, then alternate identifiers MUST be used, one of them being allowed to be the resource URI.</p>
+<p>In this case, the qualified name <span class="name">app:crime.txt</span> maps to URI <span class="name">http://example.org/crime.txt</span> still denotes the same resource; however, the perspective we take about that resource is expressed as a different entity record, happening to have the same identifier in different accounts. </p>
+
+<p> Alternatively, if we need to assert the existence of two different perspectives on the report within the same account, then alternate identifiers MUST be used, one of them being allowed to be the resource URI.</p>
<pre>
-account(acc5,
- http://example.org/asserter1,
-
- entity(http://example.org/crime.txt, [ prov:type="Document", ex:path="http://example.org/crime.txt" ])
- entity(urn:example:1, [ prov:type="Document", location="http://example.org/crime.txt", version="2.1", ex:content="...", ex:date="2011-10-07" ])
-
- ...)
+container (app: http://example.org/,
+ app2: urn:example:,
+ cr: http://example.org/crime/,
+
+ [acc5],
+
+ account(acc5,
+ http://example.org/asserter1,
+
+ entity(app:crime.txt, [ prov:type="Document", cr:path="http://example.org/crime.txt" ])
+ entity(app2:1, [ prov:type="Document", cr:path="http://example.org/crime.txt", cr:version="2.1", cr:content="...", cr:date="2011-10-07" ])
+
+ ...))
</pre>
@@ -3079,8 +3098,9 @@
<section class="appendix">
- <h2>Changes Since Previous Version</h2>
+ <h2>Changes Since First Public Working Draft</h2>
<ul>
+<li>11/25/11: Updated examples of section 8. </li>
<li>11/25/11: Definition of namespace. Clarification about interpretation of IRI occurrences. </li>
<li>11/25/11: Definition of attribute and identifier. </li>
<li>11/24/11: Added figure of Common Relations in Section 6. </li>