Ontology Management

8/14/2019 Ontology Management

1/12

Aug 14+15 OTK 2nd Review 1

OntologyManagementSurvey, Requirement and Direction

Vrije Universiteit Amsterdam


2/12


Outline

Ontology library systemq Evaluation models

q Summary and requirement

Ontology versioningq Requirement

q Proposal

Summary and conclusions


3/12


4/12


Management

Storageq Accessibility:

client/server-based architecture

web accessible

q Classification It is necessary to classify ontology in an OLS in

order to facilitate searching, managing andre-using ontology. Some of the ontology

classification mechanisms available are basedon distinguishable features of ontologies.


5/12


Management

Storageq Modular organization

serve to maximize cohesion within modules and minimizeinteraction between modules.

facilitate ontology re-use, ontology mapping and integration

ONIONS highlights the stratifieddesign of an ontology librarysystem.

Different naming policies assist OLS to achieve the modularorganization or stratified storage ofontologies.

The disjointed partitioning of classes can facilitate

modularity, assembling, integrating and consisting checkingof ontologies.

Identificationq Unique ontology URL, Identifier and name

Versioningq Unfortunately, only SHOE supports it.


6/12


Adaptation

Searching & Editingq feature a visualized browsing environment,

using hyperlinks or cross-references to closelyrelated information.

q support collaborative editingq offer advanced searching featuresq monitor user profiles based on access patterns

in order to personalize the view of ontologies

Reasoningq A simple reasoning function should be included

in order to facilitate ontology creation, ontologymapping and integration.


7/12


Standardization

Languageq Syntactically, language should be standardized or inter- or

intra- ontology language translation should be supported.q Semantically, OLS should feature the common vocabulary

(or faceted taxonomy). At any rate, it should eliminate theimplicitness and misunderstanding of terms in differentontologies.

q Preferably, OLS should also support compatibility with ormapping between multiple controlled vocabularies fromdifferent domains (The structures of these common vocabulariesor multiple controlled vocabularies must be faceted, or modulated.

These vocabularies can help in simple synonym matching, siblinganalysis, and disjoint partition checking).

Upper-level Ontologyq Standard upper-level ontology is important for better

organization of OLS(Ontolingua, IEEE SUO).


8/12


Others

Ontology scalabilityq increase the scale of ontologies.

Maintaining facilityq provide some maintenance features, such as consistency

checking, diagnostic testing, support for changes, andadaptation of ontologies for different applications.

Explicit documentationq extensively and explicitly documented

q include such information as how the ontology was

constructed, how to make extensions and what theontologys naming policy, organizational principles andfunctions are.

q pave the way for efficient ontology management and re-use.


9/12


Ontology versioning

Definition: the ability to handle changes inontologies by creating and managing differentvariants of it

Goal:exploit as much knowledge as possible

q

Identification: for every use of a concept or arelation, a versioning framework should providean unambigious reference to the intendeddefinition

q

Change tracking: a versioning frameworkshould make the relation of one version of aconcept or relation to other versions of thatconstruct explicit

q Transparent evolution versioningmethodology on the web should make clear

t


10/12


eas on onto ogyidentification

Putting it togetherq different causes of change give different

types of change

q several types of compatibilityq minimal ontological commitment for data

sources maximizes validness of data

across different versions


11/12


proposal Distinguish between three classes of resources:

q files, ontologies, lines of backward compatible ontologies Use URL for file identification, new URI scheme for

other two

Two level numberingq minor numbers for backward compatible changesq major numbers for incompatible changes

Concepts that only differ in minor number areequivalent

Backward compatible additions are added asinstance of class Addition class, e.g. Additions1.3

Data refers to the minimal necessary minor number


12/12


Summary

Well-structured Ontology Librarysystems (OLSs) are of the greatimportance to secure the efficient re-

use of ontologies, including ontologygeneration, integration, mapping,maintenance, and versioning(evolving).

Robustness for change is essential forthe Semantic Web

Ontology identification and referring is

one of the most important aspects of

Documents

Ontology Management