This document defines urn:anbs as an absolute URN form for identifying ANBS resources using a Schema.org type and a cryptographic opaque identifier.

Syntax

An ANBS URN is a URI using the urn scheme [[RFC3986]] and the URN syntax defined by [[RFC8141]].

anbs-urn = "urn:anbs:" schema-org-type "." opaque-identifier

schema-org-type = ALPHA *( ALPHA / DIGIT )
opaque-identifier = 64base64url-char
base64url-char = ALPHA / DIGIT / "-" / "_"
      

The opaque-identifier production is the fixed-length base64url presentation documented by [[CRYPTOSUITE]].

Components

URI scheme

urn

URN namespace identifier

anbs

Namespace-specific string

<SchemaOrgType>.<OpaqueIdentifier>

In RFC 8141 terms, the assigned name is "urn" ":" NID ":" NSS, where NID is anbs and NSS is <SchemaOrgType> "." <OpaqueIdentifier>. The anbs value is a URN namespace identifier, not a separate generic URI component.

<SchemaOrgType> identifies the Schema.org class shape, for example Person, Thing, or Action [[SCHEMA-ORG]] [[SCHEMA-CRDT]]. <OpaqueIdentifier> is cryptographic opaque identifier material and MUST NOT be interpreted as meaningful text.

The . separator is an RFC 3986 unreserved character and is used only as an NSS-internal separator.

Canonical Form

An ANBS URN has the form:

urn:anbs:<SchemaOrgType>.<OpaqueIdentifier>

• Producers MUST emit the lowercase prefix urn:anbs:.
• Producers MUST preserve the Schema.org type spelling and case.
• Producers MUST NOT percent-encode unreserved characters.
• Producers MUST NOT include version numbers in the URN unless the application intentionally identifies a separate Schema.org node.
• Consumers MUST compare canonical ANBS URNs by exact string equality.
• Consumers for this package MUST reject non-canonical scheme or prefix casing.

Examples

urn:anbs:Thing.abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789-_
urn:anbs:Person.abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789-_
urn:anbs:Action.abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789-_
      

Non-Goals

• No resolver protocol is defined.
• No query, resolver, or fragment semantics are defined.
• No network location is encoded.
• No authorization semantics are defined.
• No resource versioning semantics are defined.
• No JSON-LD canonicalization semantics are defined.

Security and Privacy Considerations

• The type segment is visible metadata.
• The opaque identifier MUST NOT embed personal data or semantics.
• Derived identifiers depend on the secrecy and stability of the derivation input.
• Random identifiers depend on cryptographic randomness.
• URNs identify resources; they do not prove authority, ownership, or access rights.

IANA and Namespace Registration

Formal global URN namespace registration is an IANA matter under [[RFC8141]]. This document defines the Sovereignbase project namespace syntax unless and until a corresponding namespace is formally registered.

Normative requirements are expressed with RFC 2119 keywords. A conforming ANBS URN producer or consumer implements the syntax and canonical processing requirements in this document.