Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- John Dunlop
January 27, 2005, 2:53 am
rate this thread
Standard yesterday (2005-01-25). RFC3986 obsoletes the
Draft Standard, RFC2396. Its abstract:
| 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.
Internationalised Resource Identifiers, or IRIs for short
and to skirt the -ise/-ize issue, became a Proposed Standard
yesterday. RFC3987 has all the gory details. Its abstract:
| 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.