Open Provenance ModelIntroduction | ||||||||
| Changed: | ||||||||
| < < |
Thirteen teams responded to the second Provenance challenge. Discussions at the Monterey Workshop indicated that there was substantial agreement on a core representation of provenance. As a result, a small working group met, crafted and iterated a data model, which is available from opm v1.00. Following the first OPM Workshop, a revision of the model was produced opm v1.01. Comments on the revised model can be left on the wiki version of the OPM. | |||||||
| > > |
Thirteen teams responded to the second Provenance challenge. Discussions at the Monterey Workshop indicated that there was substantial agreement on a core representation of provenance. As a result, a small working group met, crafted and iterated a data model, which is available from opm v1.00. Following the first OPM Workshop, a revision of the model was produced opm v1.01. This revision was used as the basis for a ThirdProvenanceChallenge. After this challenge, a mechanism for updating OPM was agreed upon and is now ongoing (see below). | |||||||
The starting point of this work is the community agreement summarized by Simon Miles (see SecondWorkshopMinutes). We assume that provenance of objects (whether digital or not) is represented by an annotated causality graph, which is a directed acyclic graph, enriched with annotations capturing further information pertaining to execution. For the purpose of this work, a provenance graph is defined to be a record of a past execution.
Inter-Operability Vision | ||||||||
| Changed: | ||||||||
| < < |
Our aim is to define a data format and associated semantics by which provenance systems can interchange provenance information. Ultimately, this model may also be used to express provenance queries and to record provenance information. To achieve this ambitious goal, we would like to propose the following steps: | |||||||
| > > |
Our aim is to define a data format and associated semantics by which provenance systems can interchange provenance information. Ultimately, this model may also be used to express provenance queries and to record provenance information. | |||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
OPM Community Process for Updates | |||||||
| Added: | ||||||||
| > > |
OPM is updated through a light weight community process. You can find discussions about the next revision of OPM and extensions to it at the OPM Wiki. | |||||||
| Deleted: | ||||||||
| < < |
Tentative ScheduleThe following tentative schedule identifies key milestones that would need to be met in order to agree on a provenance data model, and to define a sensible inter-operability challenge to evaluate it (Provenance Challenge 3). It is proposed that we co-locate with IPAW'08 a one-day meeting that helps finalise some of these, face to face.
Review ProcessThe page OpenProvenanceModelReview is dedicated to the OPM review process. | |||||||
OPM BindingsThe page OpenProvenanceModelBindings provides a list of OPM bindings to various technologies (XML, RDF) and libraries for working with OPM. -- LucMoreau - 18 Dec 2007 | ||||||||
| Changed: | ||||||||
| < < |
- PaulGroth - 31 Jul 2008 | |||||||
| > > |
-- PaulGroth - 31 Jul 2008 -- PaulGroth - 30 Jul 2009 | |||||||
Open Provenance Model | ||||||||
| Line: 32 to 32 | ||||||||
|---|---|---|---|---|---|---|---|---|
| The page OpenProvenanceModelReview is dedicated to the OPM review process. | ||||||||
| Added: | ||||||||
| > > |
OPM BindingsThe page OpenProvenanceModelBindings provides a list of OPM bindings to various technologies (XML, RDF) and libraries for working with OPM. | |||||||
| -- LucMoreau - 18 Dec 2007 - PaulGroth - 31 Jul 2008 | ||||||||
| Added: | ||||||||
| > > |
| |||||||
Open Provenance Model | ||||||||
Open Provenance ModelIntroduction | ||||||||
| Changed: | ||||||||
| < < |
Thirteen teams responded to the second Provenance challenge. Discussions at the Monterey Workshop indicated that there was substantial agreement on a core representation of provenance. As a result, a small working group met, crafted and iterated a data model, which is available from opm v1.00. Following the first OPM Workshop, a revision of the model was produced opm v1.01. | |||||||
| > > |
Thirteen teams responded to the second Provenance challenge. Discussions at the Monterey Workshop indicated that there was substantial agreement on a core representation of provenance. As a result, a small working group met, crafted and iterated a data model, which is available from opm v1.00. Following the first OPM Workshop, a revision of the model was produced opm v1.01. Comments on the revised model can be left on the wiki version of the OPM. | |||||||
| The starting point of this work is the community agreement summarized by Simon Miles (see SecondWorkshopMinutes). We assume that provenance of objects (whether digital or not) is represented by an annotated causality graph, which is a directed acyclic graph, enriched with annotations capturing further information pertaining to execution. For the purpose of this work, a provenance graph is defined to be a record of a past execution. | ||||||||
| Line: 33 to 33 | ||||||||
|---|---|---|---|---|---|---|---|---|
| -- LucMoreau - 18 Dec 2007 | ||||||||
| Added: | ||||||||
| > > |
- PaulGroth - 31 Jul 2008 | |||||||
Open Provenance ModelIntroduction | ||||||||
| Changed: | ||||||||
| < < |
Thirteen teams responded to the second Provenance challenge. Discussions at the Monterey Workshop indicated that there was substantial agreement on a core representation of provenance. As a result, a small working group met, crafted and iterated a data model, which is available from here. | |||||||
| > > |
Thirteen teams responded to the second Provenance challenge. Discussions at the Monterey Workshop indicated that there was substantial agreement on a core representation of provenance. As a result, a small working group met, crafted and iterated a data model, which is available from opm v1.00. Following the first OPM Workshop, a revision of the model was produced opm v1.01. | |||||||
| The starting point of this work is the community agreement summarized by Simon Miles (see SecondWorkshopMinutes). We assume that provenance of objects (whether digital or not) is represented by an annotated causality graph, which is a directed acyclic graph, enriched with annotations capturing further information pertaining to execution. For the purpose of this work, a provenance graph is defined to be a record of a past execution. | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
| Added: | ||||||||
| > > |
Open Provenance ModelIntroductionThirteen teams responded to the second Provenance challenge. Discussions at the Monterey Workshop indicated that there was substantial agreement on a core representation of provenance. As a result, a small working group met, crafted and iterated a data model, which is available from here. The starting point of this work is the community agreement summarized by Simon Miles (see SecondWorkshopMinutes). We assume that provenance of objects (whether digital or not) is represented by an annotated causality graph, which is a directed acyclic graph, enriched with annotations capturing further information pertaining to execution. For the purpose of this work, a provenance graph is defined to be a record of a past execution.Inter-Operability VisionOur aim is to define a data format and associated semantics by which provenance systems can interchange provenance information. Ultimately, this model may also be used to express provenance queries and to record provenance information. To achieve this ambitious goal, we would like to propose the following steps:
Tentative ScheduleThe following tentative schedule identifies key milestones that would need to be met in order to agree on a provenance data model, and to define a sensible inter-operability challenge to evaluate it (Provenance Challenge 3). It is proposed that we co-locate with IPAW'08 a one-day meeting that helps finalise some of these, face to face.
Review ProcessThe page OpenProvenanceModelReview is dedicated to the OPM review process. -- LucMoreau - 18 Dec 2007 | |||||||