Abstract

The W3C OWL 2 recommendation is an ontology language for the Semantic Web. It allows defining both schema (i.e., entities, axioms, and expressions) and instances (i.e., individuals) of ontologies. However, OWL 2 lacks explicit support for time-varying schema or for time-varying instances. Hence, knowledge engineers or maintainers of semantics-based Web resources have to use ad hoc techniques to specify OWL 2 time-varying ontologies. In this paper, for a disciplined and systematic approach to the temporal management of Semantic Web ontologies, we propose the adoption of a framework called temporal OWL 2 (\(\uptau \)OWL), which is inspired by the \(\uptau \)XSchema framework defined for XML data. In a way similar to what happens in \(\uptau \)XSchema, \(\uptau \)OWL allows creating a temporal OWL 2 ontology from a conventional (i.e., non-temporal) OWL 2 ontology and a set of logical and physical annotations. Logical annotations identify which elements of the ontology can vary over time; physical annotations specify how the time-varying aspects are represented in the OWL 2 document. Using annotations to integrate temporal aspects in the traditional Semantic Web, our framework (1) guarantees logical and physical data independence for temporal schemas and (2) provides a low-impact solution, since it requires neither modifications of existing Semantic Web ontologies, nor extensions to the OWL 2 recommendation and Semantic Web standards. Moreover, since the conventional schema and annotation documents could evolve over time to respond to new applications’ requirements, \(\uptau \)OWL supports temporal schema versioning by allowing changing these components and by keeping track of their evolution through the conventional schema versions and annotation document versions, respectively. Two complete sets of operations are proposed for changing the conventional schema and annotation documents; to complete the figure, a set of operations is also introduced for updating temporal schema which must be changed consequently each time one of the mentioned components evolves over time. To show the feasibility of our approach, a prototype tool, named \(\uptau \)OWL-Manager, is presented.

Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call