110
R. Pandey and M. Pande
5.1 PROV-DM
Provenance architecture is built over the provenance data model layer (PROV-DM).
PROV-DM is generic and allows applications/agents of the Semantic Web to transform provenance instances into the PROV-DM instances. A valid PROV instance
corresponds to a consistent history of objects and interactions to which logical
reasoning can be safely applied [22]. Semantic Web agents can deploy the provenance
for specific purposes.
PROV-DM groups the entire ontology in a group of core and extended structures.
Core structures are considered to map domain-specific vocabulary. An Entity a realworld, physical, or digital object that comes to existence by activities or any software
or human agents that belongs to the class of a thing. The extended structures consist
of the subtypes, plan, bundles, extended relations, revision, collections, etc. Six
elements of PROV-DM are as follows [7, 23]:
• Element 1: entities along with their associated activities, displaying the time stamp
of its evolution, utilization, and invalidation.
• Element 2: the generation of entities from other entities.
• Element 3: agent (human or software) that is responsible for performing various
activities.
• Element 4: bundles, a metadata that displays provenance of provenance
• Element 5: includes attributes that link entities of similar type.
• Element 6: collections that enable users to frame a logical structure of the
provenance instances.
These six elements address the needs through various layers on top of the PROVDM.
Motivating Features to Prefer PROV-DM Over Counterparts
Backward or across serialization of multi-format systems can enable interoperability
as is the case of XML to OWL serializations, where a XML syntax can be serialized
to an OWL syntax. Most semantic agents deploy provenance models apart from
PROV-DM, those applications prefer models such as OPM, Provenir [24], and PML
[25] for an interchange of semantic information. These semantic applications need
not be tailored to use PROV-DM, but the serialization feature of PROV-DM can be
considered for information interchange across such applications.
To ensure the interoperability of system on the level of provenance and its
analytics, we need to evaluate that the provenance data interchange across the systems
syntactically conforms to PROV-DM syntax. XML serialization of PROV-DM can be
used for provenance information interchange across systems and it allows validation
of these serializations using XML schema validators [26, 27].
The backward and across serialization is thus the primary reason for PROV-DM
to take preference over other models and be proposed by the W3C. The PROV-N,
PROV-XML are various serializations of the PROV-DM data model.
R. Pandey and M. Pande
5.1 PROV-DM
Provenance architecture is built over the provenance data model layer (PROV-DM).
PROV-DM is generic and allows applications/agents of the Semantic Web to transform provenance instances into the PROV-DM instances. A valid PROV instance
corresponds to a consistent history of objects and interactions to which logical
reasoning can be safely applied [22]. Semantic Web agents can deploy the provenance
for specific purposes.
PROV-DM groups the entire ontology in a group of core and extended structures.
Core structures are considered to map domain-specific vocabulary. An Entity a realworld, physical, or digital object that comes to existence by activities or any software
or human agents that belongs to the class of a thing. The extended structures consist
of the subtypes, plan, bundles, extended relations, revision, collections, etc. Six
elements of PROV-DM are as follows [7, 23]:
• Element 1: entities along with their associated activities, displaying the time stamp
of its evolution, utilization, and invalidation.
• Element 2: the generation of entities from other entities.
• Element 3: agent (human or software) that is responsible for performing various
activities.
• Element 4: bundles, a metadata that displays provenance of provenance
• Element 5: includes attributes that link entities of similar type.
• Element 6: collections that enable users to frame a logical structure of the
provenance instances.
These six elements address the needs through various layers on top of the PROVDM.
Motivating Features to Prefer PROV-DM Over Counterparts
Backward or across serialization of multi-format systems can enable interoperability
as is the case of XML to OWL serializations, where a XML syntax can be serialized
to an OWL syntax. Most semantic agents deploy provenance models apart from
PROV-DM, those applications prefer models such as OPM, Provenir [24], and PML
[25] for an interchange of semantic information. These semantic applications need
not be tailored to use PROV-DM, but the serialization feature of PROV-DM can be
considered for information interchange across such applications.
To ensure the interoperability of system on the level of provenance and its
analytics, we need to evaluate that the provenance data interchange across the systems
syntactically conforms to PROV-DM syntax. XML serialization of PROV-DM can be
used for provenance information interchange across systems and it allows validation
of these serializations using XML schema validators [26, 27].
The backward and across serialization is thus the primary reason for PROV-DM
to take preference over other models and be proposed by the W3C. The PROV-N,
PROV-XML are various serializations of the PROV-DM data model.