Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
email: imcdonald at sharplabs.com
From: uri-request at w3.org [mailto:uri-request at w3.org]On Behalf Of Martin
Sent: Tuesday, January 25, 2005 9:21 PM
To: uri at w3.org
Subject: Fwd: RFC 3987 on Internationalized Resource Identifiers (IRIs)
The IRI spec is a Proposed Standard! Thanks to all the people who
contributed over the long time this has been in the works!
>To: ietf-announce at ietf.org
>From: rfc-editor at rfc-editor.org
>Date: Tue, 25 Jan 2005 17:33:19 -0800
>Subject: RFC 3987 on Internationalized Resource Identifiers (IRIs)
e-request at ietf.org?subject=unsubscribe>
>List-Post: <mailto:ietf-announce at ietf.org>
>List-Help: <mailto:ietf-announce-request at ietf.org?subject=help>
e-request at ietf.org?subject=subscribe>
>A new Request for Comments is now available in online RFC libraries.
> RFC 3987
> Title: Internationalized Resource Identifiers (IRIs)
> Author(s): M. Duerst, M. Suignard
> Status: Standards Track
> Date: January 2005
> Mailbox: duerst at w3.org, michelsu at microsoft.com
> Pages: 46
> Characters: 111190
> Updates/Obsoletes/SeeAlso: None
> I-D Tag: draft-duerst-iri-11.txt
> URL: ftp://ftp.rfc-editor.org/in-notes/rfc3987.txt
>This document defines a new protocol element, the Internationalized
>Resource Identifier (IRI), as a complement to the Uniform Resource
>Identifier (URI). An IRI is a sequence of characters from the
>Universal Character Set (Unicode/ISO 10646). A mapping from IRIs to
>URIs is defined, which means that IRIs can be used instead of URIs,
>where appropriate, to identify resources.
>The approach of defining a new protocol element was chosen instead
>of extending or changing the definition of URIs. This was done in
>order to allow a clear distinction and to avoid incompatibilities with
>existing software. Guidelines are provided for the use and deployment
>of IRIs in various protocols, formats, and software components that
>currently deal with URIs.
>This is now a Proposed Standard Protocol.
>This document specifies an Internet standards track protocol for
>the Internet community, and requests discussion and suggestions
>for improvements. Please refer to the current edition of the
>"Internet Official Protocol Standards" (STD 1) for the
>standardization state and status of this protocol. Distribution
>of this memo is unlimited.
>This announcement is sent to the IETF list and the RFC-DIST list.
>Requests to be added to or deleted from the IETF distribution list
>should be sent to IETF-REQUEST at IETF.ORG. Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
>help: ways_to_get_rfcs. For example:
> To: rfc-info at RFC-EDITOR.ORG
> Subject: getting rfcs
> help: ways_to_get_rfcs
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>Submissions for Requests for Comments should be sent to
>RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>Below is the data which will enable a MIME compliant Mail Reader
>implementation to automatically retrieve the ASCII version
>of the RFCs.
>Content-ID: <050125173212.RFC at RFC-EDITOR.ORG>
>IETF-Announce mailing list
>IETF-Announce at ietf.org