tweaks in prov-o narratives - pulled from aqua.
--- a/ontology/prov-o-html-sections/description-collections.inc.html Sun Apr 15 13:28:31 2012 -0400
+++ b/ontology/prov-o-html-sections/description-collections.inc.html Sun Apr 15 14:44:39 2012 -0400
@@ -56,44 +56,64 @@
<pre class="example">
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
+@prefix : <http://example.org/> .
:e1 a prov:Entity .
:e2 a prov:Entity .
-:c a prov:EmptyCollection .
-:c1 a prov:Collection .
- prov:derivedByInsertionFrom :c ;
- prov:qualifiedInsertion [ a prov:Insertion ;
- prov:collection :c ;
- prov:inserted [ a prov:KeyValuePair ;
- prov:key "k1"^^xsd:string ;
- prov:value :e1 ;
- ], [ a prov:KeyValuePair ;
- prov:key "k2"^^xsd:string ;
- prov:value :e2 ;
- ]
- ] .
+:c a prov:EmptyCollection .
+
+:c1 a prov:Collection;
+ prov:derivedByInsertionFrom :c;
+ prov:qualifiedInsertion [
+ a prov:Insertion;
+ prov:collection :c;
+ prov:inserted [
+ a prov:KeyValuePair;
+ prov:key "k1"^^xsd:string;
+ prov:value :e1;
+ ], [
+ a prov:KeyValuePair;
+ prov:key "k2"^^xsd:string;
+ prov:value :e2;
+ ];
+ ];
+.
</pre>
</div>
+
+
+
+
<div class="exampleOuter">
<p>
The following example shows how <code>:c3</code> has been derived from
- <code>:c2</code>, which content is not asserted. The keys
+ <code>:c2</code>, whose content is not asserted. The keys
<code>"k1"</code> and <code>"k3"</code> and their corresponding
values have been removed in <code>:c3</code>.
</p>
<pre class="example">
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
+@prefix : <http://example.org/> .
:c2 a prov:Collection .
-:c3 a prov:Collection .
- prov:derivedByRemovalFrom :c2 ;
- prov:qualifiedRemoval [ a prov:Removal ;
- prov:collection :c2 ;
- prov:removed "k1"^^xsd:string, "k3"^^xsd:string
- ] .
+
+:c3 a prov:Collection;
+ prov:derivedByRemovalFrom :c2;
+ prov:qualifiedRemoval [
+ a prov:Removal;
+ prov:collection :c2;
+ prov:removed "k1"^^xsd:string,
+ "k3"^^xsd:string;
+ ];
+.
</pre>
</div>
+
+
+
+
+
<div class="exampleOuter">
<p>
The next example shows how the members of
@@ -104,15 +124,22 @@
<pre class="example">
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
+@prefix : <http://example.org/> .
-:c1 prov:knownMembership [ a prov:Membership ;
- prov:member [ a prov:KeyValuePair;
- prov:key "k1"^^xsd:string ;
- prov:value :e1
- ] , [ a prov:KeyValuePair;
- prov:key "k2"^^xsd:string ;
- prov:value :e2
- ] .
+:c1
+ prov:knownMembership [
+ a prov:Membership;
+ prov:member [
+ a prov:KeyValuePair;
+ prov:key "k1"^^xsd:string;
+ prov:value :e1
+ ], [
+ a prov:KeyValuePair;
+ prov:key "k2"^^xsd:string;
+ prov:value :e2
+ ]
+ ];
+.
</pre>
</div>
--- a/ontology/prov-o-html-sections/description-expanded-terms.inc.html Sun Apr 15 13:28:31 2012 -0400
+++ b/ontology/prov-o-html-sections/description-expanded-terms.inc.html Sun Apr 15 14:44:39 2012 -0400
@@ -12,7 +12,7 @@
*****End comments*********
-->
- <p>This section defines additional terms to describe provenance at a greater level of specificity (for example, <a href="#Person" class="qname">prov:Person</a> or <a href="#SoftwareAgent" class="qname">prov:SoftwareAgent</a> in place of <a href="#Agent" class="qname">prov:Agent</a>) and with more details (for example, <a href="#Location" class="qname">prov:Location</a> to describe address of a <a href="#Organization" class="qname">prov:Organization</a>). In addition, the new terms in this section facilitate modeling of common provenance assertions related to web resources. For example, different version of a web page can be represented using the <a href="#wasRevisionOf" class="qname">prov:wasRevisionOf</a> property and the <a href="#hadOriginalSource" class="qname">prov:hadOriginalSource</a> property can be used to reference the original source of information used in a web resource. Many of the properties introduced in this section are also "shortcut" notations for combining the PROV-O terms introduced in Section 3.1 "Starting Point Terms", which make it easier for provenance annotation of a resource.
+ <p>This section defines additional terms to describe provenance at a greater level of specificity (for example, <a href="#Person" class="qname">prov:Person</a> or <a href="#SoftwareAgent" class="qname">prov:SoftwareAgent</a> in place of <a href="#Agent" class="qname">prov:Agent</a>) and with more details (for example, <a href="#Location" class="qname">prov:Location</a> to describe the address of a <a href="#Organization" class="qname">prov:Organization</a>). In addition, the new terms in this section facilitate modeling of common provenance assertions related to web resources. For example, different version of a web page can be represented using the <a href="#wasRevisionOf" class="qname">prov:wasRevisionOf</a> property and the <a href="#hadOriginalSource" class="qname">prov:hadOriginalSource</a> property can be used to reference the original source of information used in a web resource. Many of the properties introduced in this section are also "shortcut" notations for combining the PROV-O terms introduced in Section 3.1 "Starting Point Terms", which make it easier for provenance annotation of a resource.
</p>
<div class="exampleOuter">
--- a/ontology/prov-o-html-sections/description-qualified-terms.inc.html Sun Apr 15 13:28:31 2012 -0400
+++ b/ontology/prov-o-html-sections/description-qualified-terms.inc.html Sun Apr 15 14:44:39 2012 -0400
@@ -34,16 +34,20 @@
<pre class="example">{% include "includes/eg16-journalism-qualified-association.ttl" %}</pre>
</div>
- <p>Usage and Association (described above) are accompanied by six other qualifications of Starting Point relations. The following table lists the simple relations that can be qualified, along with the qualification property, qualification class, and the property used to indicate the object of the qualified relation.
- </p>
- <div style="text-align: center;">
- {% include "includes/qualifed-forms-starting-point.html" %}
+ <div id="qualifed-forms-starting-point" style="padding: 20px">
+ <p>Usage and Association (described above) are accompanied by six other qualifications of Starting Point relations. The <a href="#qualifed-forms-starting-point">following table</a> lists the simple relations that can be qualified, along with the qualification property, qualification class, and the property used to indicate the object of the qualified relation.
+ </p>
+ <div style="text-align: center">
+ {% include "includes/qualifed-forms-starting-point.html" %}
+ </div>
</div>
- <p>Six relations from the Expanded category can also be qualified. The following table lists the simple relations that can be qualified, along with the qualification property, qualification class, and the property used to indicate the object of the qualified relation.
- </p>
- <div style="text-align: center;">
- {% include "includes/qualifed-forms-expanded.html" %}
+ <div id="qualifed-forms-expanded" style="padding: 20px">
+ <p>Six relations from the Expanded category can also be qualified. The <a href="#qualifed-forms-expanded">following table</a> lists the simple relations that can be qualified, along with the qualification property, qualification class, and the property used to indicate the object of the qualified relation.
+ </p>
+ <div style="text-align: center">
+ {% include "includes/qualifed-forms-expanded.html" %}
+ </div>
</div>
<p>This section finishes with two more examples of qualification as applied to the chart making example from <a href=#description-starting-point-terms>Section 3.1</a>.
--- a/ontology/prov-o-html-sections/description-starting-points.inc.html Sun Apr 15 13:28:31 2012 -0400
+++ b/ontology/prov-o-html-sections/description-starting-points.inc.html Sun Apr 15 14:44:39 2012 -0400
@@ -35,7 +35,7 @@
<p>
Activities may depend on each other. PROV-O distinguishes between two
kinds of dependencies which are specified using the properties
- wasInformedBy and wasStartedBy.
+ <a href="#wasInformedBy" class="qname">prov:wasInformedBy</a> and <a href="#wasStartedByActivity" class="qname">prov:wasStartedByActivity</a>.
The first is used to specify that an activity used an entity that was
generated by another activity, and the second is used to specify that an
activity was started or triggered by another activity.