W3C home > Mailing lists > Public > public-iri@w3.org > June 2004

URI schemes and IRI deployment

From: Williams, Stuart <skw@hp.com>
Date: Tue, 29 Jun 2004 11:56:22 +0100
Message-ID: <E864E95CB35C1C46B72FEA0626A2E80803615EC1@0-mail-br1.hpl.hp.com>
To: Martin Duerst <duerst@w3.org>
Cc: public-iri@w3.org


I'd like to understand expectations wrt to IANA registered URI schemes
following adoption of the IRI spec as an RFC and during deplyment of IRIs.

Do they 'instantly' become IRI schemes too? 

Will they require maintenance to allow the use of the expanded character set
allowed by the generic IRI syntax?

The IRI spec gives a generic syntax that allows a broader range of
characters to be used identifiers, but each currently registered scheme is
written from a URI perspective with the potential to narrow rather than
broaden the range characters used in an identifier from those permissablein
the URI spec.

The IRI spec. has section on upgrade strategy (7.8) which speaks of
upgrading of applications to handle IRI, but it does not appear to say
anything about upgrading of URI scheme registrations.

The identifier http://www.w3.org/People/dürst may be admissable under the
generic IRI syntax, but is it a valid HTTP scheme IRI? And if so... what
specification makes it admissable as an HTTP scheme IRI?

Simply, my question is... what is the transition plan for scheme
registrations wrt to IRI deployment?

Apologies if you have answered this before... I have looked, but did not
find anything relevant.


Stuart Williams
Received on Tuesday, 29 June 2004 06:56:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:14:31 UTC