- From: Reto Bachmann-Gmür <rbg@talis.com>
- Date: Fri, 24 Aug 2007 11:38:40 +0200
- To: Alan Ruttenberg <alanruttenberg@gmail.com>
- CC: Garret Wilson <garret@globalmentor.com>, semantic-web@w3.org
Alan Ruttenberg wrote: > On Aug 22, 2007, at 3:25 AM, Reto Bachmann-Gmür wrote: > >> Another issue is the identity of the nodes, the unique-name >> constraint of java-classes can be expressed with an identity >> constraint definition on the datatypes but I can't think of any way >> to tell an RDF or OWL processor that a resource may not have two >> different URIs of the java-scheme. >> > > Couldn't do it at the scheme level, but could at the application level > by having the documentation indicate that there is a property > "uniquename" that is a function datatype property that must be set to > the the same string as the the uri as string. > > I proposed something like this as an extension to OWL in > > http://owl-workshop.man.ac.uk/acceptedLong/submission_26.pdf (search > for uniqueName) > Interesting that this works with a hasName property pointing to the string Value of the URI. I'm wondering why not just abolish named node completely and use an inverse functional hasName property and a functional and inverse functional hasUniqueName property. For the HPL Graph Versioning System (http://gvs.hpl.hp.com/) this is exactly what happens internally: instead of having different owl:sameAs resources there's just one resource with different names as properties. reto -- Reto Bachmann-Gmür Talis Information Limited Book your free place now at Talis Insight 2007 www.talis.com/insight Find out more about Talis at www.talis.com Shared InovationTM Any views or personal opinions expressed within this email may not be those of Talis Information Ltd.
Received on Friday, 24 August 2007 12:30:27 UTC