--- a/ontology/ProvenanceFormalModel.html Tue Nov 15 15:57:05 2011 +0000
+++ b/ontology/ProvenanceFormalModel.html Tue Nov 15 15:58:06 2011 +0000
@@ -472,7 +472,7 @@
</section>
<section>
- <h4>Temporary Section for Classes</h4>
+ <h4>Classes under Discussion</h4>
<p>Temporary section for terms not part of "core" ontology.</p>
<section id="time">
@@ -746,7 +746,63 @@
<prov:hasTemporalValue rdf:resource="http://www.example.com/crimeFile#t+3"/>
</rdf:Description>
</pre>
- </div>
+ </div>
+ <section id="startedat">
+ <h4>startedAt</h4>
+ <p> This object property defines the time when <code>ProcessExecution</code> started. The time is specified as an <code>time:Instant</code> [[!OWL-TIME]].
+ </p>
+ <img src="diagram-history/khalidDiagrams/startedAt.png" style="height: 3em" alt="startedAt links ProcessExecution to Instant"/>
+ <div><b>Example</b></div>
+ <p> Example of startedAt property is that a pe1 (instance of ProcessExecution class) is "2011-10-20T17:14:12Z". The RDF/XML syntax for asserting this is given below.</p>
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
+ <prov:startedAt rdf:about="http://www.example.com/crimeFile#t1>
+ <rdf:type rdf:resource=""http://www.w3.org/2006/time#Instant"/>
+ <time:inXSDDateTime>2011-10-20T17:14:12Z</time:inXSDDateTime>
+ </prov:startedAt>
+ </rdf:Description>
+ </pre>
+ </div>
+ </div>
+ </section>
+ <section id="endedat">
+ <h4>endedAt</h4>
+ <p> This object property defines the time when a <code>ProcessExecution</code> ended. The time is specified as an <code>time:Instant</code> [[!OWL-TIME]].
+ </p>
+ <img src="diagram-history/khalidDiagrams/endedAt.png" style="height: 3em" alt="endedAt links ProcessExecution to Instant"/>
+ <div><b>Example</b></div>
+ <p> Example of endedAt property is that a pe1 (instance of ProcessExecution class) is "2011-10-20T20:14:12Z". The RDF/XML syntax for asserting this is given below.</p>
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
+ <prov:endedAt rdf:about="http://www.example.com/crimeFile#t2>
+ <rdf:type rdf:resource=""http://www.w3.org/2006/time#Instant"/>
+ <time:inXSDDateTime>2011-10-20T20:14:12Z</time:inXSDDateTime>
+ </prov:endedAt>
+ </rdf:Description>
+ </pre>
+ </div>
+ </div>
+ </section>
+ <section id="wasGeneratedat">
+ <h4>wasGeneratedAt</h4>
+ <p> This object property defines the time when a <code>Entity</code> was generated by ProcessExecution.
+ </p>
+ <img src="diagram-history/khalidDiagrams/wasGeneratedAt.png" style="height: 3em" alt="wasGeneratedAt links Entity to Instant"/>
+ <div><b>Example</b></div>
+ <p> Example of wasGeneratedAt property is that a e1 (instance of Entity class) wasGeneratedAt "2011-10-20T20:12:12Z". The RDF/XML syntax for asserting this is given below.</p>
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#e1">
+ <prov:wasGeneratedAt rdf:about="http://www.example.com/crimeFile#t3>
+ <rdf:type rdf:resource=""http://www.w3.org/2006/time#Instant"/>
+ <time:inXSDDateTime>2011-10-20T20:12:12Z</time:inXSDDateTime>
+ </prov:startedAt>
+ </rdf:Description>
+ </pre>
+ </div>
+ </section>
</section>
<section id="attribution">
@@ -895,7 +951,7 @@
<section>
- <h4>Holding Section for Properties</h4>
+ <h4>Properties under Discussion</h4>
<p>Temporary section for terms not part of "core" ontology.</p>
<section id="followed">
<h4>followed</h4>
@@ -912,98 +968,6 @@
</pre>
</div>
</section>
- <section>
- <h4>hadTemporalValue</h4>
- <p>This property can be considered an abstract property, specialised by
- <code>startedAt</code>, <code>endedAt</code>,
- <code>wasGeneratedAt</code> and
- <code>assumedRoleAt</code> where the time MUST be specified as
- an <code>time:Instant</code> or more specifically MAY be
- specified using the PROV-O subclass <code>Time</code>
- which mandates the use of the
- <code>time:inXSDDateTime</code> data property.
- </p>
- </section>
-
- <section>
- <h4>wasAssumedBy</h4>
- <p>, forming a placeholder <code>EntityInRole</code> for use in
- relations such as <code>used</code> and
- <code>wasGeneratedBy</code>.
- <code>wasAssumedBy</code> is a required, functional property of
- <code>EntityInRole</code>, so an <code>EntityInRole</code>
- is assumed by one and only one <code>Entity</code>.
- <code>wasAssumedBy</code> is a subproperty of <code>wasComplementOf</code>.</p>
- </section>
- <section id="startedAt">
- <h4>startedAt</h4>
- <p> This object property defines the time when a
- <code>ProcessExecution</code> started. The time is specified as an
- <code>time:Instant</code> [[!OWL-TIME]], which MAY be a
- <code>Time</code> subclass by specifying the time using a
- <code>time:inXSDDateTime</code> data property.
- </p>
- <img src="diagram-history/khalidDiagrams/startedAt.png"
- style="height: 3em" alt="startedAt links ProcessExecution to Instant" />
- <div class="exampleOuter">
- <pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
- <prov:startedAt rdf:parseType="Resource">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
- <time:inXSDDateTime>2011-10-20T16:26:45Z</time:inXSDDateTime>
- </prov:startedAt>
- </rdf:Description>
- </pre>
- </div>
- </section>
- <section id="endedAt">
- <h4>endedAt</h4>
- <p> This object property defines the time when a
- <code>ProcessExecution</code> ended. The time is specified as an
- <code>time:Instant</code> [[!OWL-TIME]], which MAY be a
- <code>Time</code> subclass by specifying the time using a
- <code>time:inXSDDateTime</code> data property.
- </p>
- <img src="diagram-history/khalidDiagrams/endedAt.png"
- style="height: 3em" alt="endedAt links ProcessExecution to Instant" />
- <div class="exampleOuter">
- <pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
- <prov:endedAt rdf:parseType="Resource">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
- <time:inXSDDateTime>2011-11-21T18:36:52Z</time:inXSDDateTime>
- </prov:endedAt>
- </rdf:Description>
- </pre>
- </div>
- </section>
- <section id="wasGeneratedAt">
- <h4>wasGeneratedAt</h4>
- <p> This object property defines the time when a
- <code>Entity</code> was generated (as specified using
- <code>wasGeneratedBy</code>), meaning the instant when the entity
- first existed (and could be used by other process
- executions). The time is specified as an
- <code>time:Instant</code> [[!OWL-TIME]], which MAY be a
- <code>Time</code> subclass by specifying the time using a
- <code>time:inXSDDateTime</code> data property.
- </p>
- <img src="diagram-history/khalidDiagrams/wasGeneratedAt.png"
- style="height: 3em" alt="wasGeneratedAt links Entity to Instant" />
- <p>
- Note that by constraint
- </p>
- <div class="exampleOuter">
- <pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#e2">
- <prov:wasGeneratedAt rdf:parseType="Resource">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
- <time:inXSDDateTime>2011-10-20T17:14:12Z</time:inXSDDateTime>
- </prov:wasGeneratedAt>
- </rdf:Description>
- </pre>
- </div>
- </section>
<section id="assumedRole">
<h4>assumedRole</h4>
--- a/ontology/ProvenanceOntology.owl Tue Nov 15 15:57:05 2011 +0000
+++ b/ontology/ProvenanceOntology.owl Tue Nov 15 15:58:06 2011 +0000
@@ -27,7 +27,6 @@
>This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page).
If you wish to make comments regarding this document, please send them to public-prov-wg@w3.org (subscribe, archives). All feedback is welcome.</rdfs:comment>
- <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/prov-o/"/>
</owl:Ontology>
@@ -54,15 +53,13 @@
- <!-- http://www.w3.org/ns/prov-o/followed -->
+ <!-- http://www.w3.org/ns/prov-o/endedAt -->
- <owl:ObjectProperty rdf:about="followed">
- <rdf:type rdf:resource="&owl;AsymmetricProperty"/>
- <rdf:type rdf:resource="&owl;IrreflexiveProperty"/>
- <rdf:type rdf:resource="&owl;TransitiveProperty"/>
- <rdfs:label xml:lang="en">preceded</rdfs:label>
+ <owl:ObjectProperty rdf:about="endedAt">
+ <rdf:type rdf:resource="&owl;FunctionalProperty"/>
+ <rdfs:range rdf:resource="&time;Instant"/>
<rdfs:domain rdf:resource="ProcessExecution"/>
- <rdfs:range rdf:resource="ProcessExecution"/>
+ <rdfs:subPropertyOf rdf:resource="hadTemporalValue"/>
</owl:ObjectProperty>
@@ -73,8 +70,15 @@
<rdf:type rdf:resource="&owl;AsymmetricProperty"/>
<rdf:type rdf:resource="&owl;IrreflexiveProperty"/>
<rdfs:label xml:lang="en">had location</rdfs:label>
- <rdfs:domain rdf:resource="Entity"/>
<rdfs:range rdf:resource="Location"/>
+ <rdfs:domain>
+ <owl:Class>
+ <owl:unionOf rdf:parseType="Collection">
+ <rdf:Description rdf:about="Entity"/>
+ <rdf:Description rdf:about="QualifiedInvolvement"/>
+ </owl:unionOf>
+ </owl:Class>
+ </rdfs:domain>
</owl:ObjectProperty>
@@ -194,6 +198,17 @@
+ <!-- http://www.w3.org/ns/prov-o/startedAt -->
+
+ <owl:ObjectProperty rdf:about="startedAt">
+ <rdf:type rdf:resource="&owl;FunctionalProperty"/>
+ <rdfs:range rdf:resource="&time;Instant"/>
+ <rdfs:domain rdf:resource="ProcessExecution"/>
+ <rdfs:subPropertyOf rdf:resource="hadTemporalValue"/>
+ </owl:ObjectProperty>
+
+
+
<!-- http://www.w3.org/ns/prov-o/used -->
<owl:ObjectProperty rdf:about="used">
@@ -285,6 +300,17 @@
+ <!-- http://www.w3.org/ns/prov-o/wasGeneratedAt -->
+
+ <owl:ObjectProperty rdf:about="wasGeneratedAt">
+ <rdf:type rdf:resource="&owl;FunctionalProperty"/>
+ <rdfs:range rdf:resource="&time;Instant"/>
+ <rdfs:domain rdf:resource="Entity"/>
+ <rdfs:subPropertyOf rdf:resource="hadTemporalValue"/>
+ </owl:ObjectProperty>
+
+
+
<!-- http://www.w3.org/ns/prov-o/wasGeneratedBy -->
<owl:ObjectProperty rdf:about="wasGeneratedBy">
@@ -387,12 +413,6 @@
- <!-- http://www.w3.org/2002/07/owl#Thing -->
-
- <owl:Class rdf:about="&owl;Thing"/>
-
-
-
<!-- http://www.w3.org/2006/time#Instant -->
<owl:Class rdf:about="&time;Instant">
@@ -533,23 +553,6 @@
<owl:Class rdf:about="Usage">
<rdfs:subClassOf rdf:resource="QualifiedInvolvement"/>
</owl:Class>
-
-
-
- <!--
- ///////////////////////////////////////////////////////////////////////////////////////
- //
- // Individuals
- //
- ///////////////////////////////////////////////////////////////////////////////////////
- -->
-
-
-
-
- <!-- http://www.w3.org/TR/prov-o/ -->
-
- <owl:Thing rdf:about="http://www.w3.org/TR/prov-o/"/>
</rdf:RDF>
--- a/paq/provenance-access.html Tue Nov 15 15:57:05 2011 +0000
+++ b/paq/provenance-access.html Tue Nov 15 15:58:06 2011 +0000
@@ -223,7 +223,7 @@
<pre class="pattern">
Link: <cite>provenance-URI</cite>; rel="provenance"; anchor="<cite>entity-URI</cite>"</pre>
</code>
- When used in conjunction with an HTTP success response code (<code>2xx</code>), this HTTP header indicates that <code><cite>provenance-URI</cite></code> is the URI of some provenance information associated with the requested resource and that the associated entity is identified as <code><cite>entity-URI</cite></code>. (See also <a href="#interpreting-provenance-information" class="sectionRef"></a>.)
+ When used in conjunction with an HTTP success response code (<code>2xx</code>), this HTTP header field indicates that <code><cite>provenance-URI</cite></code> is the URI of some provenance information associated with the requested resource and that the associated entity is identified as <code><cite>entity-URI</cite></code>. (See also <a href="#interpreting-provenance-information" class="sectionRef"></a>.)
</p>
<p>
If no <code>anchor</code> link is provided then the <code><cite>entity-URI</cite></code> is assumed to be the URI of the resource.
@@ -232,7 +232,7 @@
At this time, the meaning of these links returned with other HTTP response codes is not defined: future revisions of this specification may define interpretations for these.
</p>
<p>
- An HTTP response MAY include multiple <code>provenance</code> link headers, indicating a number of different provenance resources that are known to the responding server, each providing provenance information about the accessed resource.
+ An HTTP response MAY include multiple <code>provenance</code> link header fields, indicating a number of different provenance resources that are known to the responding server, each providing provenance information about the accessed resource.
</p>
<p>
The presence of a <code>provenance</code> link in an HTTP response does not preclude the possibility that other publishers may offer provenance information about the same resource. In such cases, discovery of the additional provenance information must use other means (e.g. see <a href="#provenance-services" class="sectionRef"></a>).
@@ -241,6 +241,27 @@
Provenance resources indicated in this way are not guaranteed to be authoritative. Trust in the linked provenance data must be determined separately from trust in the original resource, just as in the web at large, it is a users' responsibility to determine an appropriate level of trust in any other linked resource; e.g. based on the domain that serves it, or an associated digital signature. (Ssee also <a href="#security-considerations" class="sectionRef"></a>.)
</p>
+ <section>
+ <h2>Specifying Provenance Services</h2>
+ <p class="pending">
+ This is a new proposal. It needs to be checked as to whether it is useful. GK/PG to review nature of provenance-service-URI.
+ </p>
+ <p>
+ The document provider may indicate that provenance information about the document is provided by a <a class="internalDFN">provenance service</a>. This is done through the use of a <code>provenance-service</code> link relation type following the same pattern as above:
+ </p>
+ <code>
+ <pre class="pattern">
+ Link: <cite>provenance-service-URI</cite>; anchor="<cite>entity-URI</cite>"; rel="provenance-service"</pre>
+ </pre>
+ </code>
+ <p>
+ The <code>provenance-service</code> link identifies the <a class="internalDFN">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to determine a <a class="internalDFN">provenance-URI</a> or retrieve <a class="internalDFN">provenance information</a> for an <a class="internalDFN">entity</a>; see <a href="#provenance-services" class="sectionRef"></a> for more details.
+ </p>
+ <p>
+ There may be multiple <code>provenance-service</code> link header fields, and these may appear in the same document as <code>provenance</code> links (though, in simple cases, we anticipate that <code>provenance</code> and <code>provenance-service</code> link relations will not be used together).
+ </p>
+ </section>
+
</section>
<section>
@@ -291,15 +312,10 @@
<section>
<h2>Specifying Provenance Services</h2>
<p class="pending">
- This is a new proposal. It needs to be checked as to whether it is useful. GK/PG to review nature of provenance-service-URI.
- </p>
- <p class="issue">
- - Any reason why provenance service URI relation has not been added to the HTTP Web Linking section as a new relation type? Is is just to finish discussions about the relation before just migrating its use to HTTP Web Linking?
- <br/><br/>
- This is a new section, pending wider review. It's a fairly radical change from what I did before, so I guess I was waiting to see if people were happy with the general approach, before fully integrating it.
+ This is a new proposal. It needs to be reviewed as to whether it is useful.
</p>
<p>
- The document creator may specify that the provenance information about the document is provided by a provenance service. This is done through the use of a third link relation type following the same pattern as above:
+ The document creator may specify that the provenance information about the document is provided by a <a class="internalDFN">provenance service</a>. This is done through the use of a third link relation type following the same pattern as above:
</p>
<code>
<pre class="pattern">
@@ -316,13 +332,12 @@
</pre>
</code>
<p>
- The <code>provenance-service</code> link element identifies the <a class="internalDFN">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to determine a <a class="internalDFN">provenance-URI</a> for a <a class="internalDFN">entity</a>; see <a href="#provenance-services" class="sectionRef"></a> for more details.
+ The <code>provenance-service</code> link element identifies the <a class="internalDFN">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to access <a class="internalDFN">provenance information</a> for an <a class="internalDFN">entity</a>; see <a href="#provenance-services" class="sectionRef"></a> for more details.
+ </p>
+ <p>
There may be multiple <code>provenance-service</code> link elements, and these MAY appear in the same document as <code>anchor</code> and <code>provenance</code> link elements (though, in simple cases, we anticipate that <code>provenance</code> and <code>provenance-service</code> link relations would not be used together).
</p>
</section>
- <p class="note">
- An alternative option would be to use an HTML <code><meta></code> element to present provenance links. The <code><Link></code> is preferred as it reflects more closely the intended goal, and has been defined with somewhat consistent applicability across HTTP, HTML and potentially RDF data. A specification to use <code><meta></code> for this would miss this opportunity to build on the existing specification and registry.
- </p>
</section>
<section>