- From: Andrea Splendiani <andrea@pasteur.fr>
- Date: Tue, 30 May 2006 21:04:45 +0200
- To: "Danny Ayers" <danny.ayers@gmail.com>
- Cc: "Max Völkel" <voelkel@fzi.de>, semantic-web <semantic-web@w3.org>
Well, that <http://example.org/uno> rdf:type owl:Class . But that's already on the graph. One way would be to use some sort of filter to normalize URIs before the graph is contructed... but this would be a little bit impractical. Our may simply consider that: x erdf:sameResource y , z whatever x -> z whatever y (and so on...) This would leave to other lyers the task to perform this, and optimize it based on their reasoning system Andrea Il giorno 30/mag/06, alle ore 20:53, Danny Ayers ha scritto: > On 5/30/06, Andrea Splendiani <andrea@pasteur.fr> wrote: > >> > I suppose owl:sameAs causes problems in its lack of uniformity >> (from >> > the URI point of view), in that saying two classes are the same has >> > very different implications than saying two individuals are the >> same. >> owl:sameAs as owl:sameProperty as owl:equivalentTo presuppone we are >> already talking about indiviuals, properties, classes that is, what a >> URI represent. And from so we start semantics... >> >> I think we would need something more "syntactical". > > Yep, but if you say at the syntax level: > > <http://example.org/one> erdf:sameResource <http://example.org/uno> . > > what happens when you later get > > <http://example.org/one> rdf:type owl:Class . > > in the graph? (Or any statements about <http://example.org/uno>) > > Cheers, > Danny. > > > > -- > > http://dannyayers.com >
Received on Tuesday, 30 May 2006 19:04:32 UTC