Governance

A federated commons: global semantic rules, delegated industry stewardship, delegated regional stewardship, and native standards ownership.

Neutral governance. No company, country, or funder receives semantic ownership because it paid for implementation.
Transparent allocation. Identifier allocation and change history are public.
Open implementation. Implementations may be built independently from the published registry.
Immutable identifiers. An identifier is never reused for a different meaning.
Regional sovereignty. A country profile records national authority. It does not replace it.
Public change history. Every definition keeps its source, version, proposer, reviewers, and status.
No vendor lock-in. The registry does not require a vendor stack.
No country lock-in. No country is the mandatory semantic authority for every industry.
No mandatory global PKI. The commons does not require one global public-key infrastructure.
Open conformance. Conformance levels are published. A generated file is not a certificate.
Documented IPR policy. License fields exist for schema, registry, software, tests, and documentation. No license text is assumed.

International principles

National sovereignty. National standards and law remain in force.
Technical neutrality. The semantic layer does not mandate one vendor's protocol.
Consensus. Proposals move through recorded review before release.
Transparency. Mappings, versions, changes, and semantic loss stay visible.
Inclusiveness. Participation is open to the recorded participant kinds.
Interoperability. Different native standards can exchange meaning through the canonical layer.
Safety. The commons reduces ambiguity in safety-relevant information. It does not claim that a registry alone prevents harm.
Privacy. Country profiles can record privacy rules. None are invented here.
Security. Platform integrity is separate from operational device PKI.
Accessibility. Definitions are readable by people and usable by machines.
Sustainable development. The stated public purpose includes safer and more efficient infrastructure, health, energy, and the built environment.

Platform integrity. The software that serves the registry is a trust boundary.
Registry integrity. Canonical records change only through versioned snapshots.
Release signing. A release marked released must be signed and carry checksums. Draft releases stay unsigned until a key is approved.
Contributor identity. Reviewers are recorded on the definition they review.
Regional stewardship. Regional stewards review regional profiles. They do not own native standards.
Native security preservation. Native cryptography and PKI stay with the authority that defined them.

1. Industry charter. A written charter for the industry steward and the scope boundary.
2. Standards inventory. A sourced list of native standards. Titles are not invented.
3. Semantic domains. The domain split used by the industry registry.
4. Initial canonical registry. The first identifier allocation, with a rule that identifiers are never reused.
5. Native mappings. Mappings to native standards, each with a grade and a visible semantic loss.
6. Governance stewards. Named industry and regional stewards. Funding does not confer ownership.
7. Conformance model. Industry profiles that use the universal C1–C4 levels or add to them.
8. Reference implementation. A downloadable package built from the registry snapshot.