Internationalized Resource Identifiers (IRIs)
draft-duerst-iri-bis-07

 
Document Type Replaced Internet-Draft (individual in app area)
Last updated 2010-07-07 (latest revision 2009-10-26)
Replaced by draft-ietf-iri-3987bis
Stream IETF
Intended RFC status Proposed Standard
Formats
Expired & archived
plain text pdf html
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-iri-3987bis
Telechat date
Responsible AD Alexey Melnikov
Send notices to duerst@it.aoyama.ac.jp, michelsu@microsoft.com, draft-duerst-iri-bis@ietf.org

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-duerst-iri-bis-07.txt

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.

Authors

Martin Dürst (duerst@it.aoyama.ac.jp)
Michel Suignard (michel@unicode.org)
Larry Masinter (masinter@adobe.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)