Goto

Collaborating Authors

 Ontologies


Applications of an Ontology Engineering Methodology

AAAI Conferences

This paper examines first ideas on the applicability of Linked Data, in particular a subset of the Linked Open Drug Data (LODD), to connect radiology, human anatomy, and drug information for improved medical image annotation and subsequent search. One outcome of our ontology engineering methodology is the alignment between radiology-related OWL ontologies (FMA and RadLex). These can be used to provide new connections in the medicine-related linked data cloud. A use case scenario is provided that demonstrates the benefits of the approach by enabling the radiologist to query and explore related data, e.g., medical images and drugs. The diagnosis is on a special type of cancer (lymphoma).


Linked Data Integration for Semantic Dialogue and Backend Access

AAAI Conferences

Over the last several years, the market for speech technology has seen significant developments (Pieraccini and Huerta We learned some lessons which we use as guidelines 2005) and powerful commercial off-the-shelf solutions for in the development of multimodal dialogue systems where speech recognition (ASR) or speech synthesis (TTS). Further users can combine speech and gestures when using multiple application scenarios, more diverse and dynamic information interaction devices. In earlier projects (Wahlster 2003; Reithinger sources, and more complex prototype systems need et al. 2005) we integrated different sub-components to be addressed in the context of QA. Dialogue-based QA allows to multimodal interaction systems. Other lessons served as a user to pose questions in natural speech, followed by guidelines in the development of semantic dialogue systems answers presented in a concise form (Sonntag et al. 2007).


What Does It Mean for a URI to Resolve?

AAAI Conferences

Amongst the best practices that constitute linked data, one of the foremost is to use only HTTP-URIs as identifiers for RDF resources. This is so that the URI will resolve in a Linked Data browser to give information about the named resource. At the same time, Linked Data takes a resource-centric, as opposed to page-centric, approach to resolution. We argue that this approach can, in certain cases, obviate the need for insisting on HTTP-URIs. As a use of our “expanded” notion of Linked Data, we present as an example Life Science Identifiers.


Measuring Semantic Distance on Linking Data and Using it for Resources Recommendations

AAAI Conferences

A frequent topic discussed in the Linked Data community, especially when trying to outreach its values, is "What can we do with all this data ?". In this paper, we demonstrate (1) how to measure semantic distance on Linked Data in order to identify relatedness between resources, and (2) how such measures can be used to provide a new kind of self-explanatory recommendations, bringing together Linked Data and Artificial Intelligence principles, and demonstrating how intelligent agents could emerge in the realm of Linked Data.


Vocabulary Hosting: A Modest Proposal

AAAI Conferences

Many of the benefits of structured data come about when users can re-use existing vocabularies rather than create new ones, but it is currently difficult for users to find, create, and host new vocabularies. Moreover, the value of any given vocabulary as a foundation for applications depends on the perceived certainty that the vocabulary — both its machine-readable schemas and human-readable specification documents — will remain reliably accessible over time and that its URIs will not be sold, re-purposed, or simply forgotten. This note proposes two approaches for solving these problems: one for multiple Vocabulary Hosting Services and a Vocabulary Preservation System to keep them linked together.


Linked Data Meets Computational Intelligence - Position paper

AAAI Conferences

The Web of Data (WoD) is growing at an amazing rate and it will no longer be feasible to deal with it in a global way, by centralising the data or reasoning processes making use of that data. We believe that Computational Intelligence techniques provides the adaptiveness, robustness and scalability that will be required to exploit the full value of ever growing amounts of dynamic Semantic Web data.


A Formal Model of Queries on Interlinked RDF Graphs

AAAI Conferences

In this paper, we propose a model of the web of data as a graph of interlinked graphs which goes beyond the standard single-graph RDF semantics, describe two different ways in which a query on this structure can be answered, and characterize semantically each of these ways in terms of restrictions on the relation between the domain of interpretation of each single component graph.


An Ontology of Socio-Cultural Time Expressions

AAAI Conferences

Time is a concept that highly depends on the socio-cultural context. Its perception by humans is primarily based on the cultures, nations and social environment they belong to. Hence, different socio-cultural contexts imply different understandings of time. This leads to communication problems when their members start interacting with each other. In a dynamic and multi-cultural environment like today’s Web, where both billions of people with different socio-cultural contexts and numerous context dependent software applications interact, similar communication and inter-operability problems are expected. Expressing socio-cultural temporal information in an unambiguous, explicit and machine processable way can, however, help reduce such communication conflicts. In this way, heterogeneous temporal Web application systems can share the same concept of time. In this paper we present an ontology of socio-cultural time expressions that attempts to formalize the notion of socio-cultural time. The resulting model can then be used in a Web based temporal applications such as automated appointment scheduling services or calendars to provide more context sensitive service to its users.


Ontological Semantics for Data Privacy Compliance: The NEURONA Project

AAAI Conferences

Some of the top legal ontologies developed so far include the Functional Ontology for Law [FOLaw] The increasing need for legal information and content (Valente 1995), the Frame-Based Ontology (van Kralingen management caused by the growing amount of 1995), the LRI-Core ontology (Breuker 2004), unstructured (or poorly structured) legal data managed by DOLCE CLO [Core Legal Ontology] (Gangemi et al. legal publishing companies, law firms and public 2003), or the Ontology of Fundamental Concepts (Rubino administrations, or the increasing amount of legal et al. 2006, Sartor 2006) the basis for the LKIF-Core information directly available on the World Wide Web, Ontology (Breuker et al. 2007). Nevertheless, most legal have created an urgent need to construct conceptual ontologies are domain specific ontologies, which represent structures for knowledge representation to share and particular legal domains towards search, indexing and manage intelligently all this information, whilst making reasoning in a specific domain of national or European law human-machine communication and understanding (e.g. the IPRONTO ontology by Delgado et al. 2003, the possible.


Embedded Rule-Based Reasoning for Digital Product Memories

AAAI Conferences

A Digital Product Memory provides a digital diary of the complete product life cycle that is embedded in the product itself using smart wireless sensor technology. The data is hereby gathered by recording relevant ambient parameters in digital form. In this paper, we present the architecture and cost-efficient implementation of an autonomous digital product memory that generates and interprets its diary using rule-based reasoning methods. As we assume an open, heterogeneous sensor infrastructure, we rely on standard syntax and semantics provided by the Web Ontology Language OWL. The digital product memory collects and provides data using the OWL fragment OWL2 RL which can be processed with standard rule engines. As rule engine we use CLIPS on embedded hardware and exemplify the application of the digital product memory e.g. for predictive maintenance.