--- a/model/comments/issue-331-Cheney.txt Mon Apr 16 01:00:56 2012 +0100
+++ b/model/comments/issue-331-Cheney.txt Mon Apr 16 07:47:36 2012 +0100
@@ -13,12 +13,15 @@
> perhaps, simply drop section 2 and proceed to the specification.
-We have some suggestions
+We received suggestions
- to move prov-n section earlier (james)
- to move it later (gk)
- that the structure is right.
-It feels to me it's right!
+It feels that it's about right!
+
+Examples can optionally be hidden. There is now just one page of concept
+definitions, before getting to the class diagram.
>
@@ -27,6 +30,9 @@
> the WG's own activities sound a little self-centered.
The point was to have a *real* example with real urls.
+Furthermore, nothing in the provenance descriptions is really specific
+to the prov-wg, in the sense that all Recs go through the same kind
+of transition.
>
> Given that both the primer and ontology use extended examples, why not
@@ -34,7 +40,6 @@
As a WG, I would hope we can come up with more than one examples.
-
>
> * I feel that the document doesn't lay things out in a logical order.
> I think it would be helpful to list the basic or standard
@@ -50,7 +55,7 @@
I think it's more important to explain the various concepts first, before
some of the building blocks, e.g. namespace, identifiers, attributes.
-suggestion: one could add forwarding links for prov:type, etc
+Added forwarding links for prov:type in entity/activity examples.
>
> * PLEASE say somewhere prominently what the convention(s) are for
@@ -59,7 +64,7 @@
> Please make sure that all of the examples make sense with respect to
> whichever convention is in use.
-Need to revisit 2.6.
+Updated section 2.6 clarifying some of these issues.
>
> * Reading the document, I wondered why generation and use have time
@@ -68,8 +73,7 @@
> interval? We should say why we only care about the end of
> generation and beginning of use.
-
-We had a vote on this. I can't find it.
+We had voted definitions for generation/usage. I am just reusing them.
>
> * There are a LOT of parenthetical examples, which I think stand
@@ -85,7 +89,8 @@
>
> Why "people" and not "agents"?
-Same as Curt.
+Same commennt as Curt. I think it's important to talk about people
+here. Our agents only mean "bearer of responsibility".
>
> Why do we say that the various aspects of the standards are necessary,
@@ -95,17 +100,29 @@
> "extra-descriptions" -> "extra descriptions"
> "interval " -> "intervals"
>
+
+Done
+
> Section 4 provides the *definitions* of PROV-DM concepts, structured
> according to six components.
>
+
+Done.
+
>
> 2.2: "A same entity" -> "The same entity" - this happens many times
+
+Fixed it twice.
+
>
> 2.6. The activity in the example has the wrong number of arguments
> (the times are omitted, but I believe should be replaced with "-").
> Also, the convention about missing arguments being written "-" is very
> important and should be explained somewhere prominently, with
> examples. This happens many more times.
+
+Updated section 2.6.
+
>
> 3.1. "(some of which *locate* archived email messages, available to W3C Members)."
@@ -115,38 +132,52 @@
> 4.1.2. The reserved attribute "type" is mentioned here. Where is hte
> list of all reserved attributes? Why not list them up front as part
> of the preliminaries?
+
+In section 4, for the first occurrences of prov:type and prov:role, I have
+added link to their respective sections.
+
>
> 4.1.3. The first example in Generation: p1 and p2 should be in code font.
+
+Done
>
> 4.2.3. The missing id arguments to wasAssociatedWith in the examples
> are not marked as "-". Happens again in 4.2.4, 4.1.5, 4.1.6, etc.
> Also, many missing attribute lists are omitted without being replaced
> by "-". This is a sensible convention but is not stated anywhere.
-Revisit bullet 3 in section 2.6.
+Updated bullet 3 in section 2.6.
>
> 4.2.4. The examples discussed in the second paragraph are not
> mentioned anywhere else. So say "For example" instead of "In the
> example".
+
+Yes.
>
> 4.2.4. Here and elsewhere, the term "modalities of ..." is used to
> describe what the attributes are for.
-To replace according to GK's suggestion
+Replaced everywhere according to GK's suggestion
>
> 4.2.4. "a funder agents" - case mismatch
+
+Repharsed:
+
+"The following fragment describes three agents: a programmer, a researcher, and a funder."
>
> 4.3.1 " And to provide a completely accurate description of the
> derivation" -> "To provide a more accurate ..."
>
> 4.6. "extra-information" -> "extra information"
>
+Done
+
> 4.6. Concerning annotations, why would I want to do this instead of
> directly putting the x and y positions on the entity?
-Different moments.
+The assertions of entity and note occur at moments.
>
>
@@ -155,6 +186,7 @@
> multiple occurrences of attribute names, why stop with these two?
>
+TODO
We could allow this for prov:label and prov:location too.
Does this make sense for prov:location?
@@ -163,4 +195,4 @@
>
>
-Yes, to fix.
+Yes
--- a/model/comments/issue-331-Jun.txt Mon Apr 16 01:00:56 2012 +0100
+++ b/model/comments/issue-331-Jun.txt Mon Apr 16 07:47:36 2012 +0100
@@ -95,9 +95,9 @@
>
>
-TODO: add glossary definitions (for section 4).
+Added glossary definitions to section 4.2.1.
-Removed the three types of agents from section 2.3.
+Note: I removed the three types of agents from section 2.3.
>
@@ -150,8 +150,9 @@
> the readers, emphasizing provenance as descriptions of a past event.
>
-It's true that tense is not consistently used.
-TODO: when reorganizing example, adjust tense.
+It's true that tense was not consistently used.
+Fixed, hopefully, now, all in past tense.
+
>
>
--- a/model/comments/issue-331-Khalid.txt Mon Apr 16 01:00:56 2012 +0100
+++ b/model/comments/issue-331-Khalid.txt Mon Apr 16 07:47:36 2012 +0100
@@ -54,6 +54,10 @@
> specify whether they represent the first or the second working draft,
> whenever they are used in the text. - The figure given at the end of
> Sectio 3.1 can be more helpful in guiding the reader if it placed
+
+TODO
+
+
> earlier in that section. - Talkiing about the figure the fact there
> are two arrows that link an arrow to a class, I understand their
> meaning, by I am not sure the reader will. - Section 3.2 giving
@@ -66,8 +70,8 @@
> provenance from the process point of view.
>
-TODO:
-We could start with the author view.
+
+Done: we now start with the author view.
> - 4: PROV-DM Types and Relations I am not sure the notion of component
@@ -90,7 +94,7 @@
It's useful to have groupings of concepts, to give some structure to the dm.
The term component is reasonable for this.
-TODO: consider changing headings of components.
+
>
> - One of the consequence of trying to structure the model into
--- a/model/comments/issue-331-Tim.txt Mon Apr 16 01:00:56 2012 +0100
+++ b/model/comments/issue-331-Tim.txt Mon Apr 16 07:47:36 2012 +0100
@@ -260,7 +260,8 @@
> This could help readability.
Yes, this was suggested by Khalid.
-TODO
+Done.
+
>
> 20)
> Before section 4, the distinction between concepts and types/relations was made (to the extend of showing their mapping).
@@ -691,8 +692,7 @@
> Though, I may just be confused on this (qualified vs. unqualified). Perhaps disregard this comment.
>
-Currently no action.
-TODO: shall we rename?
+Yes, derivation-by-removal and derivation-by-insertion are now just removal and insertion, respectively.
>
>
>
--- a/model/comments/issue-331-curt.txt Mon Apr 16 01:00:56 2012 +0100
+++ b/model/comments/issue-331-curt.txt Mon Apr 16 07:47:36 2012 +0100
@@ -6,7 +6,7 @@
> optional arguments where the argument mapping is unambiguous,
> particularly at the beginning or end of the argument list.
-TODO. Need to check and better explain the convention.
+Updated Section 2.6.
>
>
@@ -191,7 +191,7 @@
Was dropped from section 2.
-TODO: add these definitions, in bold, in section 4.
+These definitions, in bold, now appear in section 4.2.1.
>
> ...member of the collections.
@@ -220,6 +220,7 @@
>
TODO.
+
>
> 2.5 Simplified Overview Diagram
> -------------------------------
--- a/model/comments/issue-331-graham.txt Mon Apr 16 01:00:56 2012 +0100
+++ b/model/comments/issue-331-graham.txt Mon Apr 16 07:47:36 2012 +0100
@@ -188,7 +188,7 @@
> allows certain inferences to be drawn if the supplied provenance satisfies
> certain strictness criteria (constraints).
-Nothing todo.
+Nothing TODO.
>
> == 1.2 PROV namespace ==
@@ -460,8 +460,7 @@
> "id: an identifier for an entity;" - this is redundant and potentially
> confusing. Suggest "id: an identifier".
-TODO
-?????????
+TODO: ?????????, no action
>
> "attributes: an optional set of attribute-value pairs ((attr1, val1), ...)
@@ -615,8 +614,8 @@
> to ignore this and just use extensibility options in the representation
> substrate (e.g. RDF) used.
-TODO:
-Probably needs some updating.
+Section was updated.
+TODO: do we need more?
>
--- a/model/extra.css Mon Apr 16 01:00:56 2012 +0100
+++ b/model/extra.css Mon Apr 16 07:47:36 2012 +0100
@@ -282,6 +282,23 @@
background-color: #f9f9f9;
}
+.conceptexample:before {
+ content: "Example:";
+ font-family: sans-serif;
+ font-size: 1.6ex;
+ font-weight: bold;
+}
+.conceptexample {
+ margin-top: 1ex;
+ margin-bottom: 1ex;
+ padding-left: 1ex;
+ padding-right: 1ex;
+ padding-top: 1ex;
+ padding-bottom: 0.6ex;
+ border: 1px dashed #2f6fab;
+ background-color: #f9f9f9;
+}
+
.pnExpression {
font-weight: normal;
font-size:120%;
--- a/model/glossary.html Mon Apr 16 01:00:56 2012 +0100
+++ b/model/glossary.html Mon Apr 16 07:47:36 2012 +0100
@@ -39,6 +39,10 @@
A <dfn id="concept-collection">collection</dfn> is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be <dfn>member of</dfn> the collections.
</span>
+<span class="glossary" id="glossary-empty-collection">
+An <dfn id="concept-empty-collection">empty collection</dfn> is a collection without member.
+</span>
+
<span class="glossary" id="glossary-account">
An <dfn id="concept-account">account</dfn> is an entity that contains a bundle of provenance descriptions.
</span>
@@ -173,3 +177,16 @@
</span>
+
+<span class="glossary" id="glossary-person">
+Agents of type <dfn id="concept-person" title="person">Person</dfn> are people.
+</span>
+
+<span class="glossary" id="glossary-software-agent">
+A <dfn id="concept-software-agent" title="software-agent">software agent</dfn> is running software.
+</span>
+
+
+<span class="glossary" id="glossary-organization">
+Agents of type <dfn id="concept-organization" title="organization">Organization</dfn> are social or legal institutions such as companies, societies, etc.
+</span>
--- a/model/glossary.js Mon Apr 16 01:00:56 2012 +0100
+++ b/model/glossary.js Mon Apr 16 07:47:36 2012 +0100
@@ -3,7 +3,7 @@
// with <script src="glossary.js" class="remove"></script>
//Insert glossary definitions with the following
// <div class="glossary-ref" ref="glossary-generation"></div>
-glossary_hg='http://dvcs.w3.org/hg/prov/file/ac1c7030a736/model/glossary.html';
+glossary_hg='http://dvcs.w3.org/hg/prov/file/31816209cab0/model/glossary.html';
glossary_string=
' ' +
'<html> ' +
@@ -46,6 +46,10 @@
'A <dfn id="concept-collection">collection</dfn> is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be <dfn>member of</dfn> the collections. ' +
'</span> ' +
' ' +
+'<span class="glossary" id="glossary-empty-collection"> ' +
+'An <dfn id="concept-empty-collection">empty collection</dfn> is a collection without member. ' +
+'</span> ' +
+' ' +
'<span class="glossary" id="glossary-account"> ' +
'An <dfn id="concept-account">account</dfn> is an entity that contains a bundle of provenance descriptions. ' +
'</span> ' +
@@ -180,4 +184,17 @@
'</span> ' +
' ' +
' ' +
+' ' +
+'<span class="glossary" id="glossary-person"> ' +
+'Agents of type <dfn id="concept-person" title="person">Person</dfn> are people. ' +
+'</span> ' +
+' ' +
+'<span class="glossary" id="glossary-software-agent"> ' +
+'A <dfn id="concept-software-agent" title="software-agent">software agent</dfn> is running software. ' +
+'</span> ' +
+' ' +
+' ' +
+'<span class="glossary" id="glossary-organization"> ' +
+'Agents of type <dfn id="concept-organization" title="organization">Organization</dfn> are social or legal institutions such as companies, societies, etc. ' +
+'</span> ' +
' ' ;
--- a/model/prov-dm.html Mon Apr 16 01:00:56 2012 +0100
+++ b/model/prov-dm.html Mon Apr 16 07:47:36 2012 +0100
@@ -352,7 +352,7 @@
<p><a href="#prov-dm-example">Section 3</a> illustrates how PROV-DM can be used
to express the provenance of a report published on the Web.</p>
-<p><a href="#data-model-components">Section 4</a> provides the definition of PROV-DM concepts, structured according to six components.</p>
+<p><a href="#data-model-components">Section 4</a> provides the definitions of PROV-DM concepts, structured according to six components.</p>
<p><a href="#extensibility-section">Section 5</a> summarizes PROV-DM extensibility points.</p>
@@ -405,6 +405,16 @@
written down.
</p>
+<form action="#"><p>
+<input id="hide-examples" onclick="set_display_by_class('div','conceptexample','none'); set_display_by_id('hide-examples','none'); set_display_by_id('show-examples','');" type="button"
+value="Hide Concept Examples" />
+<input id="show-examples" onclick="set_display_by_class('div','conceptexample',''); set_display_by_id('hide-examples',''); set_display_by_id('show-examples','none');" style="display: none"
+type="button" value="Show Concept Examples" />
+</p>
+</form>
+</div>
+
+
<section id='section-entity-activity'>
@@ -420,7 +430,7 @@
-<div class="anexample" id="entity-example">
+<div class="conceptexample" id="entity-example">
<p>An entity may be the document at URI <a href="http://www.bbc.co.uk/news/science-environment-17526723">http://www.bbc.co.uk/news/science-environment-17526723</a>, a file in a file system, a car, or an idea.</p>
</div>
@@ -432,7 +442,7 @@
-<div class="anexample" id="activity-example">
+<div class="conceptexample" id="activity-example">
<p>An activity may be the publishing of a document on the Web, sending a twitter message, extracting metadata embedded in a file, driving a car from Boston to Cambridge, assembling a data set based on a set of measurements, performing a statistical analysis over a data set, sorting news items according to some criteria, running a SPARQL query over a triple store, or editing a file.</p>
</div>
@@ -456,7 +466,7 @@
-<div class="anexample" id="generation-example">
+<div class="conceptexample" id="generation-example">
<p>Examples of generation are the completed creation of a file by a
program, the completed creation of a linked data set, and the completed
publication of a new version of a document.
@@ -464,21 +474,21 @@
-<div class="anexample" id="usage-example">
+<div class="conceptexample" id="usage-example">
<p>Usage examples include a procedure beginning to consume an argument, a service starting to read a value on a port, a program beginning to read a configuration
file, or the point at which an ingredient, such as eggs, is being added in a baking activity. Usage may entirely consume an entity (e.g. eggs are no longer available after being added to
-the mix); alternatively, a same entity may be used multiple times, possibly by different activities (e.g. a file on a file system can be read indefinitely).
+the mix); alternatively, the same entity may be used multiple times, possibly by different activities (e.g. a file on a file system can be read indefinitely).
</div>
-<p>Activities are utilize entities and are producers of entities. In some cases, utilizing an entity influences the creation of another in some way. This notion is captured by derivations, defined as follows.</p>
+<p>Activities utilize entities and producer entities. In some cases, utilizing an entity influences the creation of another in some way. This notion is captured by derivations, defined as follows.</p>
<p>
<span class="glossary-ref" data-ref="glossary-derivation" data-withspan="true"></span>
-<div class="anexample" id="derivation-example">
+<div class="conceptexample" id="derivation-example">
<p>Examples of derivation include the transformation of a relational table into a
linked data set, the transformation of a canvas into a painting, the transportation of a work of art from London to New York, and a physical transformation such as the melting of ice into water.</p>
</div>
@@ -504,7 +514,7 @@
-<div class="anexample" id="agent-example">
+<div class="conceptexample" id="agent-example">
<p>
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.
A site selling books on the Web, the services involved in the processing of orders, and the companies hosting them are also agents.
@@ -525,7 +535,7 @@
validate the execution as represented in the provenance record, to
manage expectation failures, or to provide explanations.</p>
-<div class="anexample" id="plan-example">
+<div class="conceptexample" id="plan-example">
<p>
A plan can be a blog post tutorial for how to set up a web server, a list of instructions for a micro-processor execution, a cook's written recipe for a chocolate cake, or a workflow for a scientific experiment.
</p>
@@ -540,7 +550,7 @@
<div class="glossary-ref" data-ref="glossary-attribution" data-withspan="true"></div>
-<div class="anexample" id="association-example">
+<div class="conceptexample" id="association-example">
<p>A blog post can be attributed to an author, a mobile phone to its manufacturer.</p>
</div>
@@ -557,7 +567,7 @@
<span class="glossary-ref" data-ref="glossary-activityAssociation" data-withspan="true"></span>
</p>
-<div class="anexample" id="association-example2">
+<div class="conceptexample" id="association-example2">
<p>Examples of association between an activity and an agent are:
<ul>
<li>creation of a web page under the guidance of a designer;</li>
@@ -581,7 +591,7 @@
-<div class="anexample" id="responsibilityChain-example">
+<div class="conceptexample" id="responsibilityChain-example">
<p>A student publishing a web page describing an academic
department could result in both the student and the department being
agents associated with the activity, and it may not matter which
@@ -599,7 +609,7 @@
<p>
<span class="glossary-ref" data-ref="glossary-collection" data-withspan="true"></span> This concept allows for the provenance of the collection itself to be expressed in addition to that of the members. Such a notion of collection corresponds to a wide variety of concrete data structures, such as a <em>maps</em>, <em>dictionaries</em>, or <em>associative arrays</em>.</p>
-<div class="anexample" id="collection-example">
+<div class="conceptexample" id="collection-example">
<p>
An example of collection is an archive of documents. Each document has its own provenance, but the archive itself also has some provenance: who maintained it, which documents it contained at which point in time, how it was assembled, etc.
</div>
@@ -610,7 +620,7 @@
<span class="glossary-ref" data-ref="glossary-account" data-withspan="true">
</span>Making an account an entity allows for provenance of provenance to be expressed.
-<div class="anexample" id="account-example">
+<div class="conceptexample" id="account-example">
<p>
For users to decide whether they can place their trust in
a resource, they may want to analyze the resource's provenance, but also determine
@@ -691,12 +701,14 @@
<li>The interpretation of PROV-N arguments is defined according to their <em>position</em> in the list of arguments. This convention allows for a compact notation. </li>
<li>
-PROV-N <em>optional arguments</em> need not be specified. For cases where it is desirable to indicate which arguments have not been specified, PROV-N uses the <em>syntactic marker</em> <span class="name">-</span> for unspecified arguments.
+PROV-N <em>optional arguments</em> need not be specified:
+the general rule for optional arguments is that, if none of them are used in the expression, then they are simply omitted, resulting in a simpler expression. However, it may be the case that only some of the optional arguments need to be specified. Because the position of the arguments in the expression matters, in this case an additional marker must be used to indicate that a particular term is not available. The syntactic marker <span class="name">-</span> is used for this purpose.
</li>
<li>Most expressions
-have an identifier in the <em>first position</em>,
-and an optional set of attribute-value pairs in the <em>last position</em>, delimited by square brackets.
+include an identifier
+and a set of attribute-value pairs; both are optional unless otherwise specified. By convention, the identifier occurs in the <em>first position</em>, and the the set of attribute-value pairs in the <em>last position</em>.
+Consistent with the convention on arguments, the marker <span class="name">-</span> can be used when the identifier is not available, or can be omitted altogether with no ambiguity arising.
</li>
</ul>
@@ -716,6 +728,11 @@
used(a1,e1)
wasGeneratedBy(e2,a1)
</pre>
+The same description, but with an explicit identifier <span class="name">u1</span> for the usage, and the syntactic marker <span class="name">-</span> to mark the absence of identifier in the generation.
+<pre class="codeexample" >
+used(u1,a1,e1)
+wasGeneratedBy(-,e2,a1)
+</pre>
</div>
</section>
@@ -727,7 +744,7 @@
<h2>Illustration of PROV-DM by an Example</h2>
<p>Section <a href="#starting-points">starting-points</a> has introduced some provenance concepts, and how they are expressed as types or relations in the PROV data model. The purpose of this section is to put these concepts into practice in order to express the provenance of some document published on the Web.
-With this realistic example, PROV-DM constructs are composed together, and a graphical illustration shows a provenance description forming a directed graph, rooted at the entity we want to explain the provenance of, and pointing to the entities, activities, and agents it depended on. This example also shows that, sometimes, multiple provenance descriptions about a same entity can co-exist, which then justifies the need for provenance of provenance.</p>
+With this realistic example, PROV-DM constructs are composed together, and a graphical illustration shows a provenance description forming a directed graph, rooted at the entity we want to explain the provenance of, and pointing to the entities, activities, and agents it depended on. This example also shows that, sometimes, multiple provenance descriptions about the same entity can co-exist, which then justifies the need for provenance of provenance.</p>
<p>The World Wide Web Consortium publishes many technical reports. In this example, we consider a technical report, and describe its provenance.
@@ -1062,7 +1079,7 @@
entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version="2" ])
</pre>
states the existence of an entity, denoted by identifier <span class="name">tr:WD-prov-dm-20111215</span>, with type <span class="name">document</span> and version number <span class="name">2</span>. The attribute <span class="name">ex:version</span> is application specific, whereas the attribute <span
-class="name">type</span> is reserved in the PROV-DM namespace.
+class="name">type</span> (see <a href="#term-attribute-type">Section 4.7.4.4</a>) is reserved in the <a title="prov-namespace">PROV namespace</a>.
<!--The following expression</p>
<pre class="codeexample">
entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version="2" ])
@@ -1070,7 +1087,7 @@
</pre>
states the existence of an entity, denoted by identifier <span class="name">e0</span>, with type <span class="name">File</span> and path <span class="name">/shared/crime.txt</span> in the
file system, and creator alice. The attributes <span class="name">path</span> and <span class="name">creator</span> are application specific, whereas the attribute <span
-class="name">type</span> is reserved in the PROV-DM namespace.-->
+class="name">type</span> is reserved in the PROV namespace.-->
</div>
@@ -1101,7 +1118,7 @@
</pre>
<p>states the existence of an activity with identifier <span class="name">a1</span>, start time <span class="name">2011-11-16T16:05:00</span>, and end time <span
class="name">2011-11-16T16:06:00</span>, running on host <span class="name">server.example.org</span>, and of type <span class="name">edit</span>. The attribute <span class="name">host</span> is application specific (declared in some namespace with prefix <span class="name">ex</span>). The attribute <span
-class="name">type</span> is a reserved attribute of PROV-DM, allowing for sub-typing to be expressed.</p>
+class="name">type</span> is a reserved attribute of PROV-DM, allowing for sub-typing to be expressed (see <a href="#term-attribute-type">Section 4.7.4.4</a>).</p>
</div>
@@ -1148,14 +1165,14 @@
<p>state the existence of two generations (with respective times <span class="name">2001-10-26T21:32:52</span> and <span
class="name">2001-10-26T10:00:00</span>), at which new entities, identified by <span class="name">e1</span> and <span class="name">e2</span>, are created by an
activity, identified by <span class="name">a1</span>.
-The first one is available on port p1, whereas the other is available on port p2. The semantics of <span class="name">port</span> are application specific.
+The first one is available on port <span class="name">p1</span>, whereas the other is available on port <span class="name">p2</span>. The semantics of <span class="name">port</span> are application specific.
</p>
</div>
<div class='anexample'>
<p>
-In some cases, we may want to record the time at which an entity was generated without having to specify the activity that generated it. To support this requirement, the activity component in generation is optional. Hence, the following expression indicates the time at which an entity is generated, without naming the activity that did it.</p>
+In some cases, we may want to record the time at which an entity was generated without having to specify the activity that generated it. To support this requirement, the activity element in generation is optional. Hence, the following expression indicates the time at which an entity is generated, without naming the activity that did it.</p>
<pre class="codeexample">
wasGeneratedBy(e,-,2001-10-26T21:32:52)
</pre>
@@ -1391,13 +1408,25 @@
<p>
It is useful to define some basic categories of agents from an interoperability perspective.
-There are three types of agents that are common across most anticipated domains of use:
+There are three types of agents that are common across most anticipated domains of use; It is acknowledged that these types do not cover all kinds of agent. </p>
<ul>
-<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 running software. </li>
+<li><span class="name">SoftwareAgent</span>
+<div class="glossary-ref" data-ref="glossary-software-agent"></li>
+
+<p>
+
+<li><span class="name">Organization</span>
+
+<div class="glossary-ref" data-ref="glossary-organization"></li>
+
+<p>
+
+<li><span class="name">Person</span>
+
+<div class="glossary-ref" data-ref="glossary-person"></li>
</ul>
-<p>It is acknowledged that these types do not cover all kinds of agent. </p>
+
+
@@ -1429,7 +1458,7 @@
<div class="anexample">
<p>
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 an explicit activity.
+we can ascribe <span class="name">tr:WD-prov-dm-20111215</span> to some agents without an explicit activity. The reserved attribute <span class="name">role</span> (see <a href="#term-attribute-role">Section 4.7.4.3</a>) allows for role of the agent in the attribution to be specified.
<pre class="codeexample">
agent(ex:Paolo, [ prov:type="Person" ])
agent(ex:Simon, [ prov:type="Person" ])
@@ -1458,7 +1487,7 @@
</ul></div>
<div class="anexample" id="anexample-wasAssociateWith">
-<p>In the following example, a designer and an operator agents are associated with an activity. The designer's goals are achieved by a workflow <span class="name">ex:wf</span>. </p>
+<p>In the following example, a designer and an operator agents are associated with an activity. The designer's goals are achieved by a workflow <span class="name">ex:wf</span>, described as an an entity of type <span class="name"><a>plan</a></span>. </p>
<pre class="codeexample">
activity(ex:a, [prov:type="workflow execution"])
agent(ex:ag1, [prov:type="operator"])
@@ -1496,7 +1525,7 @@
<p>PROV-DM offers a mild version of responsibility
in the form of a relation to represent when an agent acted on another
-agent's behalf. So in the example of someone running a mail program,
+agent's behalf. So for example someone running a mail program,
the program and the person are both
agents of the activity; furthermore, the mail software
agent is running on the person's behalf. In another example, the
@@ -1583,7 +1612,7 @@
<p>According to <a href="#starting-points">Section 2</a>, for an entity to be transformed from, created from, or resulting from an update to another, there must be some
underpinning activities performing the necessary actions resulting in such a derivation.
-A derivation can be described at various levels of precision. In its simplest form, derivation relates two entities. Optionally, attributes can be added to describe modalities of derivation. If the derivation is the result of a single known activity, then this activity can also be optionally expressed. And to provide a completely accurate description of the derivation, the generation and usage of the generated and used entities, respectively, can be provided. Optional information such as activity, generation, and usage can be linked to derivations to aid analysis of provenance and to facilitate provenance-based reproducibility. </p>
+A derivation can be described at various levels of precision. In its simplest form, derivation relates two entities. Optionally, attributes can be added to represent further information about the derivation. If the derivation is the result of a single known activity, then this activity can also be optionally expressed. To provide a completely accurate description of the derivation, the generation and usage of the generated and used entities, respectively, can be provided. Optional information such as activity, generation, and usage can be linked to derivations to aid analysis of provenance and to facilitate provenance-based reproducibility. </p>
<p><div class="attributes" id="attributes-derivation">A <dfn title="wasDerivedFrom">derivation</dfn><span class="withPn">, written <span class="pnExpression" id="pn-wasDerivedFrom">wasDerivedFrom(id, e2, e1, a, g2, u1, attrs)</span> in PROV-N,</span> has:
@@ -2179,8 +2208,8 @@
<p>The sixth component of PROV-DM is concerned with <a title="note">notes</a> and <a title="annotation">annotations</a>.
</p>
-<p>As provenance descriptions are exchanged between systems, it may be useful to add extra-information to what they are describing. For instance, a "trust service" may add value-judgements about the
-trustworthiness of some of the entities or agents involved. Likewise, an interactive visualization component may want to enrich a set of provenance descriptions with information helping reproduce their
+<p>As provenance descriptions are exchanged between systems, it may be useful for a third party to add extra information to what they are describing. For instance, a "trust service" may add value-judgements about the
+trustworthiness of some of the entities or agents occurring in provenance records it is given access to. Likewise, an interactive visualization component may want to enrich an existing set of provenance descriptions with information helping reproduce their
visual representation. To help with interoperability, PROV-DM introduces a simple annotation mechanism allowing anything that is identifiable to be associated with notes.
For this, a type and and a relation are introduced.</p>
@@ -2197,7 +2226,7 @@
<p><div class="attributes" id="attributes-note">A <dfn title="dfn-note" id="dfn-note">note</dfn><span class="withPn">, written <span class="pnExpression">note(id, [attr1=val1, ...])</span> in PROV-N,</span> has:
<ul>
<li><span class='attribute' id="note.id">id</span>: an identifier for a note;</li>
-<li><span class='attribute' id="note.attributes">attributes</span>: a set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing application-specific information about this relation.</li>
+<li><span class='attribute' id="note.attributes">attributes</span>: a set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing application-specific information.</li>
</ul>
</div>
@@ -2207,7 +2236,7 @@
<div class="anexample" id="anexample-note1">
<p>
The following note consists of a set of application-specific attribute-value pairs, intended
-to help the rendering of what it is associated with, by
+to help the rendering of the pre-existing entity it is associated with, by
specifying its color and its position on the screen.</p>
<pre class="codeexample">
note(ex:n1,[ex:color="blue", ex:screenX=20, ex:screenY=30])
@@ -2221,7 +2250,7 @@
</div>
<div class="anexample" id="anexample-note2">
-<p>Alternatively, a reputation service may enrich a provenance record with notes providing reputation ratings about agents. In the following fragment, both agents <span class="name">ex2:Simon</span> and <span class="name">ex2:Paolo</span> are rated "excellent".</p>
+<p>Alternatively, a reputation service may enrich an existing provenance record with notes providing reputation ratings about agents. In the following fragment, both agents <span class="name">ex2:Simon</span> and <span class="name">ex2:Paolo</span> are rated "excellent".</p>
<pre class="codeexample">
note(ex3:n2,[ex3:reputation="excellent"])
hasAnnotation(ex2:Simon,ex3:n2)
@@ -2302,7 +2331,7 @@
A <dfn id="dfn-defaultNamespaceDeclaration">default namespace declaration</dfn> consists of a namespace. Every un-prefixed qualified name in the scope of this default namespace declaration
refers to this namespace.</p>
-<p>The PROV-DM namespace is identifier by the URI <span class="name">http://www.w3.org/ns/prov#</span>.</p>
+<p>The <dfn title="prov-namespace">PROV namespace</dfn> is identified by the URI <span class="name">http://www.w3.org/ns/prov#</span>.</p>
</section>
@@ -2339,7 +2368,7 @@
<p>An <dfn title="dfn-attribute" id="dfn-attribute">attribute</dfn> is a <a>qualified name</a>.
-<p>The PROV data model introduces a pre-defined set of attributes in the <a href="#prov-dm-namespace">PROV-DM namespace</a>, which we define below.
+<p>The PROV data model introduces a pre-defined set of attributes in the <a title="prov-namespace">PROV namespace</a>, which we define below.
The interpretation of any attribute declared in another namespace is out of scope.</p>
@@ -2411,13 +2440,46 @@
<p>The following types are pre-defined in PROV, and are valid values for the <span class="name">prov:type</span> attribute.</p>
<ul>
-<li>prov:Plan</li>
-<li>prov:Account</li>
-<li>prov:SoftwareAgent</li>
-<li>prov:Organization</li>
-<li>prov:Person</li>
-<li>prov:Collection</li>
-<li>prov:EmptyCollection</li>
+<li><span class="name">prov:Plan</span></li>
+
+<!-- <div class="glossary-ref" data-ref="glossary-plan" data-withspan="true"> -->
+
+
+
+
+<li><span class="name">prov:Account</span></li>
+
+<!-- <div class="glossary-ref" data-ref="glossary-account" data-withspan="true"></li> -->
+
+
+
+<li><span class="name">prov:SoftwareAgent</span></li>
+
+<!-- <div class="glossary-ref" data-ref="glossary-software-agent" data-withspan="true"></li> -->
+
+
+
+<li><span class="name">prov:Organization</span></li>
+
+<!-- <div class="glossary-ref" data-ref="glossary-organization" data-withspan="true"></li> -->
+
+
+
+<li><span class="name">prov:Person</span></li>
+
+<!-- <div class="glossary-ref" data-ref="glossary-person" data-withspan="true"></li> -->
+
+
+
+<li><span class="name">prov:Collection</span></li>
+
+<!-- <div class="glossary-ref" data-ref="glossary-collection" data-withspan="true"></li> -->
+
+
+
+<li><span class="name">prov:EmptyCollection</span></li>
+
+<!-- <div class="glossary-ref" data-ref="glossary-empty-collection" data-withspan="true"></li> -->
</ul>
</section>
@@ -2473,7 +2535,7 @@
<div class="anexample" id="anexample-value">
<p>
-The following examples respectively are the string "abc", the string "abc", the integer number 1, and the IRI "http://example.org/foo".
+The following examples respectively are the string "abc", the integer number 1, and the IRI "http://example.org/foo".
<pre class="codeexample">
"abc"
1
@@ -2499,7 +2561,7 @@
</div>
<div class="note">
-We need to check that we are including all xsd types that are accept in the lastest version of RDF.
+We need to check that we are including all xsd types that are the latest versions of XML Schema/RDF.
</div>
</section>
</section>
@@ -2521,7 +2583,7 @@
<li> Attribute-value lists occur in all types and relations of the data model. Applications designers are free to introduce further application-specific attributes. Attributes for a given application can be distinguished by qualifying them with a prefix denoting a namespace
declared in a namespace declaration.
-<p>The <a href="#prov-dm-namespace">PROV-DM namespace</a> declares a set of reserved attributes catering for extensibility: <a href="#term-attribute-type"><span class="name">prov:type</span></a>, <a href="#term-attribute-role"><span class="name">prov:role</span></a>, <a href="#term-attribute-location"><span
+<p>The <a title="prov-namespace">PROV namespace</a> declares a set of reserved attributes catering for extensibility: <a href="#term-attribute-type"><span class="name">prov:type</span></a>, <a href="#term-attribute-role"><span class="name">prov:role</span></a>, <a href="#term-attribute-location"><span
class="name">prov:location</span></a>.</li>
<li>Sub-types and sub-relations can be expressed by means of the reserved attribute
--- a/model/working-copy/wd5-prov-invalidation.html Mon Apr 16 01:00:56 2012 +0100
+++ b/model/working-copy/wd5-prov-invalidation.html Mon Apr 16 07:47:36 2012 +0100
@@ -47,63 +47,63 @@
var extraReferences = {
"CLOCK":
"Lamport, L. "+
- "<a href=\"http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf\"><cite>Time, clocks, and the ordering of events in a distributed system</cite></a>."+
+ "<a href="\"http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf\""><cite>Time, clocks, and the ordering of events in a distributed system</cite></a>."+
"Communications of the ACM 21 (7): 558–565. 1978. "+
- "URL: <a href=\"http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf\">http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf</a> " +
+ "URL: <a href="\"http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf\"">http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf</a> " +
"DOI: doi:10.1145/359545.359563.",
"CSP":
"Hoare, C. A. R. "+
- "<a href=\"http://www.usingcsp.com/cspbook.pdf\"><cite>Communicating Sequential Processes</cite></a>."+
+ "<a href="\"http://www.usingcsp.com/cspbook.pdf\""><cite>Communicating Sequential Processes</cite></a>."+
"Prentice-Hall. 1985"+
- "URL: <a href=\"http://www.usingcsp.com/cspbook.pdf\">http://www.usingcsp.com/cspbook.pdf</a>",
+ "URL: <a href="\"http://www.usingcsp.com/cspbook.pdf\"">http://www.usingcsp.com/cspbook.pdf</a>",
"Logic":
"W. E. Johnson"+
- "<a href=\"http://www.ditext.com/johnson/intro-3.html\"><cite>Logic: Part III</cite></a>."+
+ "<a href="\"http://www.ditext.com/johnson/intro-3.html\""><cite>Logic: Part III</cite></a>."+
"1924. "+
- "URL: <a href=\"http://www.ditext.com/johnson/intro-3.html\">http://www.ditext.com/johnson/intro-3.html</a>",
+ "URL: <a href="\"http://www.ditext.com/johnson/intro-3.html\"">http://www.ditext.com/johnson/intro-3.html</a>",
"PROV-SEM":
"James Cheney "+
- "<a href=\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\"><cite>Formal Semantics Strawman</cite></a>. "+
+ "<a href="\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\""><cite>Formal Semantics Strawman</cite></a>. "+
"2011, Work in progress. "+
- "URL: <a href=\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\">http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman</a>",
+ "URL: <a href="\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\"">http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman</a>",
"PROV-PRIMER":
"Yolanda Gil and Simon Miles (eds.) Khalid Belhajjame, Helena Deus, Daniel Garijo, Graham Klyne, Paolo Missier, Stian Soiland-Reyes, and Stephan Zednik "+
- "<a href=\"http://www.w3.org/TR/prov-primer/\"><cite>Prov Model Primer</cite></a>. "+
+ "<a href="\"http://www.w3.org/TR/prov-primer/\""><cite>Prov Model Primer</cite></a>. "+
"2011, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-primer/\">http://www.w3.org/TR/prov-primer/</a>",
+ "URL: <a href="\"http://www.w3.org/TR/prov-primer/\"">http://www.w3.org/TR/prov-primer/</a>",
"PROV-O":
"Satya Sahoo and Deborah McGuinness (eds.) Khalid Belhajjame, James Cheney, Daniel Garijo, Timothy Lebo, Stian Soiland-Reyes, and Stephan Zednik "+
- "<a href=\"http://www.w3.org/TR/prov-o/\"><cite>Provenance Formal Model</cite></a>. "+
+ "<a href="\"http://www.w3.org/TR/prov-o/\""><cite>Provenance Formal Model</cite></a>. "+
"2011, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-o/\">http://www.w3.org/TR/prov-o/</a>",
+ "URL: <a href="\"http://www.w3.org/TR/prov-o/\"">http://www.w3.org/TR/prov-o/</a>",
"PROV-DM":
"Luc Moreau and Paolo Missier (eds.) ... "+
- "<a href=\"http://www.w3.org/TR/prov-dm/\"><cite>PART 1: PROV-DM ...</cite></a>. "+
+ "<a href="\"http://www.w3.org/TR/prov-dm/\""><cite>PART 1: PROV-DM ...</cite></a>. "+
"2011, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-dm/\">http://www.w3.org/TR/prov-dm/</a>",
+ "URL: <a href="\"http://www.w3.org/TR/prov-dm/\"">http://www.w3.org/TR/prov-dm/</a>",
"PROV-DM-CONSTRAINTS":
"Luc Moreau and Paolo Missier (eds.) ... "+
- "<a href=\"http://www.w3.org/TR/prov-dm-constraints/\"><cite>PROV-DM Constraints</cite></a>. "+
+ "<a href="\"http://www.w3.org/TR/prov-dm-constraints/\""><cite>PROV-DM Constraints</cite></a>. "+
"2011, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-dm-constraints/\">http://www.w3.org/TR/prov-dm-constraints/</a>",
+ "URL: <a href="\"http://www.w3.org/TR/prov-dm-constraints/\"">http://www.w3.org/TR/prov-dm-constraints/</a>",
"PROV-ASN":
"Luc Moreau and Paolo Missier (eds.) ... "+
- "<a href=\"http://www.w3.org/TR/prov-asn/\"><cite>PROV-ASN ....</cite></a>. "+
+ "<a href="\"http://www.w3.org/TR/prov-asn/\""><cite>PROV-ASN ....</cite></a>. "+
"2011, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-asn/\">http://www.w3.org/TR/prov-asn/</a>",
+ "URL: <a href="\"http://www.w3.org/TR/prov-asn/\"">http://www.w3.org/TR/prov-asn/</a>",
"PROV-AQ":
"Graham Klyne and Paul Groth (eds.) Luc Moreau, Olaf Hartig, Yogesh Simmhan, James Meyers, Timothy Lebo, Khalid Belhajjame, and Simon Miles "+
- "<a href=\"http://www.w3.org/TR/prov-aq/\"><cite>Provenance Access and Query</cite></a>. "+
+ "<a href="\"http://www.w3.org/TR/prov-aq/\""><cite>Provenance Access and Query</cite></a>. "+
"2011, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-aq/\">http://www.w3.org/TR/prov-aq/</a>",
+ "URL: <a href="\"http://www.w3.org/TR/prov-aq/\"">http://www.w3.org/TR/prov-aq/</a>",
};
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
@@ -231,7 +231,7 @@
<p>
-<div class="attributes" id="attributes-invalidation"><dfn title="dfn-Invalidation">Invalidation</dfn><span class="withAsn">, written <span class="pnExpression">wasInvalidatedBy(id,e,a,t,attrs)</span> in PROV-ASN,</span> has the following components:</p>
+<div class="attributes" id="attributes-invalidation"><dfn title="dfn-Invalidation">Invalidation</dfn><span class="withAsn">, written <span class="pnExpression">wasInvalidatedBy(id,e,a,t,attrs)</span> in PROV-ASN,</span> has:</p>
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier for a invalidation;</li>
<li><span class='attribute'>entity</span>: an identifier for the invalidated entity; </li>
@@ -239,7 +239,7 @@
<li><span class='attribute'>time</span>: an OPTIONAL "invalidation time", the time at which the entity began to be invalidated;</li>
-<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs that describes the modalities of invalidation of this entity by this activity.</li>
+<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs representing additional information about this invalidation.</li>
</ul></div>
<p>While each of the components <span class='attribute'>activity</span>, <span class='attribute'>time</span>, and <span class='attribute'>attributes</span> is OPTIONAL, at least one of them MUST be present.</p>