--- a/primer/Primer.html Fri Jul 06 13:37:23 2012 -0400
+++ b/primer/Primer.html Fri Jul 06 18:43:11 2012 +0100
@@ -46,12 +46,24 @@
"Working Draft, "+
"URL: <a href=\"http://www.w3.org/TR/prov-aq/\">http://www.w3.org/TR/prov-aq/</a>",
+ "PROV-CONSTRAINTS":
+ "James Cheney, Paolo Missier, Luc Moreau"+
+ "<a href=\"http://www.w3.org/TR/prov-constraints/\"><cite>Constraints of the Provenance Data Model</cite></a>. "+
+ "Working Draft, "+
+ "URL: <a href=\"http://www.w3.org/TR/prov-constraints/\">http://www.w3.org/TR/prov-constraints/</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>"
- };
+ "URL: <a href=\"http://www.w3.org/TR/2011/WD-turtle-20110809/\">http://www.w3.org/TR/2011/WD-turtle-20110809/</a>",
+
+ "PROVENANCE-XG":
+ "Yolanda Gil, James Cheney, Paul Groth, Olaf Hartig, Simon Miles, Luc Moreau, Paulo Pinheiro da Silva"+
+ "<a href=\"http://www.w3.org/2005/Incubator/prov/XGR-prov/\"><cite>Provenance XG Final Report</cite></a>. "+
+ "8 December 2010. "+
+ "URL: <a href=\"http://www.w3.org/2005/Incubator/prov/XGR-prov/\">http://www.w3.org/2005/Incubator/prov/XGR-prov/</a>"
+ };
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
@@ -196,14 +208,14 @@
This primer document provides an accessible introduction to the PROV
specification for provenance on the Web.
The <i>provenance</i> of digital objects represents their origins. PROV is a
- proposed specification to represent provenance records,
+ proposed specification to express 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
to records of provenance, except where the distinction is important for clarity.
By knowing the provenance of an object, we can perceive how to
- how use it. Provenance can be used for many purposes, such as
+ use it. Provenance can be used for many purposes, such as
understanding how data was collected so it can be meaningfully used, determining
ownership and rights over an object, making judgments about information to
determine whether to trust it, verifying that the process and steps used to obtain a
@@ -244,7 +256,7 @@
For general background on provenance, a
comprehensive overview of requirements, use cases, prior research, and proposed
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>.
+ Final Report of the W3C Provenance Incubator Group [[PROVENANCE-XG]].
That document contains three general scenarios
that may help identify the provenance aspects of planned applications and
help plan the design of a provenance system.
@@ -265,7 +277,7 @@
<p>There are additional reference documents for PROV that are not covered in this
primer, including the PROV Access and Query aspects of the specification [[PROV-AQ]],
- the constraints on the PROV data model (PROV-DM-CONSTRAINTS),
+ the constraints on the PROV data model [[PROV-CONSTRAINTS]],
a formal semantics of the PROV data model (PROV-SEM), and the PROV XML notation
(PROV-XML). </p>
@@ -277,8 +289,8 @@
<p>
This section provides an intuitive explanation of the main concepts in PROV.
As with the rest of this document, it should be treated as a starting point for
- understanding the model. The PROV-DM data model document [[PROV-DM]]
- provides precise definitions and constraints to be used.
+ understanding the model. The PROV data model document [[PROV-DM]]
+ provides precise definitions and constraints [[PROV-CONSTRAINTS]] to be used.
</p>
<p>
The following diagram provides a high level overview of the structure of PROV records,
@@ -286,7 +298,6 @@
The diagram is the same that appears in the [[PROV-DM]] document.
Note that because PROV is meant to describe how things were created or delivered,
PROV relations are named so they can be used in assertions about the past.
- This also affects the domain and range of the relations in PROV.
</p>
<div style="text-align: center;">
@@ -324,20 +335,21 @@
For example, if the second version of document D was generated
by a translation from the first version of the document in another language,
then this translation is an activity.
- </p>
+ </p>Use
</section>
<section>
- <h3>Use and Generation</h3>
+ <h3>Usage and Generation</h3>
<p>
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.
+ 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.
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.
+ Likewise, usage does not always occur at the beginning of an activity.
</p>
</section>
@@ -381,8 +393,8 @@
<p>
A <i>role</i> is a description of the function or the part that an entity
played in an activity. Roles specify
- the relationship between an entity and an activity, whether
- how an activity used an entity or generated an entity. Roles also specify how agents are
+ the relationship between an entity and an activity, i.e. how
+ the activity used or generated the entity. Roles also specify how agents are
involved in an activity, qualifying their participation in the activity or
specifying for what aspect of it each agent was responsible.
For example, an agent may play the role of "editor" in an activity that uses
@@ -441,7 +453,7 @@
<p>
Entities are defined in a flexible way in PROV, allowing for different
perspectives to be taken as appropriate for the application. The following
- are examples illustrate this idea.
+ are examples illustrating this idea.
</p>
<ul>
<li>The same entity can appear with different descriptions in a provenance record
@@ -481,8 +493,8 @@
<p>
In the following sections, we show how PROV can be used to model
provenance in a specific example scenario. Samples of PROV data are given.
- These samples use the namespace prefix <b>prov</b> denotes
- terms from the PROV ontology, while <b>ex</b> denotes terms specific to the example.
+ These samples use the namespace prefixes <b>prov</b>, denoting
+ terms from the PROV ontology, and <b>ex</b>, denoting terms specific to the example.
We illustrate in these examples how PROV can be used in combination with other
languages, such as FOAF and Dublin Core (with namespace prefix <b>foaf</b> and
<b>dcterms</b> respectively).
@@ -492,7 +504,7 @@
</p>
<ul>
<li>[[PROV-O]] RDF triples, expressed using the [[TURTLE]] notation.</li>
- <li>[[PROV-N]] productions.</li>
+ <li>[[PROV-N]] expressions.</li>
</ul>
<p>
Select the formats to display using the buttons below. Note that if all formats
@@ -569,7 +581,7 @@
a list of regions (<code>ex:regionList</code>),
data aggregated by region (<code>ex:composition</code>),
and a chart (<code>ex:chart1</code>), and state that each is an entity.
- Any entity may have attributes not specific to provenance, such as the title
+ Any entity may have attributes, such as the title
of the article, expressed using <code>dcterms:title</code> above.
</p>
<p>
@@ -635,12 +647,12 @@
</section>
<section>
- <h3>Use and Generation</h3>
+ <h3>Usage and Generation</h3>
<p>
Concluding the basic description of what occurred, the provenance
describes the key relations among the above
- entities and activities, i.e. the use of an entity by an activity,
+ entities and activities, i.e. the usage of an entity by an activity,
or the generation of an entity by an activity.
</p>
<p>
@@ -688,7 +700,7 @@
</div>
<p>
In visualizing the PROV data, usage and generation are connections between
- entities and activities.
+ entities and activities. The arrows point from the future to the past.
</p>
<img src="images/use-generate.png" alt="Connection of the entities and activities by use and generation links"/>
</section>
@@ -787,7 +799,7 @@
<p>
We can extend our graphical depiction to show the agents, association and attribution links.
</p>
- <img src="images/agents.png" alt="Agents added to provenance graph and linked to entities and activities"/>
+ <img src="images/agents.png" alt="Agents added to provenance graph and linked to entities and activities" width="95%"/>
</section>
<section>
@@ -835,7 +847,7 @@
provenance can contain more details of exactly how these entities and agents
were involved in the activity.
To express this, PROV-O refers to <i>qualified usage</i>, <i>qualified generation</i>, etc.,
- which are descriptions consisting of several statements about how use, generation, etc. took place.
+ which are descriptions consisting of several statements about how usage, generation, etc. took place.
For example, we may describe the plan followed by an agent in performing an activity, or
the time at which an activity generated an entity, both illustrated later.
Another example of qualified involvement is the role an entity played in an activity.
@@ -1114,7 +1126,7 @@
Time is visualized as additional information regarding activities or the
links between activities and entities or agents.
</p>
- <img src="images/time.png" alt="Annotation of provenance graph with example timestamps"/>
+ <img src="images/time.png" alt="Annotation of provenance graph with example timestamps" width="95%"/>
</section>
<section>
@@ -1205,7 +1217,7 @@
The set of provenance records above could be grouped into one or multiple bundles.
We visualize the whole example as a single bundle below.
</p>
- <img src="images/everything.png" alt="Provenance graph for whole example"/>
+ <img src="images/everything.png" alt="Provenance graph for whole example" width="95%"/>
</section>
</section>