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

Re: Proposed resolution of HRRI/IRI discussion

From: Henry S. Thompson <ht@inf.ed.ac.uk>
Date: Wed, 21 Nov 2007 16:19:02 +0000
To: Martin Duerst <duerst@it.aoyama.ac.jp>
Cc: public-i18n-core@w3.org, public-xml-core-wg@w3.org, public-iri@w3.org
Message-ID: <f5br6ijo9l5.fsf@hildegard.inf.ed.ac.uk>

Hash: SHA1

Martin Duerst writes:

> HST writes[, wrt section 6.2 of your draft]
>>    Intermediate software interfaces between IRI-capable components
>>    and URI-only components MUST map the IRIs per Section 3.1, when
>>    transferring from IRI-capable to URI-only components.  This
>>    mapping SHOULD be applied as late as possible.  It SHOULD NOT be
>>    applied between components that are known to be able to handle
>>    IRIs.

>>The Core WG likes that, and we wonder if there could be something 
>>like that for LEIRIs as well.  Would you consider adding an analogy of
>>that prose to section 7?
> I have to admit that I'm a bit reluctant here. On the one hand,
> it's never a good idea to mess around with data if you don't have to.
> On the other hand, some security-related software might e.g.
> just go in and change some characters (e.g. control characters)
> to percent-escapes, and I don't really feel like I don't want
> to discourage that. So I'm wondering whether a less strong
> wording would be more appropriate.

We assume you're referring to the "This mapping SHOULD be applied as
late as possible."  If that's so, we agree with your comment about
security, but isn't that why this is a SHOULD and not a MUST?  In any
case, less strong wording would be fine with us -- are you willing to
propose something?


- -- 
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
Version: GnuPG v1.2.6 (GNU/Linux)

Received on Wednesday, 21 November 2007 16:19:28 UTC

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