# URN syntax

Mitra (mitra@pandora.sf.ca.us)
Wed, 27 Apr 1994 16:19:24 GMT

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Terry Allen: "Voyages in URCland"
- Previous message: David Robison: "Re: Voyages in URCland"
- Next in thread: Peter Deutsch: "Re: URN syntax"
- Maybe reply: Peter Deutsch: "Re: URN syntax"
- Maybe reply: Tim Berners-Lee: "Re: URN syntax"
- Maybe reply: Peter Deutsch: "Re: URN syntax"
- Maybe reply: Peter Deutsch: "Re: URN syntax"

    From: mitra@pandora.sf.ca.us (Mitra)

    Subject: URN syntax

    Date: Wed, 27 Apr 1994 16:19:24 GMT

    Message-Id: <CoxEoE.Gqy@pandora.sf.ca.us>

Just for the record - as one of the people who proposed that the URN
format should be hierarchical with NO seperation between
publisher/naming authority and opaque string, I have been convinced by
PeterD of the error-of-my-ways, and now think only that the
publisher-i/naming-authority field should be hierarchical, so formats
along the lines of.

urn:collins/uk:12345

would work fine for me, as would

urn:collins/uk/12345 or urn:collins:uk:12345

where the seperator is defined as the last seperation char reading from
the RHS.

Any of these formats work for me, as long as a publusher - e.g. collins
in this case, can register with the service - e.g. IANA or the top level
of the uri.int domain - and then independantly allocate sub-domains.

If I was the last hold-out for hierarchical URN's then maybe we can move
on and pick a syntax.

- Mitra

- Next message: Terry Allen: "Voyages in URCland"
- Previous message: David Robison: "Re: Voyages in URCland"
- Next in thread: Peter Deutsch: "Re: URN syntax"
- Maybe reply: Peter Deutsch: "Re: URN syntax"
- Maybe reply: Tim Berners-Lee: "Re: URN syntax"
- Maybe reply: Peter Deutsch: "Re: URN syntax"
- Maybe reply: Peter Deutsch: "Re: URN syntax"