[urn] Re: Request for Registration of CTS namespace
[email protected] Fri, 3 Jul 2026 06:20:38 +0000
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <trinity-c4b97526-1df1-4f6b-bcc5-84db8371178e-1783059637955@trinity-msg-rest-gmx-gmx-live-86c95d6b76-z4mb8> |
--===============0273684761026801797== Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <html><body><div class=3D"mail_android_quote" style=3D"line-height: 1">Dear= IANA,</div><div class=3D"mail_android_quote" style=3D"line-height: 1"><br>= </div><div class=3D"mail_android_quote" style=3D"line-height: 1">I want to = bring Uwe Kretschmer into the discussion, the <span style=3D"color: rg= b(0, 0, 0); font-family: SourceSans3, sans-serif; font-size: 18px; backgrou= nd-color: rgb(242, 247, 237);">Digital Humanities Officer / data referent a= t the SAW=2E He coordinates the DFG proposal during which the registration = is planned=2E</span></div><div class=3D"mail_android_quote" style=3D"line-h= eight: 1"><font color=3D"#000000" face=3D"SourceSans3, sans-serif"><span st= yle=3D"font-size: 18px;"><br></span></font></div><div class=3D"mail_android= _quote" style=3D"line-height: 1"><font color=3D"#000000" face=3D"SourceSans= 3, sans-serif"><span style=3D"font-size: 18px;">I think the main issues (in= stitutional backing, square brackets) are now adressed, hope I did not miss= something (?)</span></font></div><div class=3D"mail_android_quote" style= =3D"line-height: 1"><font color=3D"#000000" face=3D"SourceSans3, sans-serif= "><span style=3D"font-size: 18px;"><br></span></font></div><div class=3D"ma= il_android_quote" style=3D"line-height: 1"><font color=3D"#000000" face=3D"= SourceSans3, sans-serif"><span style=3D"font-size: 18px;">Best Regards</spa= n></font></div><div class=3D"mail_android_quote" style=3D"line-height: 1"><= font color=3D"#000000" face=3D"SourceSans3, sans-serif"><span style=3D"font= -size: 18px;">Jochen</span></font></div><div class=3D"mail_android_quote" s= tyle=3D"line-height: 1"><font color=3D"#000000" face=3D"SourceSans3, sans-s= erif"><span style=3D"font-size: 18px;"><br></span></font></div><div class= =3D"mail_android_quote" style=3D"line-height: 1"><meta name=3D"viewport" co= ntent=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 18=2E06=2E26, 10:50 schrieb "Lars G= =2E Svensson" <lars=2Esvensson=3D<a href=3D"http://40web=2Ede">40web=2Ed= e</a>@<a href=3D"http://dmarc=2Eietf=2Eorg">dmarc=2Eietf=2Eorg</a>>:<blo= ckquote class=3D"gmail_quote" style=3D"margin: 0=2E8ex 0pt 0pt 0=2E8ex; bor= der-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> Dear Jochen, all,<br> <br> I, too, find Dale's idea having a registry hosted by IANA attractive=2E<br= > <br> > Do you think IANA could provide a repo that maps data namespaces to s= erver URLs?<br> <br> I think that's perfectly possible=2E We could use a format along the lines= of (taking data from <<a href=3D"https://urncts=2Eeu/">https://urncts= =2Eeu/</a>>):<br> <br> <br> <namespace> Registrant Registrant contact data Serve= r URL<br> --------------------------------------------------------------------------= ----------------------------------------------------------------<br> ancJew= Lit <Whoever=2E=2E=2E> ancjewlit@<a href=3D"http://example=2Ecom">exa= mple=2Ecom</a><a href=3D"https://example=2Ecom/ancJewLit">https://example= =2Ecom/ancJewLit</a><br> dhd Verband Digital Humanities im dhd-urn-registry= @<a href=3D"http://example=2Eorg">example=2Eorg</a><a href=3D"https://examp= le=2Eorg/dhd">https://example=2Eorg/dhd</a><br> deutschsprachigen Raum e=2EV=2E <br> =2E=2E=2E<br> <br> That registry would - of course - be only text or html, but if done in xht= ml it should be easy to build an automated process that at intervals downlo= ads the registry and builds an application that resolves namespaces to endp= oint urls=2E<br> <br> > I don't think there is anything we can do about people creating CTS U= RNs<br> > without proper registration, all we can do is create clear rules that= <br> > allow us to say that they are nonconforming=2E<br> <br> Yes, there are many cases of urn-squatting out there, urn:li comes to mind= =2E=2E=2E<br> <br> >> And finally I don't see, how a central registry could prevent<br> >> "namespace brokers" from registering and selling namespaces to<br= > >> academic institutions=2E In a decentralised registry, this busine= ss<br> >> model cannot appear=2E<br> <br> > I think the situation is similar to domain names, in that there are m= any<br> > alternative forms of the name of an institution or project, and it is= <br> > unlikely that brokers will have speculatively registered all of them= =2E<br> <br> If we make it a prerequisite for registration that registrants can only be= academic institutions or organisations working on their behalf, that dange= r could be circumvented=2E We would then, of course, need an expert committ= ee that reviews new applications, similar to the urn review group!<br> <br> Best,<br> <br> Lars<br> <br> <br> -----Urspr=C3=BCngliche Nachricht-----<br> Von: tiepilab=3D<a href=3D"http= ://40gmx=2Ede">40gmx=2Ede</a>@<a href=3D"http://dmarc=2Eietf=2Eorg">dmarc= =2Eietf=2Eorg</a> [mailto:tiepilab=3D<a href=3D"http://40gmx=2Ede">40gmx=2E= de</a>@<a href=3D"http://dmarc=2Eietf=2Eorg">dmarc=2Eietf=2Eorg</a>]<br> Gesendet: Montag, 15=2E Juni 2026 08:16<br> An: Dale R=2E Worley <worle= y@<a href=3D"http://ariadne=2Ecom">ariadne=2Ecom</a>><br> Cc: urn@<a hre= f=3D"http://ietf=2Eorg">ietf=2Eorg</a><br> Betreff: [urn] Re: Request for Registration of CTS namespace<br> <br> That is heloful to know as it sets a clear goal=2E<br> <br> Do you think IANA could provide a repo that maps data namespaces to server= URLs?<br> <br> I use such a (private) repo to direct the programming APIs to the servers= =2E The idea was to host that repo at the academy instead=2E<br> <br> If IANA registers data namespaces, it might be a good idea to have the cor= e repo located at IANA(?) and allow users to clone that(?)<br> <br> (Technically it is a trivial key-value mapping)<br> <br> <br> <br> Am 13=2E06=2E26, 04:46 schrieb "Dale R=2E Worley" <worley@<a href= =3D"http://ariadne=2Ecom">ariadne=2Ecom</a> <<a href=3D"http://ariadne= =2Ecom">http://ariadne=2Ecom</a>> >:<br> <br> tiepilab=3D<a href=3D"http://40gmx=2Ede">40gmx=2Ede</a> <<a href= =3D"http://40gmx=2Ede">http://40gmx=2Ede</a>> @<a href=3D"http://dmarc= =2Eietf=2Eorg">dmarc=2Eietf=2Eorg</a> <<a href=3D"http://dmarc=2Eietf=2E= org">http://dmarc=2Eietf=2Eorg</a>> writes:<br> > I don't have a a full list=2E The namespaces that are connected to m= y<br> > project are listed at <a href=3D"https://urncts=2Eeu">https://urncts= =2Eeu</a>=2E<br> <br> That page lists 19 data namespaces, which shows that there is<br> significant user support for CTS=2E<br> <br> > The registration process will be an interesting topic to discuss=2E = I<br> > understand your comment in a way that leads to a central authority= =2E<br> > My abstract idea is an open registration, hosted *somewhere* that<br= > > works purely on FCFS without an authority that decides who may or ma= y<br> > not register a new namespace as long as it does not collide=2E With = the<br> > option to choose your registry similiar to how you can choose your D= NS<br> > provider=2E Choosing your registry would also limit the harm that co= uld<br> > arise from misuse=2E<br> <br> We definitely need a registration system in order to ensure URN<br> uniqueness, which is a requirement of URN registration -- organizations<b= r> need to know what possible URNs they are allowed to create=2E If we get<b= r> an IANA registry established under "FCFS" policy, then there is no<br> restriction regarding who may register which new data namespace=2E Also,<= br> registration with IANA would implicitly put each data namespace owner on<= br> notice that they had to adhere to the registered CTS syntax=2E<br> <br> And I do see it as a problem that we need to ensure the users of CTS<br> conform to the proper syntax=2E<br> <br> It would be straightforward to establish an IANA registry=2E It would<br> take a great deal of work to establish a system with multiple<br> registrars=2E And it might not be possible to recruit multiple<br> registrars, whereas the IESG can direct IANA to operate a registry=2E<br> <br> In regard to trusting IANA to carry out its duties correctly =2E=2E=2E If= IANA<br> doesn't function well, the Internet has many more problems than just<br> CTS=2E<br> <br> Although if you see a way to do decentralized allocation of data<br> namespaces, I would like to see the details=2E<br> <br> > Another issue with a central registry might come from the domain=2E = It<br> > seems that the need to register namespaces is not very strong in the= <br> > humanities :) =2E The problem with unregistered URNs would escalate<= br> > further if new data sets appear without registration=2E A decentrali= sed<br> > registry would eliminate this problem because then it is the users<b= r> > responsibility=2E<br> <br> I don't think there is anything we can do about people creating CTS URNs<= br> without proper registration, all we can do is create clear rules that<br> allow us to say that they are nonconforming=2E<br> <br> > And finally I don't see, how a central registry could prevent<br> > "namespace brokers" from registering and selling namespaces to<br> > academic institutions=2E In a decentralised registry, this business<= br> > model cannot appear=2E<br> <br> I think the situation is similar to domain names, in that there are many<= br> alternative forms of the name of an institution or project, and it is<br> unlikely that brokers will have speculatively registered all of them=2E<b= r> <br> Dale<br> <br> <br> <br> </blockquote></div></div></body></html> --===============0273684761026801797== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KdXJuIG1haWxp bmcgbGlzdCAtLSB1cm5AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byB1 cm4tbGVhdmVAaWV0Zi5vcmcK --===============0273684761026801797==--