--- a/model/prov-n.html Thu Apr 12 14:48:38 2012 +0100
+++ b/model/prov-n.html Thu Apr 12 14:48:55 2012 +0100
@@ -248,21 +248,30 @@
<section id="purpose">
<h2>Purpose of this Document and target audience</h2>
-This document describes PROV-N, a formal notation designed to express instances of the PROV data model in a way that is technology independent, and with human readabilty in mind. At the same time, PROV-N is a formal language, for which parsers can be implemented.
+A key goal of PROV-DM is the specification of a machine-processable data model for provenance. However, communicating provenance between humans is also important when teaching, illustrating, formalizing, and discussing provenance-related issues.
-PROV-N has several uses:
+<!-- As such, representations of PROV-DM are available in RDF and XML. -->
+
+With these two requirements in mind, this document introduces PROV-N, a syntax notation designed to write instances of the PROV-DM data model according to the following design principles:
+<ul>
+<li>Technology independence. PROV-N provides a simple syntax that can be mapped to technology-specific formats such as XML, RDF, JSON, and possibly more;
+
+<li>Human readability. PROV-N follows a functional syntax style that is meant to be easily human-readable so it can be used in illustrative examples, such as those presented in the PROV documents suite;
+
+<li>Formality. PROV-N is defined through a formal grammar amenable to be used with standard parser generators.
+
+ </ul>
+
+PROV-N has several known uses:
<ul>
<li> It is the notation used in the examples found in [[PROV-DM]], as well as in the definition of PROV-DM constraints [[PROV-DM-CONSTRAINTS]]; </li>
<li> It is a source language for the encoding of PROV-DM instances into a variety of target languages, including amongst others RDF [[PROV-RDF]] and XML [[PROV-XML]]; </li>
<li> It provides the basis for a formal semantics of PROV-DM [[PROV-SEM]], in which an interpretation is given to each element of the PROV-N language.
</ul>
-This document introduces the PROV-N grammar along with examples of its usage, and a justification for the language design choices.<br/>
-Its target audience includes primarily implementors of new PROV-DM encodings, and thus in particular of PROV-N parsers. It also includes those readers of the [[PROV-DM]] and of [[PROV-DM-CONSTRAINTS]] documents, who are interested in the details of the formal language underpinning the notation used in the examples and in the definition of the constraints.
+This document introduces the PROV-N grammar along with examples of its usage.<br/>
+Its target audience includes both developers of provenance management application, as well as implementors of new PROV-DM encodings, and thus in particular of PROV-N parsers. It also includes those readers of the [[PROV-DM]] and of [[PROV-DM-CONSTRAINTS]] documents, who are interested in the details of the formal language underpinning the notation used in the examples and in the definition of the constraints.
-<!--
-<p>PROV-N was designed to be as close as possible to PROV-DM without the syntactic bias and modelling constraints that concrete technologies bring with them, e.g., XML's choice between attribute and element, RDF's reliance on triples, or JSON's usage of dictionaries. </p>
--->
</section>
@@ -293,7 +302,7 @@
<h3>PROV-DM Namespace</h3>
-<p>The PROV namespace is <span class="name">http://www.w3.org/ns/prov#</span>.</p>
+<p>The PROV namespace is <span class="name">http://www.w3.org/ns/prov#</span> with prefix <span class="name">prov:</span>.</p>
<p> All the elements, relations, reserved names and attributes introduced in this specification belong to the PROV namespace.</p>
</section>
@@ -312,124 +321,33 @@
</section>
-<section id="prov-n-rationale">
-<h3>Design Rationale for PROV-N</h3>
-
-<p>A key goal of PROV-DM is the specification of a machine-processable data model for provenance so that application having obtained the provenance of the resource they manipulate can reason about such provenance. As such, representations of PROV-DM are available in RDF and XML.
-</p>
-
-<p>However, communicating provenance between humans is also important when teaching, illustrating, formalizing, and discussing provenance-related issues. To this end, PROV-N is a notation that is designed to write instances of the PROV-DM data model in a compact textual form, without the syntactic baggage and constraints coming with a markup language such as XML or a description framework such as RDF. </p>
-
-<ul>
-<li>PROV-N adopts a <em>functional notation</em> consisting a name and a series of arguments in bracket.
-<div class="anexample">
-<pre class="codeexample" >
-wasDerivedFrom(e2, e1, a, g2, u1)
-</pre>
-</div>
-</li>
-
-<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><p>
-PROV-N <em>optional arguments</em> need not be specified (as long as this does not lead to ambiguity).</p>
-<div class="anexample">
-<p>The activity, generation, and usage are specified in the first derivation, whereas they are not in the second.</p>
-<pre class="codeexample" >
-wasDerivedFrom(e2, e1, a, g2, u1)
-wasDerivedFrom(e2, e1)
-</pre>
-</div>
-
-<div class="anexample">
-<p>Activity <span class="name">a1</span> does not have start and end times specified, whereas <span class="name">a2</span> does</p>
-<pre class="codeexample" >
-activity(a1)
-activity(a2, 2011-11-16T16:00:00, 2011-11-16T16:00:01)
-</pre>
-</div>
-</li>
+<section id="grammar-notation">
+<h3>Functional-style Syntax</h3>
-<li><p>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.</p>
-<div class="anexample">
-<p>The activity, generation, and usage are specified in the first derivation, whereas they are not in the second, but have been explicitly marked as such.</p>
-<pre class="codeexample" >
-wasDerivedFrom(e2, e1, a, g2, u1)
-wasDerivedFrom(e2, e1, a, -, -)
-wasDerivedFrom(e2, e1, -, -, -)
-</pre>
-</div>
-
-<div class="anexample">
-<p>Activity <span class="name">a1</span> does not have start and end times specified, but they are been marked syntactically.</p>
-<pre class="codeexample" >
-activity(a1, -, -)
-</pre>
-</div>
-</li>
-
-<li><p>When an expression has an identifier, the identifier always occur in <em>first position</em>. For expressions with optional identifier, it may be replaced by the syntactic marker <span class="name">-</span>.</p>
-
-<div class="anexample">
-<p>Derivation has an optional identifier. In the first derivation, the identifier is not expressed. It is explicit in the second, and marked by a <span class="name">-</span> in the third.</p>
-<pre class="codeexample" >
-wasDerivedFrom(e2, e1)
-wasDerivedFrom(d, e2, e1)
-wasDerivedFrom(-, e2, e1)
-</pre>
-</div>
-
-<li><p>Most expressions have an optional set of attribute-value pairs, which occur in <em>last position</em>, and delimited by square brackets. </p>
-<div class="anexample">
-The first activity does not have any attributes. The second has an empty list of attributes. The third activity has two attributes.
-<pre class="codeexample" >
-activity(ex:a10)
-activity(ex:a10, [])
-activity(ex:a10, [ex:param1="a", ex:param2="b"])
-</pre>
-</div>
-<li id="positional-vs-named-attributes"> PROV-N exposes attributes that PROV-DM provides an interpretation for [[PROV-DM-CONSTRAINTS]] directly as positional arguments of expressions, whereas those for which PROV-DM provides no interpretation are expressed among the optional attribute-value pairs. This latter category of attributes
-includes
- <span class="name">prov:label</span>,
- <span class="name">prov:location</span>,
- <span class="name">prov:role</span>, and
- <span class="name">prov:type</span>.
-
-
-<li id="subject-object-order">
+<p> PROV-N adopts a functional-style syntax consisting of a relation name and an ordered list of terms.
All PROV-DM relations involve two primary elements, the <em>subject</em> and the <em>object</em>, in this order. Furthermore, some relations also admit additional elements that further characterize it.
<div class="anexample">
The following expression should be read as "<span class="name">e2</span> was generated by <span class="name">e1</span>". Here <span class="name">e2</span> is the subject, and <span class="name">e1</span> is the object.
<pre class="codeexample" >
wasDerivedFrom(e2, e1)
</pre>
-In the following expression, the optional activity <span class="name">a</span> has been added to further qualify the derivation:
+ </div>
+
+<div class="anexample">
+In the following expressions, the optional activity <span class="name">a</span> along with the generation and usage IDs, and timestamps have been added to further qualify the derivation:
<pre class="codeexample" >
wasDerivedFrom(e2, e1, a)
+wasDerivedFrom(e2, e1, a, g2, u1)
+activity(a2, 2011-11-16T16:00:00, 2011-11-16T16:00:01)
</pre>
-
</div>
-</li>
-</ul>
-
-
-
-
-</section>
-
-<section id="grammar-notation">
-<h3>Grammar Notation</h3>
-
-<p>This specification includes a grammar for PROV-N expressed using the Extended Backus-Naur Form (EBNF) notation.</p>
-
+The grammar is specified using the Extended Backus-Naur Form (EBNF) notation.<br/>
+Each production rule (or <dfn>production</dfn>, for short) in the grammar defines one non-terminal symbol <span class="nonterminal">E</span>, in the following form:</p>
<div class="grammar">
-<p> Each production rule (or <dfn>production</dfn>, for short) in the grammar defines one non-terminal symbol, in the form:</p>
-<p>
<span class="nonterminal">E</span> ::= <em>expression</em>
-</p>
-
+</div>
Within the expression on the right-hand side of a rule, the following expressions are used to match strings of one or more characters:
<ul>
@@ -455,17 +373,10 @@
</li>
</ul>
-</div>
-
-</section>
-<section id="prov-n-expressions">
-<h2>PROV-N Productions per Component</h2>
+<div class="note">this is confusing. look at http://www.w3.org/TR/owl2-syntax/#BNF_Notation for example</div>
-<p>A PROV-N document consists of a sequence of <a title="expression">expressions</a>, wrapped up in an <a>expression container</a> with some namespace declarations. This section focuses on the definition of <a title="expression">expressions</a>. </p>
-
-
-<p>Instances of the PROV-DM data model are expressed as PROV-N <dfn title="expression">expressions</dfn>, which have a text conformant with the toplevel <a>production</a> <span class="nonterminal">expression</span> of the grammar. </p>
+The top level nonterminal of the grammar is <span class="nonterminal">expression</span>, defined as follows.
<div class='grammar'>
<table style="background: white; border=0; ">
@@ -508,9 +419,108 @@
</table>
</div>
-<p>In the rest of the section, productions are presented for each expression, followed by small examples illustrating the syntax of expressions compliant with the presented productions. </p>
+Each expression type, of the form <span class="nonterminal">XExpression</span>, i.e., <span class="nonterminal">entityExpression</span>, <span class="nonterminal">activityExpression</span> etc., corresponds to one element X (entity, activity, etc.) of PROV-DM.
+<p>A PROV-N document consists of a collection of <a title="expression">expressions</a>, wrapped in an <a>expression container</a> with some namespace declarations, such that the text for an element X matches the corresponding <span class="nonterminal">XExpression</span> production of the grammar.
+
+</section>
+
+<section id="prov-n-conventions">
+<h3>General grammar conventions</h3>
+
+The following conventions are introduced concerning the specification of optional terms in an expression, of default terms, and of terms whose value is not specified, either because it is not available, or because it does not apply.
+<section id="prov-n-optionals">
+<h3>Optional terms in a relation expression</h3>
+
+Some terms in a relation may be optional. For example:
+
+<div class="anexample">
+<pre class="codeexample" >
+wasDerivedFrom(e2, e1, a, g2, u1)
+wasDerivedFrom(e2, e1)
+</pre>
+In a derivation expression, the activity, generation, and usage are optionals. They are specified in the first derivation, but not in the second.
+</div>
+
+<div class="anexample">
+<pre class="codeexample" >
+activity(a2, 2011-11-16T16:00:00, 2011-11-16T16:00:01)
+activity(a1)
+</pre>
+The start and end times for Activity <span class="name">a1</span> are optional. They are specified in the first expression, but not in the second.
+</div>
+
+The general rule for optionals is that, if <em>none</em> of the optionals are used in the expression, then they are simply omitted, resulting in a simpler expression as in the examples above.<br/>
+However, it may be the case that only some of the optional terms are omitted. Because the position of the terms in the expression matters, in this case an additional marker must be used to indicate that a particular term is not available. The symbol <span class="name">-</span> is used for this purpose.
+
+<div class="anexample">
+<p>In the first expression below, all optionals are specified. However in the second, only the last one is specified, forcing the use of the marker for the missing terms. In the last, no marker is necessary because all <em>remaining</em> optionals after <span class="name">a</span> are missing.
+
+<pre class="codeexample" >
+wasDerivedFrom(e2, e1, a, g2, u1)
+wasDerivedFrom(e2, e1, -, -, u1)
+wasDerivedFrom(e2, e1, a)
+</pre>
+</div>
+Note that the more succinct form is just shorthand for a complete expression with all the markers specified:
+<div class="anexample">
+<pre class="codeexample" >
+activity(a1)
+activity(a1, -, -)
+</pre>
+</div>
+</li>
+
+</section>
+
+<section id="prov-n-standard-terms">
+<h3>Relation identifiers and attributes</h3>
+
+Most expression types defined in the grammar include the use of two terms: an identifier for the relation, and a set of attribute-value pairs, delimited by square brackets. Both are optional (unless specified otherwise). By convention, the identifier is the first term in any expression type, and the set of attribute-value pairs is the last. <br/>
+Consistent with the convention on optional terms, the '<span class="name">-</span>' marker can be used when the identifier is not available. Additionally, the grammar rules are defined in such a way that the optional identifier can be omitted altogether with no ambiguity arising.
+
+<div class="anexample">
+<p>Derivation has an optional identifier. In the first expression, the identifier is not available. It is explicit in the second, and marked by a <span class="name">-</span> in the third.</p>
+<pre class="codeexample" >
+wasDerivedFrom(e2, e1)
+wasDerivedFrom(d, e2, e1)
+wasDerivedFrom(-, e2, e1)
+</pre>
+</div>
+
+A distinction is made between relations with no attributes, and relations that include an empty list of attributes.
+<div class="anexample">
+<p>The first activity does not have any attributes. The second has an empty list of attributes. The third activity has two attributes.
+<pre class="codeexample" >
+activity(ex:a10)
+activity(ex:a10, [])
+activity(ex:a10, [ex:param1="a", ex:param2="b"])
+</pre>
+</div>
+
+</section>
+
+<section id="prov-n-attributes">
+<h3>Optional attributes</h3>
+
+<div class="note">This looks out of place --- why is this not in DM? </div>
+
+Name-value attribute pairs are intended for arbitrary, user-defined terms that are used to qualify the relation. Amongst these, a few are defined as standard in PROV-DM. These are:
+ <span class="name">prov:label</span>,
+ <span class="name">prov:location</span>,
+ <span class="name">prov:role</span>, and
+ <span class="name">prov:type</span>.
+
+</section>
+
+
+</section> <!-- conventions for optionals etc. -->
+
+<section id="prov-n-expressions">
+<h2>PROV-N Productions per Component</h2>
+
+This section introduces grammar productions for each expression type, followed by small examples illustrating the use of expressions in PROV-N. </p>
<section id="component1">
@@ -521,7 +531,9 @@
<div class="withPn">
<p>
-An entity's text matches the <span class="nonterminal">entityExpression</span> production.
+ The <span class="nonterminal">entityExpression</span> production is used to express entity relations:
+
+ <div class="note">only changed here to see if it works</div>
</p>
<div class='grammar'>
--- a/primer/Primer.html Thu Apr 12 14:48:38 2012 +0100
+++ b/primer/Primer.html Thu Apr 12 14:48:55 2012 +0100
@@ -31,7 +31,13 @@
"Satya Sahoo, Deborah McGuinness"+
"<a href=\"http://www.w3.org/TR/2011/WD-prov-o-20111213/\"><cite>The PROV Ontology: Model and Formal Semantics</cite></a>. "+
"13 December 2011. W3C Working Draft. (Work in progress.) "+
- "URL: <a href=\"http://www.w3.org/TR/2011/WD-prov-o-20111213/\">http://www.w3.org/TR/2011/WD-prov-o-20111213</a>"
+ "URL: <a href=\"http://www.w3.org/TR/2011/WD-prov-o-20111213/\">http://www.w3.org/TR/2011/WD-prov-o-20111213</a>",
+
+ "TURTLE":
+ "Eric Prud'hommeaux, Gavin Carothers"+
+ "<a href=\"http://www.w3.org/TR/2011/WD-turtle-20110809/\"><cite>Turtle: Terse RDF Triple Language</cite></a>. "+
+ "9 August 2011. W3C Working Draft. "+
+ "URL: <a href=\"http://www.w3.org/TR/2011/WD-turtle-20110809/\">http://www.w3.org/TR/2011/WD-turtle-20110809/</a>"
};
var respecConfig = {
@@ -126,8 +132,8 @@
PROV data model for provenance [[PROV-DM]]. PROV-DM is a core data model for
provenance for building representations of the entities, people and
processes involved in producing a piece of data or thing in the world.
- This primer explains the fundamental PROV-DM concepts in non-normative
- terms, and provides worked examples applying the PROV-O OWL2
+ This primer explains the fundamental PROV-DM concepts in an illustrative
+ fashion, and provides examples applying the PROV-O OWL2
ontology [[PROV-O]]. The primer is intended as a starting point for those wishing
to create or make use of PROV-DM data.
</p>
@@ -141,9 +147,9 @@
This document is part of a set of specifications aiming to define the
various aspects that are necessary to achieve the vision of
interoperable interchange of provenance information in heterogeneous
- environments such as the Web. This document is a non-normative,
+ environments such as the Web. This document is an
intuitive introduction and guide to the [[PROV-DM]] data model for
- provenance. It includes simple worked examples applying the [[PROV-O]]
+ provenance. It includes simple examples applying the [[PROV-O]]
OWL2 ontology.
</section>
@@ -151,22 +157,22 @@
<h2>Introduction</h2>
<p>
This primer document provides an accessible introduction to the PROV Data Model
- ([[PROV-DM]]) standard for representing provenance on the Web, and its representation
+ ([[PROV-DM]]) specification for representing provenance on the Web, and its expression
in the PROV Ontology ([[PROV-O]]). Provenance describes
the origins of things, so PROV-DM data consists of descriptions about the past.
</p>
<p>
- This primer document aims to ease the adoption of the standard by providing:
+ This primer document aims to ease the adoption of the specifications by providing:
</p>
<ul>
<li>An intuitive explanation of how PROV-DM models provenance.</li>
- <li>Worked examples that can be followed to produce your own PROV-DM data.</li>
+ <li>Examples that can be followed to produce new PROV-DM data.</li>
</ul>
<p>
The <i>provenance</i> of digital objects represents their origins. The PROV-DM is a
- proposed standard to represent provenance records, which contain <i>descriptions</i> of the entities
+ proposed specification to represent provenance records, which contain <i>descriptions</i> of the entities
and activities involved in producing and delivering or otherwise influencing a
given object.
For the remainder of this document, we use the term 'provenance' to refer also
@@ -180,7 +186,7 @@
</p>
<p>
- As a standard for provenance, PROV-DM accommodates all those different uses
+ As a specification for provenance, PROV-DM accommodates all those different uses
of provenance. Different people may have different perspectives on provenance,
and as a result different types of information might be captured in provenance records.
One perspective might focus on <i>agent-centered provenance</i>, that is, what entities
@@ -209,8 +215,8 @@
vocabularies for provenance are available from the
<a href="http://www.w3.org/2005/Incubator/prov/XGR-prov/">Final Report of the W3C Provenance Incubator Group</a>.
That document contains three general scenarios
- that may help identify the provenance aspects of your planned applications and
- help plan the design of your provenance system.
+ that may help identify the provenance aspects of planned applications and
+ help plan the design of a provenance system.
</p>
<p>
The next section gives an introductory overview of PROV-DM using simple examples.
@@ -227,11 +233,11 @@
<p>
This section provides an intuitive explanation of the concepts in PROV-DM.
As with the rest of this document, it should be treated as a starting point for
- understanding the model, and not normative in itself. The PROV-DM model specification
+ understanding the model. The PROV-DM model specification
provides precise definitions and constraints to be used.
</p>
<p>
- The following ER diagram provides a high level overview of the structure of PROV-DM records,
+ The following diagram provides a high level overview of the structure of PROV-DM records,
limited to some key PROV-DM concepts discussed in this document.
The diagram is the same that appears in the [[PROV-DM]].
</p>
@@ -243,12 +249,15 @@
<h3>Entities</h3>
<p>
- In PROV-DM, the things that one may ask the provenance of are called <i>entities</i>.
+ In PROV-DM, physical, digital, conceptual, or other kinds of thing are called
+ <i>entities</i>.
Examples of such entities are a web page, a chart, and a spellchecker.
- An entity’s provenance may refer to many other entities. For example, a document D is
+ Provenance records can describe the provenance of entities, and
+ an entity’s provenance may refer to many other entities. For example, a document D is
an entity whose provenance refers to other entities such as a chart inserted into D,
the dataset that was used to create that chart, or the author of the document.
- Entities may be described from different perspectives that may be more or less specific. For example,
+ Entities may be described as having different attributes and
+ be described from different perspectives. For example,
document D as stored in my file system, the second version of document D,
and D as an evolving document,
are three distinct entities for which we may describe provenance.
@@ -276,27 +285,28 @@
Activities <i>generate</i> new entities.
For example, writing a document brings the document into existence, while
revising the document brings a new version into existence.
- An activity may complete with the generation of an entity or generate entities
- mid-way through occurring.
+ Generation does not always occur at the end of an activity, and an activity may generate entities
+ part-way through.
Activities also make <i>use</i> of entities. For example, revising a document
to fix spelling mistakes uses the original version of the document as well
as a list of corrections.
- Descriptions can be included, in PROV-DM data, of
- particular activities using or generating particular entities.
</p>
</section>
<section>
<h3>Agents and Responsibility</h3>
<p>
- An <i>agent</i> is a type of entity that takes an active role in an activity such
+ An <i>agent</i> is a type of entity that takes an role in an activity such
that it can be assigned some degree of <i>responsibility</i> for the activity taking
- place. An agent can be a person, a piece of software, an inanimate object, an organization, or
+ place.
+ An agent can be a person, a piece of software, an inanimate object, an organization, or
other entities that may be ascribed responsibility.
- Several agents can be associated with an activity.
+ When an agent has some responsibility for an activity, PROV-DM says the agent was
+ <i>associated</i> with the activity, where several agents may be associated with
+ an activity and vice-versa.
Consider a chart displaying some statistics
regarding crime rates over time in a linear regression. To represent the
- provenance of a that chart, we could state that the person who created the
+ provenance of that chart, we could state that the person who created the
chart was an agent involved in its creation, and that the software used to
create the chart was also an agent involved in that activity.
An agent may be <i>acting on behalf</i> of others, e.g. an employee on behalf of their
@@ -332,10 +342,10 @@
<h3>Derivation and Revision</h3>
<p>
When one entity's existence, content, characteristics and so on are
- at least partly due to another entity, then we say that the former is
+ at least partly due to another entity, then we say that the former was
<i>derived</i> from the latter. For example, one document may contain
material copied from another,
- and a chart is derived from the data that is used to create it.
+ and a chart was derived from the data that it illustrates.
</p>
<p>
PROV allows some common, specialized kinds of derivation to be described.
@@ -343,8 +353,8 @@
(also called versions and other comparable terms) over time. Between revisions,
one or more attributes of the entity may change.
The result of each revision is a new entity,
- and PROV-DM allows one to relate those entities by making an description that
- one is a revision of another.
+ and PROV-DM allows one to relate those entities by making a description that
+ one was a revision of another.
Another specialized kind of derivation is to say that one entity, commonly
a document, <i>quotes</i> from another.
</p>
@@ -402,18 +412,18 @@
</section>
<section>
- <h2>Examples of Use of the PROV-O Ontology</h2>
+ <h2>Examples</h2>
<p>
In the following sections, we show how PROV-DM can be used to model
- provenance in a specific example.
+ provenance in a specific example scenario.
</p>
<p>
We include samples of how the formal ontology PROV-O
can be used to represent the PROV-DM descriptions as RDF triples.
- These are shown using the Turtle notation. In
+ These are shown using the Turtle notation [[TURTLE]]. In
the latter depictions, the namespace prefix <b>prov</b> denotes
- terms from the Prov ontology, while <b>ex</b> denotes terms specific to the example.
+ terms from the PROV ontology, while <b>ex</b> denotes terms specific to the example.
</p>
<p>We also provide a representation of the examples in the Provenance
@@ -534,7 +544,7 @@
declares that he acts on their behalf. Note that the organization is itself
an agent.
</p>
- <pre>
+ <pre class="turtle example">
ex:derek prov:actedOnBehalfOf ex:chartgen .
ex:chartgen a prov:Agent ;
a prov:Organization ;
@@ -544,7 +554,7 @@
Finally, there is an explicit statement in the provenance that the chart was
attributed to Derek.
</p>
- <pre>
+ <pre class="turtle example">
ex:chart1 prov:wasAttributedTo ex:derek .
</pre>
</section>
@@ -577,7 +587,7 @@
</pre>
<p>
Examples in the sections above show descriptions of the simple facts that the
- composition activity used, generated and was controlled by entities/agents.
+ composition activity used, generated and was enacted by entities/agents.
For example, the usage of the data set by the compose activity is expressed
as follows.
</p>
@@ -618,7 +628,7 @@
</pre>
<p>
Similarly, the provenance includes descriptions that the same activity was
- controlled in a particular way (<code>ex:analyst</code>) by Derek, and that
+ enacted in a particular way (<code>ex:analyst</code>) by Derek, and that
the entity <code>ex:composition</code> took the role of the composed
data in what the activity generated.
</p>
@@ -644,7 +654,7 @@
to be nothing wrong, so Betty concludes the error is in the government dataset.
She looks at the dataset <code>ex:dataSet1</code>,
and sees that it is missing data from one of the zipcodes in the area. She contacts
- the government, and a new version of GovData is created, declared to be the
+ the government agency, and a new version of GovData is created, declared to be the
next revision of the data. The provenance of this new dataset,
<code>ex:dataSet2</code>, states that it is a revision of the
old data set, <code>ex:dataSet1</code>.
@@ -655,7 +665,7 @@
</pre>
<p>
Derek notices that there is a new dataset available and creates a new chart based on the revised data,
- using the same compilation activity as before. Betty checks the article again at a
+ using another compilation activity. Betty checks the article again at a
later point, and wants to know if it is based on the old or new GovData.
She sees a new description stating that the new chart is derived from the new dataset.
</p>
@@ -674,23 +684,23 @@
<code>ex:dataSet2</code>, describes not only who performed the corrections,
Edith, but also what instructions she followed in doing so (in PROV terms, the plan).
First, the correction activity (<code>ex:correct</code>), the person who corrected
- it, Edith (<code>ex:edith</code>), and the correction instructions (<code>ex:corrections</code>)
+ it, Edith (<code>ex:edith</code>), and the correction instructions (<code>ex:instructions</code>)
are described.
<pre class="turtle example">
- ex:correct a prov:Activity .
- ex:edith a prov:Agent, prov:Person .
- ex:corrections a prov:Plan .
+ ex:correct a prov:Activity .
+ ex:edith a prov:Agent, prov:Person .
+ ex:instructions a prov:Plan .
</pre>
<p>
The connection between them is expressed in PROV-O using a qualified association giving details of
how Edith was associated with the correction activity,
- including that she followed the above corrections plan.
+ including that she followed the above correction instructions.
</p>
<pre class="turtle example">
ex:correct prov:qualifiedAssociation [
a Association ;
prov:agent ex:edith ;
- prov:hadPlan ex:corrections
+ prov:hadPlan ex:instructions
] .
ex:dataSet2 prov:wasGeneratedBy ex:correct .
</pre>
@@ -814,12 +824,12 @@
<section>
<h3>Use and Generation</h3>
<pre class="example asn">
- used(ex:compose, ex:dataSet1, _)
- used(ex:compose, ex:regionList, _)
- wasGeneratedBy(ex:composition, ex:compose, _)
+ used(ex:compose, ex:dataSet1, -)
+ used(ex:compose, ex:regionList, -)
+ wasGeneratedBy(ex:composition, ex:compose, -)
- used(ex:illustrate, ex:composition, _)
- wasGeneratedBy(ex:chart1, ex:illustrate, _)
+ used(ex:illustrate, ex:composition, -)
+ wasGeneratedBy(ex:chart1, ex:illustrate, -)
</pre>
</section>
@@ -828,8 +838,8 @@
<pre class="example asn">
agent(ex:derek, [ prov:type="prov:Person", foaf:givenName = "Derek",
foaf:mbox= "<mailto:derek@example.org>"])
- wasAssociatedWith(ex:compose, ex:derek, _)
- wasAssociatedWith(ex:illustrate, ex:derek, _)
+ wasAssociatedWith(ex:compose, ex:derek, -)
+ wasAssociatedWith(ex:illustrate, ex:derek, -)
agent(ex:chartgen, [ prov:type="prov:Organization",
foaf:name = "Chart Generators Inc"])
@@ -846,8 +856,8 @@
relations. Thus, the entire Turtle example in Section 3.5 is rendered as follows:
</p>
<pre class="example asn">
- used(ex:compose, ex:dataSet1, [ prov:role = "prov:dataToCompose"], _)
- used(ex:compose, ex:regionList, [ prov:role = "prov:regionsToAggregteBy"], _)
+ used(ex:compose, ex:dataSet1, [ prov:role = "ex:dataToCompose"], -)
+ used(ex:compose, ex:regionList, [ prov:role = "ex:regionsToAggregteBy"], -)
</pre>
<p>
In the first description above, note that this adds a "role" attribute to the first 'used' description of A.3.
@@ -858,7 +868,7 @@
<section>
<h3>Derivation and Revision</h3>
<pre class="example asn">
- wasRevisionOf(ex:dataSet2, ex:dataSet1, _)
+ wasRevisionOf(ex:dataSet2, ex:dataSet1, -)
</pre>
<pre class="example asn">
@@ -872,7 +882,7 @@
Similarly to roles, plans are attributes of relations, specifically association relations.
</p>
<pre class="example asn">
- wasAssociatedWith(ex:correct, ex:edith, ex:corrections)
+ wasAssociatedWith(ex:correct, ex:edith, ex:instructions)
</pre>
</section>
@@ -934,6 +944,7 @@
<li>Added intuition section on quotation.</li>
<li>Added PROV-O examples for time</li>
<li>Updated old PROV-N and added new PROV-N for all recently added concepts</li>
+ <li>Many minor corrections from Working Group reviewers</li>
</ul>
</section>