[urn] Re: [EXTERNAL] Re: [Uri-review] Request to r egister the glue URI scheme

--===============6954451789967517959==
Content-Type: multipart/alternative; boundary="6a46b00b_54e49eb4_e66"

--6a46b00b_54e49eb4_e66
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hello all,

I'd like to extend an invitation to our URI experts to join us at the spi=
ce meeting in Vienna (Wednesday, 22 July =40 16:00 CEST) to discuss this =
in person. We'll have at least 30 minutes to see if we can come to some a=
greement. If not, we'll pull the doc back into the working group and plan=
 for a longer discussion with you to figure out next steps.

Thanks=21

Heather =46lanagan (she/hers)
Principal,=C2=A0Spherical Cow Consulting
=C2=A0hlf=40sphericalcowconsulting.com
=C2=A0sphericalcowconsulting.com


On Jun 29, 2026 at 2:43=E2=80=AFPM -0700, Brent Zundel <brent.zundel=40gm=
ail.com>, wrote:
> I've been following this thread with great interest and not a little
> curiosity.
>
> It seems like there may be some folks who are struggling to understand
> what we are trying to accomplish with GLUE.
>
> Some have pointed out that global business identification is a major
> problem. One which led to the creation of GLEI=46, and has led to a num=
ber of
> other organizations pursuing URN registration for individual schemes. T=
his
> is laudable. This is good. It may even solve the problem someday, but i=
n my
> estimation those solutions are a long way off. Where we agree is that t=
here
> is a problem and many people are interested in solving it.
>
> One GLEI=46 statistic I have seen repeated often is that over 3 million=

> businesses have obtained an LEI. This is great. It is a wonderful step =
in
> the right direction, but it is a tiny drop in the bucket of the hundred=
s of
> millions of businesses and organizations engaged in trade worldwide. GL=
UE
> enables existing business identifiers to be used in the interim between=
 now
> and whenever in the future those businesses are able to themselves clai=
m an
> LEI or GLN.
>
> Pam pointed out a clear need for additional tools for identifying
> businesses, ones that are long-lasting, and can be used to help keep th=
e
> records being passed about as legible as possible. Some have argued tha=
t
> such a mess is clearly not something that a URN scheme is appropriate f=
or.
> Not in my view. The clear organizational potential that is brought to b=
ear
> by the introduction of GLUE identifiers would have a significant impact=
 in
> the clarity and legibility of these currently messy and difficult to re=
ad
> documents. They are messy because there isn't a simple scheme that can =
be
> used to organize them. That is all GLUE aims to be.
>
> Someone mentioned that a global database might be a more appropriate
> solution than an identifier scheme and an accompanying registry of
> authorities. I'm a bit confused what the difference is between a global=

> database and an IANA registry, except that an IANA registry is easier t=
o
> find, unburdened by corporate interests, and more likely to be a truste=
d
> global source of information.
>
> I'm fine if GLEI=46 or GS1 would prefer they not be listed in the regis=
try,
> since they have their own URN schemes, but such a determination to not =
be
> involved completely misses the point. Demanding to be removed from GLUE=
 is
> like the producers of some informative reference demanding it be remove=
d
> from another specification that wishes to refer to it. Supporters of GL=
UE
> are supporters of the great efforts being made by GLEI=46 and GS1. GLUE=
 is an
> attempt to make it even easier to use those identifier schemes in digit=
al
> trade credentials, alongside the myriad other business and organization=

> identifiers that are in use today.
>
> GLUE is not a business registry. It claims no authority for determining=
 the
> realities of business registration beyond the those already possessed b=
y
> the authorities themselves. GLUE is just a slightly different way to fo=
rmat
> the existing identifiers, one that is consistent with the requirements =
of
> digital identity and trade modernization schemes. It is paired with wha=
t we
> hope will someday be an expansive registry of organization identifier
> authorities. There is no registration scheme too small to fit inside GL=
UE.
>
> But, it seems to me like all of that may be beside the point. GLUE isn'=
t
> some random individual draft out of nowhere. GLUE was been adopted by a=
n
> IET=46 working group. That working group reviewed and refined the ideas=
 in
> GLUE over years. The specification found working group consensus and pa=
ssed
> working group last call. To my understanding it even passed IESG review=
.
> All that is left is to register the identifier scheme.
>
> There have been ample examples shared in this thread and others, ones I=
 am
> not going to reiterate, that make it seem as though the designated expe=
rts
> are holding GLUE to a higher bar for URN or URI registration than other=

> schemes have been held. I don't believe that the experts are acting
> inappropriately. I applaud their caution, but encourage them to act and=

> register GLUE.
>
> GLUE is not going to break the internet. If its detractors are correct,=
 and
> GLUE sees little to no use in industry, then it would certainly not be =
the
> first IET=46 specification to meet such a fate.
> I don't think they are right. I think GLUE can have a positive impact o=
n
> the disgusting mess that is global business and organization identifica=
tion

--6a46b00b_54e49eb4_e66
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<html xmlns=3D=22http://www.w3.org/1999/xhtml=22>
<head>
<title></title>
</head>
<body>
<div name=3D=22messageBodySection=22>
<div>Hello all,</div>
<div>&=23160;</div>
<div>I'd like to extend an invitation to our URI experts to join us at th=
e spice meeting in Vienna (Wednesday, 22 July =40 16:00 CEST) to discuss =
this in person. We'll have at least 30 minutes to see if we can come to s=
ome agreement. If not, we'll pull the doc back into the working group and=
 plan for a longer discussion with you to figure out next steps.</div>
<div>&=23160;</div>
<div>Thanks=21</div>
</div>
<div name=3D=22messageSignatureSection=22><br />
<div data-spark-custom-html=3D=22true=22>
<div dir=3D=22auto=22>
<table style=3D=22direction:ltr;border-collapse:collapse;=22>
<tbody>
<tr>
<td style=3D=22font-size:0;height:12px;line-height:0;=22></td>
</tr>
<tr>
<td>
<table cellpadding=3D=220=22 cellspacing=3D=220=22 border=3D=220=22 style=
=3D=22width:100%;=22 width=3D=22100%=22>
<tbody>
<tr>
<td>
<table cellpadding=3D=220=22 cellspacing=3D=220=22 style=3D=22border-coll=
apse:collapse;line-height:1.15;width:100%;=22 width=3D=22100%=22>
<tbody>
<tr>
<td style=3D=22height:1px;width:78px;vertical-align:top;padding:.01px 1px=
;=22>
<table cellpadding=3D=220=22 cellspacing=3D=220=22 style=3D=22border-coll=
apse:collapse;=22>
<tbody>
<tr>
<td style=3D=22vertical-align:top;padding:.01px 1px 0.01px 0.01px;width:7=
8px;text-align:center;=22><img border=3D=220=22 src=3D=22https://d36urhup=
7zbd7q.cloudfront.net/u/WokAvoRrM0N/1672685168849.jpeg=22 height=3D=2270=22=
 width=3D=2278=22 alt=3D=22photo=22 style=3D=22width:78px;vertical-align:=
middle;border-radius:0;height:70px;border:0;display:block;=22 /></td>
</tr>
</tbody>
</table>
</td>
<td valign=3D=22top=22 style=3D=22padding:.01px 0.01px 0.01px 14px;vertic=
al-align:top;=22>
<table cellpadding=3D=220=22 cellspacing=3D=220=22 style=3D=22border-coll=
apse:collapse;=22>
<tbody>
<tr>
<td style=3D=22line-height:1.2;padding:.01px;=22>
<p style=3D=22margin:.1px;line-height:120%;font-size:18px;=22><span style=
=3D=22margin: 0.1px; line-height: 120%; font-size: 18px;=22><span style=3D=
=22font-family:Arial;font-size:18px;font-weight:bold;color:=2345668E;lett=
er-spacing:0;white-space:nowrap;=22>Heather =46lanagan (she/hers)</span><=
br />
<span style=3D=22font-family:Arial;font-size:14px;font-weight:bold;color:=
=23212121;white-space:nowrap;=22>Principal,<span>&=23160;</span></span><s=
pan style=3D=22font-family:Arial;font-size:14px;font-weight:bold;color:=23=
212121;white-space:nowrap;=22>Spherical Cow Consulting</span></span></p>
</td>
</tr>
<tr>
<td>
<table cellpadding=3D=220=22 cellspacing=3D=220=22 style=3D=22border-coll=
apse:collapse;=22>
<tbody>
<tr>
<td nowrap=3D=22nowrap=22 width=3D=22237=22 style=3D=22padding-top:14px;w=
hite-space:nowrap;width:237px;font-family:Arial;=22>
<p style=3D=22margin:1px;line-height:99%;font-size:12px;=22><span style=3D=
=22margin: 1px; line-height: 99%; font-size: 12px;=22><span style=3D=22wh=
ite-space:nowrap;=22><img src=3D=22https://cdn.gifo.wisestamp.com/s/rfem1=
/45668E/26/trans.png=22 style=3D=22line-height:120%;width:12px;=22 width=3D=
=2212=22 alt=3D=22icon=22 />&=23160;<a href=3D=22mailto:hlf=40sphericalco=
wconsulting.com=22 target=3D=22=5Fblank=22 style=3D=22font-family:Arial;t=
ext-decoration:unset;=22 rel=3D=22nofollow noreferrer=22><span style=3D=22=
line-height:120%;font-family:Arial;font-size:12px;color-scheme:only;color=
:=23212121;white-space:nowrap;=22>hlf=40sphericalcowconsulting.com</span>=
</a></span></span></p>
</td>
</tr>
<tr>
<td nowrap=3D=22nowrap=22 width=3D=22207=22 style=3D=22padding-top:8px;wh=
ite-space:nowrap;width:207px;font-family:Arial;=22>
<p style=3D=22margin:1px;line-height:99%;font-size:12px;=22><span style=3D=
=22margin: 1px; line-height: 99%; font-size: 12px;=22><span style=3D=22wh=
ite-space:nowrap;=22><img src=3D=22https://cdn.gifo.wisestamp.com/s/rfw1/=
45668E/26/trans.png=22 style=3D=22line-height:120%;width:12px;=22 width=3D=
=2212=22 alt=3D=22icon=22 />&=23160;<a href=3D=22https://sphericalcowcons=
ulting.com/=22 target=3D=22=5Fblank=22 style=3D=22font-family:Arial;text-=
decoration:unset;=22 rel=3D=22nofollow noreferrer=22><span style=3D=22lin=
e-height:120%;font-family:Arial;font-size:12px;color-scheme:only;color:=23=
212121;white-space:nowrap;=22>sphericalcowconsulting.com</span></a></span=
></span></p>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td height=3D=2214=22 style=3D=22height:14px;=22></td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td colspan=3D=222=22 style=3D=22background-color:=2345668E;padding:12px =
6px;line-height:0;width:588px;max-width:100%;=22 width=3D=22588=22>
<table cellpadding=3D=220=22 cellspacing=3D=220=22 style=3D=22line-height=
:1.2;float:right;=22 align=3D=22right=22>
<tbody>
<tr>
<td>
<table border=3D=220=22 cellpadding=3D=220=22 cellspacing=3D=220=22>
<tbody>
<tr>
<td align=3D=22left=22 style=3D=22padding-right:6px;text-align:center;pad=
ding-top:0;=22>
<p style=3D=22margin:1px;=22><span style=3D=22margin: 1px;=22><a href=3D=22=
https://us.linkedin.com/in/hlflanagan=22 target=3D=22=5Fblank=22 rel=3D=22=
nofollow noreferrer=22><img width=3D=2224=22 height=3D=2224=22 src=3D=22h=
ttps://cdn.gifo.wisestamp.com/s/ld/=46=46=46=46=46=46/48/circle/border.pn=
g=22 style=3D=22float: left; border: none; max-width: 100%; height: auto;=
=22 border=3D=220=22 alt=3D=22linkedin=22 /></a></span></p>
</td>
<td align=3D=22left=22 style=3D=22padding-right:6px;text-align:center;pad=
ding-top:0;=22>
<p style=3D=22margin:1px;=22><span style=3D=22margin: 1px;=22><a href=3D=22=
https://github.com/hlflanagan=22 target=3D=22=5Fblank=22 rel=3D=22nofollo=
w noreferrer=22><img width=3D=2224=22 height=3D=2224=22 src=3D=22https://=
cdn.gifo.wisestamp.com/s/gh/=46=46=46=46=46=46/48/circle/border.png=22 st=
yle=3D=22float: left; border: none; max-width: 100%; height: auto;=22 bor=
der=3D=220=22 alt=3D=22github=22 /></a></span></p>
</td>
<td align=3D=22left=22 style=3D=22padding-right:6px;text-align:center;pad=
ding-top:0;=22></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td style=3D=22font-family:'ws-id M5WXzj6K';font-size:.01px;line-height:0=
;=22>&=23160;</td>
</tr>
</tbody>
</table>
<br />
<img alt=3D=22=5F=5Ftpx=5F=5F=22 style=3D=22max-width:100%;height:auto=22=
 src=3D=22https://tracy.srv.wisestamp.com/px/wsid/M5WXzj6K.png=22 /></div=
>
</div>
</div>
<div name=3D=22messageReplySection=22>On Jun 29, 2026 at 2:43=E2=80=AFPM =
-0700, Brent Zundel &lt;brent.zundel=40gmail.com&gt;, wrote:<br />
<blockquote type=3D=22cite=22>I've been following this thread with great =
interest and not a little<br />
curiosity.<br />
<br />
It seems like there may be some folks who are struggling to understand<br=
 />
what we are trying to accomplish with GLUE.<br />
<br />
Some have pointed out that global business identification is a major<br /=
>
problem. One which led to the creation of GLEI=46, and has led to a numbe=
r of<br />
other organizations pursuing URN registration for individual schemes. Thi=
s<br />
is laudable. This is good. It may even solve the problem someday, but in =
my<br />
estimation those solutions are a long way off. Where we agree is that the=
re<br />
is a problem and many people are interested in solving it.<br />
<br />
One GLEI=46 statistic I have seen repeated often is that over 3 million<b=
r />
businesses have obtained an LEI. This is great. It is a wonderful step in=
<br />
the right direction, but it is a tiny drop in the bucket of the hundreds =
of<br />
millions of businesses and organizations engaged in trade worldwide. GLUE=
<br />
enables existing business identifiers to be used in the interim between n=
ow<br />
and whenever in the future those businesses are able to themselves claim =
an<br />
LEI or GLN.<br />
<br />
Pam pointed out a clear need for additional tools for identifying<br />
businesses, ones that are long-lasting, and can be used to help keep the<=
br />
records being passed about as legible as possible. Some have argued that<=
br />
such a mess is clearly not something that a URN scheme is appropriate for=
.<br />
Not in my view. The clear organizational potential that is brought to bea=
r<br />
by the introduction of GLUE identifiers would have a significant impact i=
n<br />
the clarity and legibility of these currently messy and difficult to read=
<br />
documents. They are messy because there isn't a simple scheme that can be=
<br />
used to organize them. That is all GLUE aims to be.<br />
<br />
Someone mentioned that a global database might be a more appropriate<br /=
>
solution than an identifier scheme and an accompanying registry of<br />
authorities. I'm a bit confused what the difference is between a global<b=
r />
database and an IANA registry, except that an IANA registry is easier to<=
br />
find, unburdened by corporate interests, and more likely to be a trusted<=
br />
global source of information.<br />
<br />
I'm fine if GLEI=46 or GS1 would prefer they not be listed in the registr=
y,<br />
since they have their own URN schemes, but such a determination to not be=
<br />
involved completely misses the point. Demanding to be removed from GLUE i=
s<br />
like the producers of some informative reference demanding it be removed<=
br />
from another specification that wishes to refer to it. Supporters of GLUE=
<br />
are supporters of the great efforts being made by GLEI=46 and GS1. GLUE i=
s an<br />
attempt to make it even easier to use those identifier schemes in digital=
<br />
trade credentials, alongside the myriad other business and organization<b=
r />
identifiers that are in use today.<br />
<br />
GLUE is not a business registry. It claims no authority for determining t=
he<br />
realities of business registration beyond the those already possessed by<=
br />
the authorities themselves. GLUE is just a slightly different way to form=
at<br />
the existing identifiers, one that is consistent with the requirements of=
<br />
digital identity and trade modernization schemes. It is paired with what =
we<br />
hope will someday be an expansive registry of organization identifier<br =
/>
authorities. There is no registration scheme too small to fit inside GLUE=
.<br />
<br />
But, it seems to me like all of that may be beside the point. GLUE isn't<=
br />
some random individual draft out of nowhere. GLUE was been adopted by an<=
br />
IET=46 working group. That working group reviewed and refined the ideas i=
n<br />
GLUE over years. The specification found working group consensus and pass=
ed<br />
working group last call. To my understanding it even passed IESG review.<=
br />
All that is left is to register the identifier scheme.<br />
<br />
There have been ample examples shared in this thread and others, ones I a=
m<br />
not going to reiterate, that make it seem as though the designated expert=
s<br />
are holding GLUE to a higher bar for URN or URI registration than other<b=
r />
schemes have been held. I don't believe that the experts are acting<br />=

inappropriately. I applaud their caution, but encourage them to act and<b=
r />
register GLUE.<br />
<br />
GLUE is not going to break the internet. If its detractors are correct, a=
nd<br />
GLUE sees little to no use in industry, then it would certainly not be th=
e<br />
first IET=46 specification to meet such a fate.<br />
I don't think they are right. I think GLUE can have a positive impact on<=
br />
the disgusting mess that is global business and organization identificati=
on</blockquote>
</div>
</body>
</html>

--6a46b00b_54e49eb4_e66--


--===============6954451789967517959==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KdXJuIG1haWxp
bmcgbGlzdCAtLSB1cm5AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byB1
cm4tbGVhdmVAaWV0Zi5vcmcK

--===============6954451789967517959==--