FW: IRI and updated URI specs published as RFC 3987, RFC 3986 (STD 66)

 

-----Original Message-----
From: chairs-request@w3.org [mailto:chairs-request@w3.org] On Behalf Of
Martin Duerst
Sent: Tuesday, 25 January, 2005 20:25
To: chairs@w3.org
Subject: IRI and updated URI specs published as RFC 3987, RFC 3986 (STD
66)


Dear Chairs,

The RFC Editor has published and announced the updated URI spec
(http://www.ietf.org/rfc/rfc3986.txt) and the IRI spec
(http://www.ietf.org/rfc/rfc3987.txt). Below is the most relevant
information from the two announcements. Many thanks to all those
helping to make this possible.

As most W3C specs are using URIs, the resposible WGs and IGs have to
think about how to update their references from RFC 2396 to RFC 3986.

Also, as many W3C specs are describing or referencing to what in effect
are IRIs, the responsible WGs and IGs have to think about how to move
to directly referencing RFC 3987. In addition, specs that didn't
allow IRIs should think very seriously about allowing the use of IRIs
now that there exists a stable reference.

If you have questions, please direct them to this forum (in case of
general interest), to the I18N Core WG (mailto:public-i18n-core@w3.org
for public discussion, mailto:member-i18n-core@w3.org for Member-only
discussion), to the TAG, or to the authors of the specs.

Regards,    Martin.


 >>>>>>>>
A new Request for Comments is now available in online RFC libraries.


         STD 66
         RFC 3986

         Title:      Uniform Resource Identifier (URI): Generic Syntax
         Author(s):  T. Berners-Lee, R. Fielding, L. Masinter
         Status:     Standards Track
         Date:       January 2005
         Mailbox:    timbl@w3.org, fielding@gbiv.com, LMM@acm.org
         Pages:      61
         Characters: 141811
         Updates:    1738
         Obsoletes:  2732, 2396, 1808

         I-D Tag:    draft-fielding-uri-rfc2396bis-07.txt

         URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3986.txt


A Uniform Resource Identifier (URI) is a compact sequence of
characters that identifies an abstract or physical resource.  This
specification defines the generic URI syntax and a process for
resolving URI references that might be in relative form, along with
guidelines and security considerations for the use of URIs on the
Internet.  The URI syntax defines a grammar that is a superset of all
valid URIs, allowing an implementation to parse the common
components of a URI reference without knowing the scheme-specific
requirements of every possible identifier.  This specification does
not define a generative grammar for URIs; that task is performed by
the individual specifications of each URI scheme.

This is now a Standard Protocol.
 >>>>>>>>
 >>>>>>>>
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@w3.org, michelsu@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.
 >>>>>>>>

Received on Wednesday, 26 January 2005 14:38:56 UTC