The register as a governed object: its identity and constitution, the boundary of what it covers, and the policy controlling who may cause entries to exist.
register-identity-and-constitution
Register identity and constituting act
A register is a named, individually identified book of entries constituted by an instrument that names an accountable keeper and, where public, derives its powers from a referenced mandate. ISO/TC 211 separates the register owner from the register manager and the control body; UNIDROIT separates the Supervisory Authority from the Registrar; INSPIRE shows the operator can change while item URIs persist. The constitution is therefore distinct from both the operator and the storage.
Questions
- Which instrument constitutes this register and what does it authorise the register to contain?authority
Expected answer
- Reference to the constituting instrument or mandate record (WM-POL-013)
- Instrument type: statute, regulation, standard, charter, contract or internal policy
- Date of entry into force of the constitution
- What identifier distinguishes this register from every other register, including from the registry that operates it?identity
Expected answer
- Register identifier drawn from a governed scheme (binding to WM-XCT-011)
- Register short name and official title
- Operating registry identifier hosting the register
- Which distinct parties hold register ownership, register management and control-body review for this register?ownership
Expected answer
- Owner party reference (resolved via WM-XCT-001)
- Register manager / registrar party reference
- Control body or designated expert reference where review is delegated
- What happens to register identity and item references if the operating organisation changes?lifecycle
Expected answer
- Persistence commitment for register and item references
- Successor-operator designation rule
- Continuity conditions required of a manager (legal entity, funding, minimum commitment period)
Artifacts
- Register constitution recordThe durable statement of what this register is: identity, constituting instrument reference, role bindings, operating language and persistence commitment.
register-field-of-application
Field of application and completeness claim
The register's declared subject-matter boundary, its territorial or jurisdictional reach, and how strong a completeness claim it makes. A register that claims to hold every instance of its subject supports negative inference ('not registered means not existing'); one that does not must say so, because search results are otherwise misread.
Questions
- What classes of item does this register admit, and what closely similar items does it explicitly exclude?classification
Expected answer
- Admitted subject-matter description
- Explicit exclusion list with the register that holds each excluded class
- Derivation of the boundary from the constituting mandate
- Over which jurisdiction, territory or namespace does this register claim authority?spatial
Expected answer
- Jurisdiction or territory code
- Namespace or value-space covered where the register is non-geographic
- Overlap statement with neighbouring registers of the same kind
- Does absence of an entry permit a negative inference, and under what conditions?constraint
Expected answer
- Completeness claim level: exhaustive, compulsory-with-exceptions, voluntary or partial
- Known coverage gaps and legacy backlog statement
- Wording that must accompany a nil search result
- What events compel registration, and what remains voluntary?requirement
Expected answer
- Compulsory registration triggers
- Voluntary registration eligibility
- Consequence of non-registration (unenforceability, non-opposability, penalty or none)
registration-policy-and-submission-rights
Registration policy and submission rights
The rule fixing who may cause an entry to exist and how much review precedes it. RFC 8126 sets out an explicit strictness ladder from Private Use through First Come First Served and Expert Review to Standards Action, advises choosing the least strict policy that suits the register, and requires a named change controller; UNCITRAL by contrast permits registration by any authorised registrant without document lodgement.
Questions
- Which registration policy governs each range or class of this register, and why is that strictness chosen?decision
Expected answer
- Policy code per item class or value range
- Justification for any policy stricter than the minimum needed
- Reviewer designation where expert review applies
- Who is entitled to submit a registration request, and must the submitter be the affected subject?authority
Expected answer
- Eligible submitter classes
- Whether third-party submission on behalf of a subject is permitted
- Authorization requirement linking submitter to subject
- Who controls later changes to an individual registered value once it exists?ownership
Expected answer
- Change controller value per entry
- Escalation path when the change controller is unreachable or defunct
- Whether change control differs from original submitter
- May an entry be registered provisionally and later converted to permanent status?state
Expected answer
- Provisional registration permitted flag
- Conversion criteria to permanent status
- Maximum provisional duration