--- a/model/comments/issue-331-graham.txt Wed Apr 11 10:28:57 2012 +0100
+++ b/model/comments/issue-331-graham.txt Thu Apr 12 10:19:56 2012 +0100
@@ -11,8 +11,7 @@
> obvious, other aspects of which were just "noise") which didn't help to to
> understand what was being presented, or how to use it.
-Can you be specific about which justification is obvious or noise? Are
-they all listed below?
+Are they all listed below?
>
> I also still have problems with the overall organization. In particular, I
@@ -22,7 +21,7 @@
> of section 2 belong there, as they deal with provenance expression details, not
> concepts.
-Comment noted. Supportive comments also noted.
+Comment noted. Supportive comments from other reviewers also noted.
>
> Finally, I found many examples of unusual or awkward phrasing which I found to
@@ -44,6 +43,8 @@
> The phrase "derivations between entities" is strange and confusing. I think you
> mean something like "derivation of entities from other entities".
>
+Done
+
> "Properties that link entities that refer to a same thing". I think this is
> just wrong: I don't believe that entities *refer*. I think you mean something
> like "Properties that link entities that are based on the same thing".
@@ -51,9 +52,16 @@
This questions the definition of specialization that was agreed over email.
See ISSUE-29 discussion.
+TODO: when definition of specialization agreed.
+
>
> "collections of entities, whose provenance itself can be tracked" - this feels
> vaguely ungrammatical, and I'm not quite sure what this is trying to express.
+
+Rephrased as:
+ collections forming a logical structure for its members;
+
+
> In any case, I'll argue later that I don;t see why this is necessary as part of
> the provenance core model. (What I'm not seeing here is anything I can
> recognize as the notion of accounts, which allow for provenance of provenance to
@@ -68,14 +76,15 @@
> readers. In the abstract, I'd suggest just dropping this - the rest of the
> sentence carries the intended meaning.
-?
+Updated to: "This document introduces the provenance concepts underpinning
+ PROV-DM, and defines PROV-DM types and relations"
>
> I'm not sure what you mean by "systematically defines". Just "defines" would
> do, I think.
>
-ok todo
+Done.
> == Status of this document ==
>
@@ -85,7 +94,16 @@
> the documents into the preceding text, and drop the stuff that tries to tell
> people what to read.
-?????????
+
+This heading is also in prov-aq.
+
+We received very clear feedback, from Ivan in particular, that we need
+to be clear about the order in which readers should approach our
+documents.
+
+It is the Chairs' intent to have a PROV-overview document. In the
+meantime, this kind of information is placed in the SOTD paragram.
+
>
> "Fourth public working draft". Really!! Are we really up to 4 with this? I
@@ -107,7 +125,7 @@
This text comes from the incubator final report.
It's crucial to me to keep the term trust.
-Unclear that changes need to be made.
+No action.
>
> "The idea that ... a pragmatiuc approach is to consider ..." add's no useful
@@ -121,20 +139,22 @@
> While I sometimes think that a repeated summary can be useful, in this case I
> think it would be more helpful to simplify the preceding paragraph.
-To consider.
+Updated paragraph.
>
> The material that starts with "A set of specifications, ..." seems to be pure
> repetition of material contained in the "status of this document" - is it really
> necessary to repeat it here?
+Given that ultimately the SOTD paragraph will belong to a separate document yes.
+It's worth keeping this here.
>
> The listing of "components!" seems to be greatly redundant. Each component is
> both numbered (N) and introduced as "component N". I think a simple numbered
> list without the "component N" tags would suffice.
-OK :-)
+OK
>
> Two paragraphs starting with "This specification intentionally presents..." -
@@ -148,7 +168,7 @@
> available when those constraints are known to be satisfied."
>
-To consider.
+Some of it adopted.
> [[The next comment is rendered moot if the previous one is accepted...]]
> Paragraph: "However, if data changes...". To an uninitiated reader, it is not
@@ -158,7 +178,8 @@
> daily weather report is derived will change from day to day)." Drop the
> reference to other metadata here - it adds nothing of value.
>
-To consider.
+
+Done.
> @@(note to self) raise a separate issue about how to describe this "refinement".
> I know I have argued for "refinement" over the idea of an "updated" or
@@ -183,12 +204,12 @@
> other reserved names introduced by this document belong to a namespace
> identified by the URI http://www.w3.org/prov#".
-Merge section 1.2 and 1.3 in "conventions"
+Merged section 1.2 and 1.3 in a single section "notational conventions"
-One of the conventions is listing of namespaces uri and prefixes we use here.
-Add a reference to namespace section for explanation of namespaces in the context of prov-dm.
+This section lists prefixes and namespace uris used in this document.
+The purpose of the PROV namespace is discussed in 4.7.1
- >
+
> And: what is the consequence of these names belonging to a namespace? I think
> it would be appropriate to cite the corresponding XML and RDF documents that
> deal with namespace issues [1] [2].
@@ -199,7 +220,8 @@
> define how RDF/XML forms a URI-reference by appending a local name to a
> namespace URI.)
-We discuss namespace in 4.7.1.
+We discuss namespace in 4.7.1. This discussion of forming URIs by concatenating
+namespace URI and local name is already part of 4.7.2.
>
> == Section 2, PROV-DM staring points ==
@@ -213,8 +235,8 @@
> should be part of the early material in section 4.
>
-To consider. I think section 3 is at the right place. Section 2
-structure is does not need to be changed.
+I think section 3 is at the right place.
+Section 2 structure does not need to be changed.
> "... that a novice reader would write in a first instance". Yuk! How
@@ -225,7 +247,8 @@
> illustrative examples. Later (section @@ref), we describe how these concepts
> are described using PROV-DM types and relations."
-Adopt some of these changes. Still keep forwarding pointer to 2.5 and 2.6.
+Adopted some of these changes. I kept forwarding pointer to 2.5 and 2.6.
+
>
> (where @@ref should be in another section that actually deals with PROV-DM terms.)
>
@@ -240,10 +263,11 @@
> The final sentence is mostly noise. Why not just "Any Web resource may be an
> entity."?
-Therefore it's not noise, is it?
-Is it *is* an entity, or *can be regarded* as an entity.
+I removed this sentence. The example already mentions document at URI.
+The recent changes in PROV-AQ also indicate that web resource can also
+be activity or anything identifiable in the model.
>
> "For the purpose of this specification..." is just noise. Also, confusing
@@ -253,6 +277,8 @@
Adopt Simon's definition here.
+An entity is a physical, digital, conceptual, or other kind of thing; entities may be real or imaginary.
+
>
> "This action can take multiple forms: ..." - this is confusing; are we talking
> about a single activity having multiple forms, or different activities having
@@ -261,7 +287,9 @@
> may include consuming, processing, transforming, modifying, relocating, using,
> generating, or other associations with entities."
-I don't like the "They" here.
+Updated as follows:
+
+An activity is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, generating, or being associated with entities.
>
@@ -298,22 +326,26 @@
>
-It's exactly RDF container
+prov:Collection is similar to RDF container
http://www.w3.org/TR/rdf-schema/#ch_containermembershipproperty
-except that keys are not restricted to be rdf:_1, rdf:_2, ... but
+Except that "keys" are not restricted to be rdf:_1, rdf:_2, ... but
allowed to be prov-dm values.
-Can also describe car (rdf:first), cdr (rdf:rest) for list.
+prov:Collection can also describe car (rdf:first), cdr (rdf:rest) for list.
+
+This kind of usage should into the "collection primer", to be written.
+
+So, given this, we don't think that we are imposing a particular view
+on collections that may not be appropriate.
>
> I think accounts should have a section of their own, since they underpin the key
> feature of supporting provenance0-of-provenance.
-To be addresse later.
-An option is to drop completely the notion of account from all our documents.
+TODO: To be addressed later.
>
> However, I have a problem with the description "An account is an entity that
@@ -322,7 +354,7 @@
> don't think the core DM needs to or should expose the notion of containment,
> since that begs more questions.
-But then, why should bundle be part of dm?
+TODO: To be addressed later. bundle vs account.
>
> == 2.4 Attribution, association and responsibility ==
@@ -346,6 +378,8 @@
> sense of this, so it's hard for me to suggest alternatives.
>
+TODO
+
Does renaming the relation "Responsibility/actedOnBehalfOf" help?
And also remove the word accountable?
@@ -414,18 +448,19 @@
> digital, conceptual, or otherwise, and may be real or imaginary."
>
-Use simon's definition.
+We used Simon's definition. See above.
> "An entity, written entity(id, [attr1=val1, ...]) in PROV-N, contains:" - I
> think this is wrong - an entity does not (in general) *contain*. Suggest:
> "An entity, written entity(id, [attr1=val1, ...]) in PROV-N, has:"
>
-OK
+
+OK, updated for all.
> "id: an identifier for an entity;" - this is redundant and potentially
> confusing. Suggest "id: an identifier".
-
+TODO
?????????
>
@@ -437,7 +472,7 @@
>
-OK, still legacy. UPdate attributes everywhere.
+OK, still legacy. Updated attributes everywhere.
> == 4.1.2, et seq ==
@@ -454,7 +489,8 @@
> do you really mean to allow *any* entity here, rather than just agents?
>
-Yes: http://www.w3.org/2011/prov/meeting/2012-03-15#resolution_3
+Yes:
+This was recently agreed: http://www.w3.org/2011/prov/meeting/2012-03-15#resolution_3
> Looking forward to the example, I find the idea that an email (qua entity) can
> "trigger" an activity is incoherent. Suppose the email is drafted and never
@@ -471,6 +507,7 @@
> (Similar comments to those above.)
>
+See again:
http://www.w3.org/2011/prov/meeting/2012-03-15#resolution_3
>
@@ -484,7 +521,7 @@
In that case, one would just write.
wasGeneratedBy(e,a1)
used(a2,e)
-One doesn't need a new construct.
+One would not need a new construct.
>
> == Section 4.2.1, Agent ==
@@ -495,7 +532,7 @@
> Awkward and unnecessary phrase "situation in the world" again. See earlier for
> suggested phrasing.
-situation in the world to check everywhere.
+Removed all occurrences of "situation in the world".
>
>
@@ -507,7 +544,7 @@
> "A derivation is a transformation of an entity into another, a construction of
> an entity *from* another, or an update of an entity, resulting in a new one."
-
+TODO
yes, to look into. It would be nice to keep the same directionality for all of them.
@@ -524,6 +561,9 @@
>
> See also earlier comments.
>
+
+See earlier answer.
+
>
> == Section 4.6, Annotations ==
>
@@ -535,6 +575,9 @@
I don't think it can be added with attributes, that's the whole point, since
attributes and annotations can be added at different moments!
+This ISSUE-260.
+
+
>
>
> == Section 4.7.4 Attribute ==
@@ -543,6 +586,7 @@
> qualified name and a value?
yes, a qualifed name.
+
>
>
> == Section 5, Extensibility points ==
@@ -561,7 +605,7 @@
> be described as an extensibility point - they don't actually add any expressive
> power that I can see.
-non prov-attributes are also semantics free (from prov perspective).
+non prov-attributes are also semantics free (from a PROV perspective).
>
> The remaining points I just don't get.
@@ -571,7 +615,7 @@
> to ignore this and just use extensibility options in the representation
> substrate (e.g. RDF) used.
-
+TODO:
Probably needs some updating.
@@ -583,6 +627,7 @@
I think there is some value in stating there is an other document to
look at, and outline what it tackles.
+TODO?
>
--- a/model/prov-dm.html Wed Apr 11 10:28:57 2012 +0100
+++ b/model/prov-dm.html Thu Apr 12 10:19:56 2012 +0100
@@ -210,20 +210,20 @@
PROV-DM is structured in six components, dealing with:
(1) entities and activities, and the time at which they were created, used, or ended;
(2) agents bearing responsibility for entities that were generated and actities that happened;
-(3) derivations between entities;
+(3) derivations of entities from entities;
(4) properties to link entities that refer to a same thing;
-(5) collections of entities, whose provenance can itself be tracked;
+(5) collections forming a logical structure for its members;
(6) a simple annotation mechanism.
</p>
-<p>This document introduces the provenance concepts underpinning
-PROV-DM in natural language, and systematically defines PROV-DM types and
+<p>This document introduces the provenance concepts found in
+PROV-DM, and defines PROV-DM types and
relations. PROV data model is domain-agnostic, but is equipped with
-extensibility points allow domain-specific information to be included. </p>
+extensibility points allowing domain-specific information to be included. </p>
<p>Two further documents complete the specification of PROV-DM.
First, a companion document specifies the set of constraints that
-well-structured provenance descriptions should follow; these provide
+provenance descriptions should follow; these provide
an interpretation for provenance descriptions. Second, to
be able to provide examples of provenance, a notation is used for
expressing instances of PROV-DM for human consumption; the syntactic
@@ -233,16 +233,16 @@
<section id="sotd">
<h4>PROV Family of Specifications</h4>
-This document is part of the PROV family of specifications, a set of specifications aiming to define the various aspects that are necessary to achieve the vision of inter-operable
+This document is part of the PROV family of specifications, a set of specifications defining various aspects that are necessary to achieve the vision of inter-operable
interchange of provenance information in heterogeneous environments such as the Web. The specifications are as follows.
<ul>
-<li> PROV-DM, the PROV data model for provenance (this document),</li>
-<li> PROV-DM-CONSTRAINTS, a set of constraints applying to the PROV data model,</li>
-<li> PROV-N, a notation for provenance aimed at human consumption,</li>
+<li> PROV-DM, the PROV data model for provenance (this document);</li>
+<li> PROV-DM-CONSTRAINTS, a set of constraints applying to the PROV data model;</li>
+<li> PROV-N, a notation for provenance aimed at human consumption;</li>
<li> PROV-O, the PROV ontology, an OWL-RL ontology allowing the mapping of PROV to RDF;</li>
<li> PROV-AQ, the mechanisms for accessing and querying provenance; </li>
-<li> PROV-PRIMER, a primer for the PROV data model,</li>
-<li> PROV-SEM, a formal semantics for the PROV data model.</li>
+<li> PROV-PRIMER, a primer for the PROV data model;</li>
+<li> PROV-SEM, a formal semantics for the PROV data model;</li>
<li> PROV-XML, an XML schema for the PROV data model.</li>
</ul>
<h4>How to read the PROV Family of Specifications</h4>
@@ -296,21 +296,18 @@
<p>
-The idea that a single way of representing and collecting provenance could be adopted internally by all systems does not seem to be realistic today. Instead, a pragmatic approach is to
-consider a core data model for provenance that allows domain and application specific representations of provenance to be translated into such a data model and exchanged between systems.
-Heterogeneous systems can then export their provenance into such a core data model, and applications that need to make sense of provenance in heterogeneous systems can then import it,
+We
+consider a core data model for provenance that allows domain and application specific representations of provenance to be translated into such a data model and <em>interchanged</em> between systems.
+Thus, heterogeneous systems can export their native provenance into such a core data model, and applications that need to make sense of provenance in heterogeneous systems can then import it,
process it, and reason over it.</p>
-<p>Thus, the vision is that different provenance-aware systems natively adopt their own model for representing their provenance, but a core provenance data model can be readily adopted as a
-provenance <em>interchange</em> model across such systems.</p>
-
<p>A set of specifications, referred to as the PROV family of specifications, define the various aspects
that are necessary to achieve this vision in an interoperable
way:</p>
<ul>
<li>A data model for provenance, which is presented in three documents:
<ul>
-<li> PROV-DM (part I): the provenance data model itself, expressed in natural language (this document);
+<li> PROV-DM (part I): the provenance data model, informally described (this document);
<li> PROV-DM-CONSTRAINTS (part II): constraints underpinning the data model [[PROV-DM-CONSTRAINTS]];
<li> PROV-N (part III): a notation to express instances of that data model for human consumption [[PROV-N]];
</ul>
@@ -327,26 +324,29 @@
PROV-DM is a domain-agnostic model, but with clear extensibility points allowing further domain-specific and
application-specific extensions to be defined.
The PROV data model is structured according to six components covering various aspects of provenance:</p>
-<ol>
+<ul>
<li> component 1: entities and activities, and the time at which they were created, used, or ended;
<li> component 2: agents bearing responsibility for entities that were generated and actities that happened;
<li> component 3: derivations between entities;
<li> component 4: properties to link entities that refer to a same thing;
<li> component 5: collections of entities, whose provenance can itself be tracked;
<li> component 6: a simple annotation mechanism.
-</ol>
-
-
-<p>This specification intentionally presents the key concepts of the PROV Data Model, without drilling down into all its subtleties. Using these key concepts, it becomes possible to write useful provenance descriptions very quickly, and publish or embed them along side the data they relate to. </p>
-
-<p>However, if data changes, then it is challenging to express its provenance precisely, like it would be for any other form of metadata. To address this challenge, a <em>refinement</em> is proposed to enrich simple provenance, with extra-descriptions that help qualify the specific subject of provenance and provenance itself, with attributes and temporal interval, intended to satisfy a comprehensive set of constraints. These aspects are covered in the companion specification [[PROV-DM-CONSTRAINTS]].
+</ul>
+
+
+<p>This specification presents the key concepts of the PROV Data Model, and
+provenance types and relations, without specific concern for how they are applied.
+With these, it becomes possible to write useful provenance descriptions, and publish or embed them along side the data they relate to. </p>
+
+<p>However, if something about which provenance is expressed is subject to change, then it is challenging to express its provenance precisely (e.g. the data from which a daily weather report is derived changes from day to day).
+ To address this challenge, a <em>refinement</em> is proposed to enrich simple provenance, with extra-descriptions that help qualify the specific subject of provenance and provenance itself, with attributes and temporal information, intended to satisfy a comprehensive set of constraints. These aspects are covered in the companion specification [[PROV-DM-CONSTRAINTS]].
</p>
- <section id="structure-of-this-document">
+<section id="structure-of-this-document">
<h3>Structure of this Document</h3>
-<p><a href="#starting-points">Section 2</a> provides starting points for the PROV Data Model, listing a set of types and relations, which are allows users to make initial provenance descriptions.</p>
+<p><a href="#starting-points">Section 2</a> provides starting points for the PROV Data Model, listing a set of types and relations, which allows users to make initial provenance descriptions.</p>
<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>
@@ -358,21 +358,10 @@
<p><a href="#FurtherConsiderations">Section 6</a> introduces the idea that constraints can be applied to the PROV data model to refine provenance descriptions; these are covered in the companion specification [[PROV-DM-CONSTRAINTS]].</p>
- </section>
-
-<section id="prov-dm-namespace">
- <h3>PROV Namespace</h3>
-
-
-<p>The PROV namespace is <span class="name">http://www.w3.org/ns/prov#</span>.</p>
-
-<p> All the concepts, reserved names and attributes introduced in this specification belong to the PROV namespace.</p>
-
-</section>
-
-
- <section id="conventions">
-<h3>Conventions</h3>
+</section>
+
+<section id="conventions">
+<h3>Notational Conventions</h3>
@@ -380,7 +369,23 @@
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
[[!RFC2119]].</p>
- </section>
+
+
+<p>
+The following namespaces prefixes are used throughout this document.
+
+<div style="text-align: left;">
+<table border="1" style="margin-left: auto; margin-right: auto;">
+<caption id="namespace-table">Table 1: Prefix and Namespaces used in this specification</caption>
+<tr><td><a><bf>prefix</bf></a></td><td><bf>namespace uri</bf></td> <td><bf>definition</bf></td></tr>
+<tr><td><a>prov</a></td><td>http://www.w3.org/ns/prov#</td><td>The PROV namespace (see Section <a href="#term-NamespaceDeclaration">4.7.1</a>)</td></tr>
+<tr><td><a>xsd</a></td><td>http://www.w3.org/2000/10/XMLSchema#</td><td>XML Schema Namespace [[!XMLSCHEMA-2]]</td></tr>
+<tr><td><a>rdf</a></td><td>http://www.w3.org/1999/02/22-rdf-syntax-ns#</td><td>The RDF namespace [[!RDF-CONCEPTS]]</td></tr>
+<tr><td><a>(others)</a></td><td>(various)</td><td>All other namespace prefixes are used in examples only. <br/> In particular, URIs starting with "http://example.com" represent<br/> some application-dependent URI [[!URI]]</td></tr>
+</table>
+</div>
+
+</section>
</section>
@@ -390,11 +395,8 @@
<h1>PROV-DM Starting Points</h1>
<p>
-This section provides an introduction to the PROV data model by
-overviewing a set of concepts underpinning provenance descriptions
-that a novice reader would write in a first instance. In Sections 2.1
-to 2.4, these concepts are described in natural language and
-illustrated by small examples. Since PROV-DM is a conceptual data
+This section introduces provenance concepts with informal descriptions and illustrative
+examples. Since PROV-DM is a conceptual data
model, Section 2.5 maps the concepts to various types and relations,
which are illustrated graphically in
a <a href="#prov-dm-overview">simplified UML diagram</a>. Section 2.6
@@ -409,7 +411,7 @@
<p>Things we want to describe the provenance of are called <em>entities</em> in PROV. The term "things" encompasses a broad diversity of notions, including digital objects such as a file or web page,
-physical things such as a building or a printed book, or a car as well as abstract concepts and ideas. One can regard any Web resource as an example of Entity in this context. </p>
+physical things such as a building or a printed book, or a car as well as abstract concepts and ideas. </p>
<p>
<div class="glossary-ref" data-ref="glossary-entity" data-withspan="true">
@@ -418,7 +420,7 @@
<div class="anexample" id="entity-example">
-<p>An entity may be the document at URI <a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a>, a file in a file system, a car, or an idea.</p>
+<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>
@@ -952,14 +954,14 @@
Components and their dependencies are illustrated in Figure <a href="#prov-dm-components">prov-dm-components</a>. A component that relies on concepts defined in another also sits above it in this figure.
PROV-DM consists of the following components.</p>
-<ol>
+<ul>
<li><b>Component 1: entities and activities.</b> The first component consists of entities, activities, and all concepts linking them, such as generation, usage, start, end. The first component is the only one comprising time-related concepts. </li>
<li><b>Component 2: agents and responsibility.</b> The second component consists of agents and concepts ascribing responsibility to agents.</li>
<li><b>Component 3: derivations.</b> The third component is formed with derivations and its derivation subtypes.</li>
<li><b>Component 4: alternate.</b> The fourth component consists of relations linking entities somehow referring to a same thing. </li>
<li><b>Component 5: collections.</b> The fifth component is comprised of collections and operations related to collections. </li>
<li><b>Component 6: annotations.</b> The sixth component is concerned with annotations to PROV-DM concepts.</li>
-</ol>
+</ul>
<div style="text-align: center;">
@@ -994,15 +996,16 @@
</table>
</div>
-<p>Table <a href="#prov-dm-concepts-and-relations">prov-dm-concepts-and-relations</a> is a complete index of all the concepts and relations in prov-dm, color-coded according to the component they belong too. In the first column, one finds concept names directly linking to their English definition. In the second column, we find their representation in the PROV-N notation, directly linking to the definition of their various constituents.</p>
+<p>Table <a href="#prov-dm-concepts-and-relations">prov-dm-concepts-and-relations</a> is a complete index of all the types and relations of PROV-DM, color-coded according to the component they belong to. In the first column, concept names link to their informal definition, whereas, in the second column, representations link to the information used to represent the concept.</p>
<div style="text-align: left;">
<table border="1" style="margin-left: auto; margin-right: auto;">
-<caption id="prov-dm-concepts-and-relations">PROV-DM Concepts and Relations</caption>
+<caption id="prov-dm-concepts-and-relations">PROV-DM Types and Relations</caption>
+<tr><td><a><b>Type or Relation Name</b></a></td><td><b>Representation in the PROV-N notation</b></td></tr>
<tr class="component1-color"><td><a>Entity</a></td><td><a title="dfn-Entity">entity(id, [ attr1=val1, ...])</a></td></tr>
<tr class="component1-color"><td><a>Activity</a></td><td><a title="dfn-Activity">activity(id, st, et, [ attr1=val1, ...])</a></td></tr>
-<tr class="component1-color"><td><a>Generation</a></td><td><a title="dfn-Generation">wasGeneratedBy(id,e,a,t,attrs)</a></td></tr>
+<tr class="component1-color"><td><a>Generation</a></td><td><a title="wasGeneratedBy">wasGeneratedBy(id,e,a,t,attrs)</a></td></tr>
<tr class="component1-color"><td><a>Usage</a></td><td><a title="used">used(id,a,e,t,attrs)</a></td></tr>
<tr class="component1-color"><td><a>Start</a></td><td><a title="wasStartedBy">wasStartedBy(id,a,e,t,attrs)</a></td></tr>
<tr class="component1-color"><td><a>End</a></td><td><a title="wasEndedBy">wasEndedBy(id,a,e,t,attrs)</a></td></tr>
@@ -1023,12 +1026,16 @@
<tr class="component5-color"><td><a>Insertion</a></td><td><a title="derivedByInsertionFrom">derivedByInsertionFrom(id, c2, c1, {(key_1, e_1), ..., (key_n, e_n)}, attrs)</a></td></tr>
<tr class="component5-color"><td><a>Removal</a></td><td><a title="derivedByRemovalFrom">derivedByRemovalFrom(id, c2, c1, {key_1, ... key_n}, attrs)</a></td></tr>
<tr class="component5-color"><td><a>Membership</a></td><td><a title="memberOf">memberOf(c, {(key_1, e_1), ..., (key_n, e_n)})</a></td></tr>
-<tr class="component6-color"><td><a>Note</a></td><td><a title="note">note(id, [ attr1=val1, ...])</a></td></tr>
+<tr class="component6-color"><td><a>Note</a></td><td><a title="dfn-note">note(id, [ attr1=val1, ...])</a></td></tr>
<tr class="component6-color"><td><a>Annotation</a></td><td><a title="hasAnnotation">hasAnnotation(r,n)</a></td></tr>
</table>
</div>
-<p>In the rest of the section, each concept and relation is defined, in English initially, followed by a more formal definition and some example.</p>
+<p>
+In the rest of the section, each type and relation is defined informally,
+ followed by a summary of the information used to represent the concept, and
+ illustrated with PROV-N examples.</p>
+
<section id="component1">
<h3>Component 1: Entities and Activities</h3>
@@ -1055,10 +1062,10 @@
<div class="glossary-ref" data-ref="glossary-entity"></div>
-<p><div class="attributes" id="attributes-entity">An <dfn title="dfn-Entity">entity</dfn><span class="withPn">, written <span class="pnExpression" id="pn-entity">entity(id, [attr1=val1, ...])</span> in PROV-N, </span> contains:
+<p><div class="attributes" id="attributes-entity">An <dfn title="dfn-Entity">entity</dfn><span class="withPn">, written <span class="pnExpression" id="pn-entity">entity(id, [attr1=val1, ...])</span> in PROV-N, </span> has:
<ul>
<li><span class='attribute' id="entity.id">id</span>: an identifier for an entity; </li>
-<li><span class='attribute' id="entity.attributes">attributes</span>: an OPTIONAL set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing this entity's situation in the world.</li>
+<li><span class='attribute' id="entity.attributes">attributes</span>: an OPTIONAL set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this entity.</li>
</ul></div>
<div class="anexample">
@@ -1095,12 +1102,12 @@
<div class="glossary-ref" data-ref="glossary-activity"></div>
-<p><div class="attributes" id="attributes-activity"> An <dfn title="dfn-Activity">activity</dfn><span class="withPn">, written <span class="pnExpression" id="pn-activity">activity(id, st, et, [attr1=val1, ...])</span> in PROV-N,</span> contains:
+<p><div class="attributes" id="attributes-activity"> An <dfn title="dfn-Activity">activity</dfn><span class="withPn">, written <span class="pnExpression" id="pn-activity">activity(id, st, et, [attr1=val1, ...])</span> in PROV-N,</span> has:
<ul>
<li><span class='attribute' id="activity.id">id</span>: an identifier for an activity;</li>
<li><span class='attribute' id="activity.startTime">startTime</span>: an OPTIONAL time (<span class="name">st</span>) for the start of the activity;</li>
<li><span class='attribute' id="activity.endTime">endTime</span>: an OPTIONAL time (<span class="name">et</span>) for the end of the activity;</li>
-<li><span class='attribute' id="activity.attributes">attributes</span>: an OPTIONAL set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) for this activity.</li>
+<li><span class='attribute' id="activity.attributes">attributes</span>: an OPTIONAL set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this activity.</li>
</ul></div>
<div class="anexample">
@@ -1133,7 +1140,7 @@
<div class="glossary-ref" data-ref="glossary-generation"></div>
<p>
-<div class="attributes" id="attributes-generation"><dfn title="dfn-Generation">Generation</dfn><span class="withPn">, written <span class="pnExpression">wasGeneratedBy(id,e,a,t,attrs)</span> in PROV-N,</span> has the following components:
+<div class="attributes" id="attributes-generation"><dfn title="wasGeneratedBy">Generation</dfn><span class="withPn">, written <span class="pnExpression">wasGeneratedBy(id,e,a,t,attrs)</span> in PROV-N,</span> has:
<ul>
<li><span class='attribute' id="generation.id">id</span>: an OPTIONAL identifier for a generation;</li>
<li><span class='attribute' id="generation.entity">entity</span>: an identifier (<span class="name">e</span>) for a created entity; </li>
@@ -1141,7 +1148,7 @@
<li><span class='attribute' id="generation.time">time</span>: an OPTIONAL "generation time" (<span class="name">t</span>), the time at which the entity was completely created;</li>
-<li><span class='attribute' id="generation.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs that describes the modalities of generation of this entity by this activity.</li>
+<li><span class='attribute' id="generation.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this generation.</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>
@@ -1182,13 +1189,13 @@
<div class="glossary-ref" data-ref="glossary-usage"></div>
-<p><div class="attributes" id="attributes-usage"><dfn title="used">Usage</dfn><span class="withPn">, written <span class="pnExpression">used(id,a,e,t,attrs)</span> in PROV-N,</span> has the following constituents:
+<p><div class="attributes" id="attributes-usage"><dfn title="used">Usage</dfn><span class="withPn">, written <span class="pnExpression">used(id,a,e,t,attrs)</span> in PROV-N,</span> has:
<ul>
<li><span class='attribute' id="usage.id">id</span>: an OPTIONAL identifier for a usage;</li>
<li><span class='attribute' id="usage.activity">activity</span>: an identifier (<span class="name">a</span>) for the consuming activity;</li>
<li><span class='attribute' id="usage.entity">entity</span>: an identifier (<span class="name">e</span>) for the consumed entity;</li>
<li><span class='attribute' id="usage.time">time</span>: an OPTIONAL "usage time" (<span class="name">t</span>), the time at which the entity started to be used;</li>
-<li><span class='attribute' id="usage.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs that describe the modalities of usage of this entity by this activity.</li>
+<li><span class='attribute' id="usage.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this usage.</li>
</ul></div>
<p>
@@ -1223,13 +1230,13 @@
<div class="glossary-ref" data-ref="glossary-start"></div>
-<p><div class="attributes" id="attributes-start">An activity <dfn title="wasStartedBy">start</dfn><span class="withPn">, written <span class="pnExpression">wasStartedBy(id,a,e,t,attrs)</span> in PROV-N,</span> contains:
+<p><div class="attributes" id="attributes-start">An activity <dfn title="wasStartedBy">start</dfn><span class="withPn">, written <span class="pnExpression">wasStartedBy(id,a,e,t,attrs)</span> in PROV-N,</span> has:
<ul>
<li><span class='attribute' id="start.id">id</span>: an OPTIONAL identifier for the activity start;</li>
<li><span class='attribute' id="start.activity">activity</span>: an identifier (<span class="name">a</span>) for the started activity;</li>
<li><span class='attribute' id="start.trigger">trigger</span>: an OPTIONAL identifier (<span class="name">e</span>) for the entity triggering the activity;</li>
<li><span class='attribute' id="start.time">time</span>: the OPTIONAL time (<span class="name">t</span>) at which the activity was started; </li>
-<li><span class='attribute' id="start.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs describing modalities according to which the activity was started.
+<li><span class='attribute' id="start.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this activity start.
</ul>
</div>
@@ -1271,13 +1278,13 @@
<div class="glossary-ref" data-ref="glossary-end"></div>
-<p>An activity <dfn title="wasEndedBy">end</dfn><span class="withAsn">, written <span class="pnExpression">wasEndedBy(id,a,e,t,attrs)</span> in PROV-N,</span> contains:</p>
+<p>An activity <dfn title="wasEndedBy">end</dfn><span class="withAsn">, written <span class="pnExpression">wasEndedBy(id,a,e,t,attrs)</span> in PROV-N,</span> has:</p>
<ul>
<li><span class='attribute' id="end.id">id</span>: an OPTIONAL identifier for the activity end;</li>
<li><span class='attribute' id="end.activity">activity</span>: an identifier (<span class="name">a</span>) for the ended activity;
<li><span class='attribute' id="end.trigger">trigger</span>: an OPTIONAL identifier (<span class="name">e</span>) for the entity triggering the activity ending;
<li><span class='attribute' id="end.time">time</span>: the OPTIONAL time (<span class="name">t</span>) at which the activity was ended; </li>
-<li><span class='attribute' id="end.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs describing modalities according to which the activity was ended.
+<li><span class='attribute' id="end.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this activity end.
</ul>
<div class="anexample">
@@ -1306,12 +1313,12 @@
<p><div class="attributes" id="attributes-wasInformedBy">
A <dfn title="wasInformedBy">communication</dfn><span class="withPn">, written as
-<span class="pnExpression">wasInformedBy(id,a2,a1,attrs)</span> in PROV-N,</span> contains:
+<span class="pnExpression">wasInformedBy(id,a2,a1,attrs)</span> in PROV-N,</span> has:
<ul>
<li><span class='attribute' id="wasInformedBy.id">id</span>: an OPTIONAL identifier identifying the relation;</li>
<li><span class='attribute' id="wasInformedBy.informed">informed</span>: the identifier (<span class="name">a2</span>) of the informed activity;
<li><span class='attribute' id="wasInformedBy.informant">informant</span>: the identifier (<span class="name">a1</span>) of the informant activity;
-<li><span class='attribute' id="wasInformedBy.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs to further describe properties of the relation.</li>
+<li><span class='attribute' id="wasInformedBy.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this communication.</li>
</ul>
</div>
@@ -1338,12 +1345,12 @@
<p><div class="attributes" id="attributes-startByActivity">
A <dfn title="wasStartedByActivity">start by activity</dfn><span class="withPn">, written as
-<span class="pnExpression">wasStartedByActivity(id, a2, a1, attrs)</span> in PROV-N,</span> contains:
+<span class="pnExpression">wasStartedByActivity(id, a2, a1, attrs)</span> in PROV-N,</span> has:
<ul>
<li><span class='attribute' id="startByActivity.id">id</span>: an OPTIONAL identifier of the relation;</li>
<li><span class='attribute' id="startByActivity.started">started</span>: the identifier (<span class="name">a2</span>) of the started activity;
<li><span class='attribute' id="startByActivity.starter">starter</span>: the identifier (<span class="name">a1</span>) of the activity that started the other;</li>
-<li><span class='attribute' id="startByActivity.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs to further describe the properties of the relation.</li>
+<li><span class='attribute' id="startByActivity.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this start by activity.</li>
</ul>
</div>
@@ -1386,10 +1393,10 @@
<div class="glossary-ref" data-ref="glossary-agent"></div>
-<p><div class="attributes" id="attributes-agent">An <dfn title="dfn-agent">agent</dfn><span class="withPn">, noted <span class="pnExpression" id="pn-agent">agent(id, [attr1=val1, ...])</span> in PROV-N,</span> contains:
+<p><div class="attributes" id="attributes-agent">An <dfn title="dfn-agent">agent</dfn><span class="withPn">, written <span class="pnExpression" id="pn-agent">agent(id, [attr1=val1, ...])</span> in PROV-N,</span> has:
<ul>
<li><span class='attribute' id="agent.id">id</span>: an identifier for an agent;</li>
-<li><span class='attribute' id="agent.attributes">attributes</span>: a set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing this agent's situation in the world.
+<li><span class='attribute' id="agent.attributes">attributes</span>: a set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this agent.
</li>
</ul></div>
@@ -1424,12 +1431,12 @@
<p>When an entity <span class="name">e</span> is attributed to agent <span class="name">ag</span>, entity <span class="name">e</span> was generated by some unspecified activity that in turn was associated to agent <span class="name">ag</span>. Thus, this relation is useful when the activity is not known, or irrelevant.</p>
-<p> An <dfn title="wasAttributedTo">attribution</dfn> relation<span class="withPn">, written <span class="pnExpression">wasAttributedTo(id,e,ag,attrs)</span> in PROV-N,</span> contains the following elements:</p>
+<p> An <dfn title="wasAttributedTo">attribution</dfn> relation<span class="withPn">, written <span class="pnExpression">wasAttributedTo(id,e,ag,attrs)</span> in PROV-N,</span> has:</p>
<ul>
<li><span class='attribute' id="attribution.id">id</span>: an OPTIONAL identifier for the relation;</li>
<li><span class='attribute' id="attribution.entity">entity</span>: an entity identifier (<span class="name">e</span>);</li>
<li><span class='attribute' id="attribution.agent">agent</span>: the identifier (<span class="name">ag</span>) of the agent whom the entity is ascribed to;</li>
-<li><span class='attribute' id="attribution.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs to further describe the properties of the relation.</li>
+<li><span class='attribute' id="attribution.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this attribution.</li>
</ul>
<div class="anexample">
@@ -1454,14 +1461,13 @@
<div class="glossary-ref" data-ref="glossary-activityAssociation"></div>
-<p><div class="attributes" id="attributes-activity-association">An <dfn title="wasAssociatedWith">activity association</dfn><span class="withPn">, written <span class="pnExpression">wasAssociatedWith(id,a,ag,pl,attrs)</span> in PROV-N,</span> has the following
-constituents:
+<p><div class="attributes" id="attributes-activity-association">An <dfn title="wasAssociatedWith">activity association</dfn><span class="withPn">, written <span class="pnExpression">wasAssociatedWith(id,a,ag,pl,attrs)</span> in PROV-N,</span> has:
<ul>
<li><span class='attribute' id="association.id">id</span>: an OPTIONAL identifier for the association between an activity and an agent;</li>
<li><span class='attribute' id="association.activity">activity</span>: an identifier (<span class="name">a</span>) for the activity;</li>
<li><span class='attribute' id="association.agent">agent</span>: an OPTIONAL identifier (<span class="name">ag</span>) for the agent associated with the activity;</li>
<li><span class='attribute' id="association.plan">plan</span>: an OPTIONAL identifier (<span class="name">pl</span>) for the plan adopted by the agent in the context of this activity;
-<li><span class='attribute' id="association.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs that describe the modalities of association of this activity with this agent.</li>
+<li><span class='attribute' id="association.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this association of this activity with this agent.</li>
</ul></div>
<div class="anexample" id="anexample-wasAssociateWith">
@@ -1515,15 +1521,15 @@
<p>
-<div class="attributes" id="attributes-responsibility-chain">
-A <dfn title="actedOnBehalfOf">responsibility</dfn> relation<span class="withPn">, written <span class="pnExpression">actedOnBehalfOf(id,ag2,ag1,a,attrs)</span> in PROV-N,</span> has the following constituents:
+<div class="attributes" id="attributes-responsibility">
+A <dfn title="actedOnBehalfOf">responsibility</dfn> relation<span class="withPn">, written <span class="pnExpression">actedOnBehalfOf(id,ag2,ag1,a,attrs)</span> in PROV-N,</span> has:
<ul>
<li><span class='attribute' id="responsibility.id">id</span>: an OPTIONAL identifier for the responsibility chain;</li>
<li><span class='attribute' id="responsibility.subordinate">subordinate</span>: an identifier (<span class="name">ag2</span>) for the agent associated with an activity, acting on behalf of the responsible
agent;</li>
<li><span class='attribute' id="responsibility.responsible">responsible</span>: an identifier (<span class="name">ag1</span>) for the agent, on behalf of which the subordinate agent acted;</li>
<li><span class='attribute' id="responsibility.activity">activity</span>: an OPTIONAL identifier (<span class="name">a</span>) of an activity for which the responsibility chain holds;</li>
-<li><span class='attribute' id="responsibility.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs that describe the modalities of this relation.</li>
+<li><span class='attribute' id="responsibility.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this responsibility relation.</li>
</ul></div>
@@ -1592,7 +1598,7 @@
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. The reason for optional information such as activity, generation, and usage to be linked to derivations is 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> contains:
+<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:
<ul>
<li><span class='attribute' id="derivation.id">id</span>: an OPTIONAL identifier for a derivation;</li>
<li><span class='attribute' id="derivation.generatedEntity">generatedEntity</span>: the identifier (<span class="name">ee</span>) of the entity generated by the derivation;</li>
@@ -1600,7 +1606,7 @@
<li><span class='attribute' id="derivation.activity">activity</span>: an OPTIONAL identifier (<span class="name">a</span>) for the activity using and generating the above entities;</li>
<li><span class='attribute' id="derivation.generation">generation</span>: an OPTIONAL identifier (<span class="name">g2</span>) for the generation involving the generated entity and activity;</li>
<li><span class='attribute' id="derivation.usage">usage</span>: an OPTIONAL identifier (<span class="name">u1</span>) for the usage involving the used entity and activity;</li>
-<li><span class='attribute' id="derivation.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs that describe the modalities of this derivation.</li>
+<li><span class='attribute' id="derivation.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this derivation.</li>
</ul>
</div>
@@ -1641,13 +1647,13 @@
The agent who is responsible for the revision may optionally be specified.
Revision is a particular case of <a>derivation</a> of an entity into its revised version.</p>
-<p> A <dfn title="wasRevisionOf">revision</dfn> relation<span class="withPn">, written <span class="pnExpression">wasRevisionOf(id,e2,e1,ag,attrs)</span> in PROV-N,</span> contains:</p>
+<p> A <dfn title="wasRevisionOf">revision</dfn> relation<span class="withPn">, written <span class="pnExpression">wasRevisionOf(id,e2,e1,ag,attrs)</span> in PROV-N,</span> has:</p>
<ul>
<li><span class='attribute' id="revision.id">id</span>: an OPTIONAL identifier for the relation;</li>
<li><span class='attribute' id="revision.newer">newer</span>: the identifier (<span class="name">e2</span>) of the revised entity;
<li><span class='attribute' id="revision.older">older</span>: the identifier (<span class="name">e1</span>) of the older entity;
<li><span class='attribute' id="revision.responsibility">responsibility</span>: an OPTIONAL identifier (<span class="name">ag</span>) for the agent who approved the newer entity as a variant of the older;
-<li><span class='attribute' id="revision.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs to further describe the properties of this relation.</li>
+<li><span class='attribute' id="revision.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this relation.</li>
</ul>
@@ -1679,14 +1685,14 @@
<p>Quotation
is a particular case of <a href="#Derivation-Relation">derivation</a> in which entity <span class="name">e2</span> is derived from an original entity <span class="name">e1</span> by copying, or "quoting", some or all of it.
- A <dfn title="wasQuotedFrom">quotation</dfn> relation<span class="withPn">, written <span class="pnExpression">wasQuotedFrom(id,e2,e1,ag2,ag1,attrs)</span> in PROV-N,</span> contains:</p>
+ A <dfn title="wasQuotedFrom">quotation</dfn> relation<span class="withPn">, written <span class="pnExpression">wasQuotedFrom(id,e2,e1,ag2,ag1,attrs)</span> in PROV-N,</span> has:</p>
<ul>
<li><span class='attribute' id="quotation.id">id</span>: an OPTIONAL identifier for the relation;</li>
<li><span class='attribute' id="quotation.quote">quote</span>: an identifier (<span class="name">e2</span>) for the entity that represents the quote (the partial copy);
<li><span class='attribute' id="quotation.original">original</span>: an identifier (<span class="name">e1</span>) for the original entity being quoted;
<li><span class='attribute' id="quotation.quoterAgent">quoterAgent</span>: an OPTIONAL identifier (<span class="name">ag2</span>) for the agent who performs the quote;
<li><span class='attribute' id="quotation.originalAgent">originalAgent</span>: an OPTIONAL identifier (<span class="name">ag1</span>) for the agent to whom the original entity is attributed;
-<li><span class='attribute' id="quotation.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs to further describe the properties of the relation.</li>
+<li><span class='attribute' id="quotation.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this relation.</li>
</ul>
@@ -1726,12 +1732,12 @@
<a href="http://googlenewsblog.blogspot.com/2010/11/credit-where-credit-is-due.html">http://googlenewsblog.blogspot.com/2010/11/credit-where-credit-is-due.html</a>.</p>
-<p> An <dfn title="hadOriginalSource">original source</dfn> relation<span class="withPn">, written <span class="pnExpression">hadOriginalSource(id,e2,e1,attrs)</span>,</span> contains:</p>
+<p> An <dfn title="hadOriginalSource">original source</dfn> relation<span class="withPn">, written <span class="pnExpression">hadOriginalSource(id,e2,e1,attrs)</span>,</span> has:</p>
<ul>
<li><span class='attribute' id="originalSource.id">id</span>: an OPTIONAL identifier for the relation;</li>
<li><span class='attribute' id="originalSource.derived">derived</span>: an identifier (<span class="name">e2</span>) for the derived entity; </li>
<li><span class='attribute' id="originalSource.source">source</span>: an identifier (<span class="name">e1</span>) for the original source entity;</li>
-<li><span class='attribute' id="originalSource.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs to further describe the properties of the relation.</li>
+<li><span class='attribute' id="originalSource.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this relation.</li>
</ul>
<div class="anexample">
@@ -1761,12 +1767,12 @@
some responsibility for <span class="name">e2</span>'s existence.
-<p><dfn title="tracedTo">Traceability</dfn><span class="withPn">, written <span class="pnExpression">tracedTo(id,e2,e1,attrs)</span> in PROV-N,</span> contains:</p>
+<p><dfn title="tracedTo">Traceability</dfn><span class="withPn">, written <span class="pnExpression">tracedTo(id,e2,e1,attrs)</span> in PROV-N,</span> has:</p>
<ul>
<li><span class='attribute' id="traceability.id">id</span>: an OPTIONAL identifier identifying the relation;</li>
<li><span class='attribute' id="traceability.entity">entity</span>: an identifier (<span class="name">e2</span>) for an entity;
<li><span class='attribute' id="traceability.ancestor">ancestor</span>: an identifier (<span class="name">e1</span>) for an ancestor entity that the former depends on;
-<li><span class='attribute' id="traceability.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs to further describe properties of the relation.</li>
+<li><span class='attribute' id="traceability.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this relation.</li>
</ul>
<p>We note that the ancestor is allowed to be an agent since agents are entities. </p>
@@ -1838,7 +1844,7 @@
<p>
-<div class="attributes" id="attributes-specialization">A <dfn title="specializationOf">specialization</dfn> relation<span class="withPn">, written <span class="pnExpression">specializationOf(sub, super)</span> in PROV-N,</span> has the following constituents:
+<div class="attributes" id="attributes-specialization">A <dfn title="specializationOf">specialization</dfn> relation<span class="withPn">, written <span class="pnExpression">specializationOf(sub, super)</span> in PROV-N,</span> has:
<ul>
<li><span class='attribute' id="specialization.specializedEntity">specializedEntity</span>: an identifier (<span class="name">sub</span>) of the specialized entity;</li>
@@ -1878,7 +1884,7 @@
-<p><div class="attributes" id="attributes-alternate">An <dfn title="alternateOf">alternate</dfn> relation<span class="withPn">, written <span class="pnExpression">alternateOf(e1, e2)</span> in PROV-N,</span> has the following constituents:
+<p><div class="attributes" id="attributes-alternate">An <dfn title="alternateOf">alternate</dfn> relation<span class="withPn">, written <span class="pnExpression">alternateOf(e1, e2)</span> in PROV-N,</span> has:
<ul>
<li><span class='attribute' id="alternate.alternate1">alternate1</span>: an identifier (<span class="name">e1</span>) of the first of the two entities;</li>
<li><span class='attribute' id="alternate.alternate2">alternate2</span>: an identifier (<span class="name">e2</span>) of the second of the two entities.</li>
@@ -1989,7 +1995,7 @@
<p><div class="attributes" id="attributes-derivedByInsertionFrom">
-<p>A <dfn title="derivedByInsertionFrom">Derivation-by-Insertion</dfn> relation<span class="withPn">, written <span class="pnExpression">derivedByInsertionFrom(id, c2, c1, {(key_1, e_1), ..., (key_n, e_n)}, attrs)</span>,</span> contains:</p>
+<p>A <dfn title="derivedByInsertionFrom">Derivation-by-Insertion</dfn> relation<span class="withPn">, written <span class="pnExpression">derivedByInsertionFrom(id, c2, c1, {(key_1, e_1), ..., (key_n, e_n)}, attrs)</span>,</span> has:</p>
<ul>
<li><span class='attribute' id="derivedByInsertionFrom.id">id</span>: an OPTIONAL identifier identifying the relation;</li>
<li><span class='attribute' id="derivedByInsertionFrom.after">after</span>: an identifier (<span class="name">c2</span>) for the collection <em>after</em> insertion; </li>
@@ -1997,7 +2003,7 @@
<li><span class='attribute' id="derivedByInsertionFrom.key-entity-set">key-entity-set</span>: the inserted key-entity pairs <span class="name">(key_1, e_1)</span>, ..., <span class="name">(key_n, e_n)</span> in which each <span class="name">key_i</span> is a <a>value</a>, and <span class="name">e_i</span> is an identifier for the entity that has been inserted with the key;
each <span class="name">key_i</span> is expected to be unique for the key-entity-set;
</li>
-<li><span class='attribute' id="derivedByInsertionFrom.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs to further describe the properties of the relation.</li>
+<li><span class='attribute' id="derivedByInsertionFrom.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this relation.</li>
</ul>
</div>
@@ -2066,13 +2072,13 @@
<p>
<div class="attributes" id="attributes-derivedByRemovalFrom">
-<p> A <dfn title="derivedByRemovalFrom">Derivation-by-Removal</dfn> relation, written <span class="pnExpression">derivedByRemovalFrom(id, c2, c1, {key_1, ... key_n}, attrs)</span>, contains:</p>
+<p> A <dfn title="derivedByRemovalFrom">Derivation-by-Removal</dfn> relation, written <span class="pnExpression">derivedByRemovalFrom(id, c2, c1, {key_1, ... key_n}, attrs)</span>, has:</p>
<ul>
<li><span class='attribute' id="derivedByRemovalFrom.id">id</span>: an OPTIONAL identifier identifying the relation;</li>
<li><span class='attribute' id="derivedByRemovalFrom.after">after</span>: an identifier (<span class="name">c2</span>) for the collection <em>after</em> the deletion; </li>
<li><span class='attribute' id="derivedByRemovalFrom.before">before</span>: an identifier (<span class="name">c1</span>) for the collection <em>before</em> the deletion;</li>
<li><span class='attribute' id="derivedByRemovalFrom.key-set">key-set</span>: a set of deleted keys <span class="name">key_1</span>, ..., <span class="name">key_n</span>, for which each <span class="name">key_i</span> is a <a>value</a>;</li>
-<li><span class='attribute' id="derivedByRemovalFrom.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs to further describe the properties of the relation.</li>
+<li><span class='attribute' id="derivedByRemovalFrom.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this relation.</li>
</ul>
</div>
@@ -2116,12 +2122,12 @@
<p>
<div class="attributes" id="attributes-memberOf">
- A <dfn title="memberOf">membership</dfn> relation, written <span class="pnExpression">memberOf(id, c, {(key_1, e_1), ..., (key_n, e_n)}, attrs)</span>, contains:
+ A <dfn title="memberOf">membership</dfn> relation, written <span class="pnExpression">memberOf(id, c, {(key_1, e_1), ..., (key_n, e_n)}, attrs)</span>, has:
<ul>
<li><span class='attribute' id="memberOf.id">id</span>: an OPTIONAL identifier identifying the relation;</li>
<li><span class='attribute' id="memberOf.after">after</span>: an identifier (<span class="name">c</span>) for the collection whose members are asserted; </li>
<li><span class='attribute' id="memberOf.key-entity-set">key-entity-set</span>: a set of key-entity pairs <span class="name">(key_1, e_1)</span>, ..., <span class="name">(key_n, e_n)</span> that are members of the collection;</li>
-<li><span class='attribute' id="memberOf.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs to further describe the properties of the relation.</li>
+<li><span class='attribute' id="memberOf.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this relation.</li>
</ul>
</div>
@@ -2198,12 +2204,15 @@
<h4>Note</h4>
-
-<p><div class="attributes" id="attributes-note">A <dfn>note</dfn><span class="withPn">, noted <span class="pnExpression">note(id, [attr1=val1, ...])</span> in PROV-N,</span> contains:
+<span class="glossary-ref" data-ref="glossary-note"></span>
+
+
+<p><div class="attributes" id="attributes-note">A <dfn title="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>), ...), whose meaning is application specific.</li>
-</ul></div>
+<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>
+</ul>
+</div>
@@ -2248,7 +2257,7 @@
be associated with a given identified object; symmetrically, multiple objects can be associated with a given note. Since notes have identifiers, they can also be
annotated. </p>
-<p></p><div class="attributes" id="attributes-annotation">An <dfn title="hasAnnotation">annotation relation</dfn><span class="withPn">, written <span class="pnExpression">hasAnnotation(r,n)</span> in PROV-N,</span> has the following constituents:
+<p></p><div class="attributes" id="attributes-annotation">An <dfn title="hasAnnotation">annotation relation</dfn><span class="withPn">, written <span class="pnExpression">hasAnnotation(r,n)</span> in PROV-N,</span> has:
<ul>
<li><span class='attribute' id="annotation.id">something</span>: the identifier (<span class="name">r</span>) of something being annotated;</li>
<li><span class='attribute' id="annotation.note">note</span>: an identifier (<span class="name">n</span>) of a note.</li>