Re: [URN] Re: URI documents

Patrik Faltstrom <paf@swip.net> Sat, 27 December 1997 19:00 UTC

Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id OAA06562 for urn-ietf-out; Sat, 27 Dec 1997 14:00:43 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id OAA06552 for <urn-ietf@services.bunyip.com>; Sat, 27 Dec 1997 14:00:36 -0500 (EST)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id OAA11481 for urn-ietf@services; Sat, 27 Dec 1997 14:00:35 -0500 (EST)
Received: from nix.swip.net (nix.swip.net [192.71.220.2]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id OAA11474; Sat, 27 Dec 1997 14:00:19 -0500 (EST)
Received: from localhost (paf@localhost) by nix.swip.net (8.8.8/8.8.8) with SMTP id UAA16813; Sat, 27 Dec 1997 20:00:07 +0100 (MET)
Date: Sat, 27 Dec 1997 20:00:06 +0100
From: Patrik Faltstrom <paf@swip.net>
X-Sender: paf@nix
To: "John C. Mallery" <jcma@ai.mit.edu>
cc: Larry Masinter <masinter@parc.xerox.com>, Leslie Daigle <leslie@bunyip.com>, "Roy T. Fielding" <fielding@kiwi.ics.uci.edu>, jcurran@bbn.com, harald.t.alvestrand@uninett.no, moore@cs.utk.edu, uri@bunyip.com, urn-ietf@bunyip.com
Subject: Re: [URN] Re: URI documents
In-Reply-To: <v03130304b0c79f003145@[207.159.82.125]>
Message-ID: <Pine.GSO.3.96.971227195321.15366C-100000@nix>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Patrik Faltstrom <paf@swip.net>
Errors-To: owner-urn-ietf@Bunyip.Com

On Thu, 25 Dec 1997, John C. Mallery wrote:

> Hi Larry,
> 
> Just to be clear, I choose C.
> 
> C Separate documents for URLs, URIs, and URNs.
> 
> Meaning that:
> 
> Documents a, b, d are unacceptable.

I agree with the above. (c) is the only working solution.

This is needed because the document currently under the name of a URI
syntax document talk so much about URLs, and use a terminology that is
only valid for URLs, that confusion occurs regarding, if nothing else, the
difference between a URL and a URN. It does not help that the document
have "may" all over the place.

I think it is definitely better if we have documents about URIs, URNs and
URLs, so the number of "may" can be limited to a minimum when we talk
about so important things as grammars and what characters are allowed, how
encoding is done and how to handle/accept things like fragments, queries
and relative addressing.

Personally I have not read the URI syntax document until I, as a member of
the URN working group, was told about the URL syntax document turning into
a URI syntax document during the IETF in Washington, DC. Leslie, as the
chair of the working group, promised to talk to the authors, the area
directors and Larry as the chair of the HTTP group, about the problems we
in the URN working group saw with the intention of the document changed,
and because of that I have not said anything until now. 

I have now reread draft-fielding-uri-syntax-01.txt aswell as Leslies two
proposed documents, to test the thesis I have that (c) is the best choice,
and I must say that it is.

   Patrik