[urn] Re: Informal URN Namespace Registration Request for Tr ivore 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

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]