W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > November 2002

Re: docsync: RDF URI Reference

From: Dan Connolly <connolly@w3.org>
Date: 04 Nov 2002 13:37:21 -0600
To: Brian McBride <bwm@hplb.hpl.hp.com>
Cc: RDF Core <w3c-rdfcore-wg@w3.org>
Message-Id: <1036438641.11220.4956.camel@dirk>

On Mon, 2002-11-04 at 13:31, Brian McBride wrote:
> What do we call the things in an RDF graph that identify resources?
> These things are absolute URI's with optional fragment identifiers.  They 
> are not URI references, because URI references can contain a relative 
> URI.

quanitifer bug.

That doesn't mean absolute URI references are not URI references.

>  The concepts doc has been using, in part, the term RDF URI References 
> for these things.  Is that a term everyone feels comfortable with using?


> When talking about the RDF/XML syntax, whether in the syntax doc or the 
> primer, or anywhere else, we must be careful how we describe the value of 
> rdf:about and rdf:resource attributes.  The issue here is that we do not 
> process them the same way as the URI spec says.  We do not treat a fragment 
> identifier as a same document reference.  It is important that we are clear 
> that we are not claiming to conform to rfc 2396.


>  We process RDF URI 
> references and URI references with a relative URI the same way as rfc 2396 
> and XML base specifies.  We process fragment identifiers differently.

I don't think so.

> [Hmmm, not sure about the rdf:about="" case].
> The fragment identifier on its own is not a same document reference, as rfc 
> 2396 would have it, because if it were, it would be more difficult to 
> justify using an inscope xml base when translating it to an RDF URI 
> Reference.  So its a fragment identifier and we define our own algorithm 
> for translating those to an RDF URI Reference.
> Also need to be similarly careful describing rdf:ID and rdf:bagID.
> Does that make sense to folks?

I don't think so.

> Brian
Dan Connolly, W3C http://www.w3.org/People/Connolly/
Received on Monday, 4 November 2002 14:36:56 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:54:02 UTC