RE: xml:base (was Re: IRI meets RDF meets HTTP redirect)

Hi,

An onlooker's observation.

This situation is an interoperability mess.  The chance that
a bunch of independent implmentations and validation tools
converged on the same interpretations of allowed/disallowed
is zero - this discussion thread hasn't visibly converged.

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music / High North Inc
PO Box 221  Grand Marais, MI  49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com

-----Original Message-----
From: www-international-request@w3.org
[mailto:www-international-request@w3.org]On Behalf Of Chris Lilley
Sent: Friday, April 20, 2007 12:30 PM
To: John Cowan
Cc: Jeremy Carroll; Sandro Hawke; semantic-web@w3.org;
www-international@w3.org
Subject: Re: xml:base (was Re: IRI meets RDF meets HTTP redirect)



On Thursday, April 19, 2007, 5:14:49 PM, John wrote:


JC> Note:  I'm a member of the XML Core WG, which owns the XML Base spec,
JC> and I may speak in accordance with my best recollection of things
JC> discussed there when making statements about intentions.  However,
JC> I don't speak for the WG.

And I am equally drawing on recollections of a working lunch at the Tech Plenary, with Paul Grosso and others, where the notion that the infoset property for the base URI 'represented a URI' rather than 'contained a URI' and thus, was compatible with IRIs, was discussed.

I agree that the term IRI is a more recent coinage than many of the specifications which allowed a wider range of non-ASCII characters to 'represent URIs' after escaping.

I disagree with your assertion that simply using XML Base (without dereferencing) forces a hexification. 


-- 
 Chris Lilley                    mailto:chris@w3.org
 Interaction Domain Leader
 Co-Chair, W3C SVG Working Group
 W3C Graphics Activity Lead
 Co-Chair, W3C Hypertext CG



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 269.5.5/769 - Release Date: 4/19/2007 5:56 PM

Received on Friday, 20 April 2007 18:20:17 UTC