Re: obsoleting 3986 -- what would it look like?

On 2012/11/05 8:29, David Sheets wrote:
> Hi Larry,
>
> On Fri, Nov 2, 2012 at 12:24 AM, Larry Masinter<masinter@adobe.com>  wrote:
>> Initially as a thought experiment, I've started to sketch out what it would look like to obsolete 3986 (URI) with a document that combined it with 3987 (IRI), reverts to the "URL" name, and gave updated parsing advice.

> I am very interested in the aggregation of URI/URN/URL/IRI grammars
> and formalization of codepoint translation tables. Does IETF have an
> XML vocabulary for expressing ABNF (RFC 5234?) grammars? I am
> presently developing machinery for grammar analysis that will be used
> to generate reference parsers, serializers, and test suites directly
> from the specification(s).
>
> Is there a central repository of RFC XML (RFC 2629) documents? Are you
> drafting the neo-URI RFC in a revision control system somewhere?

The IRI WG has a subversion repository viewable at 
http://trac.tools.ietf.org/wg/iri/trac/browser/draft-ietf-iri-3987bis.

>>    <t>This document is part of a set of documents intended to
>>    replace RFCs 2141, 3986, 3987 and 4345</t>
>> </abstract>
>
> RFC 2141 is about well-known email endpoints for domains. How is this
> related to the structure of identifiers?

http://www.ietf.org/rfc/rfc2141.txt is "URN Syntax". (No well-known 
email endpoints as far as I can see.)


> RFC 4345 is about RC4 modes for SSH? How is this related? Or which
> other RFC was meant?

My guess is that Larry meant RFC 4395 
(http://www.ietf.org/rfc/rfc4395.txt), Guidelines and Registration 
Procedures for New URI Schemes.

Regards,   Martin.

Received on Tuesday, 6 November 2012 01:14:54 UTC