Outline
The idea that a single way of representing and collecting provenance could be adopted internally by all systems does not seem to be realistic today.
Instead, a pragmatic approach is to consider a core data model for provenance that allows domain and application specific representations of provenance to be translated into such a data model and exchanged between systems.
Heterogeneous systems can then export their provenance into such a core data model, and applications that need to make sense of provenance in heterogeneous systems can then import it, process it, and reason over it.
Thus, the vision is that different provenance-aware systems natively adopt their own model for representing their provenance, but a core provenance data model can be readily adopted as a provenance interchange model across such systems.
|
|
prov-primer | http://www.w3.org/TR/prov-primer/ |
prov-o | http://www.w3.org/TR/prov-o/ |
prov-dm | http://www.w3.org/TR/prov-dm/ |
prov-constraints | http://www.w3.org/TR/prov-constraints/ |
prov-n | http://www.w3.org/TR/prov-n/ |
prov-aq | http://www.w3.org/TR/prov-aq/ |
prov-sem | work in progress |
prov-xml | work in progress |
best practice | PROV-DC mapping. work in progress |
/
#