Policies and clauses: standards that apply
The 1 standard listed for policies and clauses in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.
- Nexus Standards: NS-10, NS-11, NS-14.
- Open standards: ODRL Information Model 2.2; Common Expression Language (CEL); Open Policy Agent Rego policy language; LegalRuleML Core Specification 1.0; NIST Open Security Controls Assessment Language (OSCAL); JSON Schema 2020-12.
- Data and feeds: EUR-Lex Cellar SPARQL endpoint; legislation.gov.uk API.
- Couples with: Commons and command rooms; Verification and monitoring; Conformance and crosswalk to external.
- Nexus Standards
- 3
- NS-10, NS-11, NS-14
- Open standards
- 6
- named, never copied
- Data and feeds
- 2
- listed for reference
- Couplings
- 3
- with other areas
Policies and clauses (machine-readable obligations: definition, binding, evaluation and enforcement)
Status proposed · trust, authorisation and assurance; integrated posture and executive synthesis · NXS-STD-ST-000006.
| Rule | Text |
|---|---|
NS10-R1 | Every obligation that an implementation enforces shall be a clause with a UNI; code may implement a rule, but no rule shall be enforced without a clause record that names it. |
NS10-R2 | Subjects shall be contextual UNIs; names, labels or free text shall not bind. |
NS10-R3 | The predicate shall be data in a declared language; evaluators shall record the engine and its version; two conformant evaluators shall reach the same result for the same clause and the same inputs. |
NS10-R4 | External obligations shall be cited, not copied. |
NS10-R5 | Failure effects shall be typed; refuse is the default for blocking clauses in production contexts. |
NS10-R6 | A clause or policy whose legalState is other than APPROVED may be evaluated, but its results shall be displayed as claims under review. |
NS10-R7 | Policies and clauses shall be append-only artefacts: withdrawal and supersession keep the record. |
Questions and answers.
Are these all the rules for policies and clauses?
What does a rule identifier such as NS1-R5 denote?
Around policies and clauses.
Shape the standards for policies and clauses.
Governments, regulators, standards bodies, industry, academia and communities are invited to shape the catalogue ahead of its first official release, targeted for 2030: comment on a draft, propose a change, join a working group or host a field exercise.
Status and use. The Nexus Standards are proposed standards developed through an open process under NS-13 and published for voluntary use; they do not constitute certification, accreditation or regulatory approval, and adoption remains a decision of the Global Standards Council and, in each country, of its National Standards Council. A UNI (Unique Nexus Identifier) identifies an artefact; it does not certify it. Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.
Licences: CC BY 4.0 for standards text, registries, schemas and data; Apache-2.0 for reference code. External standards are cited by name, number and link under their own licences. Third-party data, libraries and fonts keep their own licences: see Third-party notices.