# URN -- case issues

Fred Swartz (fred.swartz@umich.edu)
Fri, 22 Oct 1993 17:36:30 -0400

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Rich Wiggins: "Re: Final edits - summary of outstanding points."
- Previous message: Mark P. McCahill: "Re: Final edits - summary of outstanding points."

    Message-Id: <9310222136.AA09633@merit.edu>

    To: uri@bunyip.com

    From: "Fred Swartz" <fred.swartz@umich.edu>

    Subject: URN -- case issues

    Date: Fri, 22 Oct 1993 17:36:30 -0400

A clear specification of which URN components have case sensitivity
and insensitivity is required. Here is a specific proposal:

(1) The URN keyword -- this should obey the URL rules.
(2) The character set encoding: case insensitive.
(3) The naming authority scheme identifier: case insensitive.
(4) The naming authority identifier: case insensitive.
(5) The opaque string: case sensitive.
A case change in an opaque string may change a URN.
urn->url servers are free to ignore case for the URNs they have
issued, but they must always publish URNs in a consistent manner
so that URN equality comparisons can be made by others, who
must not assume case insensitivity.

-- Fred (fred.swartz@merit.edu)

- Next message: Rich Wiggins: "Re: Final edits - summary of outstanding points."
- Previous message: Mark P. McCahill: "Re: Final edits - summary of outstanding points."