[urn] Re: Request for Registration of CTS namespace
Jochen Tiepmar <[email protected]> Thu, 11 Jun 2026 14:04:50 +0000
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <trinity-807a363b-d1a4-4215-9686-8649643fed4a-1781186689902@trinity-msg-rest-gmx-gmx-live-6759fbb69b-mln9m> |
--===============2171158203111846618==
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<html><body>Dear reviewers,<br><br>Thank you all for your feedback=2E In my=
opinion everything that is brought up can be managed=2E On the software si=
de the brackets-issue is even solved already (with backwards-compatibility =
to [ and ], just to avoid problems )=2E<br><br>The Saxon Academy of Science=
s responded positively on the idea to work out a RFC specification=2E BUT t=
hey want to do that as part of a project proposal and asked me if I could c=
ollect letters of support as this would document the community interest for=
the DFG=2E<br><br>I understood your responses in a way that you would stro=
ngly support the idea of a registered CTS namespace and I think it would be=
hard to find a more suitable supporter for this work package than the IANA=
and researchers that are reviewing the requests for URN registration<br><b=
r>May I ask, if it is not too much, if you could provide me with a letter o=
f support for a RFC registration of the CTS URN namespace via the Saxon Aca=
demy of Sciences and Humanities as part of an text infrastructure project? =
We might be able to solve this problem until 2028 if this project proposal =
works out=2E<br><br>Best Regards<br>Jochen Tiepmar<br><br><br><br><div clas=
s=3D"signature">--<br>Gesendet mit der GMX Mail App</div><div class=3D"mail=
_android_quote" style=3D"line-height: 1"><br><meta name=3D"viewport" conten=
t=3D"width=3Ddevice-width"><meta http-equiv=3D"Content-Type" content=3D"tex=
t/vnd=2Eui=2Einsecure+html;charset=3Dutf-8"><div class=3D"mail_android_quot=
e" style=3D"line-height: 1"><br>Am 04=2E06=2E26, 03:35 schrieb "Dale R=2E W=
orley" <worley@<a href=3D"http://ariadne=2Ecom">ariadne=2Ecom</a>>:<b=
lockquote class=3D"gmail_quote" style=3D"margin: 0=2E8ex 0pt 0pt 0=2E8ex; b=
order-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> From: Jochen=
Tiepmar <tiepilab@<a href=3D"http://gmx=2Ede">gmx=2Ede</a>><br>
<br>
With regard to the brackets [ and ]=2E<br>
<br>
Would it be possible to exclude that from the registration with the<br=
>
argument that the specs must be adapted?<br>
<br>
If Neel Smith is not working on that I think it would be my right to<b=
r>
change the syntax rules if neccessary=2E<br>
<br>
Certainly it's possible to write a revised registration that has that<br>
change=2E<br>
<br>
Who "owns" the namespace specification and who "has the right to amend<br>
it" is, in theory, a matter of intellectual property rights=2E I'm<br>
sure that there is no legal precedent for guidance and likely very<br>
little custom to follow=2E<br>
<br>
It isn't the duty of the URN experts committee to decide that question=2E<=
br>
<br>
As practical advice, you should first attempt to coordinate with<br>
everybody else involved in the effort=2E If that does not produce<br>
agreement (especially if you get no response), I think a reasonable<br>
course of action would be to remove the optional "[INDEX]" from the<br>
subreference element in this version of the registration template=2E It<b=
r>
is always possible to later register an upward-compatible version 2 for<br=
>
the namespace that includes a workable way to specify INDEX=2E<br>
<br>
Dale<br>
</blockquote></div></div></body></html>
--===============2171158203111846618==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KdXJuIG1haWxp
bmcgbGlzdCAtLSB1cm5AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byB1
cm4tbGVhdmVAaWV0Zi5vcmcK
--===============2171158203111846618==--