On Tue, 6 Feb 2007 14:04:20 -0500, Jonathan Rees wrote:
> This leads me to think that the main relation we are looking for is
> one between an information resource (which may have multiple URI's)
> and a *string* that is a URL that will help us to get its
> representation.
Exactly. It would be important if this single property could be standardized.
By the way, it might be practical to make the range of this property a string, and not a resource. For example, Protege requires the user to enter URIs of resources as a QName, divided in a namespace and an ID, with restrictions on the allowed characters of the ID. I was not able to enter the URL http://eutils.ncbi.nlm.nih.gov/entrez/eutils/efetch.fcgi?db=pubmed&retmode=xml&rettype=abstract&id=11208903 as the URI of a resource because it cannot be divided into namespace and ID in this manner.
Representing the URL as a simple string would also lessen the likelihood of mistakes (mixing up URL and URI of an information resource), or the inference of sameness where such a behaviour is not intended.
Of course, representing resolvable URLs as literals might be disliked by many, because it is quite different from the original idea of RDF. However, to me it seems more practical than current approaches and might be worth considering.
-- Matthias Samwald
|