[urn] Re: Request for Registration of CTS namespace
Peter Saint-Andre <[email protected]> Thu, 11 Jun 2026 08:40:23 -0600
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <[email protected]> |
--===============4276212869688165162== Content-Type: multipart/alternative; boundary=Apple-Mail-6C9F396D-B9FA-4CAA-B70D-1C44D13E1315 Content-Transfer-Encoding: 7bit --Apple-Mail-6C9F396D-B9FA-4CAA-B70D-1C44D13E1315 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html class=3D"apple-mail-supports-explicit-dark-mode"><head><meta http-equi= v=3D"content-type" content=3D"text/html; charset=3Dutf-8"></head><body dir=3D= "auto">Hallo Jochen,<div><br></div><div>As team lead for the reviewers, and c= o-author of RFC 8141, I would be happy to provide a letter of support. I wil= l coordinate with you offlist regarding your requirements.</div><div><br></d= iv><div>Peter</div><div><br id=3D"lineBreakAtBeginningOfSignature"><div dir=3D= "ltr">Sent from mobile, might be terse </div><div dir=3D"ltr"><br><bloc= kquote type=3D"cite">On Jun 11, 2026, at 8:05=E2=80=AFAM, Jochen Tiepmar <= ;[email protected]> wrote:<br><br></blockquote></div><bl= ockquote type=3D"cite"><div dir=3D"ltr">=EF=BB=BFDear reviewers,<br><br>Than= k you all for your feedback. In my opinion everything that is brought up can= be managed. On the software side the brackets-issue is even solved already (= with backwards-compatibility to [ and ], just to avoid problems ).<br><br>Th= e Saxon Academy of Sciences responded positively on the idea to work out a R= FC specification. BUT they want to do that as part of a project proposal and= asked me if I could collect letters of support as this would document the c= ommunity interest for the DFG.<br><br>I understood your responses in a way t= hat you would strongly support the idea of a registered CTS namespace and I t= hink it would be hard to find a more suitable supporter for this work packag= e than the IANA and researchers that are reviewing the requests for URN regi= stration<br><br>May I ask, if it is not too much, if you could provide me wi= th a letter of support for a RFC registration of the CTS URN namespace via t= he Saxon Academy of Sciences and Humanities as part of an text infrastructur= e project? We might be able to solve this problem until 2028 if this project= proposal works out.<br><br>Best Regards<br>Jochen Tiepmar<br><br><br><br><d= iv class=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" co= ntent=3D"width=3Ddevice-width"><meta http-equiv=3D"Content-Type" content=3D"= text/vnd.ui.insecure+html;charset=3Dutf-8"><div class=3D"mail_android_quote"= style=3D"line-height: 1"><br>Am 04.06.26, 03:35 schrieb "Dale R. Worley" &l= t;worley@<a href=3D"http://ariadne.com">ariadne.com</a>>:<blockquote clas= s=3D"gmail_quote" style=3D"margin: 0.8ex 0pt 0pt 0.8ex; border-left: 1px sol= id rgb(204, 204, 204); padding-left: 1ex;"> From: Jochen Tiepmar <tiepila= b@<a href=3D"http://gmx.de">gmx.de</a>><br> <br> With regard to the brackets [ and ].<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<br>= change the syntax rules if neccessary.<br> <br> Certainly it's possible to write a revised registration that has that<br> change.<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. I'm<br> sure that there is no legal precedent for guidance and likely very<br> little custom to follow.<br> <br> It isn't the duty of the URN experts committee to decide that question.<br> <br> As practical advice, you should first attempt to coordinate with<br> everybody else involved in the effort. 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. It<br> is always possible to later register an upward-compatible version 2 for<br> the namespace that includes a workable way to specify INDEX.<br> <br> Dale<br> </blockquote></div></div> <span>_______________________________________________</span><br><span>urn ma= iling list -- [email protected]</span><br><span>To unsubscribe send an email to u= [email protected]</span><br></div></blockquote></div></body></html>= --Apple-Mail-6C9F396D-B9FA-4CAA-B70D-1C44D13E1315-- --===============4276212869688165162== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KdXJuIG1haWxp bmcgbGlzdCAtLSB1cm5AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byB1 cm4tbGVhdmVAaWV0Zi5vcmcK --===============4276212869688165162==--