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.comReceived on Tuesday, 30 May 2006 18:53:45 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:22:42 GMT