Guidelines for a Dynamic Ontology - Integrating Tools of Evolution and Versioning in Ontology

Ontologies are built on systems that conceptually evolve over time. In addition, techniques and languages for building ontologies evolve too. This has led to numerous studies in the field of ontology versioning and ontology evolution. This paper presents a new way to manage the lifecycle of an ontology incorporating both versioning tools and evolution process. This solution, called VersionGraph, is integrated in the source ontology since its creation in order to make it possible to evolve and to be versioned. Change management is strongly related to the model in which the ontology is represented. Therefore, we focus on the OWL language in order to take into account the impact of the changes on the logical consistency of the ontology like specified in OWL DL

Change Management: The Core Task of Ontology Versioning and Evolution

Change management as a key issue in ontology versioning and evolution is still not fully addressed, which to some extent forms a barrier against the smooth process of ontology evolution. The key issue in the support of evolving ontologies is to distinguish and recognize the changes during the process of ontology evolution. Most of the current popular work on ontology versioning do not keep a record of the changes in the ontology, thus preventing the user from tracking those changes back and forward, or to at least understand the rational behind those changes. We are proposing an approach to get the evidences of ontology changes, keep track of them, and manage them in an engineering fashion

DOOR: towards a formalization of ontology relations

In this paper, we describe our ongoing effort in describing and formalizing semantic relations that link ontolo- gies with each others on the Semantic Web in order to create an ontology, DOOR, to represent, manipulate and reason upon these relations. DOOR is a Descriptive Ontology of Ontology Relations which intends to define relations such as inclusion, versioning, similarity and agreement using ontological primitives as well as rules. Here, we provide a detailed description of the methodology used to design the DOOR ontology, as well as an overview of its content. We also describe how DOOR is used in a complete framework (called KANNEL) for detecting and managing semantic relations between ontologies in large ontology repositories. Applied in the context of a large collection of automatically crawled ontologies, DOOR and KANNEL provide a starting point for analyzing the underlying structure of the network of ontologies that is the Semantic Web

Expliciting semantic relations between ontologies in large ontology repositories

and other research outputs Expliciting semantic relations between ontologies in large ontology repositorie

An Approach to Cope with Ontology Changes for Ontology-based Applications

Keeping track of ontology changes is becoming a critical issue for ontology-based applications because updating an ontology that is in use may result in inconsistencies between the ontology and the knowledge base, dependent ontologies and dependent applications/services. Current research concentrates on the creation of ontologies and how to manage ontology changes in terms of the attempts to ease the communications between ontology versions and keep consistent with the instances, and there is little work available on controlling the impact to dependent applications/services which is the aims of the system presented in this paper. The approach we propose in this paper is to manually capture and log ontology changes, use this log to analyse incoming RDQL queries and amend them as necessary. Revised queries can then be used to query the knowledge base of the applications/services. We present the infrastructure of our approach based on the problems and scenarios identified within ontology-based systems. We discuss the issues met during our design and implementation, and consider some problems whose solutions will be beneficial to the development of our approach

Ontology Change Management in Protégé

Ontology schemas tend to change and evolve over time to meet new requirements. This change may invalidate dependent applications if there is no dynamic adaptation to the changes made to underlying ontologies. Protégé, as a popular ontology development tool, should meet the challenges addressed by the evolving ontology. In this paper, we will briefly analyse the current ontology-change management in Protégé, and propose some extensions to facilitate change traceability by external application and services

Ontology Change Management in Protégé

Ontology schemas tend to change and evolve over time to meet new requirements. This change may invalidate dependent applications if there is no dynamic adaptation to the changes made to underlying ontologies. Protégé, as a popular ontology development tool, should meet the challenges addressed by the evolving ontology. In this paper, we will briefly analyse the current ontology-change management in Protégé, and propose some extensions to facilitate change traceability by external application and services

Git4Voc: Git-based Versioning for Collaborative Vocabulary Development

Collaborative vocabulary development in the context of data integration is the process of finding consensus between the experts of the different systems and domains. The complexity of this process is increased with the number of involved people, the variety of the systems to be integrated and the dynamics of their domain. In this paper we advocate that the realization of a powerful version control system is the heart of the problem. Driven by this idea and the success of Git in the context of software development, we investigate the applicability of Git for collaborative vocabulary development. Even though vocabulary development and software development have much more similarities than differences there are still important differences. These need to be considered within the development of a successful versioning and collaboration system for vocabulary development. Therefore, this paper starts by presenting the challenges we were faced with during the creation of vocabularies collaboratively and discusses its distinction to software development. Based on these insights we propose Git4Voc which comprises guidelines how Git can be adopted to vocabulary development. Finally, we demonstrate how Git hooks can be implemented to go beyond the plain functionality of Git by realizing vocabulary-specific features like syntactic validation and semantic diffs

An Editorial Workflow Approach For Collaborative Ontology Development

The widespread use of ontologies in the last years has raised new challenges for their development and maintenance. Ontology development has transformed from a process normally performed by one ontology engineer into a process performed collaboratively by a team of ontology engineers, who may be geographically distributed and play different roles. For example, editors may propose changes, while authoritative users approve or reject them following a well defined process. This process, however, has only been partially addressed by existing ontology development methods, methodologies, and tool support. Furthermore, in a distributed environment where ontology editors may be working on local copies of the same ontology, strategies should be in place to ensure that changes in one copy are reflected in all of them. In this paper, we propose a workflow-based model for the collaborative development of ontologies in distributed environments and describe the components required to support them. We illustrate our model with a test case in the fishery domain from the United Nations Food and Agriculture Organisation (FAO)