Hi,
The successor to RFC 2396 "URI Generic Syntax" has just
been approved for publication as an RFC and Full Standard
by the IESG.
Note - quite a number of basic ABNF productions have been
simply removed and then replaced with others. Although I
complained on the URI Review list, I got shouted down.
Essentially EVERY existing URI scheme definition is now
broken, because the basic ABNF productions are gone and
actual resolution and normalization rules have been bent
into different forms.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
phone: +1-906-494-2434
email: imcdonald at sharplabs.com
-----Original Message-----
From: uri-request at w3.org [mailto:uri-request at w3.org]On Behalf Of Larry
Masinter
Sent: Monday, October 18, 2004 7:27 PM
To: uri at w3.org
Subject: FW: Protocol Action: 'Uniform Resource Identifier (URI):
Generic Syntax' to Full Standard
-----Original Message-----
From: ietf-announce-bounces at ietf.org [mailto:ietf-announce-bounces at ietf.org]
On Behalf Of The IESG
Sent: Monday, October 18, 2004 3:07 PM
To: IETF-Announce
Cc: Internet Architecture Board; RFC Editor
Subject: Protocol Action: 'Uniform Resource Identifier (URI): Generic
Syntax' to Full Standard
The IESG has approved the following document:
- 'Uniform Resource Identifier (URI): Generic Syntax '
<draft-fielding-uri-rfc2396bis-07.txt> as a Full Standard
This document has been reviewed in the IETF but is not the product of an
IETF Working Group.
The IESG contact person is Ted Hardie.
Technical Summary
This document advances the URI specification to Full Standard.
It defines the generic syntax for URIs and describes a process for resolving
URI references that are in relative form. It also contains guidelines for
the
use
of URIs on the Internet and security considerations which are
common to the use of URIs. The grammar it defines is a superset
of valid URIs, so that a common parser or similar component
can be built without scheme-specific data.
Working Group Summary
The URI working group is not active at this time, but the mailing list
(uri at w3.org) remains active. Members of the mailing list reviewed
this document extensively, and a comprehensive issues list was
maintained, with recorded resolutions of each of the issues raised.
The document also received editorial comments during Last Call;
a new version of the document with additional explanatory text
was generated in response to the issues raised. URIs are
widely in used many Internet context, and there has been no
dissent that a Full Standard updating RFC 2396 would be valuable.
Protocol Quality
This document was reviewed for the IESG by Ted Hardie.
RFC Editor Note:
OLD: URI comparison is performed in respect to some particular purpose,
and implementations with differing purposes will often be subject to
differing design trade-offs in regards to how much effort should be
spent in reducing aliased identifiers.
NEW: URI comparison is performed in respect to some particular purpose,
and protocols or implementations comparing for purposes will often be
subject to differing design trade-offs in regards to how much effort
should be spent in reducing aliased identifiers.
_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.orghttps://www1.ietf.org/mailman/listinfo/ietf-announce