[urn] Re: Request for Registration of CTS namespace
[email protected] Fri, 22 May 2026 15:12:32 +0000
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <trinity-27483f84-8770-4f78-946d-a9ac9e032f50-1779462752290@trinity-msg-rest-gmx-gmx-live-67f45748b-p9hmv> |
--===============5274818759766784202== Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <html><body>I agree with everything and will send an updated request in the= coming weeks=2E<br><br>Yes, the sort of one-man-project in which this situ= ation slipped is kind of problematic=2E I am trying my best to solve that b= c I dont actually want to be responsible for naming the sub-namespaces and = see it as a decentralised system=2E Therefore the resolver and all interfac= es are as open source as possible=2E <br><br>The issue is kind of a ch= icken-egg problem: Institutions are held back because the URNs are not regi= stered and registration requires institutional backing=2E <br><br>I am= currently in talks with the Saxon Academy of Sciences about a research pos= ition for me=2E They are also a major player in the CLARIN / Text+ environm= ent=2E I will bring this up at our next meeting=2E Hopefully they will unde= rstand this issue and help me in any case (even without a research position= )=2E<br><br>Unfortunally if these talks fail, the issue will be hard to sol= ve, as institutions might be hesitant to back a project from someone who is= not part of the institution and research positions are currently rare and = project based=2E<br><br>The suggestion that missing institutional backing i= s a show-stopper for the registration is difficult for me=2E This creates a= situation where the continuation of my work will do harm with unregisterd = URNs and I cannot just stop my research work after building it up as a pers= istently citable infrastructure=2E<br><br><br>Any help is appreciated=2E<br= ><br><br><div 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" content=3D"width=3Ddevice-width"><meta http-equiv=3D"Content-= Type" content=3D"text/vnd=2Eui=2Einsecure+html;charset=3Dutf-8"><div class= =3D"mail_android_quote" style=3D"line-height: 1"><br>Am 22=2E05=2E26, 13:11= schrieb "Lars G=2E Svensson" <lars=2Esvensson@<a href=3D"http://web=2Ed= e">web=2Ede</a>>:<blockquote class=3D"gmail_quote" style=3D"margin: 0=2E= 8ex 0pt 0pt 0=2E8ex; border-left: 1px solid rgb(204, 204, 204); padding-lef= t: 1ex;"> Dear Jochen, <br> <br> Yes, I fully agree with Peter that we should register this namespace=2E Th= e impressive list of data providers at [1] shows that the namespace is heav= ily used and that there is a demand for this=2E<br> <br> That said, I think that the registration needs some work (no pun intended= =2E=2E=2E)=2E<br> <br> First, it would be helpful if the registration template contained the comp= lete syntax information as specified in the old registration template [2]= =2E I realise that it's a lot of text but the syntax is fairly complicated = and it's easier for implementers to have all the requirements in one place,= particularly if they are going to build parsers etc=2E The text in the old= template needs to be updated: FRBR is now IFLA-LRM [4], RFC 2141 is RFC 82= 41, etc=2E but that should be fairly easy=2E<br> <br> Back in 2019, Dale commented [3] on the old registration template and I th= ink at least some of those comments still hold:<br> * The syntax is not accurately described, ABNF would help (and we can help= with that)<br> * No assignment process is specified for work, passage, or subnamespace=2E= <br> <br> This last comment of Dale's also highlights another aspect that curre= ntly would be a show-stopper: At the moment, the assignment and registratio= n processes seem to be a sort of one-man-show=2E In order to ensure the lon= g-term governing of the namespace (i=2E e=2E the next 500 years or so), it = would be necessary to get some institutional backing=2E You state in your r= egistration template that the "infrastructure is currently encorporated in = research invironments like CLARIN / Text+ and community driven infrastructu= re specifications like the Distributed Text Service Project (<a href=3D"htt= p://dtsapi=2Eorg">dtsapi=2Eorg</a>)=2E" The project partners and infrastruc= ture providers in those projects are usually either universities or researc= h libraries and I think it would be in their interest, too, to ensure that = the CTS infrastructure is available for the foreseeable future, so I'm posi= tive that we can get that solved=2E<br> <br> This is important work for the cultural heritage community and I'd be happ= y to help completing this registration=2E<br> <br> [1] <a href=3D"https://urncts=2Eeu/#textservice">https://urncts=2Eeu/#text= service</a><br> [2] <a href=3D"https://github=2Ecom/cite-architecture/ctsurn_spec/blob/mas= ter/md/specification=2Emd">https://github=2Ecom/cite-architecture/ctsurn_sp= ec/blob/master/md/specification=2Emd</a><br> [3] <a href=3D"https://mailarchive=2Eietf=2Eorg/arch/msg/urn/6V08rUjevBioT= xrZlKvB3wCR21Y/">https://mailarchive=2Eietf=2Eorg/arch/msg/urn/6V08rUjevBio= TxrZlKvB3wCR21Y/</a><br> [4] <a href=3D"https://www=2Eifla=2Eorg/files/assets/cataloguing/frbr-lrm/= ifla-lrm-august-2017=2Epdf">https://www=2Eifla=2Eorg/files/assets/catalogui= ng/frbr-lrm/ifla-lrm-august-2017=2Epdf</a><br> <br> Best,<br> <br> Lars<br> <br> -----Urspr=C3=BCngliche Nachricht-----<br> Von: Peter Saint-Andre [mailto:stpeter@stpeter=2Eim] <br> Gesendet: Donnerstag, 21=2E Mai 2026 14:12<br> An: tiepilab@<a href=3D"htt= p://gmx=2Ede">gmx=2Ede</a>; urn@<a href=3D"http://ietf=2Eorg">ietf=2Eorg</a= ><br> Betreff: [urn] Re: Request for Registration of CTS namespace<br> <br> Hi Jochen,<br> <br> Thanks for your note=2E<br> <br> My perspective is that we should get this namespace registered, whether or= not Messrs Smith and Blackwell are involved=2E It always makes me somewhat= nervous to have unregistered namespaces being used in the wild, especially= at large scale=2E<br> <br> As mentioned, I'll send a longer note soon=2E Because this namespace is ap= plicable to what I think of as an "information science" problem space, I ho= pe that folks on the expert review team (and elsewhere) with expertise in i= nformation sciences will share their perspectives, as Juha Hakala and other= s did in 2019=2E<br> <br> Peter<br> <br> On 5/20/26 4:05 PM, tiepilab@<a href=3D"http://gmx=2Ede">gmx=2Ede</a>= wrote:<br> > Hi Peter,<br> > <br> > Thank you for the archived discussion=2E Always interesting to see <b= r> > people discuss research that one currently works on :)<br> > <br> > For clarity: CTS and CITE are separate namespaces and my scope is onl= y <br> > CTS=2E I think Monica Berti is currently most associated with CITE=2E= <br> > <br> > During my dissertation phase I had several discussions with Neel Smit= h <br> > and Christopher Blackwell during Gregory Cranes professorship in <br> > Leipzig and we collaborated in the sense that I implemented my work <= br> > based on their specs and feedback=2E The (escalated) result is now th= e <br> > project that is linked in my request=2E Since Crane returned to US I = did <br> > not hear any news unfortunally=2E I am not sure if they still work on= <br> > CTS but there seem to be no updates=2E<br> > <br> > It is kind of a confusing situation for me because I just learnt this= <br> > week that the namespace is not registered and this issue landed on my= <br> > desk as the service provider and implementer of the software=2E It is= a <br> > significant problem because the software is now mass-producing URNs <= br> > for a namespace that is academically defined but not IT-technically= =2E<br> > I think that is also the core of the issue=2E For the authors of the = <br> > specifications, this is more of an academic thing that was completed = <br> > with the publication of the specs while the URN registration is a <br= > > technical (IT-) problem=2E<br> > <br> > If Christopher Blackwell or Neel Smith reply, the registration should= <br> > definitely be attributed or transferred to them=2E I would honestly <= br> > prefer if the namespace is registered to them instead of me=2E<br> > Or maybe there is a mechanism to register it on behalf as long as the= y <br> > don't register it?<br> > Or any possible solution would work for me as long as it leads to a <= br> > registered CTS namespace=2E<br> > <br> > <br> > Best Regards<br> > Jochen<br> > <br> > <br> > --<br> > Gesendet mit der GMX Mail App<br> > <br> > <br> > Am 20=2E05=2E26, 16:47 schrieb Peter Saint-Andre <stpeter@stpeter= =2Eim>:<br> > <br> > Hi Jochen,<br> > <br> > Thank you for making this request=2E I'm happy to see work contin= uing on<br> > the CTS registration, which we originally discussed on this list<= br> > back in<br> > 2019 (unfortunately the discussion petered out and we never compl= eted<br> > the registration process):<br> > <br> > <a href=3D"https://mailarchive=2Eietf=2Eorg/arch/msg/urn/Rr1IBx-"= >https://mailarchive=2Eietf=2Eorg/arch/msg/urn/Rr1IBx-</a><br> > tWGcefB4aKGeyNaxCKCo/ <<a href=3D"https://mailarchive=2Eietf= =2Eorg/arch/msg/urn/">https://mailarchive=2Eietf=2Eorg/arch/msg/urn/</a><br= > > Rr1IBx-tWGcefB4aKGeyNaxCKCo/><br> > <br> > Just curious: have you collaborated with Neel Smith and Chris Bla= ckwell<br> > on this registration, or are they no longer actively working on t= he<br> > project? Coincidentally I contacted them last month about CTS/CIT= E URNs<br> > but haven't heard back yet=2E<br> > <br> > In the next few days I will take a closer look at the registratio= n<br> > request and provide feedback on this list=2E<br> > <br> > Peter<br> > <br> > On 5/20/26 4:01 AM, Jochen Tiepmar wrote:<br> > > Dear IANA<br> > ><br> > ><br> > > Please review the attached request for the registration of = the<br> > CTS URN<br> > > namespace=2E<br> > ><br> > ><br> > > Best Regards<br> > > Jochen Tiepmar<br> > ><br> > ><br> > ><br> > ><br> > ><br> > > _______________________________________________<br> > &g= t; urn mailing list -- urn@<a href=3D"http://ietf=2Eorg">ietf=2Eorg</a> <= ;<a href=3D"http://ietf=2Eorg">http://ietf=2Eorg</a>><br> > > To u= nsubscribe send an email to urn-leave@<a href=3D"http://ietf=2Eorg">ietf=2E= org</a><br> > <<a href=3D"http://ietf=2Eorg">http://ietf=2Eorg</a>><br> > <br> <br> _______________________________________________<br> urn mailing list -- ur= n@<a href=3D"http://ietf=2Eorg">ietf=2Eorg</a><br> To unsubscribe send an e= mail to urn-leave@<a href=3D"http://ietf=2Eorg">ietf=2Eorg</a><br> <br> </blockquote></div></div></body></html> --===============5274818759766784202== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KdXJuIG1haWxp bmcgbGlzdCAtLSB1cm5AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byB1 cm4tbGVhdmVAaWV0Zi5vcmcK --===============5274818759766784202==--