Mari Carmen Suárez-Figueroa

The NeOn Methodology for Ontology Engineering

In contrast to other approaches that provide methodological guidance for ontology engineering, the NeOn Methodology does not prescribe a rigid workflow, but instead it suggests a variety of pathways for developing ontologies. The nine scenarios proposed in the methodology cover commonly occurring situations, for example, when available ontologies need to be re-engineered, aligned, modularized, localized to support different languages and cultures, and integrated with ontology design patterns and non-ontological resources, such as folksonomies or thesauri. In addition, the NeOn Methodology framework provides (a) a glossary of processes and activities involved in the development of ontologies, (b) two ontology life cycle models, and (c) a set of methodological guidelines for different processes and activities, which are described (a) functionally, in terms of goals, inputs, outputs, and relevant constraints; (b) procedurally, by means of workflow specifications; and (c) empirically, through a set of illustrative examples.

Validating ontologies with OOPS

Ontology quality can be affected by the difficulties involved in ontology modelling which may imply the appearance of anomalies in ontologies. This situation leads to the need of validating ontologies, that is, assessing their quality and correctness. Ontology validation is a key activity in different ontology engineering scenarios such as development and selection. This paper contributes to the ontology validation activity by proposing a web-based tool, called OOPS!, independent of any ontology development environment, for detecting anomalies in ontologies. This tool will help developers to improve ontology quality by automatically detecting potential errors.

Ontology Engineering in a Networked World

The Semantic Web is characterized by the existence of a very large number of distributed semantic resources, which together define a network of ontologies. These ontologies in turn are interlinked through a variety of different meta-relationships such as versioning, inclusion, and many more. This scenario is radically different from the relatively narrow contexts in which ontologies have been traditionally developed and applied, and thus calls for new methods and tools to effectively support the development of novel network-oriented semantic applications. This book by Surez-Figueroa et al. provides the necessary methodological and technological support for the development and use of ontology networks, which ontology developers need in this distributed environment. After an introduction, in its second part the authors describe the NeOn Methodology framework. The books third part details the key activities relevant to the ontology engineering life cycle. For each activity, a general introduction, methodological guidelines, and practical examples are provided. The fourth part then presents a detailed overview of the NeOn Toolkit and its plug-ins. Lastly, case studies from the pharmaceutical and the fishery domain round out the work. The book primarily addresses two main audiences: students (and their lecturers) who need a textbook for advanced undergraduate or graduate courses on ontology engineering, and practitioners who need to develop ontologies in particular or Semantic Web-based applications in general. Its educational value is maximized by its structured approach to explaining guidelines and combining them with case studies and numerous examples. The description of the open source NeOn Toolkit provides an additional asset, as it allows readers to easily evaluate and apply the ideas presented.

Scenarios for building ontology networks within the NeOn methodology

In this poster, we present a set of nine scenarios, identified in the NeOn Methodology, for building ontology networks.

Natural Language-Based Approach for Helping in the Reuse of Ontology Design Patterns

Experiments in the reuse of Ontology Design Patterns (ODPs) have revealed that users with different levels of expertise in ontology modelling face difficulties when reusing ODPs. With the aim of tackling this problem we propose a method and a tool for supporting a semi-automatic reuse of ODPs that takes as input formulations in natural language (NL) of the domain aspect to be modelled, and obtains as output a set of ODPs for solving the initial ontological needs. The correspondence between ODPs and NL formulations is done through Lexico-Syntactic Patterns, linguistic constructs that convey the semantic relations present in ODPs, and which constitute the main contribution of this paper. The main benefit of the proposed approach is the use of non-restricted NL formulations in various languages for obtaining ODPs. The use of full NL poses challenges in the disambiguation of linguistic expressions that we expect to solve with user interaction, among other strategies.

How to Write and Use the Ontology Requirements Specification Document

The goal of the ontology requirements specification activity is to state why the ontology is being built, what its intended uses are, who the end-users are, and which requirements the ontology should fulfill. The novelty of this paper lies in the systematization of the ontology requirements specification activity since the paper proposes detailed methodological guidelines for specifying ontology requirements efficiently. These guidelines will help ontology engineers to capture ontology requirements and produce the ontology requirements specification document (ORSD). The ORSD will play a key role during the ontology development process because it facilitates, among other activities, (1) the search and reuse of existing knowledge-aware resources with the aim of re-engineering them into ontologies, (2) the search and reuse of existing ontological resources (ontologies, ontology modules, ontology statements as well as ontology design patterns), and (3) the verification of the ontology along the ontology development. In parallel to the guidelines, we present the ORSD that resulted from the ontology requirements specification activity within the SEEMP project, and how this document facilitated not only the reuse of existing knowledge-aware resources but also the verification of the SEEMP ontologies. Moreover, we present some use cases in which the methodological guidelines proposed here were applied.

Common pitfalls in ontology development

The so-called Ontology Design Patterns (ODPs), which have been defined as solutions to ontological design problems, are of great help to developers when modelling ontologies since these patterns provide a development guide and improve the quality of the resulting ontologies. However, it has been demonstrated that, in many cases, developers encounter difficulties when they have to reuse the correct design patterns and include errors in the modelling. Thus, to avoid pitfalls in ontology modelling, this paper proposes classifying errors into two types: (1) errors related to existing ODPs, called anti-patterns, and (2) errors not related to existing ODPs, called pitfalls. This classification is the result of analysing a set of ontologies. This paper is focused on the pitfalls identified during the analysis. In addition the paper presents a classification of the pitfalls found and a set of pitfall examples.

The landscape of multimedia ontologies in the last decade

Many efforts have been made in the area of multimedia to bridge the so-called “semantic-gap” with the implementation of ontologies from 2001 to the present. In this paper, we provide a comparative study of the most well-known ontologies related to multimedia aspects. This comparative study has been done based on a framework proposed in this paper and called FRAMECOMMON. This framework takes into account process-oriented dimension, such as the methodological one, and outcome-oriented dimensions, like multimedia aspects, understandability, and evaluation criteria. Finally, we derive some conclusions concerning this one decade state-of-art in multimedia ontologies.

A network of ontology networks for building e-employment advanced systems ☆

This paper presents the development of a network of ontology networks that enables data mediation between the Employment Services (ESs) participating in a semantic interoperability platform for the exchange of Curricula Vitae (CVs) and job offers in different languages. Such network is formed by (1) a set of local ontology networks that are language dependent, in which each network represents the local and particular view that each ES has of the employment market; and (2) a reference ontology network developed in English that represents a standardized and agreed upon terminology of the European employment market. In this network each local ontology network is aligned with the reference ontology network so that search queries, CVs, and job offers can be mediated through these alignments from any ES. The development of the ontologies has followed the methodological guidelines issued by the NeOn Methodology and is focused mainly on scenarios that involve reusing and re-engineering knowledge resources already agreed upon by employment experts and standardization bodies. This paper explains how these methodological guidelines have been applied for building e-employment ontologies. In addition, it shows that the approach to building ontologies by reusing and re-engineering agreed upon non-ontological resources speeds the ontology development, reduces development costs, and retrieves knowledge already agreed upon by a community of people in a more formal representation.

A Pattern Based Approach for Re-engineering Non-Ontological Resources into Ontologies

With the goal of speeding up the ontology development process, ontology engineers are starting to reuse as much as possible available ontologies and non-ontological resources such as classification schemes, thesauri, lexicons and folksonomies, that already have some degree of consensus. The reuse of such non-ontological resources necessarily involves their re-engineering into ontologies. Non-ontological resources are highly heterogeneous in their data model and contents: they encode different types of knowledge, and they can be modeled and implemented in different ways. In this paper we present (1) a typology for non-ontological resources, (2) a pattern based approach for re-engineering non-ontological resources into ontologies, and (3) a use case of the proposed approach.