revised URN requirements document

Jared_Rhine@hmc.edu
Sat, 14 May 1994 03:26:09 -0700

Date: Sat, 14 May 1994 03:26:09 -0700
Message-Id: <199405141026.DAA02238@osiris.ac.hmc.edu>
From: Jared_Rhine@hmc.edu
To: Larry Masinter <masinter@parc.xerox.com>
Subject: revised URN requirements document

Larry> Now I will compress YOUR schedule by suggesting that this go forward
Larry> to the RFC editor if there are no corrections or revisions in the
Larry> next two weeks.

After review of this draft, this seems quite reasonable. I found little to
dispute and generally agree with both the requirements enumerated and their
encoding. Good work.

Nits:

I would probably change the title of section three; perhaps "Requirements
for URN encoding" instead of "Requirements for URNs as they are encoded."
Drop the trailing period, in any case.

The inclusion of "location" as meta-information (end of first paragraph,
page 2) is confusing in light of the immediately preceeding definition
provided for URLs.

I recommend the removal of the word "often" in the formal definition of URN
(2nd paragraph of page 2).

-- 
Jared_Rhine@hmc.edu | Harvey Mudd College | http://www.hmc.edu/~jared/

"To hear many religious people talk, one would think God created the torso, head, legs and arms, but the devil slapped on the genitals." -- Don Schrader