2006ePrints Soton (University of Southampton)Open access

Enabling Active Ontology Change Management within Semantic Web-based Applications. Mini-thesis: PhD upgrade report

Yaozhong Liang, Harith Alani, Nigel Shadbolt

Open full text 2 citations

Abstract

Enabling traceable ontology changes is becoming a critical issue for ontology-based applications. Updating an ontology that is in use may result in inconsistencies between the ontology and the knowledge base, dependent ontologies and applications/services. Current research concentrates on the creation of ontologies and how to manage ontology changes in terms of mapping ontology versions and keeping consistent with the instances. Very little work investigated on-the-fly keeping track of ontology changes while update (active ontology versioning) and using these information to control the impact on dependent applications/services, which is the aim of our research presented in this thesis. The approach we propose is to make use of ontology change logs as a check-point to analyse changed entities related to the requested services via end-user’s incoming queries (RDQL/SPARQL) and amend them as necessary to maintain the validation and continuousness of the dependent application. Firstly, We build up Log Ontology I as the concept structure to organize and construct the change information, develop our prototype system to demonstrate how the change information retrieved from Log Ontology I could be used to control the impacts brought by the ontology changes on the dependent applications and services. And then, by analysing the limitations and difficulties of our prototype system in maintaining the services related to the more complex ontology changes, we identify that the problem which fails the system facing the more complex ontology changes is the inabilities of Log Ontology I to represent complex change information in a semantic fashion. Therefore, we retract to put more focuses on Log Ontology I to enable the implementation of the mechanism to on-the-fly keep track of ontology change information, forming Log Ontology II, in order to reserve the semantics of ontology change from the beginning of ontology update process. Finally we discuss the future direction in terms of how the improved Log Ontology II enables the better service validation and continuousness maintenance of changing-ontology-based applications.

Open-access reader

About this research paper

What this paper is about

Enabling traceable ontology changes is becoming a critical issue for ontology-based applications. Updating an ontology that is in use may result in inconsistencies between the ontology and the knowledge base, dependent ontologies and applications/services. Current research concentrates on the creation of ontologies and how to manage ontology changes in terms of mapping ontology versions and keeping consistent with the instances. Very little work investigated on-the-fly keeping track of ontology changes while update (active ontology versioning) and using these information to control the impact on dependent applications/services, which is the aim of our research presented in this thesis. The approach we propose is to make use of ontology change logs as a check-point to analyse changed entities related to the requested services via end-user’s incoming queries (RDQL/SPARQL) and amend them as necessary to maintain the validation and continuousness of the dependent application. Firstly, We build up Log Ontology I as the concept structure to organize and construct the change information, develop our prototype system to demonstrate how the change information retrieved from Log Ontology I could be used to control the impacts brought by the ontology changes on the dependent applications and services. And then, by analysing the limitations and difficulties of our prototype system in maintaining the services related to the more complex ontology changes, we identify that the problem which fails the system facing the more complex ontology changes is the inabilities of Log Ontology I to represent complex change information in a semantic fashion. Therefore, we retract to put more focuses on Log Ontology I to enable the implementation of the mechanism to on-the-fly keep track of ontology change information, forming Log Ontology II, in order to reserve the semantics of ontology change from the beginning of ontology update process. Finally we discuss the future direction in terms of how the improved Log Ontology II enables the better service validation and continuousness maintenance of changing-ontology-based applications.

Why it matters

OpenAlex reports 2 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Enabling traceable ontology changes is becoming a critical issue for ontology-based applications. Updating an ontology that is in use may result in inconsistencies between the ontology and the knowledge base, dependent ontologies and applications/services. Current research concentrates on the creation of ontologies and how to manage ontology changes in terms of mapping ontology versions and keeping consistent with the instances. Very little work investigated on-the-fly keeping track of ontology changes while update (active ontology versioning) and using these information to control the impact on dependent applications/services, which is the aim of our research presented in this thesis. The approach we propose is to make use of ontology change logs as a check-point to analyse changed entities related to the requested services via end-user’s incoming queries (RDQL/SPARQL) and amend them as necessary to maintain the validation and continuousness of the dependent application. Firstly, We build up Log Ontology I as the concept structure to organize and construct the change information, develop our prototype system to demonstrate how the change information retrieved from Log Ontology I could be used to control the impacts brought by the ontology changes on the dependent applications and services. And then, by analysing the limitations and difficulties of our prototype system in maintaining the services related to the more complex ontology changes, we identify that the problem which fails the system facing the more complex ontology changes is the inabilities of Log Ontology I to represent complex change information in a semantic fashion. Therefore, we retract to put more focuses on Log Ontology I to enable the implementation of the mechanism to on-the-fly keep track of ontology change information, forming Log Ontology II, in order to reserve the semantics of ontology change from the beginning of ontology update process. Finally we discuss the future direction in terms of how the improved Log Ontology II enables the better service validation and continuousness maintenance of changing-ontology-based applications.

Key concepts: Ontology, Computer science, Ontology-based data integration, Suggested Upper Merged Ontology, Upper ontology, Process ontology, Ontology Inference Layer, OWL-S

Related papers

Back to paper searchBrowse research topicsOriginal source
Enabling Active Ontology Change Management within Semantic Web-based Applications. Mini-thesis: PhD upgrade report — Research Paper | ScholarLens