W3C home > Mailing lists > Public > www-international@w3.org > October to December 2004

Fwd: Protocol Action: 'Internationalized Resource Identifiers (IRIs)' to Proposed Standard

From: François Yergeau <francois@yergeau.com>
Date: Thu, 09 Dec 2004 19:45:33 -0800
To: www-international@w3.org, w3c-i18n-ig@w3.org
Message-id: <41B91BDD.9030300@yergeau.com>

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@ietf.org>
>To: IETF-Announce <ietf-announce@ietf.org>
>Date: Wed, 08 Dec 2004 09:55:16 -0500
>Cc: Internet Architecture Board <iab@iab.org>,
>         RFC Editor <rfc-editor@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.
>Technical Summary
>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 of
>the identifiers presented to end users or systems expecting a 
>different range of
>characters.  Rather than extend URIs, this document introduces a 
>new identifier
>type and a describes a relationship to URIs.    Within an IETF context, IRIs
>will likely be  used as presentation elements.  There are cases, such as XML
>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 generative
>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 that
>context.  It has also been discussed on the URI mailing list and a 
>public, open
>list (public-iri@w3.org) dedicated to the topic.  Considerable care has been
>taken to keep this specification well-synchronized with the URI specification.
>There were issues raised during IETF Last Call, and a new document version
>resolving those issues was submitted.
>IETF-Announce mailing list

Received on Friday, 10 December 2004 03:46:37 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:24 UTC