RE: last call comments, usage of IRI rather than URI

Julian,

Please make it clear in a response to (at least) xml-names-editor@w3.org
(1) whether you would like to record an official objection to the XML Core WG's
resolution of your Last Call comment and (2) in what capacity (i.e., what W3C
working group, W3C member organization, other liaison or user organization or
individual opinion) you make such an objection so that we can properly reflect
this in our CR request.

thank you,

Paul Grosso, co-chair XML Core WG

At 20:32 2002 11 29 +0100, Julian Reschke wrote:

>> From: www-tag-request@w3.org [mailto:www-tag-request@w3.org]On Behalf Of
>> Richard Tobin
>> Sent: Friday, November 29, 2002 1:38 AM
>> To: julian.reschke@greenbytes.de
>> Cc: www-tag@w3.org; xml-names-editor@w3.org
>> Subject: RE: last call comments, usage of IRI rather than URI
>>
>>
>>
>> > It has been demonstrated that using IRI (refs) as namespace names breaks
>> > existing XML applications (such as XML Schema, schemaLocation
>> attribute) and
>> > APIs (JAXP). I'd like to understand why this isn't considered a problem.
>>
>> IRIs that contain spaces can't be used with the schemaLocation
>> attribute, but IRIs in general can, as far as I can see.  It seems to
>
>Well. IRIs in general cannot be used in the schemaLocation, only a specific
>subset can (yes, I know, this isn't a contradiction, but this statement is
>equally true :-).
>
>> me that IRIs with spaces have disadvantages in other contexts too (eg
>> in plain text), and that we should either not allow spaces in IRIs or
>> live with the problem, rather than not using IRIs at all.
>
>The former. IMHO, IRIs should concentrate on their mandate (which is I18N,
>right). Lots of problems would go away if they wouldn't allow *ASCII*
>characters that are forbidden in URIs.
>
>Julian
>
>--
><green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

Received on Friday, 29 November 2002 15:44:50 UTC