Qualities of Captured Registrar Data
Purpose and Scope of this document
This document describes the types of data required from Authoritative Registrars to be recorded in the Global Registrar Information Directory (GRID). It establishes the baseline for "Global Trust" by ensuring that every entry in the GRID is backed by a clear legal mandate and a verifiable administrative origin.
Data Quality Principles
For the GRID to function as a reliable "Trust Root" for global supply chains, registrar data must adhere to three core principles:
- Authoritative Origin: Data must be sourced directly from the entity with the mandate to maintain the register for a Nation State.
- Legal Transparency: The legal basis for the registrar's Nation State authority must be publicly accessible.
- Maturity Alignment: Data requirements are tiered to allow Nation State eligible registrars of all digital maturity levels to participate.
Data Schema for the GRID
The following table defines the mandatory and optional metadata required for a Registrar to be listed in the GRID.
| Field | Type | Format | Maturity Level | Description & Comments |
|---|---|---|---|---|
| Country Code | String | ISO 3166-1 alpha-3 | Baseline | The ISO 3166/MA code for the sovereign territory of the Registrar (e.g., AUS). |
| Registrar Name | String | Free (Latin script) | Baseline | The official name of the organization (e.g., ASIC). |
| Register Name | String | Free (Latin script) | Baseline | The specific register being indexed (e.g., National Business Register). |
| Register Type | Enumeration | UN/CEFACT Code | Baseline | Classification of entities recorded (e.g., Organization, Vessel, Land, Professional). |
| Legal Basis | String | URI | Baseline | Mandatory. A persistent link to the legislation or decree establishing the registrar's authority. |
| Authoritative Body | String | URI | Baseline | Link to the parent Ministry or oversight body that guarantees the registrar’s legitimacy. |
| Register ID | string | URI | Baseline | A globally unique ID as a URI that represents this register (eg abr.business.gov.au) |
| Registered ID Pattern | string | URI | Baseline | A URI template that is used to construct a globally unique and (where possible) resolvable identifier for a registered member of the register (eg given a registered ID 50110219460 and a template abr.business.gov.au/{id} then the globally unique ID for the registered entity is abr.business.gov.au/50110219460). THis may or may not be the same as the query and resolver endpoints below |
| Query Endpoint | string | URI | Advanced | A URI template for a human readable query about the registered entry (eg https://abr.business.gov.au/ABN/View?abn={id} yielding https://abr.business.gov.au/ABN/View?abn=50110219460 |
| Resolver Endpoint | String | URI | Advanced | Identity resolver service end point per UN identity resolver standard this may or may not be the same as the query endpoint |
| DID / Public Key | String | Decentralized ID | Advanced | Required for DIA Issuance. The cryptographic identifier used to verify the Registrar’s signature on Digital Identity Anchors. |
| GRID Reference | String | URI | Advanced | The unique, persistent GTR-issued pointer for this specific Registrar entry. |
The Trust Attribution Framework
When a Registrar moves beyond a basic GRID listing to issuing Digital Identity Anchors (DIA), they must categorize any supplementary identifiers (e.g., GS1, LEI) within the DIA using the following quality tiers. This ensures that the Registrar's liability is strictly limited to their authoritative mandate.
1. Certified (Authoritative)
Data that originates directly from the Registrar's own system of record.
- Standard: High-assurance, backed by national legislation.
- Example: National Business Registration Number.
2. Verified (Recognized)
External identifiers that the Registrar has cross-referenced against their internal records.
- Standard: Medium-high assurance; the Registrar confirms the link between the entity and the third-party ID.
- Example: A Registrar confirming that a specific LEI belongs to a registered company.
3. Asserted (Claimed)
Data provided by the legal entity which the Registrar has not vetted.
- Standard: Low-assurance; conveyed "as-is" for trade convenience.
- Liability: The Registrar assumes zero liability for the accuracy of these fields.
- Example: A company-provided GS1 GLN or ISO standard certification.
Next Steps for Registrars
Registrars joining the GRID should initially focus on the Baseline data quality fields to ensure global discovery. Advanced registrars intending to issue DIAs should begin preparing their DID/Public Key infrastructure and defining their internal policy for Verified vs. Asserted identifier recognition.