[urn] Re: Informal URN Namespace Registration Request for Tr ivore Corp.
"Kari Mattsson (Trivore)" <[email protected]> Fri, 1 May 2026 12:26:07 +0000
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <MI3PR06MB10692A0A7EEE3DEBE40538D4688322@MI3PR06MB10692.eurprd06.prod.outlook.com> |
--===============3573373260263143042== Content-Language: en-GB Content-Type: multipart/alternative; boundary="_000_MI3PR06MB10692A0A7EEE3DEBE40538D4688322MI3PR06MB10692eu_" --_000_MI3PR06MB10692A0A7EEE3DEBE40538D4688322MI3PR06MB10692eu_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear all! I understod this application was "sort of" approved back in January. Maybe = it was not? Is there something else I need to do to get us on the formal na= mespace list at <https://www.iana.org/assignments/urn-namespaces/urn-namesp= aces.xhtml>? I'm asking, because I noticed list was updated about 2 weeks ago. Thank you= ! my best, Kari Mattsson ________________________________ From: Dale R. Worley <[email protected]> Sent: 26 January 2026 04:47 To: Kari Mattsson (Trivore) <[email protected]> Cc: [email protected] <[email protected]>; [email protected] <[email protected]= >; URN-admin <[email protected]> Subject: Re: [urn] Re: Informal URN Namespace Registration Request for Triv= ore Corp. "Kari Mattsson (Trivore)" <[email protected]> writes: > What you pointed out below is exactly our current state with Trivore > ID product. I am very frank with you, it is currently a mess. I > personally do not like the current state. We have scopes and claims > with https prefix, and we have plain strings. Those current url > scopes and claims are already internally deprecated, and will be > changed to urn based on this registration "urn:trviore". This > registration is part of that. > > We are modifying all those to what is according to new standard, > showing up those urn scopes and claims in the documentation in the > future releases. Trivore ID is a 10 year old product already and being > actively use by millions of people. Refactoring is currently being > done. > > I hope this clarified the current state. OK, yes, with the understanding that Trivore intends to update its scope and claim names to conform to the urn:trivore syntax, the registration looks good to me. We have approved a lot of registrations whose syntaxes were considerably broader than the registrants intended to utilize in the foreseeable future. But as long as the registrant is aware of good URN usage, the IETF does not need to supervise the details of the registrant's usage. Dale --_000_MI3PR06MB10692A0A7EEE3DEBE40538D4688322MI3PR06MB10692eu_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo= ttom:0;} </style> </head> <body dir=3D"ltr"> <div class=3D"elementToProof" style=3D"font-family: Calibri, Helvetica, san= s-serif; font-size: 11pt; color: rgb(0, 0, 0);"> Dear all!</div> <div class=3D"elementToProof" style=3D"font-family: Calibri, Helvetica, san= s-serif; font-size: 11pt; color: rgb(0, 0, 0);"> I understod this application was "sort of" approved back in Janua= ry. Maybe it was not? Is there something else I need to do to get us on the= formal namespace list at <<a href=3D"https://www.iana.org/assignments/u= rn-namespaces/urn-namespaces.xhtml" id=3D"OWA74d191ee-b42c-7ec5-65ac-56477d= da0f59" class=3D"OWAAutoLink">https://www.iana.org/assignments/urn-namespac= es/urn-namespaces.xhtml</a>>?</div> <div class=3D"elementToProof" style=3D"font-family: Calibri, Helvetica, san= s-serif; font-size: 11pt; color: rgb(0, 0, 0);"> I'm asking, because I noticed list was updated about 2 weeks ago. Thank you= !</div> <div class=3D"elementToProof" style=3D"font-family: Calibri, Helvetica, san= s-serif; font-size: 11pt; color: rgb(0, 0, 0);"> my best, Kari Mattsson</div> <div class=3D"elementToProof" style=3D"font-family: Calibri, Helvetica, san= s-serif; font-size: 11pt; color: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Calibri, Helvetica, san= s-serif; font-size: 11pt; color: rgb(0, 0, 0);"> <br> </div> <div id=3D"appendonsend"></div> <hr style=3D"display:inline-block;width:98%" tabindex=3D"-1"> <div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st= yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> Dale R. Worley <wo= [email protected]><br> <b>Sent:</b> 26 January 2026 04:47<br> <b>To:</b> Kari Mattsson (Trivore) <[email protected]><br> <b>Cc:</b> [email protected] <[email protected]>; [email protected] = <[email protected]>; URN-admin <[email protected]><br> <b>Subject:</b> Re: [urn] Re: Informal URN Namespace Registration Request f= or Trivore Corp.</font> <div> </div> </div> <div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt;= "> <div class=3D"PlainText">"Kari Mattsson (Trivore)" <kari.matts= [email protected]> writes:<br> > What you pointed out below is exactly our current state with Trivore<b= r> > ID product. I am very frank with you, it is currently a mess. I<= br> > personally do not like the current state. We have scopes and cla= ims<br> > with https prefix, and we have plain strings. Those current url<= br> > scopes and claims are already internally deprecated, and will be<br> > changed to urn based on this registration "urn:trviore".&nbs= p; This<br> > registration is part of that.<br> ><br> > We are modifying all those to what is according to new standard,<br> > showing up those urn scopes and claims in the documentation in the<br> > future releases. Trivore ID is a 10 year old product already and being= <br> > actively use by millions of people. Refactoring is currently bei= ng<br> > done.<br> ><br> > I hope this clarified the current state.<br> <br> OK, yes, with the understanding that Trivore intends to update its scope<br= > and claim names to conform to the urn:trivore syntax, the registration<br> looks good to me. We have approved a lot of registrations whose synta= xes<br> were considerably broader than the registrants intended to utilize in the<b= r> foreseeable future. But as long as the registrant is aware of good UR= N<br> usage, the IETF does not need to supervise the details of the<br> registrant's usage.<br> <br> Dale<br> </div> </span></font></div> </body> </html> --_000_MI3PR06MB10692A0A7EEE3DEBE40538D4688322MI3PR06MB10692eu_-- --===============3573373260263143042== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KdXJuIG1haWxp bmcgbGlzdCAtLSB1cm5AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byB1 cm4tbGVhdmVAaWV0Zi5vcmcK --===============3573373260263143042==--