--- a/model/comments/issue-274-daniel.txt Sat Mar 03 10:07:01 2012 -0500
+++ b/model/comments/issue-274-daniel.txt Sat Mar 03 10:11:09 2012 -0500
@@ -35,7 +35,8 @@
> 2.3
> - AccountEntity? I thought it was Bundle, but ok.
-No name had been agreed.
+No name had been agreed.
+Waiting to see how discussion on account progresses.
>
> -Three types of agents are recognized by PROV-DM because they are commonly
@@ -45,9 +46,10 @@
No consensus was reached. Document mentions both
People and Human
-So need to be consistent
-TODO
+We reverted back to the previous definiitions.
+
+
>
> 2.5: there are arrows missing: Activity wasStartedBy Activity. Entity:
@@ -57,7 +59,7 @@
including not showing some edges.
With the component-based presentation, further small diagrams will be produced.
-TODO
+TODO: add a sentence saying that it is not complete coverage of the dm in diagram.
>
@@ -142,7 +144,8 @@
To represent something that happens, then one needs to use an activity, to
which one can attach duration.
-
+This could go in a best practice document, but ... nobody is taking charge
+of such a document. Would you volunteer? ;-)
> Thanks,
> Daniel
--- a/model/comments/issue-274-eric.txt Sat Mar 03 10:07:01 2012 -0500
+++ b/model/comments/issue-274-eric.txt Sat Mar 03 10:11:09 2012 -0500
@@ -19,8 +19,9 @@
> until section 5.8. While they are important perhaps could this
> section be left out of section 2?
-TODO: to consider. At this stage, I would prefer to keep them there, until
-the model is completely finalized. We could reassess then.
+This comment needs to be re-considered later. At this stage, I would
+prefer to keep these concepts there, until the model is completely
+finalized. We could reassess then.
>
> Section 3 Example
@@ -75,7 +76,7 @@
> 4.2 Activity names in the table need updating.
>
-??? which table?
+ which names in the table?
> 4.3.3.5 prov:location – Could we change the wording slightly to say
> that Location is loosely based on an ISO 19112 but can also refer to
--- a/model/comments/issue-274-jun.txt Sat Mar 03 10:07:01 2012 -0500
+++ b/model/comments/issue-274-jun.txt Sat Mar 03 10:11:09 2012 -0500
@@ -21,6 +21,8 @@
> think this is a key that should be brought in the front, and which
> should be used to structure the rest of the document. And this is not
> the case atm, IMO.
+
+Terminology does not appear in the paper any more, as agreed by WG.
>
> 2. The Overview section: I am not sure I see much difference between
> this section and the section giving definitions to the 'core'. I would
@@ -29,12 +31,20 @@
> level etc. I am sure Luc knows that the overview diagram needs update
> and I couldn't read the figure properly even printed the doc with
> high-resolution laser printer:)
+
+Components will be put in place in WD5.
+
+Note added to file.
+
>
> 3. I used the terminology of "terms" and "properties", but actually I
> don't what this data model is. What do we mean by "data model"? Is it a
> conceptual model, logical model, entity relationship model, or something
> else? It's not clearly stated and I am confused what terminologies I
> should used when referring to the model:(
+
+TODO: we need to say it's a conceptual model
+
>
> 4. The Example section: Would it be a good idea to define an example up
> in the front and use it throughout the whole document? I don't find a
@@ -42,6 +52,11 @@
> follow the 'examples' given in Section 3. And in the rest of the
> document, examples from many different scenarios are used. I wonder
> whether that prevents us from simplifying the reading of the spec.
+
+Now we have descriptions of the examples up front.
+The example is not intended to cover all concepts.
+Hence, other smaller examples appear in the various sections.
+
>
> 5. Section 4, the PROM-DM Core: There are a lot of repetition with the
> overview section. And I wonder what we mean by "core". The core almost
@@ -55,12 +70,20 @@
> (extended??), maybe the core part can be used to correspond to the
> "scruffy" part, and make it lighter, more succinct, and easier and
> quicker to grasp and follow?
+
+
+Core/common will be replaced by components in WD5.
+See above regarding scruffy.
+
>
> 6. There are many cross-references that don't quite work in the current
> working draft, like saying some terms are mentioned in the previous or
> another section. I didn't include these problems here because I think
> these were caused by the re-structuring. I could list them out once the
> structure gets more stable.
+
+We need a pass of link editing, as part of WD5.
+
>
> 7. There are also some technical points that I marked down in the
> review, which I didn't raise here either, because I am 'new' to the
--- a/model/comments/issue-274-khalid.txt Sat Mar 03 10:07:01 2012 -0500
+++ b/model/comments/issue-274-khalid.txt Sat Mar 03 10:11:09 2012 -0500
@@ -17,8 +17,10 @@
> part-1, and “extended prov-dm” for part 2, but that is not really what
> the two parts are about.
-GK also made a suggestion for part 2: prov-algebra.
-This is to be considered.
+Part 1 definitely remains prov-dm.
+
+We feel that there is no 'extended prov-dm' in part 2, but simply a set of constraints.
+So, we propose to keep it for now.
>
> - ASN is used in part-1, but not introduced. A brief definition when it
@@ -33,6 +35,7 @@
> case, provenance of entities is not the same as provenance of things.
But, this is compatible with our definition: "Entities are things in the world one wants to provide provenance for."
+
>
> - In the same section 2.1, it is said that “The definition of agent
> intentionally stays away from using concepts such as enabling, causing,
@@ -41,8 +44,10 @@
> of an activity?
Yes, but the definition of agent is independent of these terms.
-That's the key thing.
-Of course, relations will link agents in various ways.
+That's the key thing. Of course, relations will link agents in various ways.
+We have added the following sentence:
+
+ "Concepts such as initiating are themselves defined as relations between agent and activities."
>
> - The examples of generation and usage that are given in Section 2.2 are
@@ -52,7 +57,8 @@
> that at the stage it would be less confusing for the reader to simply
> know that the creation of a file is an example of generation.
-I would prefer keeping 'completed' to avoid any confusion.
+The reason for the term 'completed' has explained, by rephrasing the first paragraph of this section.
+So, we are keeping the term.
>
> - In Section 2.3, plan is used in the text without being introduced before.
@@ -64,11 +70,13 @@
> - I have the impression that the diagram presented in Section 2.5 would
> be more useful if placed at the beginning of Section 2. Also, this
> diagram was not clear, i.e., the quality of the image is bad, when I
- > printed it out on paper.
+ > printed it out on pape
+
+The diagram is probably in the right place but requires narrative to justify it.
TODO: check printed quality.
-TODO: to consider where to move it.
+
>
> - The title of Section 3.2 “The Authors View” is confusing. A reader
@@ -86,6 +94,10 @@
>
> - In the definition of Entity in Section 4.1.1: “id: an identifier
> identifying an entity” -> “id: an entity identifier”.
+
+It has become:
+ an identifier for an entity
+
>
> - In the definition of Entity in Section 4.1.1: “attributes: an Optional
> set of attribute-value pairs *representing this entity’s situation in
@@ -105,10 +117,9 @@
> moving the discussion about the above constraint, i.e., that entities
> and activities are disjoint to the constraint document.
-As a compromise, maybe keep the statement on disjointness.
-But move explanation to part II.
+As a compromise, we keep the statement on disjointness in part 1,
+but move explanation to part II.
-TODO: Paolo what do you think?
>
> - In Section 4.2.1.1 Generation, it is said that “While each of the
@@ -117,7 +128,7 @@
> encode this constraints in the serializations of prov-dm, in particular
> prov-o.
-This is a prov-o issue. Not all constraint need to be implemented in
+This is a prov-o issue. Not all constraints need to be implemented in
an ontology/schema. This applies equally to xml schema.
>
@@ -128,7 +139,7 @@
> that a given agent ag1 acts on behalf of another agent ag2 in all the
> activities that ag1 is involved in?
-TODO.
+Yes, this has now been added.
>
@@ -154,6 +165,8 @@
I don't think so, they should stay here. The examples are simple enough.
+Part II is not about new elements/relations it's about their constraints.
+
>
> - Section 4.2 Relation, I think the order in which the subsections of
> this section are presented should be re-thinked. In particular, I have
--- a/model/comments/issue-274-tim.txt Sat Mar 03 10:07:01 2012 -0500
+++ b/model/comments/issue-274-tim.txt Sat Mar 03 10:11:09 2012 -0500
@@ -110,7 +110,7 @@
>
> "Section 4 provides the definition of PROV-DM." is a bit ambiguous. Please elaborate.
-of PROV-DM constructs.
+Section 4 provides the definition of PROV-DM constructs.
>
>
@@ -129,41 +129,78 @@
>
> perhaps add the person invoking the grammar checker to the following example (to illustrate the levels of responsibility):
> "Software for checking the use of grammar in a document may be defined as an agent of a document preparation activity, and at the same time one can describe its provenance, including for instance the vendor and the version history."
+
+This is just an example for agent, we shouldn't illustrate responsibility here. This comes laters.
+
>
> add "an" to "Generation is the completed production of a new entity by activity." -> "Generation is the completed production of a new entity by an activity."
+
+done
+
>
> reads oddly: "the activity had not begun to consume or use to this entity"
+
+dropped 'to'.
+
>
>
> avoid parens in a definition: "(and could not have been affected by the entity)"
>
+
+Done
>
> avoid "internal" in collection definition "A collection is an entity that has internal structure." -> "A collection is an entity provides structure to some constituents." (or something)
+
+Yes, done.
+
>
>
> shocked by naming of "AccountEntity" why not "PlanEntity" and "CollectionEntity" (no, I don't want that...) I propose to rename "AccountEntity" to "Provenance"
+
+
+This will revisited as part of the overall discussion on accounts.
+So, for now, no action.
+
+Other option is to drop this subtype of entity. We don't need to express provenance of provenance.
+
>
>
> This sentence is long. Suggest stopping it at the first comma. "It is important to reflect that there is a degree in the responsibility of agents, and that is a major reason for distinguishing among all the agents that have some association with an activity and determine which ones are really the originators of the entity."
> ("and that is a major reason for distinguishing" -> "There is a major reason for distinguishing")
>
+
+This paragraph was edited.
+
>
> Suggest removing "active" in "indicating that the agent had an active role in the activity". Does RPI have an active role in the writing of this email (since I'm an RPI student...)? I'd say they have a role, but not an active one.
>
+
+OK, dropped.
+
>
>
> http://dvcs.w3.org/hg/prov/raw-file/default/model/working-copy/towards-wd4.html#section-UML shows Activity wasStartedBy Agent, but Luc just said in email recently that only Activity wasStartedBy Activity is the way forward. I prefer Activity wasStartedBy Agent and think that some other involvement should be named for the special informed involvement Activity ?triggered? Activity.
>
>
+
+A proposal, towards WD5, will be submitted to discussion by the WG. It will address that point.
+
>
> "ex:pub2" is a bad name - is it an activity or entity? I recommend "ex:act2"
>
+
+Done
+
>
> why aren't the edges labeled in the example?
+
+To be done, there is a note to that effect.
>
>
> avoid term "minted" when talking about choosing a URI for a Resource. "minted" is colloquial.
>
+
+OK, generated.
>
> "3.3 Attribution of Provenance" -- YES! :-)
>
@@ -171,13 +208,24 @@
> The definition of Activity "An activity is anything that can operate on entities." seems to talk about the future
>
>
+
+It's general property of definitions, they don't refer to the past explicitly. We think it's fine.
+
>
> activity(id, st, et, [ attr1=val1, ...]) does include brackets for optional constituents st and et
>
+
+This is not a grammar, so it's not appropriate to use square brackets mark the optional nature.
+The square brackets used for [ attr1=val1, ...] are part of the syntax!
+
+
>
> "(This type is equivalent to a "foaf:person" [FOAF])" --> we should not bind ourselves to FOAF:
>
>
+
+We removed references to FOAF.
+
>
>
> Please add a note to section Note to encourage people to use Account / AccountEntity/ Provenance to annotate provenance assertions as a better practice. When using AccountEntity, the annotated thing can be described _directly_ as a single triple instead of using Notes. Notes are very much "scruffy provenance" and do not benefit from the directness afforded by AccountEntity / prov:Provenance.
@@ -196,25 +244,50 @@
>
> :prov_1 a prov:Provenance; prov:wasAttributedTo :first_asserter .
> :prov_2 a prov:Provenance; prov:wasAttributedTo :trust_evaluator_agent. .
+
+See email discussion. I don't think we have reached agreement yet.
+
>
>
> I'm starting to agree that wasGeneratedBy(id,e,a,t,attrs) should become Generation(id,e,a,t,attrs)
+ >
>
- >
+
+We feel that even if the activity is not specified, there is an implied activity, so this is reasonable to keep
+the name wasGeneratedBy. Thoughts?
+
>
>
> This starts to distract, I think: "While each of the components activity, time, and attributes is optional, at least one of them must be present."
> Permitting degenerate cases should not be a priority. If not much (or nothing) is said with an assertion, let it be.
>
>
+
+It's to address ISSUE-XXX that we have introducing this statement. We don't feel it's a distraction.
+
>
>
> remove "order" from "wasGeneratedBy(e1,a1, 2001-10-26T21:32:52, [ex:port="p1", ex:order=1])" because it is distracting and encourages not using PROV for things that PROV should do.
> I think Paolo agreed to this before.
+
+
+We don't see this distracting, it's an example, a real-use case in workflow.
+What is it that is being discouraged by this example?
+
>
>
> both agents are responsible in Responsibility. Suggest to rename "responsible" to "superior" in "responsible: an identifier for the agent, on behalf of which the subordinate agent acted;" in section 4.2.3.1
>
+
+What about deputy and superior?
+
+(PS. Oxford American suggests 'second banana' ;-)
+
+
>
>
> two wasQuotedFroms in the UML diagram in section 5
+
+Should be original Source. Figure edited.
+
+
--- a/model/examples/w3c-publication1.prov-asn Sat Mar 03 10:07:01 2012 -0500
+++ b/model/examples/w3c-publication1.prov-asn Sat Mar 03 10:11:09 2012 -0500
@@ -26,21 +26,21 @@
wasDerivedFrom(tr:WD-prov-dm-20111215,tr:WD-prov-dm-20111018)
-activity(ex:pub1,,,[prov:type="publish"])
-activity(ex:pub2,,,[prov:type="publish"])
+activity(ex:act1,,,[prov:type="publish"])
+activity(ex:act2,,,[prov:type="publish"])
-wasGeneratedBy(tr:WD-prov-dm-20111018, ex:pub1)
-wasGeneratedBy(tr:WD-prov-dm-20111215, ex:pub2)
+wasGeneratedBy(tr:WD-prov-dm-20111018, ex:act1)
+wasGeneratedBy(tr:WD-prov-dm-20111215, ex:act2)
-used(ex:pub1,ar1:0004)
-used(ex:pub1,ar2:0141)
-used(ex:pub2,ar3:0111)
+used(ex:act1,ar1:0004)
+used(ex:act1,ar2:0141)
+used(ex:act2,ar3:0111)
agent(w3:Consortium, [ prov:type="Organization" ])
-wasAssociatedWith(ex:pub1, w3:Consortium @ pr:rec-advance)
-wasAssociatedWith(ex:pub2, w3:Consortium @ pr:rec-advance)
+wasAssociatedWith(ex:act1, w3:Consortium @ pr:rec-advance)
+wasAssociatedWith(ex:act2, w3:Consortium @ pr:rec-advance)
--- a/model/glossary.html Sat Mar 03 10:07:01 2012 -0500
+++ b/model/glossary.html Sat Mar 03 10:11:09 2012 -0500
@@ -18,13 +18,13 @@
</span>
<span class="glossary" id="glossary-generation">
-<dfn id="concept-generation">Generation</dfn> is the completed production of a new entity by activity.
+<dfn id="concept-generation">Generation</dfn> is the completed production of a new entity by an activity.
This entity become available for usage after this generation. This entity did not exist before generation.
</span>
<span class="glossary" id="glossary-usage">
<dfn id="concept-usage">Usage</dfn> is the beginning on an entity being consumed by an activity.
-Before usage, the activity had not begun to consume or use to this entity (and could not have been affected by the entity).
+Before usage, the activity had not begun to consume or use this entity and could not have been affected by the entity.
</span>
<span class="glossary" id="glossary-derivation">
@@ -38,7 +38,7 @@
</span>
<span class="glossary" id="glossary-collection">
-A <dfn id="concept-collection">collection</dfn> is an entity that has internal structure.
+A <dfn id="concept-collection">collection</dfn> is an entity that provides structure to some constituents, which are themselves entities.
</span>
<span class="glossary" id="glossary-accountEntity">
@@ -63,7 +63,7 @@
-->
<span class="glossary" id="glossary-activityAssociation">
-An <dfn title="concept-activityAssociation">activity association</dfn> is an assignment of responsibility to an agent for an activity, indicating that the agent had an active role in the activity. It further allows for a plan to be specified, which is the plan
+An <dfn title="concept-activityAssociation">activity association</dfn> is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan
intended by the agent to achieve some goals in the context of this activity.
</span>
--- a/model/glossary.js Sat Mar 03 10:07:01 2012 -0500
+++ b/model/glossary.js Sat Mar 03 10:11:09 2012 -0500
@@ -25,13 +25,13 @@
'</span> ' +
' ' +
'<span class="glossary" id="glossary-generation"> ' +
-'<dfn id="concept-generation">Generation</dfn> is the completed production of a new entity by activity. ' +
+'<dfn id="concept-generation">Generation</dfn> is the completed production of a new entity by an activity. ' +
' This entity become available for usage after this generation. This entity did not exist before generation. ' +
'</span> ' +
' ' +
'<span class="glossary" id="glossary-usage"> ' +
'<dfn id="concept-usage">Usage</dfn> is the beginning on an entity being consumed by an activity. ' +
-'Before usage, the activity had not begun to consume or use to this entity (and could not have been affected by the entity). ' +
+'Before usage, the activity had not begun to consume or use this entity and could not have been affected by the entity. ' +
'</span> ' +
' ' +
'<span class="glossary" id="glossary-derivation"> ' +
@@ -45,7 +45,7 @@
'</span> ' +
' ' +
'<span class="glossary" id="glossary-collection"> ' +
-'A <dfn id="concept-collection">collection</dfn> is an entity that has internal structure. ' +
+'A <dfn id="concept-collection">collection</dfn> is an entity that provides structure to some constituents, which are themselves entities. ' +
'</span> ' +
' ' +
'<span class="glossary" id="glossary-accountEntity"> ' +
@@ -70,7 +70,7 @@
'--> ' +
' ' +
'<span class="glossary" id="glossary-activityAssociation"> ' +
-'An <dfn title="concept-activityAssociation">activity association</dfn> is an assignment of responsibility to an agent for an activity, indicating that the agent had an active role in the activity. It further allows for a plan to be specified, which is the plan ' +
+'An <dfn title="concept-activityAssociation">activity association</dfn> is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan ' +
'intended by the agent to achieve some goals in the context of this activity. ' +
'</span> ' +
' ' +
--- a/model/prov-asn.html Sat Mar 03 10:07:01 2012 -0500
+++ b/model/prov-asn.html Sat Mar 03 10:11:09 2012 -0500
@@ -1,7 +1,8 @@
<!DOCTYPE html>
<html><head>
- <title>PROV-DM Part 3: PROV-ASN: The Provenance Abstract Syntax Notation</title>
+<!-- <title>PROV-DM Part 3: PROV-ASN: The Provenance Abstract Syntax Notation</title> -->
+ <title>PROV-DM Part 3: PROV-N: The Provenance Notation</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<!--
=== NOTA BENE ===
--- a/model/prov-dm-constraints.html Sat Mar 03 10:07:01 2012 -0500
+++ b/model/prov-dm-constraints.html Sat Mar 03 10:11:09 2012 -0500
@@ -611,6 +611,20 @@
For the interpretation of an activity, see <a href="#start-precedes-end">start-precedes-end</a>.
</div>
+<p>Further considerations:</p>
+<ul>
+<li>An activity is not an entity.
+Indeed, an entity exists in full at
+any point in its lifetime, persists during this
+interval, and preserves the characteristics that makes it
+identifiable. In contrast, an activity is something that happens,
+unfolds or develops through time, but is typically not identifiable by
+the characteristics it exhibits at any point during its duration.
+This distinction is similar to the distinction between
+'continuant' and 'occurrent' in logic [[Logic]].</li>
+</ul>
+
+
</section>
<section id="term-Agent">
--- a/model/prov-dm.html Sat Mar 03 10:07:01 2012 -0500
+++ b/model/prov-dm.html Sat Mar 03 10:11:09 2012 -0500
@@ -358,7 +358,7 @@
<section id='conceptualization'>
<h1>Overview</h1>
-This section provides an overview of the main elements and relations of the PROV data model.
+<p>This section provides an overview of the main concepts found in the PROV data model. </p>
@@ -400,7 +400,7 @@
<p>The motivation for introducing agents in the model is to denote the agent's responsibility for activities.
The definition of agent intentionally stays away from using concepts such as enabling, causing, initiating, affecting, etc, because many entities also enable, cause, initiate, and affect in some way
-the activities. So the notion of having some degree of responsibility is really what makes an agent.</p>
+the activities. Concepts such as initiating are themselves defined as relations between agent and activities. So the notion of having some degree of responsibility is really what makes an agent.</p>
<p>An agent is a particular type of Entity. This means that the model can be
@@ -417,7 +417,8 @@
<section id="section-generation-usage-derivation">
<h2>Generation, Usage, Derivation</h2>
-<p>Activities and entities are associated with each other in two different ways: activities are consumers of entities and activities are producers of entities. For the purpose of provenance, we define the following notions of generation and usage. </p>
+<p>Activities and entities are associated with each other in two different ways: activities are consumers of entities and activities are producers of entities. The act of producing or consuming an entity may have a duration.
+ The term 'generation' refers to the completion of the the act of producing; likewise, the term 'usage' refers to the beginning of the act of consuming entities. Thus, we define the following notions of generation and usage. </p>
<p>
<div class="glossary-ref" ref="glossary-generation">
@@ -592,8 +593,13 @@
<div class="note">
TODO: short text required to explain the overview diagram
+<p> add a sentence saying that it is not complete coverage of the dm in diagram.</p>
+<p>The text should say that we introduce a few relations based on the concepts introduced in section 2.1-2.4, that these relations are used in the example of section 3, and are fully defined in section 4-5.</p>
+<p>The note should also say why relations are in past tense (we had something in previous version of prov-dm)</p>
<p>I have the impression that the diagram presented in Section 2.5 would
> be more useful if placed at the beginning of Section 2 [KB]
+<p>There is some comments that the picture does not print well. We need to check. </p>
+<p>Add links in the svg so that we can click on the figure. </p>
</div>
@@ -641,14 +647,14 @@
<ul>
<li> Two versions of the technical report are involved: <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft);</li>
<li> Both <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> were published by the WWW Consortium agent (<span class="name"><a href="http://www.w3.org/Consortium">w3:Consortium</a></span>); </li>
-<li> The publication activity for <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> is <span class="name">ex:pub2</span>;</li>
-<li> The publication activity for <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> is <span class="name">ex:pub1</span>;
+<li> The publication activity for <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> is <span class="name">ex:act2</span>;</li>
+<li> The publication activity for <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> is <span class="name">ex:act1</span>;
</li>
<li> The report <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> is derived from <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span>;</li>
-<li> The publication activity <span class="name">ex:pub1</span> used a <a href="http://www.w3.org/2005/08/01-transitions.html#pubreq">publication request</a> (<span class="name"><a href="https://lists.w3.org/Archives/Member/w3c-archive/2011Oct/0141">ar2:0141</a></span>) and a <a href="http://www.w3.org/2005/08/01-transitions.html#transreq">transition request</a> (<span class="name"><a href="https://lists.w3.org/Archives/Member/chairs/2011OctDec/0004">ar1:0004</a></span>);</li>
-<li> The publication activity <span class="name">ex:pub1</span> used a <a href="http://www.w3.org/2005/08/01-transitions.html#pubreq">publication request</a> (<span class="name"><a href="https://lists.w3.org/Archives/Member/w3c-archive/2011Dec/0111">ar3:0111</a></span>);</li>
+<li> The publication activity <span class="name">ex:act1</span> used a <a href="http://www.w3.org/2005/08/01-transitions.html#pubreq">publication request</a> (<span class="name"><a href="https://lists.w3.org/Archives/Member/w3c-archive/2011Oct/0141">ar2:0141</a></span>) and a <a href="http://www.w3.org/2005/08/01-transitions.html#transreq">transition request</a> (<span class="name"><a href="https://lists.w3.org/Archives/Member/chairs/2011OctDec/0004">ar1:0004</a></span>);</li>
+<li> The publication activity <span class="name">ex:act1</span> used a <a href="http://www.w3.org/2005/08/01-transitions.html#pubreq">publication request</a> (<span class="name"><a href="https://lists.w3.org/Archives/Member/w3c-archive/2011Dec/0111">ar3:0111</a></span>);</li>
<li> Technical reports were published according to the process rules (<span class="name"><a href="http://www.w3.org/2005/10/Process-20051014/tr.html#rec-advance">pr:rec-advance</a></span>), a plan in PROV-DM terminology.</li>
</ul>
@@ -663,13 +669,13 @@
</li>
<li>There is a publication activity.
<pre>
-activity(ex:pub2,,,[prov:type="publish"])
+activity(ex:act2,,,[prov:type="publish"])
</pre>
</li>
<li>The technical report was generated by the publication activity: this is a <a title="concept-Generation">Generation</a>.
<pre>
-wasGeneratedBy(tr:WD-prov-dm-20111215, ex:pub2)
+wasGeneratedBy(tr:WD-prov-dm-20111215, ex:act2)
</pre>
</li>
@@ -682,13 +688,13 @@
<li>The activity required a publication request: this is a <a title="concept-Usage">Usage</a>.
<pre>
-used(ex:pub2,ar3:0111)
+used(ex:act2,ar3:0111)
</pre>
</li>
<li>The activity was associated with the Consortium agent, and proceeded according to its publication policy: this is an <a title="concept-activityAssociation">Activity Association</a>.
<pre>
-wasAssociatedWith(ex:pub2, w3:Consortium @ pr:rec-advance)
+wasAssociatedWith(ex:act2, w3:Consortium @ pr:rec-advance)
</pre>
</li>
</ul>
@@ -721,7 +727,7 @@
</div>
-<p> This simple example has shown a variety of PROV-DM constructs, such as Entity, Agent, Activity, Usage, Generation, Derivation, and ActivityAssociation. In this example, it happens that all entities were already Web resources, with readily available URIs, which we used. We note that some of the resources are public, whereas others have restricted access: provenance statements only make use of their identifiers. If identifiers do not pre-exist, e.g. for activities, then they can be minted, for instance <span class="name">ex:pub2</span>, occurring in the namespace identified by prefix <span class="name">ex</span>. We note that the URI scheme developed by W3C is particularly suited for expressing provenance of these reports, since each URI denotes a specific version of a report. It then becomes very easy to relate the various versions, with PROV-DM constructs. </p>
+<p> This simple example has shown a variety of PROV-DM constructs, such as Entity, Agent, Activity, Usage, Generation, Derivation, and ActivityAssociation. In this example, it happens that all entities were already Web resources, with readily available URIs, which we used. We note that some of the resources are public, whereas others have restricted access: provenance statements only make use of their identifiers. If identifiers do not pre-exist, e.g. for activities, then they can be generated, for instance <span class="name">ex:act2</span>, occurring in the namespace identified by prefix <span class="name">ex</span>. We note that the URI scheme developed by W3C is particularly suited for expressing provenance of these reports, since each URI denotes a specific version of a report. It then becomes very easy to relate the various versions, with PROV-DM constructs. </p>
</section>
@@ -774,8 +780,8 @@
<li>There are some agents.
<pre>
-agent(ex:Paolo, [ prov:type="Human" ])
-agent(ex:Simon, [ prov:type="Human" ])
+agent(ex:Paolo, [ prov:type="Person" ])
+agent(ex:Simon, [ prov:type="Person" ])
</pre>
</li>
@@ -850,7 +856,7 @@
<p><div class="attributes" id="attributes-entity">An entity<span class="withAsn">, written <span class="name">entity(id, [ attr1=val1, ...])</span> in PROV-ASN, </span> contains:</p>
<ul>
-<li><span class='attribute'>id</span>: an identifier identifying an entity; </li>
+<li><span class='attribute'>id</span>: an identifier for an entity; </li>
<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs representing this entity's situation in the world.</li>
</ul></div>
@@ -874,7 +880,7 @@
<p>Further considerations:</p>
<ul>
-<li>The sets of Activities and Entities are disjoint, as explained below.</li>
+<li>The sets of Activities and Entities are disjoint, as described below.</li>
</ul>
@@ -902,7 +908,7 @@
<p><div class="attributes" id="attributes-activity"> An activity<span class="withAsn">, written <span class="name">activity(id, st, et, [ attr1=val1, ...])</span> in PROV-ASN,</span> contains:</p>
<ul>
-<li><span class='attribute'>id</span>: an identifier identifying an activity;</li>
+<li><span class='attribute'>id</span>: an identifier for an activity;</li>
<li><span class='attribute'>startTime</span>: an OPTIONAL time for the start of the activity;</li>
<li><span class='attribute'>endTime</span>: an OPTIONAL time for the end of the activity;</li>
<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs for this activity.</li>
@@ -924,15 +930,9 @@
<p>Further considerations:</p>
<ul>
-<li>An activity is not an entity.
-Indeed, an entity exists in full at
-any point in its lifetime, persists during this
-interval, and preserves the characteristics that makes it
-identifiable. In contrast, an activity is something that happens,
-unfolds or develops through time, but is typically not identifiable by
-the characteristics it exhibits at any point during its duration.
-This distinction is similar to the distinction between
-'continuant' and 'occurrent' in logic [[Logic]].</li>
+<li>An activity is not an entity. This distinction is similar to the distinction between
+'continuant' and 'occurrent' in logic [[Logic]].
+</li>
</ul>
@@ -946,7 +946,7 @@
<p><div class="attributes" id="attributes-agent">An agent<span class="withAsn">, noted <span class="name">agent(id, [ attr1=val1, ...])</span> in PROV-ASN,</span> contains:</p>
<ul>
-<li><span class='attribute'>id</span>: an identifier identifying an agent;</li>
+<li><span class='attribute'>id</span>: an identifier for an agent;</li>
<li><span class='attribute'>attributes</span>: a set of attribute-value pairs representing this agent's situation in the world.
</li>
</ul></div>
@@ -958,10 +958,9 @@
There should be very few of these basic categories to keep the model simple and accessible.
There are three types of agents in the model since they are common across most anticipated domains of use:
<ul>
-<li><span class="name">Human</span>: agents of type Human are people. (This type is equivalent to a "foaf:person" [[FOAF]])</li>
-<li><span class="name">Organization</span>: agents of type Organization are social institutions such as companies, societies etc. (This type is equivalent to a "foaf:organization"
-[[FOAF]])</li>
-<li><span class="name">ComputingSystem</span>: a computing system agent is a piece of software and/or hardware. </li>
+<li><span class="name">Person</span>: agents of type Person are people.</li>
+<li><span class="name">Organization</span>: agents of type Organization are social institutions such as companies, societies etc.</li>
+<li><span class="name">SoftwareAgent</span>: a software agent is a piece of software. </li>
</ul>
<p>These types are mutually exclusive, though they do not cover all kinds of agent. </p>
@@ -970,7 +969,7 @@
<div class="anexample">
<p>The following expression is about an agent identified by <span class="name">e1</span>, which is a person, named Alice, with employee number 1234.</p>
<pre class="codeexample">
-agent(e1, [ex:employee="1234", ex:name="Alice", prov:type="prov:Human" %% xsd:QName])
+agent(e1, [ex:employee="1234", ex:name="Alice", prov:type="prov:Person" %% xsd:QName])
</pre>
<p>It is optional to specify the type of an agent. When present, it is expressed using the <span class="name">prov:type</span> attribute.</p>
</div>
@@ -990,7 +989,7 @@
<p><div class="attributes" id="attributes-note">A <dfn title="dfn-note">note</dfn><span class="withAsn">, noted <span class="name">note(id, [ attr1=val1, ...])</span> in PROV-ASN,</span> contains:</p>
<ul>
-<li><span class='attribute'>id</span>: an identifier identifying the note;</li>
+<li><span class='attribute'>id</span>: an identifier for a note;</li>
<li><span class='attribute'>attributes</span>: a set of attribute-value pairs, whose meaning is application specific.</li>
</ul></div>
@@ -1066,9 +1065,9 @@
<p>
<div class="attributes" id="attributes-generation"><dfn title="dfn-Generation">Generation</dfn><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><span class='attribute'>id</span>: an OPTIONAL identifier identifying a generation;</li>
-<li><span class='attribute'>entity</span>: an identifier identifying a created entity; </li>
-<li><span class='attribute'>activity</span>: an OPTIONAL identifier identifying the activity that creates the entity;</li>
+<li><span class='attribute'>id</span>: an OPTIONAL identifier for a generation;</li>
+<li><span class='attribute'>entity</span>: an identifier for a created entity; </li>
+<li><span class='attribute'>activity</span>: an OPTIONAL identifier for the activity that creates the entity;</li>
<li><span class='attribute'>time</span>: an OPTIONAL "generation time", the time at which the entity was completely created;</li>
@@ -1116,7 +1115,7 @@
<p><div class="attributes" id="attributes-usage"><dfn title="dfn-Usage">Usage</dfn><span class="withAsn">, written <span class="name">used(id,a,e,t,attrs)</span> in PROV-ASN,</span> has the following constituents:</p>
<ul>
-<li><span class='attribute'>id</span>: an OPTIONAL identifier identifying a usage;</li>
+<li><span class='attribute'>id</span>: an OPTIONAL identifier for a usage;</li>
<li><span class='attribute'>activity</span>: an identifier for the consuming activity;</li>
<li><span class='attribute'>entity</span>: an identifier for the consumed entity;</li>
<li><span class='attribute'>time</span>: an OPTIONAL "usage time", the time at which the entity started to be used;</li>
@@ -1220,16 +1219,16 @@
<p>An activity start<span class="withAsn">, written <span class="name">wasStartedBy(id,a,ag,attrs)</span> in PROV-ASN,</span> contains:</p>
<ul>
-<li><span class='attribute'>id</span>: an OPTIONAL identifier identifying the activity start;</li>
-<li><span class='attribute'>activity</span>: an identifier identifying the started activity;
+<li><span class='attribute'>id</span>: an OPTIONAL identifier for the activity start;</li>
+<li><span class='attribute'>activity</span>: an identifier for the started activity;
<li><span class='attribute'>agent</span>: an identifier for the agent starting the activity;
<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs describing modalities according to which the agent started the activity.
</ul>
<p>An activity end<span class="withAsn">, written <span class="name">wasEndedBy(id,a,ag,attrs)</span> in PROV-ASN,</span> contains:</p>
<ul>
-<li><span class='attribute'>id</span>: an OPTIONAL identifier identifying the activity end;</li>
-<li><span class='attribute'>activity</span>: an identifier identifying the ended activity;
+<li><span class='attribute'>id</span>: an OPTIONAL identifier for the activity end;</li>
+<li><span class='attribute'>activity</span>: an identifier for the ended activity;
<li><span class='attribute'>agent</span>: an identifier for the agent ending the activity;
<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs describing modalities according to which the agent ended the activity.
</ul>
@@ -1294,7 +1293,7 @@
<p><div class="attributes" id="attributes-responsibility-chain">A <dfn title="dfn-responsibility-chain">responsibility chain</dfn><span class="withAsn">, written <span class="name">actedOnBehalfOf(id,ag2,ag1,a,attrs)</span> in PROV-ASN,</span> has the following constituents:</p>
<ul>
-<li><span class='attribute'>id</span>: an OPTIONAL identifier identifying the responsibility chain;</li>
+<li><span class='attribute'>id</span>: an OPTIONAL identifier for the responsibility chain;</li>
<li><span class='attribute'>subordinate</span>: an identifier for the agent associated with an activity, acting on behalf of the responsible
agent;</li>
<li><span class='attribute'>responsible</span>: an identifier for the agent, on behalf of which the subordinate agent acted;</li>
@@ -1319,7 +1318,12 @@
</pre>
</div>
-
+<p>Further considerations:</p>
+<ul>
+<li>If an activity is not specified, then the subordinate agent is considered to act on behalf of
+the responsible agent, in all the activities the subordinate agent is associated with.
+</li>
+</ul>
</section>
<section id="Derivation-Relation">
@@ -1678,7 +1682,7 @@
<div class="anexample">
<p>The following describes an agent of type software agent.</p>
<pre class="codeexample">
- agent(ag, [prov:type="prov:ComputingSystem" %% xsd:QName])
+ agent(ag, [prov:type="prov:SoftwareAgent" %% xsd:QName])
</pre>
</div>
</section>
@@ -1714,7 +1718,7 @@
<section id="term-attribute-location">
<h4>prov:location</h4>
-<p>A <dfn title="dfn-Location">location</dfn> can be not only an identifiable geographic place (ISO 19112), but it can also be a non-geographic place such as a directory, row, or column. As such, there are numerous ways in which location can be expressed, such as by a coordinate,
+<p>A <dfn title="dfn-Location">location</dfn> can be an identifiable geographic place (ISO 19112), but it can also be a non-geographic place such as a directory, row, or column. As such, there are numerous ways in which location can be expressed, such as by a coordinate,
address, landmark, and so forth. This document does not specify how to concretely express locations, but instead provide a mechanism to introduce locations, by means of attributes. </p>
@@ -1875,8 +1879,8 @@
Revisiting the example of <a href="#section-example-b">Section 3.2</a>,
we can ascribe <span class="name">tr:WD-prov-dm-20111215</span> to some agents without having to make an activity explicit.
<pre class="codeexample">
-agent(ex:Paolo, [ prov:type="Human" ])
-agent(ex:Simon, [ prov:type="Human" ])
+agent(ex:Paolo, [ prov:type="Person" ])
+agent(ex:Simon, [ prov:type="Person" ])
entity(tr:WD-prov-dm-20111215, [ prov:type="pr:RecsWD" %% xsd:QName ])
wasAttributedTo(tr:WD-prov-dm-20111215, ex:Paolo, [prov:role="editor"])
wasAttributedTo(tr:WD-prov-dm-20111215, ex:Simon, [prov:role="contributor"])