Status of This Document
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
PROV Family of Specifications
This document is part of the PROV family of specifications, a set of specifications defining various aspects that are necessary to achieve the vision of inter-operable
interchange of provenance information in heterogeneous environments such as the Web. The specifications are:
- PROV-DM, the PROV data model for provenance;
- PROV-CONSTRAINTS, a set of constraints applying to the PROV data model;
- PROV-N, a notation for provenance aimed at human consumption;
- PROV-O, the PROV ontology, an OWL-RL ontology allowing the mapping of PROV to RDF; (this document)
- PROV-AQ, the mechanisms for accessing and querying provenance;
- PROV-PRIMER, a primer for the PROV data model;
- PROV-SEM, a formal semantics for the PROV data model;
- PROV-XML, an XML schema for the PROV data model.
How to read the PROV Family of Specifications
- The primer is the entry point to PROV offering an introduction to the provenance model.
- The Linked Data and Semantic Web community should focus on PROV-O defining PROV classes and properties specified in an OWL-RL ontology. For further details, PROV-DM and PROV-CONSTRAINTS specify the constraints applicable to the data model, and its interpretation. PROV-SEM provides a mathematical semantics.
- The XML community should focus on PROV-XML defining an XML schema for PROV. Further details can also be found in PROV-DM, PROV-CONSTRAINTS, and PROV-SEM.
- Developers seeking to retrieve or publish provenance should focus on PROV-AQ.
- Readers seeking to implement other PROV serializations
should focus on PROV-DM and PROV-CONSTRAINTS. PROV-O, PROV-N, PROV-XML offer examples of mapping to RDF, text, and XML, respectively.
PROV-O Second Working Draft
This specification defines the PROV Ontology as the normative representation of the PROV Data Model using the Web Ontology Language (OWL2). Following feedback, the structure of the document has been reorganized to suit a gradual introduction to the terms available in PROV-O, permitting the addition of more elaborate terms as users understand the earlier terms. A cross reference was added and is created directly from the OWL ontology. Examples throughout this document are taken directly from the working group's version control system.
This document was published by the Provenance Working Group as a Working Draft. This document is intended to become a W3C Recommendation. If you wish to make comments regarding this document, please send them to public-prov-wg@w3.org (subscribe, archives). All feedback is welcome.
Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
1. Introduction
The PROV Ontology (PROV-O) defines the normative OWL2 Web Ontology Language encoding of the PROV Data Model [PROV-DM]. This document describes the set of classes, properties, and restrictions that constitute the PROV Ontology. This ontology specification provides the foundation to implement provenance applications in different domains that can represent, exchange, and integrate provenance information generated in different systems and under different contexts. Together with the PROV Access and Query [PROV-PAQ] and PROV Data Model [PROV-DM], this document forms a framework for provenance information interchange and management in domain-specific Web-based applications.
PROV-O conforms to the OWL-RL profile and is lightweight so that it can be adopted in the widest range of applications. The PROV Ontology classes and properties are defined such that they can not only be used directly to represent provenance information, but also can be specialized for modeling application-specific provenance details in a variety of domains. Thus, the PROV Ontology is expected to be both directly usable in applications as well as serve as a reference model for creating domain-specific provenance ontologies and thereby facilitate interoperable provenance modeling. To demonstrate the use of PROV-O classes and properties, this document uses an example provenance scenario similar to the one introduced in the PROV-Primer [PROV-PRIMER]. PROV-O conforms to the OWL-RL profile and is lightweight so that it can be adopted in the widest range of applications.
The PROV Data Model [PROV-DM] introduces a minimal set of concepts to represent provenance information in a variety of application domains. This document maps the PROV Data Model to PROV Ontology using the OWL2 ontology language, which facilitates a fixed interpretation and use of the PROV Data Model concepts based on the formal semantics of OWL2 [OWL2-RDF-BASED-SEMANTICS].
We briefly introduce some of the OWL2 modeling terms that will be used to describe the PROV Ontology. An OWL2 instance is an individual object in a domain of discourse, for example a person named Alice or a car, and a set of individuals sharing a set of additional characteristics is called a class. Person and Car are examples of classes representing the set of individual persons and cars respectively. The OWL2 object properties are used to link individuals, classes, or create a property hierarchy. For example, the object property "hasOwner" can be used to link car with person. The OWL2 datatype properties are used to link individuals or classes to data values, including XML Schema datatypes [XMLSCHEMA-2].
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].
3. The PROV-O Ontology Description
This section introduces the terms in each of the following categories:
3.1 Starting Point Terms
The Starting Point category is a small collection 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:
- prov:Entity: An entity is a thing one wants to provide provenance for. Things can be physical, digital, conceptual, or otherwise.
- prov:Activity: An activity is something that occurs over a period of time and acts upon or with entities. This action can take multiple forms: consuming, processing, transforming, modifying, relocating, using, generating, etc.
- prov:Agent: An agent bears some form of responsibility for an activity taking place. Further, an agent may act on behalf of another agent when involved with an activity.
These three classes and the properties that relate them are illustrated in the following figure.
Entities are related to each other using derivation, which is used to
specify that the creation/existence of an entity was influenced in some
way by the consumption of another entity.
An entity can be attributed to an agent to specify that the entity was
generated by some activity that the agent in question was associated
with.
Activities may depend on each other. PROV-O distinguishes between two
kinds of dependencies which are specified using the properties
prov:wasInformedBy and prov:wasStartedByActivity.
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.
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 ex: <http://example.org#> .
ex:bar_chart
a prov:Entity;
prov:wasGeneratedBy ex:illustrationActivity;
prov:wasDerivedFrom ex:aggregatedByRegions;
.
ex:illustrationActivity
a prov:Activity;
prov:used ex:aggregatedByRegions;
prov:wasAssociatedWith ex:derek;
prov:wasInformedBy ex:aggregationActivity;
.
ex:aggregatedByRegions
a prov:Entity;
prov:wasGeneratedBy ex:aggregationActivity;
.
ex:aggregationActivity
a prov:Activity;
prov:wasStartedAt "2011-07-14T01:01:01Z"^^xsd:dateTime;
prov:wasAssociatedWith ex:derek;
prov:used ex:crimeData;
prov:used ex:nationalRegionsList;
prov:wasEndedAt "2011-07-14T02:02:02Z"^^xsd:dateTime;
.
ex:crimeData
a prov:Entity;
prov:wasAttributedTo ex:government;
.
ex:nationalRegionsList
a prov:Entity;
prov:wasAttributedTo ex:civil_action_group;
.
ex:aggregatedByRegions prov:wasAttributedTo ex:derek .
ex:bar_chart prov:wasAttributedTo ex:derek .
ex:derek
a prov:Agent;
a foaf:Person;
foaf:givenName "Derek"^^xsd:string;
foaf:mbox <mailto:dererk@example.org>;
prov:actedOnBehalfOf ex:chartgen
.
ex:chartgen
a prov:Agent;
a prov:Organization;
foaf:name "Chart Generators";
.
ex:government a prov:Organization, foaf:Organization .
ex: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:chartgen.
3.2 Expanded Terms
This section defines additional terms for describing provenance at a greater level of specificity in Agents (i.e., prov:Person or
prov:SoftwareAgent and prov:Organization) and entities
(prov:specializationOf and prov:AlternateOf).
Additionally, some of these terms provide the means to assert extended details about the concepts introduced in section 3.1
(prov:wasStartedBy and (prov:wasEndedBy in activities
and prov:Location in entities).
Further annotations on provenance records can be done through prov:Notes, although we can group the provenance statements in
prov:Accounts in order to keep the record of the provenance metadata itself.
The new terms in this section also facilitate the modeling of common provenance assertions related to web resources.
For example, different versions of a web page can be represented using the prov:wasRevisionOf
property, the prov:hadOriginalSource property can be used to reference the original source
of information used in a web resource and users can quote existent entities using the prov:wasQuotedFrom property.
For expressing the dependency between two different entities, users can assert the prov:tracedTo property.
We illustrate below the use of the expanded terms using the crime file example from the previous section as reference. Agent Derek now publishes a post about
his work with the aggregated file, while Monica publishes an alternate version to reach a more casual audience.
@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 ex: <http://example.org#> .
ex:accountPost {
ex:accountPost a prov:Account .
ex:derek
a prov:Agent, foaf:Person;
foaf:givenName "Derek"^^xsd:string;
foaf:mbox <mailto:dererk@example.org>;
prov:actedOnBehalfOf ex:chartgen;
.
ex:monica
a prov:Agent, foaf:Person;
foaf:givenName "Monica"^^xsd:string;
foaf:mbox <mailto:monica@example.org>
.
ex:chartgen
a prov:Agent, prov:Organization;
foaf:name "Chart Generators, Inc.";
.
ex:aggregatedByRegions
a prov:Entity;
prov:atLocation <file://Users/aggr.txt>;
.
ex:post9821
a prov:Entity, sioc:Post;
prov:wasGeneratedBy ex:publicationActivity1123;
prov:atLocation ex:more-crime-happens-in-cities; ## PERMALINK of the post
ex:snapshotContent ex:postContent0; ## Snapshot with the content of this version
prov:qualifiedGeneration [
a prov:Generation;
prov:activity ex:publicationActivity1123;
prov:atTime "2011-07-16T01:52:02Z"^^xsd:dateTime;
prov:atLocation <http://dbpedia.org/resource/Madrid>;
];
sioc:title "More crime happens in cities"^^xsd:string;
prov:hadOriginalSource ex:aggregatedByRegions;
prov:wasAttributedTo ex:derek
.
## Version 2 of the post
ex:post9821v1
a prov:Entity, sioc:Post;
prov:atLocation ex:more-crime-happens-in-cities; ## PERMALINK of the post
ex:snapshotContent ex:postContent1; ## Snapshot with the content of this version
prov:wasRevisionOf ex:post9821;
prov:specializationOf ex:post9821;
prov:wasAttributedTo ex:derek;
.
## Rephrasing of the post in a new version
ex:post9821v2
a prov:Entity, sioc:Post;
prov:atLocation ex:more-crime-happens-in-cities-for-dummies; ## PERMALINK of the post
ex:snapshotContent ex:postContent2; ## Snapshot with the content of this version
prov:alternateOf ex:post9821v1;
prov:specializationOf ex:post9821;
prov:tracedTo ex:aggregatedByRegions; ## If the file hadn't existed, Monica would have not written the post.
sioc:title "More crime happens in cities for dummies"^^xsd:string;
prov:wasAttributedTo ex:monica;
.
<http://dbpedia.org/resource/Madrid>
a prov:Location;
.
ex:publicationActivity1123
a prov:Activity;
prov:wasStartedAt "2011-07-16T01:01:01Z"^^xsd:dateTime;
prov:wasEndedAt "2011-07-16T01:52:02Z"^^xsd:dateTime;
prov:wasAssociatedWith ex:derek;
prov:used ex:aggregatedByRegions;
prov:generated ex:post9821;
prov:wasStartedBy ex:derek;
prov:wasEndedBy ex:derek
.
}
Agent ex:derek, acting again in behalf of the ex:chartgenerators organization,
publishes a post about his recent changes to the aggregated file (ex:aggregatedByRegions). He also provides the location for the crime file, so everyone knows the content he has been browsing,
and records the city where the publishing took place (Madrid). 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:post9821) 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, inmediately after having published the post, Derek detects a typo. He doesnt' 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:post9821v1). This revision is also a specialization of the original post, since it is a refined version.
Thus, the location of the new revision has the same permalink, but a different url for its snapshot (ex:postContent1).
Shortly after Derek's post publication, ex:monica adapts the text for a wider audience in a new version (ex:post9821v2). This version is an specialization of the original post,
and an alternate of the first version modified by Derek. Since the provenance produced by Derek and Monica is related to the same resources, the system
automatically groups it in the same prov:Account (ex:accountPost).
Some time passes by, and John writes his own conclusions quoting the previous two posts:
@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#> .
:accountPost2 {
:accountPost2
a prov:Account;
prov:hasAnnotation :noteMadeByParser;
.
:john
a prov:Agent;
.
#Rows of the post quoting post :post9821v1
:quote1
a prov:Entity;
:value "Analysis of the datasets demonstrate that there is more crime";
wasQuotedFrom :post9821v1.
#Rows of the post quoting post :post9821v2
:quote2
a prov:Entity;
:value "In sumary, there are clearly more crimes in the country";
wasQuotedFrom :post9821v2.
:publicationActivity1123
a prov:Axtivity;
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:hadOriginalSource :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:Account (ex:accountPost2).
Finally, a web crawler (ex:boogleParser) parses the second post. The crawler acts in behalf of Boogle, an organization that want to index the posts. It also adds an
annotation on the second account (ex:accountPost2), stating at which date the parsing was made.
@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 ex: <http://example.org#> .
ex:noteMadeByParser {
ex:noteMadeByParser
a prov:Note;
prov:wasAttributedTo ex:boogleParser;
.
ex:boogleParser
a prov:SoftwareAgent;
prov:actedOnBehalfOf ex:boogle;
.
ex:boogle
a prov:Organization;
.
ex:accountPost2
ex:parsedDate "2011-08-16T00:00:02Z"^^xsd:dateTime;
.
}
3.3 Qualified Terms
The classes and properties in the Qualified terms category are for users who wish to provide additional details about the relationships between entities, activities, and agents.
The terms in this category are the result of applying the Qualification Pattern to the simple relations available in the
Starting Point and Expanded categories.
For example, Figure 2 illustrates the classes and properties needed to fulfill the qualification pattern for the prov:used and prov:wasAssociatedWith properties. 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 relations that can be qualified.
In the example, the prov:qualifiedUsage property parallels the prov:used property, and references an instance of prov:Usage that 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.
Similarly, the prov:qualifiedAssociation property parallels the prov:wasAssociatedWith property, and references an instance of prov:Association that provides attributes of the prov:wasAssociatedWith relation between the Activity and Agent. The prov:agent property is used to cite the Agent that was involved in the Activity. In this case, the plan that the Agent used is provided using the prov:hadPlan property and an instance of prov:Plan.
The following two examples show the result of applying the Usage and Association patterns to the chart making example from Section 3.1.
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.
];
.
Qualified Association
The prov:qualifiedAssociation property parallels the prov:wasAssociatedWith property to provide an additional description to ex:illustrationActivity. The instance of prov:Association cites the agent (ex:derek) that followed the instructions (ex:tutorial_blog).
@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;
];
.
ex:tutorial_blog a prov:Plan, prov:Entity .
This section finishes with two more examples of qualification as applied to the chart making example from Section 3.1.
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.
];
.
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?
];
.
3.4 Collections Terms
A prov:Dictionary is an prov:Entity that acts as a container to some members,
which are themselves entities.
Specifically, a dictionary is composed of set of key-value pairs, where a
literal key is used to identify a constituent entity within the dictionary.
To illustrate this, the example below describes a dictionary :c1
that has as members the two key value pairs ("k1", :e1)
and ("k2", :e2).
@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 .
:c1 a prov:Dictionary;
prov:membership [
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
];
];
.
It is worth noting that :c1 may also
have other members (i.e. prov:knownMembership is
not functional). A dictionary may be empty and thus not have any known
memberships, in which case it should be described as an instance of the
subclass prov:EmptyDictionary.
To describe the provenance of a dictionary, PROV-O provides two
kinds of involvements: prov:qualifiedInsertion is used to
describe that a dictionary was obtained from an existing dictionary by
inserting a set of key-value pairs. prov:qualifiedRemoval is used to specify
that a given dictionary was obtained from an existing dictionary by
removing a set of key-value pairs. The example below specifies that
the dictionary :c1 was obtained from the empty dictionary
:c1 by inserting the key-value pairs ("k1",
:e1) and ("k2", :e2).
@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:EmptyDictionary .
:c1 a prov:Dictionary;
prov:derivedByInsertionFrom :c;
prov:qualifiedInsertion [
a prov:Insertion;
prov:dictionary :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;
];
];
.
Similarly, the example below specifies that the dictionary
:c3 was obtained by removing the key-value pairs associated with
the keys "k1" and "k2" from the dictionary
:c2. Thus, :c3 does not contain the
members ("k1", :e1) and ("k2",
:e2( from :c2.
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix : <http://example.org/> .
:c2 a prov:Dictionary .
:c3 a prov:Dictionary;
prov:derivedByRemovalFrom :c2;
prov:qualifiedRemoval [
a prov:Removal;
prov:dictionary :c2;
prov:removed "k1"^^xsd:string,
"k3"^^xsd:string
];
.
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.