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 applying usage and generation, one can construct provenance chains comprising both Activities and Entities.
In addiition, 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 not interesting or is unknown.
So, the prov:wasInformedBy property allows the assertion 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 interesting or is unknown,
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 to a particular application (for example,
the file size and format of the dataset, or the aspect ratio of the bar chart).
An Agent can be responsible for an Activity or an Entity, which is described using the properties prov:wasAssociatedWith and prov:wasAttributedTo, respectively. Agents can also be responsible for other Agents' actions. In this case, the Agent that influenced an Activity or Entity prov:actedOnBehalfOf another Agent that also bears some responsibility for the resulting Activity or Entity.
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 prov: <http://www.w3.org/ns/prov#> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix : <http://example.org#> .
:bar_chart
a prov:Entity;
prov:wasGeneratedBy :illustrationActivity;
prov:wasDerivedFrom :aggregatedByRegions;
.
:illustrationActivity
a prov:Activity;
prov:used :aggregatedByRegions;
prov:wasAssociatedWith :derek;
prov:wasInformedBy :aggregationActivity;
.
:aggregatedByRegions
a prov:Entity;
prov:wasGeneratedBy :aggregationActivity;
.
: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;
.
:nationalRegionsList
a prov:Entity;
prov:wasAttributedTo :civil_action_group;
.
:aggregatedByRegions prov:wasAttributedTo :derek .
:bar_chart prov:wasAttributedTo :derek .
:derek
a prov:Agent;
a foaf:Person;
foaf:givenName "Derek"^^xsd:string;
foaf:mbox <mailto:derek@example.org>;
prov:actedOnBehalfOf :natonal_newspaper_inc;
.
:national_newspaper_inc
a prov:Agent;
a prov:Organization;
foaf:name "National Newspaper, Inc.";
.
:government a prov:Organization, foaf:Organization .
:civil_action_group a prov:Organization, foaf:Organization .
The example states that the agent ex:derek was associated with two
activities: ex:aggregationActivity and ex:illustrationActivity. The
activity ex:aggregationActivity used
the entities ex:crimeData (a crime statistics dataset) and ex:nationalRegionsList (a list of national regions), and
generated a new entity, ex:aggregatedByRegions, that aggregates the statistics in
ex:crimeData according to the regions in ex:nationalRegionsList.
The ex:aggregatedByRegions entity was then used by the ex:illustrationActivity activity,
to generate a new entity ex:chart1 that depicts the aggregated statistics.
The example also states that the activity ex:illustrationActivity was
informed by the activity ex:aggregationActivity. Indeed, the former used
the entity ex:aggregatedByRegions, which was generated by the latter.
Because the agent ex:derek was associated with the activities
ex:aggregationActivity and ex:illustrationActivity, the entities
generated by these activities, i.e., ex:aggregatedByRegions and ex:chart1, were
attributed to him.
Finally, the example states that the agent ex:derek acted on behalf of the organization ex: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 one 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 maintains the collection (attribution), which members it contains as it evolves, 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 provenance descriptions may be expressed as PROV-O or in some other form.
The subclass of Bundle that contains 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 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.
More specifically, three subproperties of prov:wasDerivedFrom are 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 original,
prov:wasRevisionOf indicates that the derived Entity contains substantial content from the original Entity
(e.g., two editions of a book), and
prov:hadPrimarySource cites an older 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 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).
prov:mentionOf is a special type of prov:specializationOf whose subject presents as an aspect a particular prov:Bundle in which its more general Entity was described (prov:asInBundle is used to cite the Bundle in which the generalization was mentioned).
The prov:mentionOf and prov:asInBundle properties are "at risk" and may be removed from this specification based on feedback. Please send feedback to public-prov-comments@w3.org.
These two properties are used to encode the PROV-DM's Mention construct, which might be removed from PROV if implementation experience reveals problems with supporting this construct.
The third category allows further description of Entities. The property prov:value holds a literal value for the 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., generation, usage, or invalidation of an entity and the starting or ending of an activity).
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 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.
The fifth category 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.
We illustrate below the use of the expanded terms using the crime file example from the previous section as reference. Derek then published a post about
his work with the aggregated file.
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://example.org/my#> .
@prefix : <http://example.org#> .
:bundlePost {
:bundlePost a prov:Bundle .
:derek
a prov:Person, prov:Agent, foaf:Person; ## Typically prov:Agent will be inferred from prov:Person
foaf:givenName "Derek"^^xsd:string;
foaf:mbox <mailto:derek@example.org>;
prov:actedOnBehalfOf :national_newspaper_inc;
.
:national_newspaper_inc
a prov:Organization, prov:Agent; ## Typically prov:Agent will be inferred from prov:Organization
foaf:name "National Newspaper, Inc.";
.
:postEditor
a prov:SoftwareAgent, prov:Agent; ## Typically prov:Agent will be inferred from prov:SoftwareAgent
foaf:name "Post Editor 3000";
.
:aggregatedByRegions
a prov:Entity;
prov:atLocation <file://Users/aggr.txt>;
.
:more-crime-happens-in-cities
a prov:Location, sioc:Post, prov:Entity;
sioc:latest_version :post9821v2;
sioc:previous_version :post9821v1;
.
## Version 1 of the post
:post9821v1
a prov:Entity, sioc:Post;
prov:wasGeneratedBy :publicationActivity1123;
prov:atLocation :more-crime-happens-in-cities; ## PERMALINK to the (latest revision of the) post
my:snapshotContent :postContent0; ## Snapshot with the content of this version
sioc:title "More crime happens in cities"^^xsd:string;
prov:hadPrimarySource :aggregatedByRegions; ## This version of the post used the file "aggregatedByRegions" as a primary source.
## Since the author stated that he based his post in the file,
## the system used this relationship to keep the attribution clear.
prov:wasAttributedTo :derek;
prov:generatedAtTime "2011-07-16T01:52:02Z"^^xsd:dateTime;
.
## Version 2 of the post
:post9821v2
a prov:Entity, sioc:Post;
prov:atLocation :more-crime-happens-in-cities; ## PERMALINK to the (latest revision of the) post
my:snapshotContent :postContent1; ## Snapshot with the content of this version
prov:wasRevisionOf :post9821v1;
prov:alternateOf :post9821v1;
prov:wasAttributedTo :derek;
.
:publicationActivity1123
a prov:Activity;
prov:wasStartedAt "2011-07-16T01:01:01Z"^^xsd:dateTime;
prov:wasEndedAt "2011-07-16T01:52:02Z"^^xsd:dateTime;
prov:wasAssociatedWith :derek,
:postEditor;
prov:used :aggregatedByRegions;
prov:generated :post9821v1;
prov:wasStartedBy :derek;
prov:wasEndedBy :derek
.
}
Agent ex:derek, acting again on behalf of the :national_newspaper_inc organization,
publishes a post about his recent changes to the aggregated file (ex:aggregatedByRegions) using the tool ex:postEditor. Since he is the one who started and ended the publishing activity (ex:publicationActivity1123), that information
is recorded as well. The post produced by ex:derek (ex:post9821v1) includes a permanent link where the content of the latest version is shown
(ex:more-crime-happens-in-cities) plus a snapshot of the content of the current version (ex:postContent0). Derek also adds additional metadata of the post, like the title.
However, shortly after having published the post, Derek detects a typo. He does not want to record the activity that led to the new version, so he just creates a new version and
summarizes the changes in a revision of the original post (ex:post9821v2). This revision is also an alternate of the original post,
since they are both forms of the long-standing blog.
Thus, the permalink to the latest version (ex:more-crime-happens-in-cities) remains the same in the new revision, but a different URL is given for its snapshot (ex:postContent1).
Shortly after Derek's post publication, Monica adapts the text for a wider audience in a new post (ex:post9822). This version is a specialization of the original post,
and an alternate of the version modified by Derek. Since the provenance produced by the activities of Derek and Monica correspond to different user views, the system
automatically publish it in different prov:Bundles (ex:bundlePost and ex:bundlePost1).
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 my: <http://example.org#my> .
@prefix : <http://example.org#> .
:bundlePost1 {
:bundlePost1 a prov:Bundle .
:monica
a prov:Person, prov:Agent, foaf:Person;
foaf:givenName "Monica"^^xsd:string;
foaf:mbox <mailto:monica@example.org>
.
## Rephrasing of the post in a new resource for a different audience
:post9822
a prov:Entity, sioc:Post;
prov:atLocation :more-crime-happens-in-cities-for-dummies; ## PERMALINK to the (latest revision of the) post
my:snapshotContent :postContent2; ## Snapshot with the content of this version
prov:alternateOf :post9821v2; ## This post is an alternate of the second version modified by Derek.
prov:specializationOf :more-crime-happens-in-cities; ## This post is an specialization of the post initially created by Derek.
prov:wasInfluencedBy :aggregatedByRegions; ## If the file hadn't existed, Monica would have not written the post.
## However the file is not what Monica used as primary source for writting the new post,
## so we can't consider the post to have "been derived from" it.
sioc:title "More crime happens in cities (for dummies)"^^xsd:string;
prov:wasAttributedTo :monica;
.
}
Some time passes by, and John writes his own conclusions quoting the previous two posts:
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://example.org#> .
:bundlePost2 {
:bundlePost2
a prov:Bundle;
prov:hasAnnotation :noteMadeByParser;
.
:john
a prov:Agent;
.
# Rows of the post quoting post :post9821v1
:quote1
a prov:Entity;
prov:value "Analysis of the datasets demonstrate that there is more crime";
prov:wasQuotedFrom :post9821v1.
# Rows of the post quoting post :post9821v2
:quote2
a prov:Entity;
prov:value "In sumary, there are clearly more crimes in the country";
prov:wasQuotedFrom :post9821v2.
:publicationActivity1123
a prov:Activity;
prov:used :quote1,
:quote2,
:aggregatedByRegions;
prov:generated :post19201.
:post19201
a prov:Entity, sioc:Post;
prov:wasAttributedTo :john;
prov:wasDerivedFrom :post9821v1,
:post9821v2;
prov:wasGeneratedBy :publicationActivity1123;
prov:hadPrimarySource :aggregatedByRegions;
.
}
Agent ex:John also names the URI of the original source (ex:aggregatedByRegions). All the provenance statements related to his post
are grouped in a new prov:Bundle (ex:bundlePost2).
Unfortunately, there is a problem in the servers where :post19201 is being stored, and all the data related to the post is lost. Thus, the system
invalidates the entity automatically and notifies 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 prov:Entity, sioc:Post;
prov:invalidatedAtTime "2012-09-02T01:31:00Z"^^xsd:dateTime;
prov:wasInvalidatedBy :hard_disk_failure;
.
:hard_disk_failure
a prov:Activity;
prov:wasEndedAt "2012-09-02T01:31:00Z"^^xsd:dateTime;
.
3.3 Qualified Terms
The Qualified Terms category is for users who wish to provide further details about the provenance-related influence among
Entities, Activities, and Agents. The terms in this category are the result of
applying the Qualification Pattern [LD-Patterns-QR] to the simple (unqualified)
relations available in the Starting Point and
Expanded categories.
The Qualification Pattern consists of restating the unqualified
relation by using an intermediate class that represents the influence between two resources.
This new instance, in turn, can be annotated with additional descriptions about the influence relationship between the two resources cited.
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.
While the prov:Usage cites the influencing entity with the prov:entity property,
the influenced prov:Activity cites the prov:Usage with the property prov:qualifiedUsage.
This structure is illustrated in Figure 4a below.
The qualification classes and properties shown in the previous two tables can also be found in the 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 to use to cite the influencing resource (either
prov:entity,
prov:activity, or
prov:agent, respectively).
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
and the class prov:Generation (a subclass of prov:ActivityInfluence).
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
.
:a1 a prov:Activity .
:e1Gen
a prov:Generation;
prov:activity :a1; # Cite the influencing Activity.
ex:foo :bar; # Add additional attributes about the influence relation.
.
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 the thirteen unqualified 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 eleven 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 ex:illustrationActivity. The instance of prov:Usage cites the data used (ex: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 ex: <http://example.org#> .
ex:illustrationActivity
a prov:Activity; ## (Using Starting Point terms)
prov:used ex:aggregatedByRegions; ## The aggregated data was used to create the chart.
.
ex:aggregatedByRegions a prov:Entity .
ex:illustrationActivity
prov:qualifiedUsage [
a prov:Usage;
prov:entity ex:aggregatedByRegions; ## Qualification: The aggregated data was used
prov:atTime "2011-07-14T03:03:03Z"^^xsd:dateTime; ## at a particular time when creating the chart.
];
.
Example 9:
Qualified Association
The prov:qualifiedAssociation property parallels the
prov:wasAssociatedWith property to provide an additional description about the ex:illustrationActivity that Derek influenced.
The instance of prov:Association cites the influencing agent (ex:derek) that followed the instructions (ex:tutorial_blog).
Further, Derek served the role of illustrationist during the activity.
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix ex: <http://example.org#> .
ex:illustrationActivity
a prov:Activity; ## (Using Starting Point terms)
prov:wasAssociatedWith ex:derek; ## Derek was responsible for the chart making in some way.
.
ex:derek a prov:Agent .
ex:illustrationActivity
prov:qualifiedAssociation [ ## Qualification: What plan (or recipe, instructions)
a prov:Association; ## did Derek follow when creating the graphical chart?
prov:agent ex:derek
prov:hadPlan ex:tutorial_blog;
prov:hadRole ex:illustrationist;
];
.
ex:tutorial_blog a prov:Plan, prov:Entity .
ex: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 ex:chart1. The instance of prov:Generation cites the time (2011-07-14T15:52:14Z) that the activity (ex:illustrationActivity) generated the chart (ex:chart1).
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix ex: <http://example.org#> .
ex:chart1
a prov:Entity; ## (Using Starting Point terms)
prov:wasGeneratedBy ex:illustrationActivity; ## The chart was generated in an illustration activity.
.
ex:illustrationActivity a prov:Activity .
ex:chart1
prov:qualifiedGeneration [
a prov:Generation;
prov:activity ex:illustrationActivity; ## Qualification: The chart was
prov:atTime "2011-07-14T15:52:14Z"^^xsd:dateTime; ## generated at a particular time.
];
.
Example 11:
Qualified Derivation
The prov:qualifiedDerivation property parallels the prov:wasDerivedFrom property to provide an additional description to ex:chart1. The instance of prov:Derivation cites the activity (ex:illustrationActivity) and the Usages and Generations that the activity conduced to create the chart (ex:chart1).
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix ex: <http://example.org#> .
ex:chart1
a prov:Entity; ## (Using Starting Point terms)
prov:wasDerivedFrom ex:aggregatedByRegions; ## The chart was derived from the aggregate.
.
ex:aggregatedByRegions a prov:Entity .
ex:chart1
prov:qualifiedDerivation [
a prov:Derivation;
prov:entity ex:aggregatedByRegions; ## Qualification: additional information about the derivation:
prov:hadUsage ex:usage; ## Which activity derived the aggregate?
prov:hadActivity ex:activity; ## What did the activity use to derive the aggregate?
prov:hadGeneration ex:generation; ## How did the activity generate the derived aggregate?
];
.
An object property to express the accountability of an agent towards another agent. The subordinate agent acted on behalf of the responsible agent in an actual activity.