W3C home > Mailing lists > Public > public-xml-core-wg@w3.org > November 2007

Re: Proposed resolution of HRRI/IRI discussion

From: Martin Duerst <duerst@it.aoyama.ac.jp>
Date: Tue, 06 Nov 2007 15:42:53 +0900
Message-Id: <>
To: Richard Tobin <richard@inf.ed.ac.uk>, Konrad Lanz <Konrad.Lanz@iaik.tugraz.at>
Cc: "Grosso, Paul" <pgrosso@ptc.com>, Richard Ishida <ishida@w3.org>, public-i18n-core@w3.org, public-xml-core-wg@w3.org, public-iri@w3.org

At 07:58 07/11/06, Richard Tobin wrote:
>> > And require normative changes to all the specs, which is what we
>> > want to avoid.
>> Why would allowing what was allowed by the Grammar in RFC 2732 require
>> to change all the specs?
>Because they don't allow them now.  All the specs exclude square
>brackets from the list of characters %-encoded by the processor,
>either by explicitly saying so, or by not listing them.
>If LEIRIs said that square brackets in the fragment get %-escaped
>by the processor, and we changed the specs to refer to LEIRIs, that
>would be a normative change.

Hello Richard, Konrad,

Many thanks for discussing all these details. Please feel free to
send further contributions.

On looking through XML itself, XML Schema, and XLink, my understanding
of what these specs allow as syntax in the respective slots coincides
with that of Richard, for the arguments given. However, if the XML
Core WG thinks that additional changes are necessary in the iri-bis
Internet Draft, I'll try to incorporate them.

With kind regards,   Martin.

P.S.: Please note that on strict reading, the href attribute in XLink
does not allow '[' and ']' for IPv6, because it only cites RFC 2732
for explaining why '[' and ']' are excluded, not when defining the
correct target syntax after escaping. This has been fixed in XML V4
by referencing RFC 3986.

Regards,    Martin.

#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#  http://www.sw.it.aoyama.ac.jp       mailto:duerst@it.aoyama.ac.jp     
Received on Tuesday, 6 November 2007 06:46:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:40:35 UTC