Please refer to the errata for this document, which may include some normative corrections.
The English version of this specification is the only normative version. Non-normative translations may also be available.
Provenance is information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness. PROV-DM is the conceptual data model that forms a basis for the W3C provenance (PROV) family of specifications. PROV-DM distinguishes core structures, forming the essence of provenance information, from extended structures catering for more specific uses of provenance. PROV-DM is organized in six components, respectively dealing with: (1) entities and activities, and the time at which they were created, used, or ended; (2) derivations of entities from entities; (3) agents bearing responsibility for entities that were generated and activities that happened; (4) a notion of bundle, a mechanism to support provenance of provenance; (5) properties to link entities that refer to the same thing; and, (6) collections forming a logical structure for its members.
This document introduces the provenance concepts found in PROV and defines PROV-DM types and relations. The PROV data model is domain-agnostic, but is equipped with extensibility points allowing domain-specific information to be included.
Two further documents complete the specification of PROV-DM. First, a companion document specifies the set of constraints that provenance should follow. Second, a separate document describes a provenance notation for expressing instances of provenance for human consumption; this notation is used in examples in this document.
The PROV Document Overview describes the overall state of PROV, and should be read before other PROV documents.
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/.
This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.
This document was published by the Provenance Working Group as a Recommendation. If you wish to make comments regarding this document, please send them to email@example.com (subscribe, archives). All comments are welcome.
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.
For the purpose of this specification, provenance ◊ is defined as a record that describes the people, institutions, entities, and activities involved in producing, influencing, or delivering a piece of data or a thing. In particular, the provenance of information is crucial in deciding whether information is to be trusted, how it should be integrated with other diverse information sources, and how to give credit to its originators when reusing it. In an open and inclusive environment such as the Web, where users find information that is often contradictory or questionable, provenance can help those users to make trust judgements.
We present the PROV data model, PROV-DM, a generic data model for provenance that allows domain and application specific representations of provenance to be translated into such a data model and interchanged between systems. Thus, heterogeneous systems can export their native provenance into such a core data model, and applications that need to make sense of provenance can then import it, process it, and reason over it.
The PROV data model distinguishes core structures from extended structures: core structures form the essence of provenance information, and are commonly found in various domain-specific vocabularies that deal with provenance or similar kinds of information [Mappings]. Extended structures enhance and refine core structures with more expressive capabilities to cater for more advanced uses of provenance. The PROV data model, comprising both core and extended structures, is a domain-agnostic model, but with clear extensibility points allowing further domain-specific and application-specific extensions to be defined.
The PROV data model has a modular design and is structured according to six components covering various facets of provenance:
This specification presents the concepts of the PROV data model, and provenance types and relations, without specific concern for how they are applied. With these, it becomes possible to write useful provenance, and publish or embed it alongside the data it relates to.
However, if something about which provenance is expressed is subject to change, then it is challenging to express its provenance precisely (e.g. the data from which a daily weather report is derived changes from day to day). This is addressed in a companion specification [PROV-CONSTRAINTS] by proposing formal constraints on the way that provenance is related to the things it describes (such as the use of attributes, temporal information and specialization of entities), and additional conclusions that are valid to infer.
For the purpose of compliance, the normative sections of this document are Section 1.1, Section 1.3, Section 5., and Appendix A.
This section is non-normative.
Section 2 provides an overview of the PROV data model, distinguishing a core set of types and relations, commonly found in provenance, from extended structures catering for more specific uses. It also introduces a modular organization of the data model in components.
Section 3 overviews the Provenance Notation used to illustrate examples of provenance.
Section 4 illustrates how the PROV data model can be used to express the provenance of a report published on the Web.
Section 5 provides the definitions of PROV concepts, structured according to six components.
Section 6 summarizes PROV-DM extensibility points.
Section 7 introduces the idea that constraints can be applied to the PROV data model to validate provenance; these are covered in the companion specification [PROV-CONSTRAINTS].
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].
Examples throughout this document use the PROV-N Provenance Notation, briefly introduced in Section 3 and specified fully in a separate document [PROV-N].
This section is non-normative.
The following namespaces prefixes are used throughout this document.
|prov||http://www.w3.org/ns/prov#||The PROV namespace (see Section 5.7.4)|
|xsd||http://www.w3.org/2000/10/XMLSchema#||XML Schema Namespace [XMLSCHEMA11-2]|
|rdf||http://www.w3.org/1999/02/22-rdf-syntax-ns#||The RDF namespace [RDF-CONCEPTS]|
|(others)||(various)||All other namespace prefixes are used in examples only. |
In particular, IRIs starting with "http://example.com" represent
some application-dependent IRI [RFC3987]
This section is non-normative.
This section introduces provenance concepts with informal explanations and illustrative examples. PROV distinguishes core structures, forming the essence of provenance, from extended structures catering for more specific uses of provenance. Core and extended structures are respectively presented in Section 2.1 and Section 2.2. Furthermore, the PROV data model is organized according to components, which form thematic groupings of concepts (see Section 2.3). A provenance description is an instance of a provenance structure, whether core or extended, described below.
This section is non-normative.
At its core, provenance describes the use and production of entities by activities, which may be influenced in various ways by agents. These core types and their relationships are illustrated by the UML diagram of Figure 1.
The concepts found in the core of PROV are introduced in the rest of this section. They are summarized in Table 2, where they are categorized as type or relation. The first column lists concepts, the second column indicates whether a concept maps to a type or a relation, whereas the third column contains the corresponding name, as it appears in Figure 1. Names of relations have a verbal form in the past tense to express what happened in the past, as opposed to what may or will happen. In the core of PROV, all relations are binary.
|PROV Concepts||PROV-DM types or relations||Name||Overview|
|Entity||PROV-DM Types||Entity||Section 2.1.1|
|Generation||PROV-DM Relations||WasGeneratedBy||Section 2.1.1|
This section is non-normative.
In PROV, things we want to describe the provenance of are called entities and have some fixed aspects. The term "things" encompasses a broad diversity of notions, including digital objects such as a file or web page, physical things such as a mountain, a building, a printed book, or a car as well as abstract concepts and ideas.
An entity is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary. [Detailed specification]
An entity may be the document at IRI http://www.bbc.co.uk/news/science-environment-17526723, a file in a file system, a car, or an idea.
An 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. [Detailed specification] Just as entities cover a broad range of notions, activities can cover a broad range of notions: information processing activities may for example move, copy, or duplicate digital entities; physical activities can include driving a car between two locations or printing a book.
An activity may be the publishing of a document on the Web, sending a twitter message, extracting metadata embedded in a file, driving a car from Boston to Cambridge, assembling a data set based on a set of measurements, performing a statistical analysis over a data set, sorting news items according to some criteria, running a SPARQL query over a triple store, or editing a file.
Activities and entities are associated with each other in two different ways: activities utilize entities and activities produce entities. The act of utilizing or producing an entity may have a duration. The term 'generation' refers to the completion of the act of producing; likewise, the term 'usage' refers to the beginning of the act of utilizing entities. Thus, we define the following concepts of generation and usage.
Generation is the completion of production of a new entity by an activity. This entity did not exist before generation and becomes available for usage after this generation. [Detailed specification]
Usage is the beginning of utilizing an entity by an activity. Before usage, the activity had not begun to utilize this entity and could not have been affected by the entity. [Detailed specification]
Examples of generation are the completed creation of a file by a program, the completed creation of a linked data set, and the completed publication of a new version of a document.
Usage examples include a procedure beginning to consume an argument, a service starting to read a value on a port, a program beginning to read a configuration file, or the point at which an ingredient, such as eggs, is being added in a baking activity. Usage may entirely consume an entity (e.g. eggs are no longer available after being added to the mix); in contrast, the same entity may be used multiple times, possibly by different activities (e.g. a file on a file system can be read indefinitely).
Let us consider the activity of driving a car from Boston to Cambridge. One might reasonably ask what entities are used and generated by this activity. This is answered by considering that a single artifact may correspond to several entities; in this case, a car in Boston may be a different entity from the same car in Cambridge. Thus, among other things, an entity "car in Boston" would be used, and a new entity "car in Cambridge" would be generated by this activity of driving. The provenance trace of the car might include: designed in Japan, manufactured in Korea, shipped to Boston USA, purchased by customer, driven to Cambridge, serviced by engineer in Cambridge, etc., all of which might be important information when deciding whether or not it represents a sensible second-hand purchase. Or some of it might alternatively be relevant when trying to determine the truth of a web page reporting a traffic violation involving that car. This breadth of provenance allows descriptions of interactions between physical and digital artifacts.
The generation of an entity by an activity and its subsequent usage by another activity is termed communication.
Communication is the exchange of some unspecified entity by two activities, one activity using some entity generated by the other. [Detailed specification]
The activity of writing a celebrity article was informed by (a communication instance) the activity of intercepting voicemails.
Activities utilize entities and produce entities. In some cases, utilizing an entity influences the creation of another in some way. This notion of 'influence' is captured by derivations, defined as follows.
A derivation is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity. [Detailed specification]
Examples of derivation include the transformation of a relational table into a linked data set, the transformation of a canvas into a painting, the transportation of a work of art from London to New York, and a physical transformation such as the melting of ice into water.
The focus of derivation is on connecting a generated entity to a used entity. While the basic idea is simple, the concept of derivation can be quite subtle: implicit is the notion that the generated entity was affected in some way by the used entity. If an artifact was used by an activity that also generated a new artifact, it does not always follow that the second artifact was derived from the first. In the activity of creating a painting, an artist may have mixed some paint that was never actually applied to the canvas: the painting would typically not be considered a derivation from the unused paint. PROV does not attempt to specify the conditions under which derivations exist; rather, derivation is considered to have been determined by unspecified means. Thus, while a chain of usage and generation is necessary for a derivation to hold between entities, it is not sufficient; some form of influence occurring during the activities involved is also needed.
For many purposes, a key consideration for deciding whether something is reliable and/or trustworthy is knowing who or what was reponsible for its production. Data published by a respected independent organization may be considered more trustworthy than that from a lobby organization; a claim by a well-known scientist with an established track record may be more believed than a claim by a new student; a calculation performed by an established software library may be more reliable than by a one-off program.
An 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. [Detailed specification] An agent may be a particular type of entity or activity. This means that the model can be used to express provenance of the agents themselves.
Software for checking the use of grammar in a document may be defined as an agent of a document preparation activity; one can also describe its provenance, including for instance the vendor and the version history. A site selling books on the Web, the services involved in the processing of orders, and the companies hosting them are also agents.
Agents can be related to entities, activities, and other agents.
Attribution is the ascribing of an entity to an agent. [Detailed specification]
A blog post can be attributed to an author, a mobile phone to its manufacturer.
Agents are defined as having some kind of responsibility for activities.
An activity association is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. [Detailed specification]
Examples of association between an activity and an agent are:
Delegation is the assignment of authority and responsibility to an agent (by itself or by another agent) to carry out a specific activity as a delegate or representative, while the agent it acts on behalf of retains some responsibility for the outcome of the delegated work. [Detailed specification] The nature of this relation is intended to be broad, including contractual relation, but also altruistic initiative by the representative agent.
A student publishing a web page describing an academic department could result in both the student and the department being agents associated with the activity. It may not matter which actual student published a web page, but it may matter significantly that the department told the student to put up the web page.
While the core of PROV focuses on essential provenance structures commonly found in provenance descriptions, extended structures are designed to support more advanced uses of provenance. The purpose of this section is twofold. First, mechanisms to specify these extended structures are introduced. Second, two further kinds of provenance structures are overviewed: they cater for provenance of provenance and collections, respectively.
Extended structures are defined by a variety of mechanisms outlined in this section: subtyping, expanded relations, optional identification, and new relations.
This section is non-normative.
Subtyping can be applied to core types. For example, a software agent is special kind of agent, defined as follows.A software agent is running software.
Subtyping can also be applied to core relations. For example, a revision is a special kind of derivation, defined as follows.
A revision is a derivation for which the resulting entity is a revised version of some original.
Section 2.1 shows that seven concepts are mapped to binary relations in the core of PROV. However, some advanced uses of these concepts cannot be captured by a binary relation, but require relations to be expanded to n-ary relations.
Indeed, binary relations are actually shorthands that can be 'opened up' by applications and filled in with further application details. For example, derivation is a very high level relationship between two entities: an application may decide to 'open up' that relationship in an expanded relation that describes how an entity was derived from another by virtue of listing the generation, usage, and activity involved in the derivation relationship. Applications are free to decide which level of granularity they want describe, and PROV gives them the way to do that.
To illustrate expanded relations, we revisit the concept of association, introduced in Section 2.1.3 (full definition of the expanded association can be found in Section 5.3.3). Agents may rely on plans, i.e. sets of actions or steps, to achieve their goals in the context of an activity. Hence, an expanded form of association relation allows for a plan to be specified. Plan is defined by subtyping and full association by an expanded relation, as follows.
A plan is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals.
An activity association is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity.
There exist no prescriptive requirements on the nature of plans, their representation, the actions or steps they consist of, or their intended goals. Since plans may evolve over time, it may become necessary to track their provenance, so plans themselves are entities. Representing the plan explicitly in the provenance can be useful for various tasks: for example, to validate the execution as represented in the provenance record, to manage expectation failures, or to provide explanations.
An example of association between an activity and an agent involving a plan is: an XSLT transform (an activity) launched by a user (an agent) based on an XSL style sheet (a plan).
Some concepts exhibit both a core use, expressed as binary relation, and an extended use, expressed as n-ary relation. In some cases, mapping the concept to a relation, whether binary or n-ary, is not sufficient: instead, it may be required to identify an instance of such concept. In those cases, PROV allows for an optional identifier to be expressed to identify an instance of an association between two or more elements. This optional identifier can then be used to refer to an instance as part of other concepts.
A service may read a same configuration file on two different occasions. Each usage can be identifed by its own identifier, allowing them to be distinguished.
Finally, PROV supports further relations that are not subtypes or expanded versions of existing relations (such as specialization, alternate).
A bundle is a named set of provenance descriptions, and is itself an entity, so allowing provenance of provenance to be expressed.
For users to decide whether they can place their trust in something, they may want to analyze its provenance, but also determine the agent its provenance is attributed to, and when it was generated. In other words, users need to be able to determine the provenance of provenance. Hence, provenance is also regarded as an entity (of type Bundle), by which provenance of provenance can then be expressed.
In a decision making situation, decision makers may be presented with the same piece of knowledge, issued by multiple sources. In order to validate this piece of knowledge, decision makers can consider its provenance, but also the provenance of its provenance, which may help determine whether it can be trusted.
A collection is an entity that provides a structure to some constituents that must themselves be entities. These constituents are said to be member of the collections. Many different types of collections exist, such as sets, dictionaries, or lists. Using Collections, one can express the provenance of the collection itself in addition to that of the members.
An example of collection is an archive of documents. Each document has its own provenance, but the archive itself also has some provenance: who maintained it, which documents it contained at which point in time, how it was assembled, etc.
Besides the separation between core and extended structures, PROV-DM is further organized according to components, grouping concepts in a thematic manner.
Table 3 enumerates the six components, five of which have already been implicitly overviewed in this section. All components contain extended structures, whereas only the first three contain core structures.
|1||Entities and Activities||✔||2.1.1||5.1||about entities and activities, and their interrelations|
|2||Derivation||✔||2.1.2||5.2||about derivation and its subtypes|
|3||Agent and Responsibility||✔||2.1.3||5.3||about agents and concepts ascribing responsibility to them|
|4||Bundles||2.2.2||5.4||about bundles, a mechanism to support provenance of provenance|
|5||Alternate||—||5.5||about relations linking entities referring to the same thing|
This section is non-normative.
To illustrate the application of PROV concepts to a concrete example (see Section 4) and to provide examples of concepts (see Section 5), we introduce PROV-N, a notation for writing instances of the PROV data model. For full details and for a normative reference, the reader is referred to the companion specification [PROV-N]. PROV-N is a notation aimed at human consumption, with the following characteristics:
An activity with identifier a1 and an attribute type with value createFile.
activity(a1, [ prov:type="createFile" ])Two entities with identifiers e1 and e2.
entity(e1) entity(e2)The activity a1 used e1, and e2 was generated by a1.
used(a1, e1) wasGeneratedBy(e2, a1)The same descriptions, but with an explicit identifier u1 for the usage, and the syntactic marker '-' to mark the absence of identifier in the generation. Both are followed by ';'.
used(u1; a1, e1) wasGeneratedBy(-; e2, a1)
This section is non-normative.
Section 2 has introduced some provenance concepts, and how they are expressed as types or relations in the PROV data model. The purpose of this section is to put these concepts into practice in order to express the provenance of some document published on the Web. With this realistic example, PROV concepts are composed together, and a graphical illustration shows a provenance description forming a directed graph, rooted at the entity we want to explain the provenance of, and pointing to the entities, activities, and agents it depended on. This example also shows that, sometimes, multiple provenance descriptions about the same entity can co-exist, which then justifies the need for provenance of provenance.
In this example, we consider one of the many documents published by the World Wide Web Consortium, and describe its provenance. Specifically, we consider the document identified by http://www.w3.org/TR/2011/WD-prov-dm-20111215. Its provenance can be expressed from several perspectives: first, provenance can take the authors' viewpoint; second, it can be concerned with the W3C process. Then, attribution of these two provenance descriptions is provided.
This section is non-normative.
Description: A document is edited by some editor, using contributions from various contributors.
In this perspective, provenance of the document http://www.w3.org/TR/2011/WD-prov-dm-20111215 is concerned with the editing activity as perceived by authors. This kind of information could be used by authors in their CV or in a narrative about this document.
We paraphrase some PROV descriptions, express them with the PROV-N notation, and depict them with a graphical illustration (see Figure 2). Full details of the provenance record can be found here.
entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version="2" ])
activity(ex:edit1, [ prov:type="editing" ])
wasGeneratedBy(tr:WD-prov-dm-20111215, ex:edit1, -)
agent(ex:Paolo, [ prov:type='prov:Person' ]) agent(ex:Simon, [ prov:type='prov:Person' ])
wasAssociatedWith(ex:edit1, ex:Paolo, -, [ prov:role="editor" ]) wasAssociatedWith(ex:edit1, ex:Simon, -, [ prov:role="contributor" ])
Provenance descriptions can be illustrated graphically. The illustration is not intended to represent all the details of the model, but it is intended to show the essence of a set of provenance descriptions [PROV-LAYOUT]. Therefore, it should not be seen as an alternate notation for expressing provenance.
The graphical illustration takes the form of a graph. Entities, activities and agents are represented as nodes, with oval, rectangular, and pentagonal shapes, respectively. Usage, Generation, Derivation, and Association are represented as directed edges.
Entities are laid out according to the ordering of their generation. We endeavor to show time progressing from left to right. This means that edges for Usage, Generation, Derivation, Association typically point leftwards
Description: The World Wide Web Consortium publishes documents according to its publication policy. Working drafts are published regularly to reflect the work accomplished by working groups. Every publication of a working draft must be preceded by a "publication request" to the Webmaster. The very first version of a document must also be preceded by a "transition request" to be approved by the W3C director. All working drafts are made available at a unique IRI. In this scenario, we consider two successive versions of a given document, the policy according to which they were published, and the associated requests.
We describe the kind of provenance record that the WWW Consortium could keep for auditors to check that due processes are followed. All entities involved in this example are Web resources, with well-defined IRIs (some of which refer to archived email messages, available to W3C Members).
We now paraphrase some PROV descriptions, and express them with the PROV-N notation, and depict them with a graphical illustration (see Figure 3). Full details of the provenance record can be found here.
entity(tr:WD-prov-dm-20111215, [ prov:type='rec54:WD' ])
activity(ex:act2, [ prov:type="publish" ])
wasGeneratedBy(tr:WD-prov-dm-20111215, ex:act2, -)
used(ex:act2, email:2011Dec/0111, -)
wasAssociatedWith(ex:act2, w3:Consortium, process:rec-advance)This relation is illustrated in Figure 3 with a multi-edge labelled wasAssociatedWith pointing to an agent and entity (representing a plan).
This simple example has shown a variety of PROV concepts, such as Entity, Agent, Activity, Usage, Generation, Derivation, and Association. In this example, it happens that all entities were already Web resources, with readily available IRIs, which we used. We note that some of the resources are public, whereas others have restricted access: provenance statements only make use of their identifiers. If identifiers do not pre-exist, e.g. for activities, then they can be generated, for instance ex:act2, occurring in the namespace identified by prefix ex. We note that the IRI scheme developed by W3C is particularly suited for expressing provenance of these documents, since each IRI denotes a specific version of a document. It then becomes easy to relate the various versions with PROV relations. We note that an Association is a ternary relation (represented by a multi-edge labeled wasAssociatedWith) from an activity to an agent and a plan.
The two previous sections offer two different perspectives on the provenance of a document. PROV allows for multiple sources to provide the provenance of a subject. For users to decide whether they can place their trust in the document, they may want to analyze its provenance, but also determine who the provenance is attributed to, and when it was generated, etc. In other words, we need to be able to express the provenance of provenance.
PROV-DM offers a construct to name a bundle of provenance descriptions (full details: ex:author-view).
bundle ex:author-view agent(ex:Paolo, [ prov:type='prov:Person' ]) agent(ex:Simon, [ prov:type='prov:Person' ]) ... endBundleLikewise, the process view can be expressed as a separate named bundle (full details: ex:process-view).
bundle ex:process-view agent(w3:Consortium, [ prov:type='prov:Organization' ]) ... endBundle
To express their respective provenance, these bundles must be seen as entities, and all PROV constructs are now available to express their provenance. In the example below, ex:author-view is attributed to the agent ex:Simon, whereas ex:process-view to w3:Consortium.
entity(ex:author-view, [ prov:type='prov:Bundle' ]) wasAttributedTo(ex:author-view, ex:Simon) entity(ex:process-view, [ prov:type='prov:Bundle' ]) wasAttributedTo(ex:process-view, w3:Consortium)
Provenance concepts, expressed as PROV-DM types and relations, are organized according to six components that are defined in this section. The components and their dependencies are illustrated in Figure 4. A component that relies on concepts defined in another is displayed above it in the figure. So, for example, component 5 (alternate) depends on concepts defined in component 4 (bundles), itself dependent on concepts defined in component 1 (entity and activity).
While not all PROV-DM relations are binary, they all involve two primary elements. Hence, Table 4 indexes all relations (except wasInfluencedBy) according to their two primary elements (referred to as subject and object). The table adopts the same color scheme as Figure 4, allowing components to be readily identified. Relation names appearing in bold correspond to the core structures introduced in Section 2.1.
The letters 'R' and 'L' appearing in the right-hand side of some cells of Table 4 indicate that attributes prov:role (Section 18.104.22.168) and prov:location (Section 22.214.171.124) are permitted for these relations. The letter 'T' indicates an OPTIONAL time is also permitted.
Some PROV-DM relations are not binary and involve extra optional element. They are summarized in Table 5 grouping secondary objects, according to their type. The table also adopts the same color scheme as Figure 4, allowing components to be readily identified. None of these relations correspond to the core structures introduced in Section 2.1.
|Activity||WasAssociatedWith (plan)||WasStartedBy (starter)|
Table 6 is a complete index of all the types and relations of PROV-DM, color-coded according to the component they belong to. In the first column, concept names link to their informal definition, whereas, in the second column, representations link to the information used to represent the concept. Concept names appearing in bold in the first column are the core structures introduced in Section 2.1. Likewise, these core structures have their names and parameters highlighted in bold in the second column (prov-n representation); expanded structures are not represented with a bold font.
|Type or Relation Name||Representation in the PROV-N notation||Component|
|Entity||entity(id, [ attr1=val1, ...])||Component 1: Entities/Activities|
|Activity||activity(id, st, et, [ attr1=val1, ...])|
|Derivation||wasDerivedFrom(id; e2, e1, a, g2, u1, attrs)||Component 2: Derivations|
|Revision||... prov:type='prov:Revision' ...|
|Quotation||... prov:type='prov:Quotation' ...|
|Primary Source||... prov:type='prov:PrimarySource' ...|
|Agent||agent(id, [ attr1=val1, ...])||Component 3: Agents, Responsibility, Influence|
|Plan||... prov:type='prov:Plan' ...|
|Person||... prov:type='prov:Person' ...|
|Organization||... prov:type='prov:Organization' ...|
|SoftwareAgent||... prov:type='prov:SoftwareAgent' ...|
|Bundle constructor||bundle id description_1 ... description_n endBundle||Component 4: Bundles|
|Bundle type||... prov:type='prov:Bundle' ...|
|Alternate||alternateOf(alt1, alt2)||Component 5: Alternate|
|Collection||... prov:type='prov:Collection' ...||Component 6: Collections|
|EmptyCollection||... prov:type='prov:EmptyCollection' ...|
In the rest of the section, each type and relation is defined informally, followed by a summary of the information used to represent the concept, and illustrated with PROV-N examples.
The first component of PROV-DM is concerned with entities and activities, and their interrelations: Used (Usage), WasGeneratedBy (Generation), WasStartedBy (Start), WasEndedBy (End), WasInvalidatedBy (Invalidation), and WasInformedBy (Communication). Figure 5 uses UML to depict the first component. Core structures are displayed in the yellow area, consisting of two classes (Entity, Activity) and three binary associations between them: Used (Usage), WasGeneratedBy (Generation), and WasInformedBy (Communication). The rest of the figure displays extended structures, including UML association classes (see [UML], section 7.3.4, p. 42), represented in gray, to express expanded n-ary relations for Used (Usage), WasGeneratedBy (Generation), WasInvalidatedBy (Invalidation), WasStartedBy (Start), WasEndedBy (End). The figure also makes explicit associations with time for these concepts (time being marked with the primitive stereotype). When not specified, cardinality is assumed to be 0..*.
The following expression
entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version="2" ])states the existence of an entity, denoted by identifier tr:WD-prov-dm-20111215, with type document and version number 2. The attribute ex:version is application specific, whereas the attribute type (see Section 126.96.36.199) is reserved in the PROV namespace.
The following expression
activity(a1, 2011-11-16T16:05:00, 2011-11-16T16:06:00, [ ex:host="server.example.org", prov:type='ex:edit' ])
states the existence of an activity with identifier a1, start time 2011-11-16T16:05:00, and end time 2011-11-16T16:06:00, running on host server.example.org, and of type edit. The attribute host is application specific (declared in some namespace with prefix ex). The attribute type is a reserved attribute of PROV-DM, allowing for sub-typing to be expressed (see Section 188.8.131.52).
Given that a generation is the completion of production of an entity, it is instantaneous.
While each of id, activity, time, and attributes is OPTIONAL, at least one of them MUST be present.
The following expressions
wasGeneratedBy(e1, a1, 2001-10-26T21:32:52, [ ex:port="p1" ]) wasGeneratedBy(e2, a1, 2001-10-26T10:00:00, [ ex:port="p2" ])
state the existence of two generations (with respective times 2001-10-26T21:32:52 and 2001-10-26T10:00:00), at which new entities, identified by e1 and e2, were created by an activity, identified by a1. The first one was available on port p1, whereas the other was available on port p2. The semantics of port are application specific.
In some cases, we may want to record the time at which an entity was generated without having to specify the activity that generated it. To support this requirement, the activity element in generation is optional. Hence, the following expression indicates the time at which an entity is generated, without naming the activity that did it.
wasGeneratedBy(e, -, 2001-10-26T21:32:52)
Usage ◊ is the beginning of utilizing an entity by an activity. Before usage, the activity had not begun to utilize this entity and could not have been affected by the entity. (Note: This definition is formulated for a given usage; it is permitted for an activity to have used a same entity multiple times.)
Given that a usage is the beginning of utilizing an entity, it is instantaneous.
While each of id, entity, time, and attributes is OPTIONAL, at least one of them MUST be present.
A reference to a given entity MAY appear in multiple usages that share a given activity identifier.
The following usages
used(a1, e1, 2011-11-16T16:00:00, [ ex:parameter="p1" ]) used(a1, e2, 2011-11-16T16:00:01, [ ex:parameter="p2" ])
state that the activity identified by a1 used two entities identified by e1 and e2, at times 2011-11-16T16:00:00 and 2011-11-16T16:00:01, respectively; the first one was found as the value of parameter p1, whereas the second was found as value of parameter p2. The semantics of parameter is application specific.
A communication implies that activity a2 is dependent on another a1, by way of some unspecified entity that is generated by a1 and used by a2.
Consider two activities a1 and a2, the former performed by a government agency, and the latter by a driver caught speeding.
activity(a1, [ prov:type="traffic regulations enforcing" ]) activity(a2, [ prov:type="fine paying" ]) wasInformedBy(a2, a1)The last line indicates that some implicit entity was generated by a1 and used by a2; this entity may be a traffic ticket that had a notice of fine, amount, and payment mailing details.
Given that a start is when an activity is deemed to have started, it is instantaneous.
While each of id, trigger, starter, time, and attributes is OPTIONAL, at least one of them MUST be present.
The following example contains the description of an activity a1 (a discussion), which was started at a specific time, and was triggered by an email message e1.
entity(e1, [ prov:type="email message"] ) activity(a1, [ prov:type="Discuss" ]) wasStartedBy(a1, e1, -, 2011-11-16T16:05:00)Furthermore, if the message is also an input to the activity, this can be described as follows:
used(a1, e1, -)
Alternatively, one can also describe the activity that generated the email message.
activity(a0, [ prov:type="Write" ]) wasGeneratedBy(e1, a0) wasStartedBy(a1, e1, a0, 2011-11-16T16:05:00)
If e1 is not known, it would also be valid to write:
wasStartedBy(a1, -, a0, 2011-11-16T16:05:00)
In the following example, a race is started by a bang, and responsibility for this trigger is attributed to an agent ex:Bob.
activity(ex:foot_race) entity(ex:bang) wasStartedBy(ex:foot_race, ex:bang, -, 2012-03-09T08:05:08-05:00) agent(ex:Bob) wasAttributedTo(ex:bang, ex:Bob)
In this example, filling the fuel tank was started as a consequence of observing low fuel. The trigger entity is unspecified, it could for instance have been the low fuel warning light, the fuel tank indicator needle position, or the engine not running properly.
activity(ex:filling-fuel) activity(ex:observing-low-fuel) agent(ex:driver, [ prov:type='prov:Person' ) wasAssociatedWith(ex:filling-fuel, ex:driver) wasAssociatedWith(ex:observing-low-fuel, ex:driver) wasStartedBy(ex:filling-fuel, -, ex:observing-low-fuel, -)
The relations wasStartedBy and used are orthogonal, and thus need to be expressed independently, according to the situation being described.
Given that an end is when an activity is deemed to have ended, it is instantaneous.
While each of id, trigger, ender, time, and attributes is OPTIONAL, at least one of them MUST be present.
The following example is a description of an activity a1 (editing) that was ended following an approval document e1.
entity(e1, [ prov:type="approval document" ]) activity(a1, [ prov:type="Editing" ]) wasEndedBy(a1, e1, -, -)
Given that an invalidation is the start of destruction, cessation, or expiry, it is instantaneous.
Entities have a duration. Generation marks the beginning of an entity, whereas invalidation marks its end. An entity's lifetime can end for different reasons:
In the first two cases, the entity has physically disappeared after its termination: there is no more soup, or painting. In the third case, there may be an "offer voucher" that still exists, but it is no longer valid; likewise, on April 4th, the BBC news site still exists but it is not the same entity as BBC news Web site on April 3rd; or the green traffic light (an entity with a fixed aspect green light) became the red traffic light (another entity with a fixed aspect red light).
While each of id, activity, time, and attributes is OPTIONAL, at least one of them MUST be present.
The Painter, a Picasso painting, is known to have been destroyed in a plane accident.
entity(ex:The-Painter) agent(ex:Picasso) wasAttributedTo(ex:The-Painter, ex:Picasso) activity(ex:crash) wasInvalidatedBy(ex:The-Painter, ex:crash, 1998-09-03T01:31:00, [ ex:circumstances="plane accident" ])
The BBC news home page on 2012-04-03 ex:bbcNews2012-04-03 contained a reference to a given news item bbc:news/uk-17595024, but the BBC news home page on the next day did not.
entity(ex:bbcNews2012-04-03) hadMember(ex:bbcNews2012-04-03, bbc:news/uk-17595024) wasGeneratedBy (ex:bbcNews2012-04-03, -, 2012-04-03T00:00:01) wasInvalidatedBy(ex:bbcNews2012-04-03, -, 2012-04-03T23:59:59)We refer to example Example 43 for further descriptions of the BBC Web site, and to Section 5.6.2 for a description of the relation hadMember.
In this example, the "buy one beer, get one free" offer expired at the end of the happy hour.
entity(buy_one_beer_get_one_free_offer_during_happy_hour) wasAttributedTo(buy_one_beer_get_one_free_offer_during_happy_hour, proprietor) wasInvalidatedBy(buy_one_beer_get_one_free_offer_during_happy_hour, -,2012-03-10T18:00:00)
In contrast, in the following descriptions, Bob redeemed the offer 45 minutes before it expired, and got two beers.
entity(buy_one_beer_get_one_free_offer_during_happy_hour) wasAttributedTo(buy_one_beer_get_one_free_offer_during_happy_hour, proprietor) activity(redeemOffer) entity(twoBeers) wasAssociatedWith(redeemOffer, bob) used(redeemOffer, buy_one_beer_get_one_free_offer_during_happy_hour, 2012-03-10T17:15:00) wasInvalidatedBy(buy_one_beer_get_one_free_offer_during_happy_hour, redeemOffer, 2012-03-10T17:15:00) wasGeneratedBy(twoBeers,redeemOffer)
We see that the offer was both used to be converted into twoBeers and invalidated by the redeemOffer activity: in other words, the combined usage and invalidation indicate consumption of the offer.
The second component of PROV-DM is concerned with: derivations of entities from other entities and derivation subtypes WasRevisionOf (Revision), WasQuotedFrom (Quotation), and HasPrimarySource (Primary Source). Figure 6 depicts the third component with PROV core structures in the yellow area, including two classes (Entity, Activity) and binary association WasDerivedFrom (Derivation). PROV extended structures are found outside this area. UML association classes express expanded n-ary relations. The subclasses are marked by the UML stereotype "prov:type" to indicate that the corresponding types are valid values for the attribute prov:type.
According to Section 2, for an entity to be transformed from, created from, or resulting from an update to another, there must be some underpinning activity or activities performing the necessary action(s) resulting in such a derivation. A derivation can be described at various levels of precision. In its simplest form, derivation relates two entities. Optionally, attributes can be added to represent further information about the derivation. If the derivation is the result of a single known activity, then this activity can also be optionally expressed. To provide a completely accurate description of the derivation, the generation and usage of the generated and used entities, respectively, can be provided, so as to make the derivation path, through usage, activity, and generation, explicit. Optional information such as activity, generation, and usage can be linked to derivations to aid analysis of provenance and to facilitate provenance-based reproducibility.
The following descriptions are about derivations between e2 and e1, but no information is provided as to the identity of the activity (and usage and generation) underpinning the derivation. In the second line, a type attribute is also provided.
wasDerivedFrom(e2, e1) wasDerivedFrom(e2, e1, [ prov:type="physical transform" ])
The following description expresses that activity a, using the entity e1 according to usage u1, derived the entity e2 and generated it according to generation g2. It is followed by descriptions for generation g2 and usage u1.
wasDerivedFrom(e2, e1, a, g2, u1) wasGeneratedBy(g2; e2, a, -) used(u1; a, e1, -)
With such a comprehensive description of derivation, a program that analyzes provenance can identify the activity underpinning the derivation, it can identify how the preceding entity e1 was used by the activity (e.g. for instance, which argument it was passed as, if the activity is the result of a function invocation), and which output the derived entity e2 was obtained from (say, for a function returning multiple results).
A revision ◊ is a derivation for which the resulting entity is a revised version of some original.
The implication here is that the resulting entity contains substantial content from the original. A revision ◊ relation is a kind of derivation relation from a revised entity to a preceding entity. The type of a revision relation is denoted by: prov:Revision ◊. PROV defines no revision-specific attributes.
Revisiting the example of Section 4.2, we can now state that the report tr:WD-prov-dm-20111215 was a revision of the report tr:WD-prov-dm-20111018.
entity(tr:WD-prov-dm-20111215, [ prov:type='rec54:WD' ]) entity(tr:WD-prov-dm-20111018, [ prov:type='rec54:WD' ]) wasDerivedFrom(tr:WD-prov-dm-20111215, tr:WD-prov-dm-20111018, [ prov:type='prov:Revision' ])
A quotation ◊ is the repeat of (some or all of) an entity, such as text or image, by someone who may or may not be its original author.
A quotation ◊ relation is a kind of derivation relation, for which an entity was derived from a preceding entity by copying, or "quoting", some or all of it. The type of a quotation relation is denoted by: prov:Quotation ◊. PROV defines no quotation-specific attributes.
The following paragraph is a quote from one of the author's blogs.
"During the workshop, it became clear to me that the consensus based models (which are often graphical in nature) can not only be formalized but also be directly connected to these database focused formalizations. I just needed to get over the differences in syntax. This could imply that we could have nice way to trace provenance across systems and through databases and be able to understand the mathematical properties of this interconnection."
If wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/ denotes the original blog by agent ex:Paul, and dm:bl-dagstuhl denotes the above paragraph, then the following descriptions express that the above paragraph was copied by agent ex:Luc from a part of the blog, attributed to the agent ex:Paul.
entity(wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/) entity(dm:bl-dagstuhl) agent(ex:Luc) agent(ex:Paul) wasDerivedFrom(dm:bl-dagstuhl, wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/, [ prov:type='prov:Quotation' ]) wasAttributedTo(dm:bl-dagstuhl, ex:Luc) wasAttributedTo(wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/, ex:Paul)
A primary source ◊ for a topic refers to something produced by some agent with direct experience and knowledge about the topic, at the time of the topic's study, without benefit from hindsight.
Because of the directness of primary sources, they "speak for themselves" in ways that cannot be captured through the filter of secondary sources. As such, it is important for secondary sources to reference those primary sources from which they were derived, so that their reliability can be investigated.
It is also important to note that a given entity might be a primary source for one entity but not another. It is the reason why Primary Source is defined as a relation as opposed to a subtype of Entity.
A primary source ◊ relation is a kind of a derivation relation from secondary materials to their primary sources. It is recognized that the determination of primary sources can be up to interpretation, and should be done according to conventions accepted within the application's domain. The type of a primary source relation is denoted by: prov:PrimarySource ◊. PROV defines no attributes specific to primary source.
Let us consider Charles Joseph Minard's flow map of Napoleon's March in 1812, which was published in 1869. Although the map is not a primary source, Minard probably used the journal of Pierre-Irénée Jacob, pharmacist to Napoleon's army during the Russian campaign. This primary source relation can be encoded as follows.
entity(ex:la-campagne-de-Russie-1812-1813, [ prov:type="map" ]) entity(ex:revue-d-Histoire-de-la-Pharmacie-t-XVIII, [ prov:type="journal" ]) wasDerivedFrom(ex:la-campagne-de-Russie-1812-1813, ex:revue-d-Histoire-de-la-Pharmacie-t-XVIII, [ prov:type='prov:PrimarySource' ])
The third component of PROV-DM, depicted in Figure 7, is concerned with agents and the relations WasAttributedTo (Attribution), WasAssociatedWith (Association), and ActedOnBehalfOf (Delegation), relating agents to entities, activities, and agents, respectively. Core structures are displayed in the yellow area and include three classes and three binary associations. Outside the yellow area, extended structures comprise UML association classes to express expanded n-ary relations, and subclasses Plan, Person, SoftwareAgent, and Organization. The subclasses are marked by the UML stereotype "prov:type" to indicate that that these are valid values for the attribute prov:type.
Component 3 further defines a general notion of influence, a relation implied by all relations defined so far. Figure 8 displays one new association class, generalizing previously introduced associations.
An agent may be a particular type of entity or activity. This means that the model can be used to express provenance of the agents themselves.
It is useful to define some basic categories of agents from an interoperability perspective. There are three types of agents that are common across most anticipated domains of use; it is acknowledged that these types do not cover all kinds of agent.
PROV defines no attributes specific to SoftwareAgent, Organization, and Person.
The following expression is about an agent identified by e1, which is a person, named Alice, with employee number 1234.
agent(e1, [ex:employee="1234", ex:name="Alice", prov:type='prov:Person' ])
It is optional to specify the type of an agent. When present, it is expressed using the prov:type attribute.
When an entity e is attributed to agent ag, entity e was generated by some unspecified activity that in turn was associated to agent ag. Thus, this relation is useful when the activity is not known, or irrelevant.
Revisiting the example of Section 4.1, we can ascribe tr:WD-prov-dm-20111215 to some agents without an explicit activity.
agent(ex:Paolo, [ prov:type='prov:Person' ]) agent(ex:Simon, [ prov:type='prov:Person' ]) entity(tr:WD-prov-dm-20111215, [ prov:type='rec54:WD' ]) wasAttributedTo(tr:WD-prov-dm-20111215, ex:Paolo, [ prov:type="editorship" ]) wasAttributedTo(tr:WD-prov-dm-20111215, ex:Simon, [ prov:type="authorship" ])
While each of id, agent, plan, and attributes is OPTIONAL, at least one of them MUST be present.
A plan ◊ is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals. The type of a Plan entity is denoted by prov:Plan ◊.
PROV defines no plan-specific attributes.
In the following example, a designer agent and an operator agent are associated with an activity. The designer's goals are achieved by a workflow ex:wf, described as an entity of type plan.
activity(ex:a, [ prov:type="workflow execution" ]) agent(ex:ag1, [ prov:type="operator" ]) agent(ex:ag2, [ prov:type="designer" ]) wasAssociatedWith(ex:a, ex:ag1, -, [ prov:role="loggedInUser", ex:how="webapp" ]) wasAssociatedWith(ex:a, ex:ag2, ex:wf, [ prov:role="designer", ex:context="project1" ]) entity(ex:wf, [ prov:type='prov:Plan' , ex:label="Workflow 1", prov:location="http://example.org/workflow1.bpel" %% xsd:anyURI ])Since the workflow ex:wf is itself an entity, its provenance can also be expressed in PROV: it can be generated by some activity and derived from other entities, for instance.
In some cases, one wants to indicate a plan was followed, without having to specify which agent was involved.
activity(ex:a, [ prov:type="workflow execution" ]) wasAssociatedWith(ex:a, -, ex:wf) entity(ex:wf, [ prov:type='prov:Plan', ex:label="Workflow 1", ex:url="http://example.org/workflow1.bpel" %% xsd:anyURI])In this case, it is assumed that an agent exists, but it has not been specified.
For example, a student acted on behalf of his or her supervisor, who acted on behalf of the department chair, who acted on behalf of the university; all those agents are responsible in some way for the activity that took place but we do not say explicitly who bears responsibility and to what degree.
The following fragment describes three agents: a programmer, a researcher, and a funder. The programmer and researcher are associated with a workflow activity. The programmer acts on behalf of the researcher (line-management) encoding the commands specified by the researcher; the researcher acts on behalf of the funder, who has a contractual agreement with the researcher. The terms 'line-management' and 'contract' used in this example are domain specific.
activity(a,[ prov:type="workflow" ]) agent(ag1, [ prov:type="programmer" ]) agent(ag2, [ prov:type="researcher" ]) agent(ag3, [ prov:type="funder" ]) wasAssociatedWith(a, ag1, [ prov:role="loggedInUser" ]) wasAssociatedWith(a, ag2) wasAssociatedWith(a, ag3) actedOnBehalfOf(ag1, ag2, a, [ prov:type="line-management" ]) actedOnBehalfOf(ag2, ag3, a, [ prov:type="contract" ])
Influence ◊ is the capacity of an entity, activity, or agent to have an effect on the character, development, or behavior of another by means of usage, start, end, generation, invalidation, communication, derivation, attribution, association, or delegation.
An influence relation between two objects o2 and o1 is a generic dependency of o2 on o1 that signifies some form of influence of o1 on o2.
A usage, start, end, generation, invalidation, communication, derivation, attribution, association, and delegation is also an influence. It is RECOMMENDED to adopt these more specific relations when writing provenance descriptions. It is anticipated that the Influence relation may be useful to express queries over provenance information.
wasInfluencedBy(tr:WD-prov-dm-20111215, w3:Consortium)Instead, it is recommended to express the more specific description:
The fourth component of PROV-DM is concerned with bundles, a mechanism to support provenance of provenance. Figure 9 depicts a UML class diagram for the fourth component. It comprises a Bundle class defined as a subclass of Entity.
A bundle ◊ is a named set of provenance descriptions, and is itself an entity, so allowing provenance of provenance to be expressed.
A bundle's identifier id identifies a unique set of descriptions.
There may be other kinds of bundles not directly expressible by this constructor, such as provenance descriptions handwritten on a letter or a whiteboard, etc. Whatever the means by which bundles are expressed, all can be described, as in the following section.
A bundle is a named set of descriptions, but it is also an entity so that its provenance can be described.
PROV defines the following type for bundles ◊:
PROV defines no bundle-specific attributes.
A bundle description is of the form entity(id, [ prov:type='prov:Bundle', attr1=val1, ...] ) where id is an identifier denoting a bundle, a type prov:Bundle and an OPTIONAL set of attribute-value pairs ((attr1, val1), ...) representing additional information about this bundle.
The provenance of provenance can then be described using PROV constructs, as illustrated by Example 40 and Example 41.
Let us consider two entities ex:report1 and ex:report2.
entity(ex:report1, [ prov:type="report", ex:version=1 ]) wasGeneratedBy(ex:report1, -, 2012-05-24T10:00:01) entity(ex:report2, [ prov:type="report", ex:version=2]) wasGeneratedBy(ex:report2, -, 2012-05-25T11:00:01) wasDerivedFrom(ex:report2, ex:report1)
Let us assume that Bob observed the creation of ex:report1. A first bundle can be expressed.
bundle bob:bundle1 entity(ex:report1, [ prov:type="report", ex:version=1 ]) wasGeneratedBy(ex:report1, -, 2012-05-24T10:00:01) endBundle
In contrast, Alice observed the creation of ex:report2 and its derivation from ex:report1. A separate bundle can also be expressed.
bundle alice:bundle2 entity(ex:report1) entity(ex:report2, [ prov:type="report", ex:version=2 ]) wasGeneratedBy(ex:report2, -, 2012-05-25T11:00:01) wasDerivedFrom(ex:report2, ex:report1) endBundle
The first bundle contains the descriptions corresponding to Bob observing the creation of ex:report1. Its provenance can be described as follows.
entity(bob:bundle1, [ prov:type='prov:Bundle' ]) wasGeneratedBy(bob:bundle1, -, 2012-05-24T10:30:00) wasAttributedTo(bob:bundle1, ex:Bob)
In contrast, the second bundle is attributed to Alice who observed the derivation of ex:report2 from ex:report1.
entity(alice:bundle2, [ prov:type='prov:Bundle' ]) wasGeneratedBy(alice:bundle2, -, 2012-05-25T11:15:00) wasAttributedTo(alice:bundle2, ex:Alice)
A provenance aggregator could merge two bundles, resulting in a novel bundle, whose provenance is described as follows.
bundle agg:bundle3 entity(ex:report1, [ prov:type="report", ex:version=1 ]) wasGeneratedBy(ex:report1, -, 2012-05-24T10:00:01) entity(ex:report2, [ prov:type="report", ex:version=2 ]) wasGeneratedBy(ex:report2, -, 2012-05-25T11:00:01) wasDerivedFrom(ex:report2, ex:report1) endBundle entity(agg:bundle3, [ prov:type='prov:Bundle' ]) agent(ex:aggregator01, [ prov:type='ex:Aggregator' ]) wasAttributedTo(agg:bundle3, ex:aggregator01) wasDerivedFrom(agg:bundle3, bob:bundle1) wasDerivedFrom(agg:bundle3, alice:bundle2)
The new bundle is given a new identifier agg:bundle3 and is attributed to the ex:aggregator01 agent.
The fifth component of PROV-DM is concerned with relations SpecializationOf (Specialization) and AlternateOf (Alternate) between entities. Figure 10 depicts the fifth component with a single class and two binary associations.
Two provenance descriptions about the same thing may emphasize differents aspects of that thing.
User Alice writes an article. In its provenance, she wishes to refer to the precise version of the article with a date-specific IRI, as she might edit the article later. Alternatively, user Bob refers to the article in general, independently of its variants over time.
The PROV data model introduces relations, called specialization and alternate that allow entities to be linked together. They are defined as follows.
Examples of aspects include a time period, an abstraction, and a context associated with the entity.
A specialization is not, as defined here, also an influence, and therefore does not have an id and attributes.
The BBC news home page on 2012-03-23 ex:bbcNews2012-03-23 is a specialization of the BBC news page in general bbc:news/. This can be expressed as follows.
specializationOf(ex:bbcNews2012-03-23, bbc:news/)We have created a new qualified name, ex:bbcNews2012-03-23, in the namespace ex, to identify the specific page carrying this day's news, which would otherwise be the generic bbc:news/ page.
An alternate is not, as defined here, also an influence, and therefore does not have an id and attributes.
Note that alternateOf is a necessarily very general relationship that, in reasoning, only states that the two alternate entities respectively fix some aspects of some common thing (possibly evolving over time), and so there is some relevant connection between the provenance of the alternates. In a specific application context, alternateOf, or a subtype of it, could allow more inferences.
entity(bbc:news/science-environment-17526723, [ prov:type="a news item for desktop"]) entity(bbc:news/mobile/science-environment-17526723, [ prov:type="a news item for mobile devices"]) alternateOf(bbc:news/science-environment-17526723, bbc:news/mobile/science-environment-17526723)
entity(tr:WD-prov-dm-20111018) entity(tr:WD-prov-dm-20111215) alternateOf(tr:WD-prov-dm-20111018, tr:WD-prov-dm-20111215)
They are both specializations of the page http://www.w3.org/TR/prov-dm/.
The sixth component of PROV-DM is concerned with the notion of collections. A collection is an entity that has some members. The members are themselves entities, and therefore their provenance can be expressed. Some applications need to be able 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 purpose of Component 6 is to define the types and relations that are useful to express the provenance of collections.
Figure 11 depicts the sixth component with two new classes (Collection, Empty Collection) and one association HadMember (Membership).
PROV-DM defines the following types related to collections:
PROV defines no collection-specific attributes.
entity(c0, [ prov:type='prov:EmptyCollection' ]) // c0 is an empty collection entity(c1, [ prov:type='prov:Collection' ]) // c1 is a collection, with unknown content
A membership relation is defined for stating the members of a Collection.Membership ◊ is the belonging of an entity to a collection.
Membership is not, as defined here, also an influence, and therefore does not have an id and attributes.
In this example, c is a collection known to have e0, e1, and e2 as members, and may have other members.
entity(e0) entity(e1) entity(e2) entity(c, [prov:type='prov:Collection' ]) // c is a collection, with unknown content hadMember(c, e0) hadMember(c, e1) hadMember(c, e2)
An identifier ◊ is a qualified name.
Entity, Activity, and Agent have a mandatory identifier. Two entities (resp. activities, agents) are equal if they have the same identifier.
Generation, Usage, Communication, Start, End, Invalidation, Derivation, Attribution, Association, Delegation, Influence have an optional identifier. Two generations (resp. usages, communications, etc.) are equal if they have the same identifier.
An attribute ◊ is a qualified name.
The PROV data model introduces a pre-defined set of attributes in the PROV namespace, which we define below. This specification does not provide any interpretation for any attribute declared in any other namespace.
|prov:label||any construct||A Value of type xsd:string||Section 184.108.40.206|
|prov:location||Entity, Activity, Agent, Usage, Generation, Invalidation, Start, and End||A Value||Section 220.127.116.11|
|prov:role||Usage, Generation, Invalidation, Association, Start, and End||A Value||Section 18.104.22.168|
|prov:type||any construct||A Value||Section 22.214.171.124|
|prov:value||Entity||A Value||Section 126.96.36.199|
The attribute prov:label ◊ provides a human-readable representation of an instance of a PROV-DM type or relation. The value associated with the attribute prov:label MUST be a string.
The following entity is provided with a label attribute.
entity(ex:e1, [ prov:label="This is a human-readable label" ])
The following entity has two label attributes, in French and English.
entity(ex:car01, [ prov:label="Voiture 01"@fr, prov:label="Car 01"@en ])
A location ◊ can be an identifiable geographic place (ISO 19112), but it can also be a non-geographic place such as a directory, row, or column. As such, there are numerous ways in which location can be expressed, such as by a coordinate, address, landmark, and so forth. This document does not specify how to concretely express locations, but instead provide a mechanism to introduce locations, by means of a reserved attribute.
The attribute prov:location is an OPTIONAL attribute of Entity, Activity, Agent, Usage, Generation, Invalidation, Start, and End. The value associated with the attribute prov:location MUST be a PROV-DM Value, expected to denote a location.
While the attribute prov:location is allowed for several PROV concepts, it may not make sense to use it in some cases. For example, an activity that describes the relocation of an entity will have start and end locations, as well as every place in between those points.
The following expression describes entity Mona Lisa, a painting, with a location attribute.
entity(ex:MonaLisa, [ prov:location="Le Louvre, Paris", prov:type="StillImage" ])
The following expression describes a cell, at coordinates (5,5), with value 10.
entity(ex:cell, [ prov:location="(5,5)", prov:value="10" %% xsd:integer ])
A role ◊ is the function of an entity or agent with respect to an activity, in the context of a usage, generation, invalidation, association, start, and end.
The attribute prov:role is allowed to occur multiple times in a list of attribute-value pairs. The value associated with a prov:role attribute MUST be a PROV-DM Value.
The following activity is associated with an agent acting as the operator.
wasAssociatedWith(a, ag, [ prov:role="operator" ])
In the following expression, the activity ex:div01 used entity ex:cell in the role of divisor.
used(ex:div01, ex:cell, [ prov:role="divisor" ])
The attribute prov:type ◊ provides further typing information for any construct with an optional set of attribute-value pairs.
PROV-DM liberally defines a type as a category of things having common characteristics. PROV-DM is agnostic about the representation of types, and only states that the value associated with a prov:type attribute MUST be a PROV-DM Value. The attribute prov:type is allowed to occur multiple times.
The following describes an agent of type software agent.
agent(ag, [ prov:type='prov:SoftwareAgent' ])
The following types are pre-defined in PROV, and are valid values for the prov:type attribute.
The attribute prov:value ◊ provides a value that is a direct representation of an entity as a PROV-DM Value.
The attribute prov:value is an OPTIONAL attribute of entity. The value associated with the attribute prov:value MUST be a PROV-DM Value. The attribute prov:value MAY occur at most once in a set of attribute-value pairs.
The following example illustrates the provenance of the number 4 obtained by an activity that computed the length of an input string "abcd". The input and the output are expressed as entities ex:in and ex:out, respectively. They each have a prov:value attribute associated with the corresponding value.
entity(ex:in, [ prov:value="abcd" ]) entity(ex:out, [ prov:value=4 ]) activity(ex:len, [ prov:type="string-length" ]) used(ex:len, ex:in) wasGeneratedBy(ex:out, ex:len) wasDerivedFrom(ex:out, ex:in)
Two different entities MAY have the same value for the attribute prov:value. For instance, when two entities, with the same prov:value, are generated by two different activities, as illustrated by the following example.
Example 52 illustrates an entity with a given value 4. This examples shows that another entity with the same value may be computed differently (by an addition).
entity(ex:in1, [ prov:value=3 ]) entity(ex:in2, [ prov:value=1 ]) entity(ex:out2, [ prov:value=4 ]) // ex:out2 also has value 4 activity(ex:add1, [ prov:type="addition" ]) used(ex:add1, ex:in1) used(ex:add1, ex:in2) wasGeneratedBy(ex:out2, ex:add1)
A value ◊ is a constant such as a string, number, time, qualified name, IRI, and encoded binary data, whose interpretation is outside the scope of PROV. Values can occur in attribute-value pairs.
Each kind of such values is called a datatype. Use of the following data types is RECOMMENDED.
The normative definitions of these datatypes are provided by their respective specifications.
Conformance to RDF Datatypes As of the publication of this document, RDF 1.1 Concepts and Abstract Syntax [RDF-CONCEPTS11] is not yet a W3C Recommendation (see http://www.w3.org/TR/rdf11-concepts/ for the latest version). Both the Provenance Working Group and the RDF Working Group are confident that there will be only minor changes before it becomes a W3C Recommendation. In order to take advantage of the anticipated corrections and new features sooner, while also providing stability in case the specification does not advance as expected, conformance to PROV as it relates to RDF Datatypes is defined as follows:
This "change in normative reference" is effective as of the publication of RDF 1.1 as a W3C Recommendation. However, W3C expects to publish a new edition of PROV once RDF 1.1 becomes a Recommendation to update the reference explicitly.
The following examples respectively are the string "abc", the integer number 1, and the IRI "http://example.org/foo".
"abc" "1" %% xsd:integer "http://example.org/foo" %% xsd:anyURI
"ex:value" %% prov:QUALIFIED_NAMEAlternatively, the same value can be expressed using the following convenience notation.
We note that PROV time instants ◊ are defined according to xsd:dateTime [XMLSCHEMA11-2].
A namespace ◊ is identified by an IRI [RFC3987]. In PROV-DM, attributes, identifiers, and values with qualified names as data type can be placed in a namespace using the mechanisms described in this specification.
A namespace declaration ◊ consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this declaration refers to this namespace.
A default namespace declaration ◊ consists of a namespace. Every un-prefixed qualified name refers to default namespace declaration.
The PROV namespace ◊ is identified by the IRI http://www.w3.org/ns/prov#.
PROV-DM stipulates that a qualified name can be mapped into an IRI by concatenating the IRI associated with the prefix and the local part.
A qualified name's prefix is OPTIONAL. If a prefix occurs in a qualified name, it refers to a namespace declared in a namespace declaration. In the absence of prefix, the qualified name refers to the default namespace.
The PROV data model provides extensibility points that allow designers to specialize it for specific applications or domains. We summarize these extensibility points here.
The PROV namespace declares a set of reserved attributes catering for extensibility: prov:type, prov:role, prov:location.
In the following example, e2 is a translation of e1, expressed as a sub-type of derivation.
wasDerivedFrom(e2,e1, [prov:type='ex:Translation' ])
In the following example, e is described as a Car, a type of entity.
entity(e, [prov:type='ex:Car' ])
In the following example, two computers ex:laptop4 and ex:desktop9 are used in different roles in a work activity.
activity(ex:work) entity(ex:laptop4) entity(ex:desktop9) used(ex:work, ex:laptop4, [prov:role="day-to-day machine"]) used(ex:work, ex:desktop9, [prov:role="backup machine"])
The PROV data model is designed to be application and technology independent, but implementers are welcome and encouraged to specialize PROV-DM to specific domains and applications. To ensure interoperability, specializations of the PROV data model that exploit the extensibility points summarized in this section must preserve the semantics specified in this document and in [PROV-CONSTRAINTS].
This specification defines PROV-DM, a data model that allows descriptions of the people, institutions, entities, and activities, involved in producing, influencing, or delivering a piece of data or a thing to be expressed. However, with this data model, it is also possible to compose descriptions that would not make sense: for instance, one could express that an entity was used before it was generated, or that the activity that generated an entity started after the entity generation. A set of constraints have been defined for PROV and can be found in a companion specification [PROV-CONSTRAINTS]. They SHOULD be used by developers to compose provenance descriptions that are valid, and by implementers of reasoning engines aiming to check whether provenance descriptions have problems.
The example of section 3 contains identifiers such as tr:WD-prov-dm-20111215, which denotes a specific version of a technical report. On the other hand, an IRI such as http://www.w3.org/TR/prov-dm/ denotes the latest version of a document. One needs to ensure that provenance descriptions for the latter resource remain valid as the resource state changes.
To this end, PROV allows asserters to describe "partial states" of entities by means of attributes and associated values. Some further constraints apply to the use of these attributes, since the values associated with them are expected to remain unchanged for some period of time. The constraints associated to attributes allow provenance descriptions to be refined, they can also be found in the companion specification [PROV-CONSTRAINTS].
PROV-DM is a conceptual data model which can be serialized in various ways. The following table contains the PROV-O classes and properties, as described in [PROV-O], and PROV-N productions, as described in [PROV-N] that correspond to PROV-DM concepts.
|Primary Source||hadPrimarySource, PrimarySource||type
|Bundle constructor||bundle description||
Please see the Responses to Public Comments on the Last Call Working Draft for more details about the justification of these changes.
This document has been produced by the Provenance Working Group, and its contents reflect extensive discussion within the Working Group as a whole. The editors extend special thanks to Sandro Hawke (W3C/MIT) and Ivan Herman (W3C/ERCIM), W3C contacts for the Provenance Working Group.
The editors acknowledge valuable contributions from the following: Tom Baker, David Booth, Robert Freimuth, Satrajit Ghosh, Ralph Hodgson, Renato Iannella, Jacek Kopecky, James Leigh, Jacco van Ossenbruggen, Alan Ruttenberg, Reza Samavi, and Antoine Zimmermann.
Members of the Provenance Working Group at the time of publication of this document were: Ilkay Altintas (Invited expert), Reza B'Far (Oracle Corporation), Khalid Belhajjame (University of Manchester), James Cheney (University of Edinburgh, School of Informatics), Sam Coppens (iMinds - Ghent University), David Corsar (University of Aberdeen, Computing Science), Stephen Cresswell (The National Archives), Tom De Nies (iMinds - Ghent University), Helena Deus (DERI Galway at the National University of Ireland, Galway, Ireland), Simon Dobson (Invited expert), Martin Doerr (Foundation for Research and Technology - Hellas(FORTH)), Kai Eckert (Invited expert), Jean-Pierre EVAIN (European Broadcasting Union, EBU-UER), James Frew (Invited expert), Irini Fundulaki (Foundation for Research and Technology - Hellas(FORTH)), Daniel Garijo (Universidad Politécnica de Madrid), Yolanda Gil (Invited expert), Ryan Golden (Oracle Corporation), Paul Groth (Vrije Universiteit), Olaf Hartig (Invited expert), David Hau (National Cancer Institute, NCI), Sandro Hawke (W3C/MIT), Jörn Hees (German Research Center for Artificial Intelligence (DFKI) Gmbh), Ivan Herman, (W3C/ERCIM), Ralph Hodgson (TopQuadrant), Hook Hua (Invited expert), Trung Dong Huynh (University of Southampton), Graham Klyne (University of Oxford), Michael Lang (Revelytix, Inc.), Timothy Lebo (Rensselaer Polytechnic Institute), James McCusker (Rensselaer Polytechnic Institute), Deborah McGuinness (Rensselaer Polytechnic Institute), Simon Miles (Invited expert), Paolo Missier (School of Computing Science, Newcastle university), Luc Moreau (University of Southampton), James Myers (Rensselaer Polytechnic Institute), Vinh Nguyen (Wright State University), Edoardo Pignotti (University of Aberdeen, Computing Science), Paulo da Silva Pinheiro (Rensselaer Polytechnic Institute), Carl Reed (Open Geospatial Consortium), Adam Retter (Invited Expert), Christine Runnegar (Invited expert), Satya Sahoo (Invited expert), David Schaengold (Revelytix, Inc.), Daniel Schutzer (FSTC, Financial Services Technology Consortium), Yogesh Simmhan (Invited expert), Stian Soiland-Reyes (University of Manchester), Eric Stephan (Pacific Northwest National Laboratory), Linda Stewart (The National Archives), Ed Summers (Library of Congress), Maria Theodoridou (Foundation for Research and Technology - Hellas(FORTH)), Ted Thibodeau (OpenLink Software Inc.), Curt Tilmes (National Aeronautics and Space Administration), Craig Trim (IBM Corporation), Stephan Zednik (Rensselaer Polytechnic Institute), Jun Zhao (University of Oxford), Yuting Zhao (University of Aberdeen, Computing Science).