- From: Martin J. Dürst <duerst@it.aoyama.ac.jp>
- Date: Fri, 29 Jan 2010 20:15:35 +0900
- To: "public-iri@w3.org" <public-iri@w3.org>
- Message-ID: <4B62C357.9020201@it.aoyama.ac.jp>
Dear IETF IRI WG members, I just managed to submit what is essentially draft-duerst-iri-bis-07.txt as draft-ietf-iri-3987bis-00.txt (see http://www.ietf.org/id/draft-ietf-iri-3987bis-00.txt). In due time, this also should be available as http://tools.ietf.org/html/draft-ietf-iri-3987bis-00 (the rendering I personally prefer, because it includes links but otherwise looks like the text/plain version, and it prints in more settings than the text/plain version). This means we have our first working draft to work on. Regards, Martin. -------- Original Message -------- Subject: I-D Action:draft-ietf-iri-3987bis-00.txt Date: Fri, 29 Jan 2010 03:00:01 -0800 (PST) From: Internet-Drafts@ietf.org Reply-To: internet-drafts@ietf.org To: i-d-announce@ietf.org CC: public-iri@w3.org A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Internationalized Resource Identifiers Working Group of the IETF. Title : Internationalized Resource Identifiers (IRIs) Author(s) : M. Duerst, et al. Filename : draft-ietf-iri-3987bis-00.txt Pages : 58 Date : 2010-01-29 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 version is essentially identical to draft-duerst-iri-bis-07.txt, and is submitted as an initial draft to start WG discussions. For discussion and comments on this draft, please join the IETF IRI WG by subscribing to the mailing list public-iri@w3.org. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-iri-3987bis-00.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.
Attachments
- Message/External-body attachment: draft-ietf-iri-3987bis-00.txt
- text/plain attachment: Attached_Message_Part
Received on Friday, 29 January 2010 11:16:30 UTC