The PROV working group received a question from Mike:
My understanding is that an entity referenced in a PROV bundle (e.g. via wasGeneratedBy) must be in the bundle…but I do not wish to duplicate entity definitions through out my bundles. My entities are long lived and will exist in multiple bundles.
So lets say I have a resource for alarms which contains a list of all alarms my company monitors. If I turn off the alarm at
alarm/1, my understanding is that in PROV a new entity is created for the new state of
alarm/1. But in my actual data store, I don’t create a new record, I just toggle a flag.
So there is a disconnect between how my PROV looks and how my data looks. This is by design is my understanding. So I would have a new entity in my prov for the
alarm/1 in the new state which is a specialization of
Ultimately, I want to display all of the provenance for
alarm/1 so I can see its history from creation to invalidation. Am I going about this the wrong way?
Here is my reply (slightly revised for this post). My examples use the Turtle syntax and PROV-O, but are also applicable to other serializations of PROV, like PROV-XML or PROV-JSON.
Continue reading “Resources that change state”
This blog post shows how RESTful web services can provide, and link to, provenance data for their exposed resources by using the PROV-AQ mechanism of HTTP Link headers. This is demonstrated by showing how to update a hello world REST service implemented with Java and JAX-RS 2.0 to provide these links.
The PROV-AQ HTTP mechanism is easiest explained by an example:
This request for
http://example.com/resource.html returns some HTML, but also provides a
Link: header that says that the provenance is located at
http://example.com/resource-provenance. Within this file, the resource is known as the anchor
http://example.com/resource rather than
http://example.com/resource.html. The anchor URI can be omitted if it is the same as the one requested.
Link headers are specified by RFC 5988, which also defines standard relations like
rel="previous". PROV-AQ uses
rel="http://www.w3.org/ns/prov#has_provenance" to say that the linked resource has the provenance data for the requested resource. PROV-AQ also defines other relations for provenance query services and provenance pingback, which is not covered by this blog post.
Continue reading “Locating provenance for a RESTful web service”
Provenance, a form of structured metadata designed to record the origin or source of information, can be instrumental in deciding whether information is to be trusted, how it can be integrated with other diverse information sources, and how to establish attribution of information to authors throughout its history.
The PROV set of specifications, produced by the World Wide Web Consortium (W3C), is designed to promote the publication of provenance information on the Web, and offers a basis for interoperability across diverse provenance management systems. The PROV provenance model is deliberately generic and domain-agnostic, but extension mechanisms are available and can be exploited for modelling specific domains.
Paolo Missier, Khalid Belhajjame and James Cheny gave a tutorial at the EDBT conference on 2013-03-20 in Genova, Italy. The tutorial provided an account of these specifications. Starting from intuitive and informal examples that present idiomatic provenance patterns, it progressively introduces the relational model of provenance along with the constraints model for validation of provenance documents, and concludes with example applications that show the extension points in use.
The tutorial is in three parts, each about 30 minutes long, and consists of the following material:
There is also a short paper describing the motivation, structure and content of the tutorial, published in the EDBT’13 proceedings: The W3C PROV family of specifications for modelling provenance metadata, Paolo Missier, Khalid Belhajjame, and James Cheney
Also available on Slideshare and as pptx.
The above presentation was originally given at the Metagenomics, metagenetics and Pylogenetic workflows for Ocean Sampling Day Workshop at Max Planck Institute for Marine Microbiology on 2013-03-21 by Stian Soiland-Reyes. Reuse allowed under the Creative Commons Attribution license