[urn] Informal URN Namespace Registration Request for Trivore Corp.

Dear IANA URN Namespace Registration Team / mailing list,

(As requested by the registration team, I'll mail this to the list.)

I would like to request the registration of a new Informal URN Namespace Identifier (NID) in accordance with RFC 8141.


URN Namespace Registration for Trivore Corp.


Namespace Identifier (NID):
urn-#


Registration information:
Version: 1
Revision information: 1
Date: 2026-01-01


Declared registrant of the namespace:
Organization: Trivore Corp.
Contact Role: URN Administrator, [email protected]
Contact Person: Kari Mattsson (URN Administrator)
Address: Helsinginkatu 15, 20500 Turku, Finland
Website: https://www.trivore.com/


Purpose:
This namespace is intended to provide persistent, globally unique, location-independent identifiers for resources defined and managed by the declared registrant. The identifiers are not intended to resolve to network locations.


Syntax:
URNs in this namespace follow the syntax:
urn:urn-#:<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 “.”.


Namespace semantics:
Each URN identifies exactly one logical resource defined by the registrant. The identifiers are opaque and do not embed personal data.


Assignment:
URNs are assigned exclusively by the declared registrant. Each identifier is guaranteed to be unique within the namespace. Reassignment is not permitted.


Persistence:
URNs in this namespace are intended to be persistent. Once assigned, an identifier will not be reused.


Resolution:
No resolution mechanism is defined for this namespace. Any resolution services, if provided, are outside the scope of this registration.


Lexical equivalence:
Lexical equivalence follows the rules defined in RFC 8141.


Security and privacy considerations:
The namespace does not include secrets, authentication material, or personally identifiable information (PII). Identifiers must not be used as access control mechanisms. The namespace does not encode personal data, and correlation risks are minimized by avoiding meaningful identifiers.


Interoperability:
No specific mechanisms are defined to support interoperability with other systems or namespaces. The identifiers are primarily intended for internal use and management by the registrant.


Documentation:
No external documentation is currently provided. This registration document is the primary documentation for the "trivore" namespace.


IANA considerations:
This document requests the registration of the Informal URN Namespace Identifier “trivore”.


Please let me know if any additional information or clarification is required.

Kind regards,
Kari Mattsson
URN Administrator
Trivore Corp.
[email protected]

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