Skip to content
RUMLRUML

Open Format for Digital Law

1.5 Relationship to Other Standards

1.5 Relationship to Other Standards

This section names the standards that RUML uses or refers to. It makes no comparative claims about coverage or suitability.

Standards Used Directly by RUML

StandardUse in RUML
RFC 8259 — JSON Data Interchange FormatEvery RUML file is a valid JSON document.
JSON Schema draft 2020-12 — JSON SchemaThe format of the schemas shipped with this specification.
JSONata 2.2.0Expression language of ruml:query, ruml:expression and computed DataPoints.
RFC 8785 — JSON Canonicalization SchemeCanonical hash computation at container level.
RFC 7515 — JSON Web SignatureContainer signature format jws-detached.
RFC 7516 — JSON Web EncryptionContainer encryption format jwe.
RFC 5652 — Cryptographic Message SyntaxContainer formats cms-detached and cms-enveloped.
RFC 2119 — Keyword Requirement LevelsMeaning of MUST, SHOULD, MAY, and related keywords.
ISO 3166-1, ISO 3166-2Country and subdivision codes in metadata.jurisdiction.
ISO 639-1Language codes in metadata.language.
ISO 8601Date and datetime values throughout the format.
ISO 4217Currency codes recommended for the unit field of currency DataPoints.
RFC 5322Email format used by the email DataPoint type.
E.164Phone format used by the phone DataPoint type.
RFC 3986URI format used by the url DataPoint type.

Adjacent Standards

Other standards address overlapping or adjacent concerns in the legal-data-modeling space. This specification does not define formal mappings to such standards. Their use alongside RUML is not addressed.