W3C home > Mailing lists > Public > public-iri@w3.org > October 2009

FW: New Version Notification for draft-duerst-iri-bis-07

From: Larry Masinter <masinter@adobe.com>
Date: Wed, 28 Oct 2009 18:20:58 -0700
To: "PUBLIC-IRI@W3.ORG" <PUBLIC-IRI@w3.org>
Message-ID: <8B62A039C620904E92F1233570534C9B0118DC708E41@nambx04.corp.adobe.com>
Due to some personal difficulties, the split of the document
into three parts (parsing, domain names, BCP on character
handling, BIDI, etc.) didn't happen. However, Martin did
heroically get a new draft out based on some if the
interim work.



-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] 
Sent: Monday, October 26, 2009 6:08 AM
To: duerst@it.aoyama.ac.jp
Cc: michel@unicode.org; Larry Masinter
Subject: New Version Notification for draft-duerst-iri-bis-07 


A new version of I-D, draft-duerst-iri-bis-07.txt has been successfuly submitted by Martin Duerst and posted to the IETF repository.

Filename:	 draft-duerst-iri-bis
Revision:	 07
Title:		 Internationalized Resource Identifiers (IRIs)
Creation_date:	 2009-10-26
WG ID:		 Independent Submission
Number_of_pages: 58

Abstract:
This document defines the Internationalized Resource Identifier (IRI)
protocol element, as an extension of the Uniform Resource Identifier
(URI).  An IRI is a sequence of characters from the Universal
Character Set (Unicode/ISO 10646).  Grammar and processing rules are
given for IRIs and related syntactic forms.

In addition, this document provides named additional rule sets for
processing otherwise invalid IRIs, in a way that supports other
specifications that wish to mandate common behavior for 'error'
handling.  In particular, rules used in some XML languages (LEIRI)
and web applications are given.

Defining IRI as new protocol element (rather than updating or
extending the definition of URI) allows independent orderly
transitions: other protocols and languages that use URIs must
explicitly choose to allow IRIs.

Guidelines are provided for the use and deployment of IRIs and
related protocol elements when revising protocols, formats, and
software components that currently deal only with URIs.

[RFC Editor: Please remove this paragraph before publication.]  This
document is intended to update RFC 3987 and move towards IETF Draft
Standard.  This is an interim version in preparation for the IRI BOF
at IETF 76 in Hiroshima.  For discussion and comments on this draft,
please use the public-iri@w3.org mailing list.
                                                                                  


The IETF Secretariat.


Received on Thursday, 29 October 2009 01:21:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 April 2012 19:51:55 GMT