This is the companion to RFC 2396 (Generic URI Syntax)
for internationalized resource identifiers. Developed
in the W3C with major input from ISO language folks.
The revision of RFC 2396 is also complete and should
soon be IETF adopted (probably as Draft Standard,
PS - A number of W3C standards already use IRIs, so it's
worth learning about them, because they're becoming common
in the wild.
Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
email: imcdonald at sharplabs.com
From: www-international-request at w3.org
[mailto:www-international-request at w3.org]On Behalf Of François Yergeau
Sent: Thursday, December 09, 2004 10:47 PM
To: www-international at w3.org; w3c-i18n-ig at w3.org
Subject: Fwd: Protocol Action: 'Internationalized Resource Identifiers
(IRIs)' to Proposed Standard
It's for real now! IRIs are on the map.
Warm congrats to the co-authors, Martin Dürst and Michel Suignard, for
shperding this to completion.
>From: The IESG <iesg-secretary at ietf.org>
>To: IETF-Announce <ietf-announce at ietf.org>
>Date: Wed, 08 Dec 2004 09:55:16 -0500
>Cc: Internet Architecture Board <iab at iab.org>,
> RFC Editor <rfc-editor at rfc-editor.org>
>Subject: Protocol Action: 'Internationalized Resource Identifiers
> (IRIs)' to Proposed Standard
>>The IESG has approved the following document:
>>- 'Internationalized Resource Identifiers (IRIs) '
> <draft-duerst-iri-11.txt> as a Proposed Standard
>>This document has been reviewed in the IETF but is not the product of an
>IETF Working Group.
>>The IESG contact person is Ted Hardie.
>>This document describes Internationalized Resource Identifiers and their
>relationship to URIs. While the character limitations of URIs are not
>usually an issue for protocol processing, they may restrict the usefulness
>the identifiers presented to end users or systems expecting a
>different range of
>characters. Rather than extend URIs, this document introduces a
>type and a describes a relationship to URIs. Within an IETF context,
>will likely be used as presentation elements. There are cases, such as
>namespaces, in which an IRI may be used as a token, because
>character-by-character equivalence is the only property used for protocol
>processing. In no case should an implementor assume that an IRI may be
>substituted for a URI in an existing protocol grammar; either the
>grammar associated with the protocol must be updated to specify IRIs or the
>implementation must transform an IRI into a URI before use.
>>Working Group Summary
>>This work was initiated in the W3C, and it has been broadly accepted in
>context. It has also been discussed on the URI mailing list and a
>list (public-iri at w3.org) dedicated to the topic. Considerable care has
>taken to keep this specification well-synchronized with the URI
>There were issues raised during IETF Last Call, and a new document version
>resolving those issues was submitted.
>IETF-Announce mailing list
>IETF-Announce at ietf.org>https://www1.ietf.org/mailman/listinfo/ietf-announce