[urn] Re: The URN:GLUE proposal
"Henry S. Thompson" <[email protected]> Thu, 02 Apr 2026 15:24:40 +0100
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <[email protected]> |
Peter Saint-Andre writes:
> Focusing on only one point for now...
>
> On 4/1/26 8:22 PM, Dale R. Worley wrote:
>
>> 2. The politics of using someone else's identifier
> ...
>
> Until draft-ietf-spice-glue came along, in the entire history of URN
> namespace registrations going back 25 years or more (the earliest one
> I see is `pin` in RFC 3043, not including `ietf` in RFC 2648), I
> believe that "we" - the folks involved with the URN WG and
> subsequently the URN namespaces expert review team set up by RFC 8141
> - never imagined such a "creative" registration as GLUE. We always
> assumed that other SDOs would make requests of us to register their
> own namespaces so as to incorporate their own identifier systems, not
> that what you are calling third-party organizations (or WGs) would
> register namespaces to incorporate identifier systems defined
> elsewhere.
Apologies for flogging a dead quadruped, but that's at least somewhat
misleading. In November 2022 we approved, after lengthy argument which
I lost, 'pwid', which existed solely to give authority to 3rd parties
to wrap their URIs, which might be URNs, in a PWID, without any
engagement with the 3rd party at all.
Notwithstanding that precedent (which has not received much (any?)
use) I agree with the concern expressed by others about the GLUE
proposal.
I'm sure I yet see how offering 'glue' as a URI scheme solves the
'political' objection, but that's for another thread.
As far as the concern for the authors' frustration, yes, I sympathise,
but as far as I can see we're doing our job here, and hard cases make
bad law, as the saying goes, or, in this case, a long time to arrive
at the best resolution.
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND
e-mail: [email protected]
URL: https://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged spam]
_______________________________________________
urn mailing list -- [email protected]
To unsubscribe send an email to [email protected]