Towards Unified Provenance Granularities

Abstract

As Open Data becomes commonplace, methods are needed to integrate disparate data from a variety of sources. Although Linked Data design has promise for integrating world wide data, integrators often struggle to provide appropriate transparency for their sources and transformations. Without this transparency, cautious consumers are unlikely to find enough information to allow them to trust third party content. While capturing provenance in RPI's Linking Open Government Data project, we were faced with the common problem that only a portion of provenance that is captured is effectively used. Using our water quality portal's use case as an example, we argue that one key to enabling provenance use is a better treatment of provenance granularity. To address this challenge, we have designed an approach that supports deriving abstracted provenance from granular provenance in an open environment. We describe the approach, show how it addresses the naturally occurring unmet provenance needs in a family of applications, and describe how the approach addresses similar problems in open provenance and open data environments.

Provenance-Aware Knowledge Representation: A Survey of Data Models and Contextualized Knowledge Graphs

“…Data inferred by software agents should be distinguished from data explicitly provided by data publishers, because they differ in terms of trustworthiness [107]. Without sufficient transparency for Linked Data sources and transformations, government agencies and scientists cannot 66 https://franz.com/agraph/support/documentation/6.1.6/tripleattributes.html 67 https://neo4j.com 68 https://github.com/plus-provenance/plus 69 https://virtuoso.openlinksw.com 70 http://d2rq.org/d2r-server trust third-party LOD datasets [82]. The data interlinking mechanism used by LOD datasets can be utilized for coarse provenance information in the form of data associations, but these do not cover data transformations [108].…”

“…Beyond Provenance Tool Suite's ProvValidator, there are other tools to check provenance data, such as prov-check 80 and prov-constraints. 81 One of the six web applications of the eagle-I software suite, 82 a resource discovery tool for translational science research, is an RDF repository that can be used to store resource and provenance metadata as RDF triples. The Linked Open Data output can be exported via SPARQL endpoints, flat RDF files, or published URI lists.…”

“…dardized in 2013 by the W3C[82], serving as the basis for the Provenance Interchange Ontology (PROV-O),…”

Next Generation Cancer Data Discovery, Access, and Integration Using Prizms and Nanopublications

“…All processing steps record a wealth of provenance described in best practice vocabularies such as Dublin Core, VoID, 7 and PROV-O, which enables transparency of any of Prizms’ data products. For example, any RDF triple or RDF file can be traced back to the original data file(s) and the original publisher(s) [8]. This is important to maintain the reputability of Prizms, which serves as a third party integrator of others’ data.…”

AcCORD: um modelo colaborativo assíncrono para a reconciliação de dados

“…O primeiro deles investiga "quais dados de procedência armazenar", e inclui a definição de quais tipos de dados de procedência devem ser armazenados e qual a granularidade desses dados [Lebo et al 2012]. Deve-se levar em consideração o custo para armazenar esses dados e os resultados obtidos posteriormente.…”