The Open Provenance Model core specification (v1.1)

Abstract

The Open Provenance Model is a model of provenance that is designed to meet the following requirements: (1) To allow provenance information to be exchanged between systems, by means of a compatibility layer based on a shared provenance model. (2) To allow developers to build and share tools that operate on such a provenance model. (3) To define provenance in a precise, technologyagnostic manner. (4) To support a digital representation of provenance for any "thing", whether produced by computer systems or not. (5) To allow multiple levels of description to coexist. (6) To define a core set of rules that identify the valid inferences that can be made on provenance representation. This document contains the specification of the Open Provenance Model (v1.1) resulting from a community-effort to achieve inter-operability in the Third Provenance Challenge.

Exploring complex and big data

“…To collect, represent, store, and share provenance data, the open provenance model (OPM) (Moreau et al, 2011) was proposed. It recommends to use five components, namely, (i) an abstract model, (ii) a domain-specific model, (iii) mechanisms for model extension, (iv) data acquisition and mapping to RDF, and (5) APIs for querying.…”

A Formal Framework for Provenance Security

“…Kepler [8] and Taverna [7] among many others); the Open Provenance Model [14] is a popular format for this kind of provenance but in this paper, we will focus on a simple form of OPM-like graphs. Our presentation draws primarily on the model introduced by Davidson et al [?]…”

“…As a result there is a variety of models and styles of provenance for workflows. Recently, a community effort to develop a common data model for provenance has converged on the Open Provenance Model (OPM) [14], but so far this effort has focused on the syntax or structure of provenance graphs and not on their semantics or their relationship to the behavior of the systems that generate them. Our previous paper [27] made one proposal for interpreting OPM-style provenance graphs in terms of structural causal models [35], and Davidson et al [25] adopt a similar model; however, both approaches stop well short of addressing the all of the features employed by workflow provenance systems.…”

“…A great deal of work has focused on design of efficient techniques for recording some additional so-called provenance information, often in the context of a specific system (see e.g. [7]- [11]); other work has emphasized defining formal models of provenance and exploring their properties [12], [13], or identifying and solving particular decision problems that arise for forms of data frequently used as provenance, such as directed acyclic graphs [14], [15]. However, the wide variety of such models and the applications that have inspired them begs several questions: 1) What is (and isn't) provenance?…”

“…This is part of the motivation for dependency provenance [24] and provenance traces [23], and is an implicit motivation for viewing provenance graphs as conveying causal information [14], [27]. We develop specific instances of our framework with these provenance queries in mind, focusing on the availability and confidentiality properties.…”