01. Introduction
This chapter establishes what RUML is for and how the rest of the specification is to be read: which documents it governs, what its normative language means, and what an implementation must do to call itself conformant.
- 1.1 Scope — What RUML encodes, and the problems it addresses
- 1.2 Document Conventions — RFC 2119 keywords (MUST, SHOULD, MAY) and notation
- 1.3 Terminology — The terms used throughout, from node and LexID to modular node
- 1.4 Conformance — What a conformant document, parser, and producer must satisfy
- 1.5 Relationship to Other Standards — How RUML relates to JSON Schema, JSONata, and legal markup formats