W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2004

Re: Some thoughts on XCAP's resource architecture

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 26 Nov 2004 10:11:39 +0100
Message-ID: <41A6F34B.4090401@gmx.de>
To: Jamie Lokier <jamie@shareable.org>
CC: Lisa Dusseault <lisa@osafoundation.org>, HTTP working group <ietf-http-wg@w3.org>, "'simple@ietf.org'" <simple@ietf.org>

Jamie Lokier wrote:
> ...
>>...by any XML compliant recipient. Anyway, validaty of relative (URI) 
>>references is a problem, but a bigger one. Consider
>><x xml:base="foo"><y/></x>
>>If you just address y, you'll loose the base URI information. So to make 
>>this work, an XCAP server would need to know about base URIs and 
>>xml:base anyway.
> xml:base at the top-most tag is essentially document metadata.  (I
> don't know about xml:base - is it allowed to appear anywhere?)


> Other things such as the charset in the <?xml?> declaration also need
> to be passed.  Any XCAP server will have a mechanism for extracting

Not necessarily.  A server could serve all fragments encoded in UTF-8 
and would never have to send an XML declaration.  Strictly speaking, it 
wouldn't need to send it as well if it's specified in the Content-Type 
response header.

> and passing document metadata along with the response, and xml:base or
> HTML's <base/> are just another part of that.
> My main point is that when an XML document contains relative URIs,
> those are relative to the _document as a whole_.

That's not true. The relative references need to get resolved to 
whatever the *current* base URI is. The base URI may change due to 
entity inclusion and xml:base processing.

> It's a conceptual thing.
> The concept with XCAP is to address portions of an XML document.  The
> XML rules and general practice mean that relative URIs appearing in
> those portions are still _supposed_ to be relative to the whole document.

No, that's incorrect.

> Therefore _conceptually_, the XCAP selectors should not change the
> base path for relative URI resolution.

Yes, but as demonstrated, that's fixable.

> As it is now, an XCAP server would have to parse and modify the entire
> selected portion to transform every relative URI, not just the single
> base URI.

No, that's incorrect.

> (Alternatively it could add its own xml:base to the served response,
> but that might not be so reliably understood by recipients.)
> This is because of the mismatch between the two concepts.

That's what I already proposed (I think). Just clarify it in the spec, 
and there should be a problem with it.

Best regards, Julian

<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Friday, 26 November 2004 09:12:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:38 UTC