W3C home > Mailing lists > Public > public-iri@w3.org > October 2007

Re: internationalization of URIs

From: Ted Hardie <hardie@qualcomm.com>
Date: Wed, 24 Oct 2007 10:55:43 -0700
Message-Id: <p06240602c3453209e29f@[]>
To: Martin Duerst <duerst@it.aoyama.ac.jp>, Thomas Narten <narten@us.ibm.com>, discuss@apps.ietf.org
Cc: public-iri@w3.org

Hi Martin,
	Some comments below.  I've kept your distribution,
but I'd suggest we pick a place to continue discussion; suggest
public-iri for followups.

>- There is in principle nothing that would prevent the IETF from
>  using IRIs as protocol elements in a new protocol. In my opinion,
>  this would actually be the right thing. The conversion to URIs
>  as protocol elements is there first and foremost for existing
>  protocols that are based on URIs.

I agree that there is nothing to prevent the IETF from using IRIs
as protocol elements.  For the large majority of IETF protocols,
though, this isn't the optimal choice.  For most protocol slots,
the aim isn't to present the element to a human, but to enable
protocol processing to proceed in a deterministic way.    This
means that most protocol slots don't benefit in any meaningful
way from the greatly increased  set of unreserved characters.
IRIs do introduce increased complexity in protocol processing
(I believe your "Ladder of comparison" section describes some
of the most critical ways), and when this is not needed because
of human interaction it is simpler to avoid it. 

Any protocol that wishes to use IRIs is also strongly advised
to take into account what restrictions of the UCS it wishes to
make; as you point out in IRI-bis, section 6.1, a scheme-specific
definition or processor may need to make a number of rules that exclude
look-alikes in both characters and delims.  Those will add increased
complexity as well, especially if they vary from scheme to scheme.

>>When I read Martin's comments about drop-downs, elided scheme
>>names, and similar tricks, my protocol-geek hat tightened on my head
> >and gave me a pretty severe headache.  Taking it off for a moment,
> >though, showed me things are still okay.  As presentation elements,
>>things like drop-downs, inference of scheme by an initial www, and
>>similar tricks are more reasonable.
>Detail: the scheme isn't inferenced by an initial www. A very quick
>test on one single browser showed that a leading 'ftp' label inferences
>ftp://, but there is no need for an initial www to infer http://.

I actually didn't mean in browser behavior; sorry for being unclear.  I mean
that humans see "www" now and assume that they should plug it into a web browser;
"infer a scheme" was probably not the ideal way of describing that, since most
users don't think of the scheme in that process (though many browsers do
prepend the scheme in final display).

> >We also have agreed, as a community, to take on work on some work
>>that does not rely on a presentation layer separation from the protocol.
>>We have agreed to work on email addresses, as one example,
>>and that working group decided not to use a pure presentation layer
>Yes. I expect this way of designing protocols to become more frequent.
>For new protocols, for me, it would be a non-brainer. For existing
>protocols, the decision is of course much more difficult, and
>will once go one way, and once the other way.

For new protocol slots that will be exposed to humans, I agree that
this will be more frequent.  The tricky bit is always figuring out
what will be.

Thanks for your comments,
Received on Wednesday, 24 October 2007 18:05:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:39:39 UTC