--- a/model/working-copy/towards-wd4.html Tue Feb 07 21:51:22 2012 +0000
+++ b/model/working-copy/towards-wd4.html Tue Feb 07 22:05:07 2012 +0000
@@ -730,7 +730,7 @@
<h4>Generation</h4>
-<p>Generation<span class="withAsn">, written <span class="name">wasGeneratedBy(id,e,a,t,attrs)</span></span> in PROV-ASN, has the following components:</p>
+<p>Generation<span class="withAsn">, written <span class="name">wasGeneratedBy(id,e,a,t,attrs)</span> in PROV-ASN,</span> has the following components:</p>
<ul>
<li><em>id</em>: an OPTIONAL identifier identifying the generation;</li>
<li><em>entity</em>: an identifier identifying a created entity; </li>
@@ -1298,10 +1298,13 @@
<p>The PROV data model introduces a fixed set of attributes in the <a href="#prov-dm-namespace">PROV-DM namespace</a>, which we define below.
The interpretation of any attribute declared in another namespace is out of scope.</p>
-<ul>
-<li> The attribute <dfn id="dfn-role"><span class="name">prov:role</span></dfn> denotes the function of an entity with respect to an activity, in the context of a usage, generation,
+
+<section id="record-attribute-role">
+<h4>prov:role</h4>
+
+<p>The attribute <dfn id="dfn-role"><span class="name">prov:role</span></dfn> denotes the function of an entity with respect to an activity, in the context of a usage, generation,
activity association, activity start, and activity end. The attribute <span class="name">prov:role</span> is allowed to occur multiple times in such assertions. The value associated with a <span
-class="name">prov:role</span> attribute MUST be conformant with <span class="nonterminal">Literal</span>.
+class="name">prov:role</span> attribute MUST be conformant with <span class="nonterminal">Literal</span>.</p>
<div class="anexample">
<p>The following activity start describes the role of the agent identified by <span class="name">ag</span> in this start relation with activity <span class="name">a</span>. </p>
@@ -1309,12 +1312,15 @@
wasStartedBy(a,ag, [prov:role="program-operator"])
</pre>
</div>
- </li>
+</section>
-<li> The attribute <dfn id="dfn-type"><span class="name">prov:type</span></dfn> provides further typing information for an element or relation. PROV-DM liberally
+<section id="record-attribute-type">
+<h4>prov:type</h4>
+
+<p>The attribute <dfn id="dfn-type"><span class="name">prov:type</span></dfn> provides further typing information for an element or relation. PROV-DM liberally
defines a type as a category of things having common characteristics. PROV-DM is agnostic about the representation of types, and only states that
the value associated with a <span class="name">prov:type</span> attribute MUST be conformant with <span class="nonterminal">Literal</span>. The attribute <span class="name">prov:type</span>
-is allowed to occur multiple times.
+is allowed to occur multiple times.</p>
<div class="anexample">
<p>The following record declares an agent of type software agent</p>
@@ -1322,13 +1328,15 @@
agent(ag, [prov:type="prov:SoftwareAgent" %% xsd:QName])
</pre>
</div>
-</li>
+</section>
+<section id="record-attribute-steps">
+<h4>prov:steps</h4>
-<li> The attribute <dfn id="dfn-steps"><span class="name">prov:steps</span></dfn> defines the level of precision associated with a derivation. The value associated with a <span
+<p> The attribute <dfn id="dfn-steps"><span class="name">prov:steps</span></dfn> defines the level of precision associated with a derivation. The value associated with a <span
class="name">prov:steps</span> attribute MUST be <span class="name">"single"</span> or <span class="name">"any"</span>. The attribute <span class="name">prov:step</span> occurs at most
once in a derivation. A derivation without attribute <span class="name">prov:step</span> is considered to be equivalent to the same derivation extended with an extra attribute
-<span class="name">prov:step</span> and associated value <span class="name">"any"</span>.
+<span class="name">prov:step</span> and associated value <span class="name">"any"</span>. </p>
<div class="anexample">
<p>The following expression declares an imprecise-1 derivation, which is known to involve one activity, though its identity, usage details of <span class="name">ex:e1</span>, and generation
@@ -1337,15 +1345,16 @@
wasDerivedFrom(ex:e2, ex:e1, [prov:steps="single"])
</pre>
</div>
-</li>
+</section>
-<li> The attribute <dfn id="dfn-label"><span class="name">prov:label</span></dfn> provides a human-readable representation of a PROV-DM element or relation.
+<section id="record-attribute-label">
+<h4>prov:label</h4>
+
+<p> The attribute <dfn id="dfn-label"><span class="name">prov:label</span></dfn> provides a human-readable representation of a PROV-DM element or relation.</p>
<div class='issue'>
This is <a href="http://www.w3.org/2011/prov/track/issues/219">ISSUE-219</a>. </div>
-</li>
-
-</ul>
+</section>
</section>
@@ -1422,109 +1431,11 @@
<section id="common-relations">
<h2>PROV-DM Common Relations</h2>
-</section>
-
-<section id="bundle">
-<h3>Bundle ????</h3>
-
-<p>In this section, two constructs are introduced to group
-PROV-DM records. The first
-one, <a>account record</a> is itself a
-record, whereas the second
-one <a>record container</a> is not.
-</p>
-
-
-<section id="record-Account">
-<h3>Account Record</h3>
-
-
-
-<p>It is common for multiple provenance records to co-exist. For instance, when emailing
- a file, there could be a provenance record kept by the mail client,
- and another by the mail server. Such provenance records may provide different explanations about something happening in the world, because they are created by different parties or observed
-by different witnesses. A given party could also create multiple provenance records about an execution, to capture different levels of details, targeted at different end-users: the
-programmer of an experiment may be interested in a detailed log of execution, while the scientists may focus more on the scientific-level description. Given that multiple provenance
-records can co-exist, it is important to know who asserted these records. </p>
-
-
-<p><em>All the rest removed</em></p>
-
+<div class='note'>
+Paolo to reinsert the common relations sections from WD3.
+</div>
</section>
-<section id="RecordContainer">
-<h4>Record Container</h4>
-
-<p>A <dfn id="dfn-RecordContainer">record container</dfn> is a house-keeping construct of PROV-DM, also capable of bundling PROV-DM <a title="record">records</a>. A record container is the
-root of a provenance record and can be exploited to package up PROV-DM <a title="record">records</a> in response to a request for the provenance of something ([[PROV-AQ]]). Given that a
-record container is the root of a provenance record, it is not defined as a PROV-DM record (production <span class="nonterminal">record</span>), since otherwise it could appear arbitrarily
-nested inside accounts.</p>
-
-
-<p>A record container, written <span class="name">container decls recs endContainer</span> in PROV-ASN, contains:
-<ul>
-<li><em>namespaceDeclarations</em>: a set <span class="name">decls</span> of namespace declarations, declaring namespaces and associated prefixes, which can be used in <a
-title="attribute">attributes</a> and <a title="identifier">identifiers</a> occurring inside <span class="name">recs</span>;</li>
-<li><em>records</em>: a non-empty set of records <span class="name">recs</span>.</li>
-</ul>
-<p>All the records in <span class="name">recs</span> are implictly wrapped in a default account, scoping all the record identifiers they declare directly, and constituting a toplevel
-account, in the hierarchy of accounts. Consequently, every provenance record is always expressed in the context of an account, either explicitly in an asserted account, or implicitly in a
-container's default account.</p>
-
-<p>In PROV-ASN, a record container's text matches the <span class="nonterminal">recordContainer</span> production of the grammar defined in this specification document.</p>
-
-
-<div class='grammar'>
-<span class="nonterminal">recordContainer</span> ::=
-<span class="name">container</span>
-<span class="nonterminal">namespaceDeclarations</span>
-<span class="plus"> <span class="nonterminal">record</span> </span>
-<span class="name">endContainer</span>
-</div>
-
-
-<div class="anexample">
-<p>
-The following container contains records related to the provenance of entity
-<span class="name">e2</span>.
-</p>
-<pre class="codeexample">
-container
- prefix ex: http://example.org/,
- entity(e2, [ prov:type="File", ex:path="/shared/crime.txt", ex:creator="Alice",
- ex:content="There was a lot of crime in London last month."])
- activity(a1, 2011-11-16T16:05:00,,[prov:type="edit"])
- wasGeneratedBy(e2, a1, [ex:fct="save"])
- wasAssociatedWith(a1, ag2, [prov:role="author"])
- agent(ag2, [ prov:type="prov:Person" %% xsd:QName, ex:name="Bob" ])
-endContainer
-</pre>
-<p>This container could for instance be returned by querying a provenance store for the provenance of entity <span class="name">e2</span> [[PROV-AQ]]. All these assertions are implicitly
-wrapped in a default account. In the absence of an explicit account, such provenance records remain unattributed.
-</p>
-</div>
-
-<div class="anexample">
-<p>
-The following container </p>
-<pre class="codeexample">
-container
- prefix ex: http://example.org/,
-
- account(ex:acc1,http://example.org/asserter1,...)
- account(ex:acc2,http://example.org/asserter1,...)
-endContainer
-</pre>
-<p> illustrates how two accounts with identifiers <span class="name">ex:acc1</span> and <span class="name">ex:acc2</span> can be returned in a PROV-ASN serialization of the provenance of
-something.
-</p>
-</div>
-
-
-<div class='issue'>
-Clarify what records are. This is <a href="http://www.w3.org/2011/prov/track/issues/208">ISSUE-208</a>. </div>
-</section>
-</section>
<section id="extensibility-section">
<h2>PROV-DM Extensibility Points</h2>
@@ -1577,11 +1488,14 @@
</div>
<ul>
-<li> Provenance of Provenance and Provenance from Multiple Perspectives/Providers
<li> Ordering Constraints
<li> Attributes, fixed values over some intervals.
+
+<li> Provenance of Provenance and Provenance from Multiple Perspectives/Providers
+
+<li>Bundles, containers</li>
</ul>