[urn] Re: Informal URN Namespace Registration Request for Tr ivore Corp.

Thanks, Kari. The updated registration request looks good to me.

Peter

On 1/11/26 9:39 AM, Kari Mattsson (Trivore) wrote:
> Hello Date (and others)!
> 
> https://id.trivore.com/apidoc/oidc <https://id.trivore.com/apidoc/ 
> oidc> was geo-blocked, not any more. That IdP instance is our own, and 
> mostly used within Finland only. The service contains PII like all IdPs 
> do. Thus geo-blocking.
> 
> Initially the intention was to have documentation always online in the 
> product, for OIDC IdP, the path would be /apidoc/oidc. It is however a 
> good idea to have more permanent single address for documentation of the 
> URN. I amended the application to contain that address <https:// 
> doc.trivoreid.com/>. The actual page is not yet there. When a more exact 
> permanent address is created, the documentation section of the 
> application shall be amended.
> 
> On exact URNs for scopes and claims, yes your correction is the right 
> one, and it is important on the web page to document this clearly:
>      urn:trivore:id:scope:<scope-name>
>      urn:trivore:id:claim:<claim-name>
> As the need for other kind of information arises, documentation shall be 
> amended again, and the web page shall be updated.
> 
> Case-sensitivity catch was a good one. It was not meant to be like that, 
> as it is way too common place to have human typo errors. This I reworded 
> it for case-insensitivity. And I hope I got it right.
> 
> Another good catch was number of sections with ":" as separator. As 
> future needs are currently unknown, it is not wise to limit to only 3 
> colons. Hierarchy requires more in real life.
> 
> Thus, I also amended the Syntax section. I hope I got that right, too.
> I defined after consultation max length to be 512 characters for the URN 
> just to be on the safe side on complex use cases.
> 
> Attached are (text and PDF) new revisions.
> 
> Thanks all for your patience with us 🙂
> 
> My best, Kari
> 
> 
> 
> ------------------------------------------------------------------------
> *From:* Dale R. Worley <[email protected]>
> *Sent:* 08 January 2026 22:55
> *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 
> Trivore Corp.
> "Kari Mattsson (Trivore)" <[email protected]> writes:
>  > Truth is, we'd like to have a formal namespace "trivore" registered.
> 
> That seems like a good choice to me.
> 
>  > OIDC has concept of Claims and Scopes. And we have so many of those
>  > built in, and users may also create their own.
>  > Current list is not very beautiful: https://id.trivore.com/apidoc/ 
> oidc <https://id.trivore.com/apidoc/oidc>
> 
> That URL gave me 403.
> 
> But if the intention is for the list of trivore URNs to be public at
> that URL, why not mention that in the Documentation section of the
> registration?
> 
> Indeed, why not put the discussion you provided into the registration?
> 
>  > We are changing those to be URN formatted, thus this application.
>  > urn:trivore:id:scope:
>  > urn:trivore:id:claim:
>  > etc. — I hope you get the idea. Those will be public and publicly 
> documented.
> 
> I assume you mean
> 
>      urn:trivore:id:scope:<scope-name>
>      urn:trivore:id:claim:<claim-name>
> 
> But those don't match the declared syntax; the syntax requires exactly 3
> colons in the URN.
> 
>  > Syntax:
>  > URNs in this namespace follow the syntax:
>  > urn:trivore:<NSS>
>  >
>  > The Namespace Specific String (NSS) is defined as:
>  > <NSS> = <resource-type> ":" <resource-id>
>  > Where <resource-type> and <resource-id> consist of ASCII letters, 
> digits, and the characters “-”, “_”, and “.”.
>  >
>  > Maximum length for resource-id is 256 characters.
> 
> However, you do not state a maximum length for resource-type, so URNs
> have unlimited length.  If you expect the URNs to always be considerably
> less than 256 characters, it would probably be better to specify that
> the maximum length for trivore URNs is 256 characters.
> 
>  > Lexical equivalence:
>  > Lexical equivalence follows the rules defined in RFC 8141.
> 
> Which means the default applies; the URNs are case-sensitive.
> 
> Dale

_______________________________________________
urn mailing list -- [email protected]
To unsubscribe send an email to [email protected]