W3C home > Mailing lists > Public > public-lod@w3.org > June 2009

Re: http://ld2sd.deri.org/lod-ng-tutorial/

From: Martin Hepp (UniBW) <martin.hepp@ebusiness-unibw.org>
Date: Tue, 23 Jun 2009 09:33:48 +0200
Message-ID: <4A40855C.6020604@ebusiness-unibw.org>
To: Dan Brickley <danbri@danbri.org>
CC: hepp@ebusiness-unibw.org, Yves Raimond <yves.raimond@gmail.com>, Michael Hausenblas <michael.hausenblas@deri.org>, Richard Cyganiak <richard@cyganiak.de>, "Hepp, Martin" <mhepp@computer.org>, Hugh Glaser <hg@ecs.soton.ac.uk>, mark.birbeck@webbackplane.com, "Booth, David (HP Software - Boston)" <dbooth@hp.com>, "public-lod@w3.org" <public-lod@w3.org>
Hi Dan:
I think Alan already gave examples this morning. An ontology can contain 
statements about the relationship between conceptual elements - classes, 
properties, individuals - that (1) influence the result to queries but 
(2) are not likely retrieved when you just dereference an element from 
that ontology. The more complex an ontology is, the more difficult is it 
to properly modularize it.

But basically my main point is that the use of owl:imports is defined 
pretty well in

http://www.w3.org/TR/owl-ref/#imports-def

and there is no need to deviate from the spec just for the matter of gut 
feeling and annoyance about the past dominance of DL research in the 
field. And as the spec says - with a proper owl:imports statement, any 
application can decide if and what part of the imported ontologies are 
being included to the local model for the task at hand.

Martin


Dan Brickley wrote:
> On 22/6/09 23:16, Martin Hepp (UniBW) wrote:
>>
>>
>> Yves Raimond wrote:
>>>> Ontology modularization is
>>>> a pretty difficult task, and people use various heuristics for 
>>>> deciding what
>>>> to put in the subset being served for an element. There is no 
>>>> guarantee that
>>>> the fragment you get contains everything that you need.
>
>> There is no safe way of importing only parts of an ontology, unless you
>> know that its modularization is 100% reliable.
>> Serving fragments of likely relevant parts of an ontology for reducing
>> the network overhead is not the same as proper modularization of the
>> ontology.
>
> Can you give a concrete example of the danger described here? ie. the 
> pair of a complete ("safe") ontology file and a non-safe subset, and 
> an explanation of the problems caused.
>
> I can understand "there is no guarantee that the fragment you get 
> contains everything you need", and I also remind everyone that 
> dereferencing is a privilege not a right: sometimes the network won't 
> give you what you want, when you want it. But I've yet to hear of 
> anyone who has suffered due to term-oriented ontology fragment 
> downloads. I guess medical ontologies would be the natural place for 
> horror stories?
>
> cheers,
>
> Dan
>
>

-- 
--------------------------------------------------------------
martin hepp
e-business & web science research group
universitaet der bundeswehr muenchen

e-mail:  mhepp@computer.org
phone:   +49-(0)89-6004-4217
fax:     +49-(0)89-6004-4620
www:     http://www.unibw.de/ebusiness/ (group)
         http://www.heppnetz.de/ (personal)
skype:   mfhepp 
twitter: mfhepp

Check out the GoodRelations vocabulary for E-Commerce on the Web of Data!
========================================================================

Webcast:
http://www.heppnetz.de/projects/goodrelations/webcast/

Talk at the Semantic Technology Conference 2009: 
"Semantic Web-based E-Commerce: The GoodRelations Ontology"
http://tinyurl.com/semtech-hepp

Tool for registering your business:
http://www.ebusiness-unibw.org/tools/goodrelations-annotator/

Overview article on Semantic Universe:
http://tinyurl.com/goodrelations-universe

Project page and resources for developers:
http://purl.org/goodrelations/

Tutorial materials:
Tutorial at ESWC 2009: The Web of Data for E-Commerce in One Day: A Hands-on Introduction to the GoodRelations Ontology, RDFa, and Yahoo! SearchMonkey

http://www.ebusiness-unibw.org/wiki/GoodRelations_Tutorial_ESWC2009





Received on Tuesday, 23 June 2009 07:34:31 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:21 UTC