• Aucun résultat trouvé

Ontology of Ontology Patterns as Linked Data Integration Tool

N/A
N/A
Protected

Academic year: 2022

Partager "Ontology of Ontology Patterns as Linked Data Integration Tool"

Copied!
2
0
0

Texte intégral

(1)

Ontology of Ontology Patterns as Linked Data Integration Tool

Miroslav Vacura and Vojtˇech Sv´atek

Faculty of Informatics and Statistics, University of Economics W. Churchill Sq.4, 130 67 Prague 3,

Czech Republic vacuram|svatek@vse.cz

Abstract. The paper present preview of ontology of ontology design patterns and transformation patterns being developed as support tool for emerging ontology design techniques and methodologies.

The Linked Data initiative was started by Tim Berners-Lee as an architec- tural vision for the Semantic Web. It explores the idea of Semantic Web as puting emphasis on making links so both people and machines can explore the interconnected web of data [1].

Person Person

knows

Person (n-ary relator) Person Relation-type

Person (n-ary relator) Person Relation-type

T1

Role

Event Person (n-ary relator) Person

Relation-type

T2

Role

Event

Event Time-interval

T3 FOAF

Fig. 1.FOAF Transformations

As an use-case we choose the FOAF project and it’s ‘knows’ relation. Since 2004 there was more than 1 million FOAF documents and 79% of them utilized the knowsproperty [2]. The typical needs of ontology engineer working on top of some Linked Data source comprises of transformation or aligning data to some more complex ontology either newly designed or already existing. This is also case of knowsrelation that in its FOAF implementation is very simple and doesn’t allow expressing more complex relations among individuals.

(2)

In the case of newly designed ontology use of ontology design patterns (ODPs) proved the most effective and the least time consuming way of doing it. In con- text of our use-case we can think of several iterations of ODPs that represent more or less complex or expanded view on ‘knows’ relation as is depicted on Fig. 1. These ODPs can be connected together using predefined transformation patterns (OPPL), It seems to us that having library of such predefined pattern transformations at hand could make such design tasks easier and much faster.

Our ongoing work proposes development of such library on top of existing por- talOntologyDesignPatterns.org, but 1) in form of ontology, 2) with explicitly stated relations, 3) that are formally defined and 4) with appropriate transforma- tions (OPPL) between related patterns, that enable automatic transformation from one pattern to another. We also focus on providing more fine-grained anal- ysis of relations (like specialization/generalization) between ontology ODPs.

Content ODP

SpecialisationOf

ODP

Ontology Patterns (OP)

OTP SourceODP TargetODP Logical ODP

Fig. 2.Design Patterns Transformations Ontology

Such a library would could be easily integrated with methodologies likeEx- treme Design (XD) [3] and respective development tools like NeON or Proteg´e.

This extended abstracts presents early preview of architecture of ontology being developed on Fig. 2. For additional information seehttp://keg.vse.cz.

Acknowledgments

This work has been partially partially supported by the IGS 4/2010 and by the CSF grant no. P202/10/1825 (PatOMat - Automation of Ontology Pattern Detection and Exploitation).

References

1. Tim Berners-Lee. LinkedData. http://www.w3.org/DesignIssues/LinkedData.

html, 2009.

2. Li Ding, Lina Zhou, Tim Finin, and Anupam Joshi. How the semantic web is being used: An analysis of foaf documents. InProc. of the 38th ICSS, 2005.

3. Valentina Presutti et al. eXtreme Design with Content Ontology Design Patterns.

In Eva Blomqvist et. al., editor, Proc. of the WOP 2009, coll. with ISWC-2009, volume 516. CEUR Workshop Proceedings, 2009.

Références

Documents relatifs

The aspect-weaver presented here is able to identify particular kind of aspects, using the OPPL selection language and transforming them into valid OWL 2 constructs, preserving

The same Java project will be given to all groups and it contains the main method (Main) with features not implemented. The groups goal is run the Main method. Therefore, the

If the repository contains multiple equiva- lent core hierarchies, then the reduction will contain multiple definably equivalent core ontologies, and hence there might exist

This paper describes the ini- tial step of the development of the optics ontology and discusses some problems of knowledge engineering and representation in this

[r]

For the purpose of formalizing the relations used in the GENIA corpus, we make use of sev- eral biomedical domain ontologies: the Information Artifact Ontology 1 (IAO), the

 We present the architecture of a data integration system, named Evolving Data Integration (EDI) system, that allows the evolution of the ontology used as global

As noted by the Linked Data tutorial, this implies there is another kind of resource, non-information resources, for things that are not possibly Web-accessible, like a URI