[urn] Re: Informal URN Namespace Registration Request for Tr ivore Corp.
"Kari Mattsson (Trivore)" <[email protected]> Sun, 25 Jan 2026 18:50:15 +0000
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <PAWPR06MB90106C4EEA28AF81D7B4D1368892A@PAWPR06MB9010.eurprd06.prod.outlook.com> |
Thank you Lars, Dale, and others! 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. my best, Kari ________________________________ From: Lars G. Svensson <[email protected]> Sent: 23 January 2026 14:02 To: Kari Mattsson (Trivore) <[email protected]> Cc: [email protected] <[email protected]>; URN-admin <[email protected]> Subject: AW: [urn] Re: Informal URN Namespace Registration Request for Trivore Corp. Dear Kari, Apologies for the delay with our review. Apart from the documentation issue addressed by Dale (below), we approve of the registration request. Best, Stephanie and Lars -----Ursprüngliche Nachricht----- Von: Dale R. Worley [mailto:[email protected]] Gesendet: Mittwoch, 14. Januar 2026 05:14 An: Kari Mattsson (Trivore) <[email protected]> Cc: [email protected]; [email protected]; [email protected] Betreff: [urn] Re: Informal URN Namespace Registration Request for Trivore Corp. The new registration says: The Namespace Specific String (NSS) is defined as a hierarchical sequence of segments: <NSS> = <segment> 1*(":" <segment>) Where: <segment> consists of ASCII letters, digits, and the characters “-”, “_”, and “.”, and the NSS must contain at least one colon (implying at least two segments). > 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> Looking at https://id.trivore.com/apidoc/oidc, it doesn't seem on first reading to document the URN formats clearly; it gives a list of "Supported scopes" and "Supported claims" but does not specify how these are used to form URNs. Also the following scopes and claims are listed that do not conform to the specified syntax, in that they contain "/". They also contain ":" in a way which is correct according to the syntax but seems to not have the intended semantics: according to the syntax specification the ":" separates segments (the first one being "http", the second one starts with "//") rather than being an internal part of the scope/claim name (which is suggested by the web page). Scopes https://oneportal.trivore.com/scope/accesscontrol https://oneportal.trivore.com/scope/accesscontrol.readonly https://oneportal.trivore.com/scope/accessrights https://oneportal.trivore.com/scope/accessrights.readonly https://oneportal.trivore.com/scope/address.update https://oneportal.trivore.com/scope/authorisation.grant.rights https://oneportal.trivore.com/scope/authorisation.grant.rights.readonly https://oneportal.trivore.com/scope/authorisations https://oneportal.trivore.com/scope/authorisations.readonly https://oneportal.trivore.com/scope/authorisations.sources https://oneportal.trivore.com/scope/authorisations.sources.readonly https://oneportal.trivore.com/scope/authorisations.types https://oneportal.trivore.com/scope/authorisations.types.readonly https://oneportal.trivore.com/scope/commerce.product.suppliers.read https://oneportal.trivore.com/scope/commerce.product.suppliers.write https://oneportal.trivore.com/scope/commerce.sales.products.query https://oneportal.trivore.com/scope/commerce.wallet.read https://oneportal.trivore.com/scope/commerce.wallet.transfer https://oneportal.trivore.com/scope/commerce.wallet.write https://oneportal.trivore.com/scope/consent https://oneportal.trivore.com/scope/consent.readonly https://oneportal.trivore.com/scope/contract.read https://oneportal.trivore.com/scope/contract.sign https://oneportal.trivore.com/scope/contract.terminate https://oneportal.trivore.com/scope/contract.write https://oneportal.trivore.com/scope/datastorage https://oneportal.trivore.com/scope/datastorage.admin https://oneportal.trivore.com/scope/datastorage.readonly https://oneportal.trivore.com/scope/email.update https://oneportal.trivore.com/scope/email.verify https://oneportal.trivore.com/scope/filestorage https://oneportal.trivore.com/scope/filestorage.readonly https://oneportal.trivore.com/scope/groups https://oneportal.trivore.com/scope/groups.readonly https://oneportal.trivore.com/scope/legalinfo.readonly https://oneportal.trivore.com/scope/mfa https://oneportal.trivore.com/scope/mgmt.api.client https://oneportal.trivore.com/scope/mgmt.api.client.readonly https://oneportal.trivore.com/scope/mydata.download https://oneportal.trivore.com/scope/mydata.request https://oneportal.trivore.com/scope/namespace https://oneportal.trivore.com/scope/namespace.readonly https://oneportal.trivore.com/scope/other.app.access https://oneportal.trivore.com/scope/other.app.access.readonly https://oneportal.trivore.com/scope/password https://oneportal.trivore.com/scope/paycards https://oneportal.trivore.com/scope/paycards.number https://oneportal.trivore.com/scope/paycards.number.readonly https://oneportal.trivore.com/scope/paycards.readonly https://oneportal.trivore.com/scope/phone.update https://oneportal.trivore.com/scope/products.catalog.read https://oneportal.trivore.com/scope/products.catalog.write https://oneportal.trivore.com/scope/products.pricingplan.read https://oneportal.trivore.com/scope/products.pricingplan.write https://oneportal.trivore.com/scope/products.product.read https://oneportal.trivore.com/scope/products.product.write https://oneportal.trivore.com/scope/profile https://oneportal.trivore.com/scope/profile.update https://oneportal.trivore.com/scope/sms.verify https://oneportal.trivore.com/scope/sso.consume https://oneportal.trivore.com/scope/studentinfo.readonly https://oneportal.trivore.com/scope/user.custom.fields https://oneportal.trivore.com/scope/user.custom.fields.readonly https://oneportal.trivore.com/scope/user.invite https://oneportal.trivore.com/scope/user.tokens https://oneportal.trivore.com/scope/user.tokens.readonly https://oneportal.trivore.com/scope/users https://oneportal.trivore.com/scope/users.readonly Claims https://oneportal.trivore.com/claims/active_external_permissions https://oneportal.trivore.com/claims/consents https://oneportal.trivore.com/claims/custom_fields https://oneportal.trivore.com/claims/domicile_classes https://oneportal.trivore.com/claims/dynamic_custom_fields https://oneportal.trivore.com/claims/group_ids https://oneportal.trivore.com/claims/groupmembership https://oneportal.trivore.com/claims/groups https://oneportal.trivore.com/claims/legal_locality https://oneportal.trivore.com/claims/legal_names https://oneportal.trivore.com/claims/locality https://oneportal.trivore.com/claims/minor https://oneportal.trivore.com/claims/namespace https://oneportal.trivore.com/claims/personal_id_code https://oneportal.trivore.com/claims/screen_name https://oneportal.trivore.com/claims/strong_identification https://oneportal.trivore.com/claims/student https://oneportal.trivore.com/claims/tags https://oneportal.trivore.com/claims/user_namespace Dale _______________________________________________ urn mailing list -- [email protected] To unsubscribe send an email to [email protected]