W3C home > Mailing lists > Public > www-international@w3.org > October to December 2002

IRIs and XLink/XPointer spec

From: Martin Duerst <duerst@w3.org>
Date: Fri, 06 Dec 2002 06:44:42 +0900
Message-Id: <4.2.0.58.J.20021119052349.05148e20@localhost>
To: w3c-xml-linking-wg@w3.org
Cc: www-international@w3.org, Michel Suignard <michelsu@microsoft.com>

Dear XLink/XPointer specialists,

As the authors of the IRI spec
(http://www.ietf.org/internet-drafts/draft-duerst-iri-02.txt)
for the I18N WG, we need your input.

As you may remember, XLink uses what's now called IRIs in the
xlink:href attribute. XPointer is also defined in a way that
makes it easy to interact with IRIs.

IRIs were specified to fit together well with XPointer.
In particular, XPointer was the main reason that IRIs currently
not only allow URI characters and non-ASCII characters, but also
some ASCII characters that are excluded in URIs, such as
<, >, {, }, |, \, ^, `, and in particular SPACE. This makes it
very easy to use XPointers directly in IRIs, without too much
escaping.

However, I have seen various comments recently that including
space and these other characters was going too far. These
comments have come both publicly, on www-international@w3.org,
where the IRI draft is discussed, and also privately.

See e.g.:
http://lists.w3.org/Archives/Public/www-tag/2002Dec/0058.html
http://lists.w3.org/Archives/Public/www-tag/2002Dec/0000.html

I would like to invite you to www-international@w3.org (a publicly
archived list, crossposted) to express your input on why
IRIs should include the above characters (<, >, {, }, |, \, ^, `,
and SPACE), or to tell us that you would be fine with a change
back to excluding these characters.


With kind regards,     Martin.
Received on Thursday, 5 December 2002 16:46:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:16:59 GMT