- From: M. Scott Marshall <marshall@science.uva.nl>
- Date: Mon, 16 Jul 2007 16:10:08 +0200
- To: Eric Jain <Eric.Jain@isb-sib.ch>
- CC: Khalid Belhajjame <Khalid.Belhajjame@cs.man.ac.uk>, 'Matthias Samwald' <samwald@gmx.at>, 'Alan Ruttenberg' <alanruttenberg@gmail.com>, wangxiao@musc.edu, 'Michel_Dumontier' <Michel_Dumontier@carleton.ca>, 'public-semweb-lifesci' <public-semweb-lifesci@w3.org>, 'Mark Wilkinson' <markw@illuminae.com>, 'Benjamin Good' <goodb@interchange.ubc.ca>, 'Natalia Villanueva Rosales' <naty.vr@gmail.com>
Eric Jain wrote: > Khalid Belhajjame wrote: >> I am not sure whether the following issue has already been discussed. >> By using the identifiers to also locate where the RDFs statements >> describing >> the resource in question are, don’t we somehow dictate where the >> document(s) >> containing the RDFs statements describing a given resource are to be >> located? > > Not dictating anything, just providing some useful default behavior. If > you prefer to resolve http://purl.uniprot.org/uniprot/P12345 to let's > say http://www.ebi.uniprot.org/entry/P12345, you can do so in your > application. From the recent threads, I get the impression that we are trying to do combine two functions into the URI: 1) the unambiguous *identification* of a given concept in our own RDF 2) retrieve associated data records from the same URI Although 2) seems like a nice convenience feature, we have the problem of ambiguity that Alan pointed out: It should be possible to distinguish statements about a particular data record associated with a concept from statements about the concept. See, for example, http://beta.uniprot.org/uniprot/?query=p53&sort=score . "Which data record for P53 did you mean?" -scott -- M. Scott Marshall http://staff.science.uva.nl/~marshall http://adaptivedisclosure.org
Received on Monday, 16 July 2007 14:09:34 UTC