106
R. Pandey and M. Pande
3 Provenance: Types and Models
Provenance understood as a lineage refers to the records describing the Activity,
Entity, and Agent that helped or contributed to the creation, updating, usage, and
enhancement of data items present on the web or IoE. Trust depends upon provenance
to a great extent as the same help in answering the questions like:
• When, by whom and how was a data item created?
• Where and by whom the data item was updated?
Provenance describes those activities that contributed to its creation, and entities
involved in the creation [3].
Various organizations are using provenance for ascertaining the quality of information available on the web, however, its integration with ontologies is not done.
Provenance as a data trail of when, who, and where is being used by the American
Food and Drug Administration to keep the record of drug ingredients. The medical
history of patients is also being recorded in hospitals using provenance. The design
of aircraft is also undertaken using provenance in various organizations [4, 5].
PROV [3], a specification that relates all the recommendations of provenance and
is organized as a layered arrangement, Fig. 2 is a process-flow model. PROV helps
to represent and interchange provenance information using widely available formats
such as RDF and XML.The base class Activity denotes things that evolve, and act
upon with entities. Activities are ordered within a provenance trace. Thus, alignment
with OWL is natural [6].
Ongoing researches [8–11] prove that semantic web applications can successfully
use provenance in healthcare, banking, finance, and life sciences. Thus, the given
scenarios prove that provenance can be used in one way or the other in the semantic
systems. Though the mathematical models of provenance are present, yet the domainspecific implementation of provenance needs to be enhanced in scale across domains.
This chapter suggests one such domain-specific assertions for provenance on a
University Ontology using the PROV-DM data model.
Fig. 2 The provenance architecture stack [7]
R. Pandey and M. Pande
3 Provenance: Types and Models
Provenance understood as a lineage refers to the records describing the Activity,
Entity, and Agent that helped or contributed to the creation, updating, usage, and
enhancement of data items present on the web or IoE. Trust depends upon provenance
to a great extent as the same help in answering the questions like:
• When, by whom and how was a data item created?
• Where and by whom the data item was updated?
Provenance describes those activities that contributed to its creation, and entities
involved in the creation [3].
Various organizations are using provenance for ascertaining the quality of information available on the web, however, its integration with ontologies is not done.
Provenance as a data trail of when, who, and where is being used by the American
Food and Drug Administration to keep the record of drug ingredients. The medical
history of patients is also being recorded in hospitals using provenance. The design
of aircraft is also undertaken using provenance in various organizations [4, 5].
PROV [3], a specification that relates all the recommendations of provenance and
is organized as a layered arrangement, Fig. 2 is a process-flow model. PROV helps
to represent and interchange provenance information using widely available formats
such as RDF and XML.The base class Activity denotes things that evolve, and act
upon with entities. Activities are ordered within a provenance trace. Thus, alignment
with OWL is natural [6].
Ongoing researches [8–11] prove that semantic web applications can successfully
use provenance in healthcare, banking, finance, and life sciences. Thus, the given
scenarios prove that provenance can be used in one way or the other in the semantic
systems. Though the mathematical models of provenance are present, yet the domainspecific implementation of provenance needs to be enhanced in scale across domains.
This chapter suggests one such domain-specific assertions for provenance on a
University Ontology using the PROV-DM data model.
Fig. 2 The provenance architecture stack [7]