--- a/model/working-copy/towards-wd4.html Tue Feb 07 16:50:34 2012 +0000
+++ b/model/working-copy/towards-wd4.html Tue Feb 07 21:15:54 2012 +0000
@@ -172,10 +172,112 @@
</section>
-<!--
-<section id='preliminaries'>
-<h2>Preliminaries</h2>
--->
+
+ <section id="introduction">
+ <h2>Introduction<br>
+</h2>
+
+<p>
+For the purpose of this specification, <dfn>provenance</dfn> is defined as a record that describes the people,
+institutions, entities, and activities, involved in producing,
+influencing, or delivering a piece of data or a thing in the world.
+In particular, the provenance of information is crucial in deciding
+whether information is to be trusted, how it should be integrated with
+other diverse information sources, and how to give credit to its
+originators when reusing it. In an open and inclusive environment
+such as the Web, users find information that is often contradictory or
+questionable: provenance can help those users to make trust judgments.
+</p>
+
+
+<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,
+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 inter-operable
+way, the first of which is this document:</p>
+<ul>
+<li>PROV-DM: a data model for provenance, accompanied with a notation to express instances of that data model for human consumption (this document); </li>
+<li>PROV-O: a normative serialization of PROV-DM in RDF [[!PROV-O]], specified by means of a mapping to the OWL2 Web Ontology Language [[!OWL2-SYNTAX]];</li>
+<li>PROV-AQ: the mechanisms for accessing and querying provenance [[!PROV-AQ]];</li>
+<li>PROV-PRIMER: a primer for the PROV approach [[!PROV-PRIMER]];</li>
+<li>PROV-SEM: semantics of the PROV-DM data model [[PROV-SEM]];</li>
+</ul>
+
+
+<p>
+The PROV-DM data model for provenance consists of a set of core
+concepts, and a few common relations, based on these core concepts. PROV-DM is a domain-agnotisc model, but with clear extensibility points allowing further domain-specific and
+application-specific extensions to be defined.</p>
+
+<p>This specification also introduces
+PROV-ASN, an abstract syntax that is primarily aimed at human consumption. PROV-ASN allows
+serializations of PROV-DM instances to be written in a technology independent manner,
+it facilitates its mapping to concrete syntax, and it is used as the basis for a
+formal semantics. This specification uses instances of provenance written in PROV-ASN
+to illustrate the data model.
+</p>
+
+ <section id="structure-of-this-document">
+<h3>Structure of this Document</h3>
+
+<p>In <a href="#preliminaries">section 2</a>, a set of preliminaries are introduced, including concepts that underpin PROV-DM and motivations for the PROV-ASN notation.</p>
+
+<p><a href="#prov-dm-overview">Section 3</a> provides an overview of PROV-DM listing its core types and their relations.</p>
+
+<p>In <a href="#prov-dm-example">section 4</a>, PROV-DM is
+applied to a short scenario, encoded in PROV-ASN, and illustrated
+graphically.</p>
+
+<p><a href="#data-model-concepts">Section 5</a> provides the normative definition of PROV-DM and the notation PROV-ASN.</p>
+
+<p><a href="#common-relations">Section 6</a> introduces further relations offered by PROV-DM, including relations for data collections and domain-independent common relations.</p>
+
+<p><a href="#interpretation">Section 7</a> provides an interpretation of PROV-DM in terms of ordering constraints between events, and also presents a set of structural constraints to be
+satisfied by PROV-DM.</p>
+
+<p><a href="#extensibility-section">Section 8</a> summarizes PROV-DM extensibility points.</p>
+
+<p><a href="#resource-section">Section 9</a> discusses how PROV-DM can be applied to the notion of resource.</p>
+
+
+ </section>
+
+<section id="prov-dm-namespace">
+ <h3>PROV-DM Namespace</h3>
+
+
+<p>The PROV-DM namespace is <span class="name">http://www.w3.org/ns/prov-dm/</span> (TBC).</p>
+
+<p> All the elements, relations, reserved names and attributes introduced in this specification belong to the PROV-DM namespace.</p>
+
+<div class="issue">
+There is a desire to use a single namespace that all specifications of the PROV family can share to refer to common provenance terms. This is <a href="http://www.w3.org/2011/prov/track/issues/224">ISSUE-224</a>.
+</div>
+
+</section>
+
+
+ <section id="conventions">
+<h3>Conventions</h3>
+
+
+
+<p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
+ NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
+ "OPTIONAL" in this document are to be interpreted as described in
+ [[!RFC2119]].</p>
+ </section>
+
+</section>
+
+
<section id='conceptualization'>
<h1>Overview</h1>
@@ -226,10 +328,10 @@
used to express provenance of the agents themselves. </p>
<div class="anexample" id="agent-example">
+<p>
For
- example, a software for checking the use of grammar in a document may be defined as an agent of a document
- preparation activity, and at the same time one can describe its provenance, including for instance the vendor and the version history.</p>
-
+ example, a software for checking the use of grammar in a document may be defined as an agent of a document preparation activity, and at the same time one can describe its provenance, including for instance the vendor and the version history.</p>
+</div>
</section>
@@ -244,7 +346,8 @@
<p><dfn id="concept-usage">Usage</dfn> is the beginning on an entity being consumed by an activity.
Before usage, the activity had not begun to consume or use to this entity (and could not have been affected by the entity).</p>
-</p>
+
+
<div class="anexample" id="generation-usage-example">
<p>Examples of generation are the completed creation of a file by a
@@ -285,7 +388,7 @@
prescriptive about the nature of plans, their representation, the
actions and steps they consist of, and their intended goals. Since plans may evolve over time,
it may become necessary to track their provenance, and hence, plans are
-entities.</li>
+entities.</p>
<div class="anexample" id="plan-example">
<p>
@@ -347,16 +450,12 @@
associated with plans. </p>
</section>
- <section id="section-ER">
-<h2>Overview ER Diagram</h2>
-
-<div class='note'>
-<p>For the overview, we should simplify the diagram.</p>
-</div>
+ <section id="section-UML">
+<h2>Overview Diagram</h2>
<div style="text-align: center;">
<figure>
- <img src="../overview.png" alt="PROV-DM overview"/>
+ <img src="OverviewDiagram.png" alt="PROV-DM overview"/>
<figcaption>PROV-DM overview</figcaption>
</figure>
</div>
@@ -369,13 +468,20 @@
<section id="section-example">
<h2>Example</h2>
-
-<div class='note'>
-<p>Provenance of a W3C tech report. To develop.</p>
+<div class="note">
+Example to be developed.
</div>
-<p>This example describes the provenance of the prov-dm (version 2) document http://www.w3.org/TR/2011/WD-prov-dm-20111215. The purpose of this example is to bring up potential issues with identifiers in the data model.</p>
+<p>This example describes the provenance of the second version of the prov-dm document http://www.w3.org/TR/2011/WD-prov-dm-20111215. Its provenance can be described from several perspectives. </p>
+
+
+<section id="section-example-a">
+<h3>The Process View</h3>
+
+
+
+
<p>
@@ -387,7 +493,7 @@
<li> the publication activity for WD-prov-dm-20111215 used a publication request (req3)</li>
<li> the publication activity for WD-prov-dm-20111018 used another publication request (req2) and a transition request (req1)</li>
<li> publications were according to the process rules (rec-advance: a plan).</li>
-
+</ul>
<div style="text-align: center;">
@@ -399,6 +505,26 @@
</section>
+<section id="section-example-b">
+<h3>The Authors View</h3>
+
+<div style="text-align: center;">
+ <figure>
+ <img src="http://www.w3.org/2011/prov/wiki/images/c/cd/W3c-publication3.png" alt="Provenance of a Tech Report (b)" style="max-width: 98%; "/>
+<figcaption>Provenance of a Tech Report (b)</figcaption>
+ </figure>
+</div>
+
+
+
+</section>
+
+<section id="section-example-c">
+<h3>Attribution of Provenance</h3>
+
+</section>
+
+</section>
<section id="data-model-concepts">
@@ -1135,28 +1261,11 @@
<li> both of e1 and e2 provide a more concrete perspective on Bob than e1 does (each of them provides more details).
</ol>
-<!--
-For example:
-</p>
-<ol>
- <li> Entity denoted by <span class="name">e1</span> provides a <em>more concrete</em> characterization of Bob than <span class="name">e3</span> does;
- <li> Entity denoted by <span class="name">e2</span> provides a <em>more concrete</em> characterization of Bob than <span class="name">e3</span> does;
- <li> The entities denoted by <span class="name">e1</span> and <span class="name">e2</span> provide two different characterizations of the same thing, i.e., Bob.
-</ol>
--->
<p>The following two relations are introduced for expressing alternative or specialized characterisations. </p>
-<!--
-
-<ul>
- <li> e2 is a <em>specialization</em> of e1<span class="withAsn">, written <span class="name">specializationOf(e2,e1)</span>,</span> captures the intent of (1);
- <li> e2 is an <em>alternative characterization</em> of e1<span class="withAsn">, written <span class="name">alternateOf(e2,e1)</span>,</span> captures the intent of assertion (3).
-
- </ul>
--->
<p>An <dfn id="dfn-Alternate">alternate relation</dfn><span class="withAsn">, written <span class="name">alternateOf(id, alt1, alt2, attrs)</span> in PROV-ASN,</span> addresses case (1). It has the following constituents:</p>
@@ -1177,7 +1286,7 @@
<li><em>general entity</em>: an identifier of the entity that is being specialised</li>
<li><em>attrs</em>: an OPTIONAL set of attribute-value pairs to further describe this relation.</li>
</ul>
-</p>
+
<!--
<p>To promote take up of these relations, it is not specified whether they are transitive or symmetric. We anticipate that applications will specialize these relations according to their needs. </p>
@@ -1243,18 +1352,33 @@
<section id="sub-record">
-<h3>Further Terms of PROV-DM</h3>
+<h3>Further Elements of PROV-DM</h3>
-This section introduces further terms of PROV-DM.
+This section introduces further elements of PROV-DM.
+<section id="record-NamespaceDeclaration">
+<h3>Namespace Declaration</h3>
+
+<p>A PROV-DM <dfn id="dfn-namespace">namespace</dfn> is identified by an IRI reference [[!IRI]]. In PROV-DM, attributes, identifiers, and literals of with datatype <span
+class="name">xsd:QName</span> can be placed in a namespace using the mechanisms described in this specification. </p>
-<section id="record-attribute">
-<h4>Attribute</h4>
+<p>A <dfn id="dfn-namespaceDeclaration">namespace declaration</dfn> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this
+declaration refers to this namespace.
+A <dfn id="dfn-defaultNamespaceDeclaration">default namespace declaration</dfn> consists of a namespace. Every unprefixed qualified name in the scope of this default namespace declaration
+refers to this namespace.</p>
+</section>
-<p>An <dfn id="dfn-attribute">attribute</dfn> is a <em>qualified name</em>.
-An <dfn id="dfn-qualified name">qualified name</dfn> is a name subject to namespace interpretation. It consists of namespace, denoted by an optional prefix, and a local name. The namespace
-is denoted by an IRI [[!IRI]].</p>
+<section id="record-identifier">
+<h4>Identifier</h4>
+
+<p>
+An <dfn id="dfn-identifier">identifier</dfn> is a <a>qualified
+ name</a>.
+</p>
+
+<p>
+A <dfn id="dfn-qualifiedname">qualified name</dfn> is a name subject to <a>namespace</a> interpretation. It consists of <a>namespace</a>, denoted by an optional prefix, and a local name.</p>
<p>PROV-DM stipulates that a qualified name can be mapped into an IRI
@@ -1263,8 +1387,14 @@
<p>A qualified name's prefix is OPTIONAL. If a prefix occurs in a
qualified name, it refers to a <a>namespace</a> declared in the
record container. In the absence of prefix, the qualified name
- refers to the default namespace declared in the container.</p>
+ refers to the <a title="default namespace declaration">default namespace</a>.</p>
+</section>
+
+<section id="record-attribute">
+<h4>Attribute</h4>
+
+<p>An <dfn id="dfn-attribute">attribute</dfn> is a <a>qualified name</a>.
<p>The PROV data model introduces a fixed set of attributes in the <a href="#prov-dm-namespace">PROV-DM namespace</a>, which we define below.
@@ -1319,16 +1449,6 @@
-<section id="record-identifier">
-<h4>Identifier</h4>
-
-
-<p>An <dfn id="dfn-identifier">identifier</dfn> is a <em>qualified
- name</em>. A qualified name can be mapped into an IRI by
- concatenating the IRI associated with the prefix and the local
- part.</p>
-
-</section>
<section id="record-literal">
<h4>Literal</h4>
@@ -1377,18 +1497,6 @@
</section>
-<section id="record-NamespaceDeclaration">
-<h3>Namespace Declaration</h3>
-
-<p>A PROV-DM <dfn id="dfn-namespace">namespace</dfn> is identified by an IRI reference [[!IRI]]. In PROV-DM, attributes, identifiers, and literals of with datatype <span
-class="name">xsd:QName</span> can be placed in a namespace using the mechanisms described in this specification. </p>
-
-
-<p>A <dfn id="dfn-namespaceDeclaration">namespace declaration</dfn> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this
-declaration refers to this namespace.
-A <dfn id="dfn-defaultNamespaceDeclaration">default namespace declaration</dfn> consists of a namespace. Every unprefixed qualified name in the scope of this default namespace declaration
-refers to this namespace.</p>
-</section>
<section id="record-Location">
<h3>Location</h3>
@@ -1517,7 +1625,18 @@
</section>
+<section id="FurtherConsiderations">
+<h4>Further Considerations</h4>
+<ul>
+<li> Provenance of Provenance and Provenance from Multiple Perspectives/Providers
+
+<li> Ordering Constraints
+
+<li>
+</ul>
+
+</section>
</section>