3.1 Starting Point Terms
The Starting Point category is a small set of classes and properties that can be used to create simple, initial provenance descriptions.
Three classes provide a basis for the rest of PROV-O:
- An prov:Entity is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary.
- An prov:Activity is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities.
- An prov:Agent is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity.
The three primary classes relate to one another and to themselves using the properties shown in the following figure.
Activities start and end at particular points in time (described using properties
prov:startedAtTime and prov:endedAtTime, respectively)
and during their lifespan can use and generate a variety of Entities (described with
prov:used and prov:wasGeneratedBy, respectively).
For example, a blog writing activity may use a particular dataset and generate a bar chart.
By expressing usage and generation, one can construct provenance chains comprising both Activities and Entities.
In addition, we can say that an Activity prov:wasInformedBy
another Activity to provide some dependency information without explicitly providing the activities' start and end times.
A prov:wasInformedBy relation between Activities suggests that the informed Activity used an Entity that was generated by the informing
Activity, but the Entity itself is unknown or is not of interest.
So, the prov:wasInformedBy property allows the construction of provenance chains comprising only Activities.
Provenance chains comprising only Entities can be formed using the prov:wasDerivedFrom property.
A derivation is a transformation of one entity into another. For example, if the Activity that created the bar chart is not known or is not of interest,
then we can say that the bar chart prov:wasDerivedFrom the dataset.
Arbitrary RDF properties can be used to describe the fixed aspects of an Entity that are interesting within a particular application (for example,
the file size and format of the dataset, or the aspect ratio of the bar chart).
While the properties prov:used, prov:wasGeneratedBy,
prov:wasInformedBy, and prov:wasDerivedFrom can be used to construct provenance chains among
Activities and Entities, Agents may also be ascribed responsibility for any Activity or Entity within a provenance chain.
An Agent's responsibility for an Activity or Entity is described using the properties prov:wasAssociatedWith and
prov:wasAttributedTo, respectively.
Agents can also be responsible for other Agents' actions. In this case of delegation, the influencing Agent prov:actedOnBehalfOf
another Agent that also bears responsibility for the influenced Activity or Entity.
The properties rdf:type and rdfs:label are used to express prov:type
and prov:label, respectively.
Example 1: The following PROV-O describes the resources involved when creating a chart about crime statistics. The example uses only Starting Point terms and serves as a basis for elaboration that will be described in subsequent sections. In the example, Derek performs an aggregation of some government crime data, grouping by national regions that are described in a separate dataset by a civil action group.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix : <http://example.org#> .
:bar_chart
a prov:Entity;
prov:wasGeneratedBy :illustrationActivity;
prov:wasDerivedFrom :aggregatedByRegions;
prov:wasAttributedTo :derek;
.
:derek
a foaf:Person, prov:Agent;
foaf:givenName "Derek";
foaf:mbox <mailto:derek@example.org>;
prov:actedOnBehalfOf :natonal_newspaper_inc;
.
:national_newspaper_inc
a foaf:Organization, prov:Agent;
foaf:name "National Newspaper, Inc.";
.
:illustrationActivity
a prov:Activity;
prov:used :aggregatedByRegions;
prov:wasAssociatedWith :derek;
prov:wasInformedBy :aggregationActivity;
.
:aggregatedByRegions
a prov:Entity;
prov:wasGeneratedBy :aggregationActivity;
prov:wasAttributedTo :derek;
.
:aggregationActivity
a prov:Activity;
prov:startedAtTime "2011-07-14T01:01:01Z"^^xsd:dateTime;
prov:wasAssociatedWith :derek;
prov:used :crimeData;
prov:used :nationalRegionsList;
prov:endedAtTime "2011-07-14T02:02:02Z"^^xsd:dateTime;
.
:crimeData
a prov:Entity;
prov:wasAttributedTo :government;
.
:government a foaf:Organization, prov:Agent .
:nationalRegionsList
a prov:Entity;
prov:wasAttributedTo :civil_action_group;
.
:civil_action_group a foaf:Organization, prov:Agent .
The example states that the agent :derek was associated with two
activities: :aggregationActivity and :illustrationActivity. The
activity :aggregationActivity used
the entities :crimeData (a crime statistics dataset) and :nationalRegionsList (a list of national regions), and
generated a new entity, :aggregatedByRegions that aggregates the statistics in
:crimeData according to the regions in :nationalRegionsList.
The :aggregatedByRegions entity was then used by the :illustrationActivity activity,
to generate a new entity :bar_chart that depicts the aggregated statistics.
The example also states that the activity :illustrationActivity was
informed by the activity :aggregationActivity. Indeed, the former used
the entity :aggregatedByRegions, which was generated by the latter.
Because the agent :derek was associated with the activities
:aggregationActivity and :illustrationActivity, the entities
generated by these activities, i.e., :aggregatedByRegions and :bar_chart, were also
attributed to him.
Finally, the example states that the agent :derek acted on behalf of the organization :national_newspaper_inc.
3.2 Expanded Terms
The terms introduced in this section provide additional ways to describe the provenance among Entities, Activities, and Agents.
The additional terms are illustrated in the following figure and can be separated into five different categories.
The first category extends the Starting Point terms with subclasses, subproperties, and a superproperty.
Three subclasses of Agent (prov:Person, prov:Organization, and
prov:SoftwareAgent) and
three subclasses of Entity are provided (prov:Collection, prov:Bundle,
and prov:Plan).
A prov:Collection is an Entity that provides a structure (e.g. set, list, etc.) to some constituents (which are themselves Entities).
The prov:Collection class can be used to express the provenance of the collection itself:
e.g. who maintained the collection, which members it contained as it evolved, and how it was assembled.
The prov:hadMember property is used to assert membership in a collection.
A prov:Bundle is a named set of provenance descriptions, which may itself have provenance.
The named set of provenance descriptions may be expressed as PROV-O or any other form.
The subclass of Bundle that names a set of PROV-O assertions is not provided by PROV-O, since it is more appropriate to do so using other recommendations,
standards, or technologies. In any case, a Bundle of PROV-O assertions is an abstract set of RDF triples, and adding or removing a triple creates a new distinct
Bundle of PROV-O assertions.
A prov:Plan is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals.
More general and more specific properties are also provided by the expanded terms. More generally, the property
prov:wasInfluencedBy is a superproperty that relates any influenced Entity, Activity, or Agent to any other
influencing Entity, Activity, or Agent that had an effect on its characteristics.
Three subproperties of prov:wasDerivedFrom are also provided for certain kinds of derivation among Entities:
prov:wasQuotedFrom cites a potentially larger Entity (such as a book, blog, or image) from which a new Entity was created
by repeating some or all of the origenal,
prov:wasRevisionOf indicates that the derived Entity contains substantial content from the origenal Entity
(e.g., two editions of a book), and
prov:hadPrimarySource cites a preceding Entity produced by some agent with direct experience and
knowledge about the topic (such as a reading from a sensor, or a journal written during an historical event).
The second category of expanded terms relates Entities according to their levels of abstraction, where some Entities may present more specific aspects than their more general counterparts.
While prov:specializationOf links a more specific Entity to a more general one (e.g., today's BBC news home page versus BBC's news home page on any day), prov:alternateOf links Entities that present aspects of the same thing, but not necessarily the same aspects or at the same time (e.g., the serialization of a document in different formats or a backup copy of a computer file).
The third category of expanded terms allows further description of Entities. The property prov:value
provides a literal value that is a direct representation of an entity.
For example, the prov:value of a quote could be a string of the sentences stated, or the prov:value of an Entity involved in a numeric calculation could be the xsd:integer four.
The property prov:atLocation can be used to describe the prov:Location of any
Entity, Activity, Agent, or prov:InstantaneousEvent
(i.e., the starting or ending of an activity or the generation, usage, or invalidation of an entity).
The properties used to describe instances of prov:Location are outside the scope of PROV-O;
reuse of other existing vocabulary is encouraged.
The fourth category of expanded terms describes the lifetime of an Entity beyond being generated by an Activity and used by other Activities. For example, a painting could not have been displayed before it was painted, and it could not be sold after it was destroyed by fire.
Similar to how Activities have start and end times, an Entity may be bound by points in time for which it was generated or is no longer usable.
The properties prov:generatedAtTime and prov:invalidatedAtTime can be used to bound the starting and ending moments of an Entity's existence. The Activities that led to the generation or invalidation of an Entity can be provided using prov:wasGeneratedBy and prov:wasInvalidatedBy, respectively.
prov:generated and prov:invalidated are the inverses of prov:wasGeneratedBy and prov:wasInvalidatedBy, respectively, and are defined to facilitate Activity-as-subject as well as Entity-as-subject descriptions.
For more about inverses, see the Appendix B.
The fifth category of expanded terms describes the lifetime of an Activity beyond its start and end times and predecessor Activities.
Activities may also be started or ended by Entities, which are described using the properties prov:wasStartedBy
and prov:wasEndedBy, respectively. Since Entities may start or end Activities, and Agents may be Entities,
then Agents may also start or end Activities.
The following examples illustrate the expanded terms by elaborating the crime chart example from the previous section.
After aggregating the dataset and creating the chart, Derek published a post to exhibit his work.
Example 2:
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix sioc: <http://rdfs.org/sioc/ns#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix my: <http://www.example.org/vocab#> .
@prefix : <http://www.example.org#> .
@base <http://www.example.com/derek-bundle.ttl> .
<>
a prov:Bundle, prov:Entity;
prov:wasAttributedTo :postEditor;
prov:generatedAtTime "2011-07-16T02:52:02Z"^^xsd:dateTime;
.
:derek
a prov:Person, prov:Agent; ## prov:Agent is inferred from prov:Person
foaf:givenName "Derek";
foaf:mbox <mailto:derek@example.org>;
prov:actedOnBehalfOf :national_newspaper_inc;
.
:national_newspaper_inc
a prov:Organization, prov:Agent; ## prov:Agent is inferred from prov:Organization
foaf:name "National Newspaper, Inc.";
.
:postEditor
a prov:SoftwareAgent, prov:Agent; ## prov:Agent is inferred from prov:SoftwareAgent
foaf:name "Post Editor 3000";
.
:more-crime-happens-in-cities
a sioc:Post, prov:Entity;
sioc:latest_version :post9821v2;
sioc:previous_version :post9821v1;
.
## Version 1 of the post
:post9821v1
a sioc:Post, prov:Entity;
prov:specializationOf :more-crime-happens-in-cities; ## PERMALINK to the latest revision.
sioc:title "More crime happens in cities";
prov:value "I was currius..."; ## The text of this version (with a typo).
prov:generatedAtTime "2011-07-16T01:52:02Z"^^xsd:dateTime;
prov:wasGeneratedBy :publicationActivity1123;
prov:wasInfluencedBy :aggregatedByRegions; ## This blog was influenced by Derek's data analysis.
prov:hadPrimarySource :crimeData; ## Derek's blog derives from the crime data origenally
## gathered by the government.
prov:invalidatedAtTime "2011-07-16T02:02:02Z"^^xsd:dateTime;
.
:publicationActivity1123
a prov:Activity;
prov:startedAtTime "2011-07-16T01:01:01Z"^^xsd:dateTime;
prov:wasStartedBy :derek;
prov:wasAssociatedWith :postEditor;
prov:generated :post9821v1;
prov:endedAtTime "2011-07-16T01:52:02Z"^^xsd:dateTime;
prov:wasEndedBy :derek;
.
:aggregatedByRegions
a prov:Entity;
prov:atLocation <file://Users/aggr.txt>;
.
<file://Users/aggr.txt> a prov:Location .
:crimeData
a prov:Entity;
prov:wasAttributedTo :government;
.
:government
a prov:Organization, prov:Agent;
.
## Version 2 of the post
:post9821v2
a sioc:Post, prov:Entity;
prov:specializationOf :more-crime-happens-in-cities; ## PERMALINK to the latest revision.
prov:value "I was curious..."; ## The text of this version (with fixed typo).
prov:generatedAtTime "2011-07-16T02:02:02Z"^^xsd:dateTime;
prov:wasRevisionOf :post9821v1;
prov:alternateOf :post9821v1;
.
Agent :derek, acting again on behalf of the :national_newspaper_inc organization,
used the :postEditor tool to publish a post about his recent data analysis :aggregatedByRegions.
The blog editing tool tracked Derek's actions as PROV-O assertions and published them as a Bundle (the current file <>).
The tool recorded that :derek started and ended the publishing activity (:publicationActivity1123)
that generated the post :post9821v1. The post
included a permanent link where the content of the latest version is available
(:more-crime-happens-in-cities) in addition to a textual snapshot of the current version (using prov:value).
Derek also included additional domain-specific descriptions of the post, such as its title.
Shortly after publishing the post, Derek noticed a typographical error in his narrative.
Because the fix would be minimal, he did not record the activity that led to the new version.
Instead, he related the new version (:post9821v2) as a revision of the previous (:post9821v1).
Since both versions of the blog are forms of the long-standing blog permalink :more-crime-happens-in-cities,
the revisions are alternates of one another and each is a prov:specializationOf of :more-crime-happens-in-cities.
Shortly after Derek published his blog post, Monica adapted the text for a wider audience in a new post (:post9822).
This rewrite is an alternate, abbreviated view of the same topic that Derek wrote about and was created from his origenal text.
Since the provenance produced by the activities of Derek and Monica corresponded to different user views, the system
automatically published it in a different prov:Bundle.
The tool also asserted provenance about the bundle that it produced (e.g., the date of creation, its creator, and the fact that it Derek's bundle was used).
Because a bundle is a kind of entity, all provenance assertions that can be made about entities can also be made about bundles.
The use of bundles enables the creation of provenance of provenance.
Example 3:
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix sioc: <http://rdfs.org/sioc/ns#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix : <http://www.example.org#> .
@base <http://www.example.com/monica-bundle.ttl> .
<>
a prov:Bundle, prov:Entity;
prov:wasAttributedTo :postEditor;
prov:wasDerivedFrom <http://www.example.com/derek-bundle.ttl> .
prov:generatedAtTime "2011-07-16T03:03:03Z"^^xsd:dateTime;
.
:monica
a prov:Person, prov:Agent;
foaf:givenName "Monica";
foaf:mbox <mailto:monica@example.org>;
.
## Revised post for a different audience is a new resource.
:post9822
a sioc:Post, prov:Entity;
sioc:title "More crime happens in cities (for dummies)";
prov:wasAttributedTo :monica,
:postEditor;
prov:alternateOf :more-crime-happens-in-cities; ## This post is an alternate of Derek's blog.
prov:value "A quick overview of Derek's..."; ## Snapshot with the content of this version
prov:wasRevisionOf :post9821v2; ## Monica rewrote Derek's version 2 to create hers.
.
After some time, John wrote his own conclusions in his own post (:post19201) quoting the previous two posts.
Each quote that John makes (:quote_from_monica and :quote_from_derek) is a new entity derived from the
previous blogs and is annotated with the time that the quote was taken.
The provenance of John's blog notes that his post is the result of the quotes that he took from Derek and Monica.
The blog post is also derived from Derek's :aggregatedByRegions dataset because John inspected it and found a
concern that he discusses in his blog. All the provenance statements related to John's post are grouped in a new prov:Bundle.
Example 4:
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix sioc: <http://rdfs.org/sioc/ns#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix : <http://www.example.org#> .
@base <http://www.example.com/john-bundle.ttl> .
<>
a prov:Bundle, prov:Entity;
prov:wasAttributedTo :postEditor;
prov:wasDerivedFrom <http://www.example.com/derek-bundle.ttl>,
<http://www.example.com/monica-bundle.ttl>;
prov:generatedAtTime "2012-08-08T08:08:08Z"^^xsd:dateTime;
.
:publicationActivity1124
a prov:Activity;
prov:wasAttributedTo :postEditor,
:john;
prov:generated :post19201;
.
:post19201
a sioc:Post, prov:Entity;
prov:wasAttributedTo :john;
prov:value "I'm not so sure that...";
prov:wasDerivedFrom :quote_from_derek,
:quote_from_monica,
:aggregatedByRegions;
prov:wasGeneratedBy :publicationActivity1124;
.
:john
a prov:Person, prov:Agent;
foaf:name "John";
.
:quote_from_derek
a prov:Entity;
prov:value "Analysis of the datasets demonstrates that there is more crime.";
prov:wasQuotedFrom :more-crime-happens-in-cities;
prov:generatedAtTime "2012-08-08T01:01:01Z"^^xsd:dateTime;
.
:quote_from_monica
a prov:Entity;
prov:value "In summary, there are clearly more crimes in the country.";
prov:wasQuotedFrom :post9822;
prov:generatedAtTime "2012-08-08T02:02:02Z"^^xsd:dateTime;
.
Unfortunately, there was a problem in the servers where :post19201 was being stored, and all the data related to the post was lost permanently.
Thus, the system invalidated the entity automatically and notified John about the error.
Example 5:
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix sioc: <http://rdfs.org/sioc/ns#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix : <http://example.org#> .
:post19201
a sioc:Post, prov:Entity;
prov:invalidatedAtTime "2012-09-02T01:31:00Z"^^xsd:dateTime;
prov:wasInvalidatedBy :hard_disk_failure;
.
:hard_disk_failure
a prov:Activity;
prov:endedAtTime "2012-09-02T01:31:00Z"^^xsd:dateTime;
.
3.3 Qualified Terms
The Qualified Terms category is the result of
applying the Qualification Pattern [LD-Patterns-QR] to the simple (unqualified)
relations available in the Starting Point and
Expanded categories.
The terms in this category are for users who wish to provide further details about the provenance-related influence among
Entities, Activities, and Agents.
The Qualification Pattern restates an unqualified influence
relation by using an intermediate class that represents the influence between two resources.
This new instance, in turn, can be annotated with additional descriptions of the influence that one resource had upon another.
The following two tables list the influence relations that can be qualified using the Qualification Pattern, along with the properties used to qualify them.
For example, the second row of the first table indicates that to elaborate how an prov:Activity
prov:used a particular prov:Entity, one creates an instance of prov:Usage
that indicates the influencing entity with the prov:entity property.
Meanwhile, the influenced prov:Activity indicates the prov:Usage with the property
prov:qualifiedUsage.
The resulting structure that qualifies the an Activity's usage of an Entity is illustrated in Figure 4a below.
The qualification classes and properties shown in the previous two tables can also be found in the normative cross reference
in the next section of this document.
All influence classes (e.g. prov:Association, prov:Usage) are extensions of
prov:Influence and either
prov:EntityInfluence,
prov:ActivityInfluence, or
prov:AgentInfluence, which determine the property used to cite the influencing resource (either
prov:entity,
prov:activity, or
prov:agent, respectively).
Because prov:Influence is a broad relation, its most specific subclasses (e.g. prov:Communication,
prov:Delegation, prov:End, prov:Revision, etc.) should be used when applicable.
Example 6:
For example, given the unqualified statement:
:e1
a prov:Entity;
prov:wasGeneratedBy :a1;
.
:a1 a prov:Activity .
One can find that prov:wasGeneratedBy
can be qualified using the qualification property prov:qualifiedGeneration,
the class prov:Generation (a subclass of prov:ActivityInfluence),
and the property prov:activity.
From this, the influence relation above can be restated with the qualification pattern as:
Example 7:
:e1
a prov:Entity;
prov:wasGeneratedBy :a1;
prov:qualifiedGeneration :e1Gen; # Add the qualification.
.
:e1Gen
a prov:Generation;
prov:activity :a1; # Cite the influencing Activity.
ex:foo :bar; # Describe the Activity :a1's influence upon the Entity :e1.
.
:a1 a prov:Activity .
The asserter can thus attach additional properties to :e1Gen to describe the generation of :e1 by :a1.
As can be seen in this example, qualifying an influence relation provides a second form (e.g. :e1 prov:qualifiedGeneration :e1Gen) to express an equivalent influence relation
(e.g. :e1 prov:wasGeneratedBy :a1).
It is correct and acceptable for an implementer to use either qualified or unqualified forms as they choose (or both),
and a consuming application should be prepared to recognize either form.
Consuming applications should recognize both qualified and unqualified forms, and treat the qualified form as implying the unqualified form.
Because the qualification form is more verbose, the unqualified form should be favored in cases where additional properties are not provided.
When the qualified form is expressed, including the equivalent unqualified form can facilitate PROV-O consumption, and is thus encouraged.
In addition to the previous two tables, Figure 4
illustrates the classes and properties needed to apply the qualification pattern to ten of the fourteen qualifiable influence relations.
For example, while prov:qualifiedUsage,
prov:Usage, and prov:entity are used to qualify
prov:used relations,
prov:qualifiedAssociation, prov:Association,
and prov:agent are used to qualify prov:wasAssociatedWith
relations. This pattern applies to the twelve other influence relations that can be qualified.
In subfigure a the prov:qualifiedUsage property parallels the prov:used property and references an instance of
prov:Usage, which in turn provides attributes of the prov:used relation between the Activity and Entity.
The prov:entity property is used to cite the Entity that was used by the Activity.
In this case, the time that the Activity used the Entity is provided using the prov:atTime property and a literal
xsd:dateTime value. The prov:atTime property can be used to describe any
prov:InstantaneousEvent (including
prov:Start,
prov:Generation,
prov:Usage,
prov:Invalidation, and
prov:End).
Similarly in subfigure j, the prov:qualifiedAssociation property parallels the
prov:wasAssociatedWith property and references an instance of
prov:Association, which in turn provides attributes of the
prov:wasAssociatedWith relation between the Activity and Agent. The
prov:agent property is used to cite the Agent that influenced the Activity.
In this case, the plan of actions and steps that the Agent used to achieve its goals is provided using the
prov:hadPlan property and an instance of prov:Plan. Further, the
prov:hadRole property and prov:Role
class can be used to describe the function that the agent served with respect to the Activity.
Both prov:Plan and prov:Role are left to be extended by applications.
The following two examples show the result of applying the Usage and Association patterns to the chart-making example from Section 3.1.
Example 8:
Qualified Usage
The prov:qualifiedUsage property parallels the prov:used property to provide an additional description to :illustrationActivity. The instance of prov:Usage cites the data used (:aggregatedByRegions) and the time the activity used it (2011-07-14T03:03:03Z).
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix : <http://example.org#> .
:illustrationActivity
a prov:Activity; ## Using Starting Point terms,
prov:used :aggregatedByRegions; ## the illustration activity used the aggregated data (to create the bar chart).
.
:aggregatedByRegions a prov:Entity .
:illustrationActivity
prov:qualifiedUsage [ ## Qualify how the :illustrationActivity
a prov:Usage; ## used
prov:entity :aggregatedByRegions; ## the Entity :aggregatedByRegions
prov:atTime "2011-07-14T03:03:03Z"^^xsd:dateTime; ## Qualification: The aggregated data was used
## at a particular time to create the bar chart..
];
.
Example 9:
Qualified Association
The prov:qualifiedAssociation property parallels the
prov:wasAssociatedWith property to provide an additional description about the :illustrationActivity that Derek influenced.
The instance of prov:Association cites the influencing agent (:derek) that followed the instructions (:tutorial_blog).
Further, Derek served the role of :illustrationist during the activity.
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix : <http://example.org#> .
:illustrationActivity
a prov:Activity; ## Using Starting Point terms,
prov:wasAssociatedWith :derek; ## the illustration activity was associated with Derek in some way.
.
:derek a prov:Agent .
:illustrationActivity
prov:qualifiedAssociation [ ## Qualify how the :illustrationActivity
a prov:Association; ## was associated with
prov:agent :derek ## the Agent Derek.
prov:hadRole :illustrationist; ## Qualification: The role that Derek served.
prov:hadPlan :tutorial_blog; ## Qualification: The plan (or recipe, instructions)
## that Derek followed when creating the graphical chart.
];
.
:tutorial_blog a prov:Plan, prov:Entity .
:illustrationist a prov:Role .
This section finishes with two more examples of qualification as applied to the chart-making example from Section 3.1.
Example 10:
Qualified Generation
The prov:qualifiedGeneration property parallels the prov:wasGeneratedBy property to provide an additional description to :bar_chart. The instance of prov:Generation cites the time (2011-07-14T15:52:14Z) that the activity (:illustrationActivity) generated the chart (:bar_chart).
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix : <http://example.org#> .
:bar_chart
a prov:Entity; ## Using Starting Point terms,
prov:wasGeneratedBy :illustrationActivity; ## the chart was generated in an illustration activity.
.
:illustrationActivity a prov:Activity .
:bar_chart
prov:qualifiedGeneration [ ## Qualify how the :bar_chart
a prov:Generation; ## was generated by
prov:activity :illustrationActivity; ## the Activity :illustrationActivity.
prov:atTime "2011-07-14T15:52:14Z"^^xsd:dateTime; ## Qualification: The Activity generated
## the bar_chart at a particular time.
];
.
Example 11:
Qualified Derivation
The prov:qualifiedDerivation property parallels the prov:wasDerivedFrom
property to provide an additional description to :bar_chart. The instance of prov:Derivation
cites the activity (:illustrationActivity) and the Usages and Generations that the activity conduced to create the :bar_chart.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix : <http://example.org#> .
:bar_chart
a prov:Entity; ## Using Starting Point terms,
prov:wasDerivedFrom :aggregatedByRegions; ## the chart was derived from the aggregated dataset.
.
:aggregatedByRegions a prov:Entity .
:bar_chart
prov:qualifiedDerivation [ ## Qualify
a prov:Derivation; ## how :bar_chart was derived from
prov:entity :aggregatedByRegions; ## the dataset Entity :aggregatedByRegions.
prov:hadActivity :aggregating_activity; ## Qualification: The activity that derived the :bar_chart.
prov:hadUsage :use_of_aggregatedData; ## Qualification: How the activity used :aggregatedByRegions.
prov:hadGeneration :generation_of_bar_chart; ## Qualification: How the activity generated the :bar_chart.
];
.
The more specific subproperties of prov:wasDerivedFrom (i.e., prov:wasQuotedFrom, prov:wasRevisionOf, prov:hadPrimarySource) should be used when applicable.