W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > July 2003

Re: Review of RDF primer Revised Editor's Draft 21 July 2003

From: Frank Manola <fmanola@mitre.org>
Date: Thu, 31 Jul 2003 11:22:40 -0400
Message-ID: <3F293440.4020903@mitre.org>
To: Dave Beckett <dave.beckett@bristol.ac.uk>
CC: w3c-rdfcore-wg@w3.org, Eric Miller <em@w3.org>


I understand that it's the pair (rdf:ID value, in-scope base URI) that 
must be unique.  The question is, within what scope must it be unique? 
That is, a uniqueness check involves checking all the values (the above 
pairs in this case) within some scope to see that there aren't 
duplicates.  What is that scope?


Dave Beckett wrote:

> On Thu, 31 Jul 2003 10:15:49 -0400
> Frank Manola <fmanola@mitre.org> wrote:
>>>How about:
>>>rdf:ID is useful to abbreviate URIrefs but also provides an additional
>>>useful check that the value of the rdf:ID attribute is unique against the
>>>current base URI (usually document URI).  This helps pick up repeating
>>>rdf:ID values such as when defining properties and classes in RDF schemas.
>>This is good (but we might want to say this in Section 3, where rdf:ID 
>>is first introduced, rather than here (?).  In addition, this raises an 
>>additional question:  it's fairly clear how this works if the id values 
>>are being checked within the scope of a particular document, but if you 
>>use rdf:ID in combination with a base URI defined with xml:base, how do 
>>you really do a uniqueness check, since there's no guarantee that all 
>>the rdf:ID values in question are in the same document?
> The rdf:ID values are checked against hte current in-scope base URI.
> That is either the innermost xml:base value or the document URI.
> i.e. the pair (rdf:ID value, in-scope base URI) must be unique.
> Dave

Frank Manola                   The MITRE Corporation
202 Burlington Road, MS A345   Bedford, MA 01730-1420
mailto:fmanola@mitre.org       voice: 781-271-8147   FAX: 781-271-875
Received on Thursday, 31 July 2003 10:59:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:24:24 UTC