DISL — Diagram Specification Language
Contents of DISL 0.2
Specification, version 0.2 (Working Draft)
| Date | 2026-09-30 |
| Specification schema | disl.schema.json (JSON Schema, draft 2020-12), $defs/Specification |
| Definition language | DID, the Diagram Definition Language, in ../did/ |
| Expression language | CEL — Common Expression Language (https://cel.dev) |
| Media type (provisional) | application/vnd.disl.specification+json |
| File extension | .dis |
This is a working draft, version 0.2. It is complete enough to implement a conforming validator, a documentation generator and a reference runtime, but individual constructs may still change before version 1.0. DISL 0.1 continued the earlier combined format (DEDL became DISL and DID); section 18 lists the old identifiers that runtimes still read. DISL 0.2 adds declarative constructs to 0.1 (declared identity, findings that point at files, reasons the tool gives, derived elements, gestures and menus, view state, budgets, notation and time details). Every valid 0.1 specification is a valid 0.2 specification and keeps its meaning, except in the places listed in Changes from 0.1, where 0.1 was silent or ambiguous and 0.2 now says what it means. Sections and paragraphs marked (informative) explain intent and give guidance; everything else is normative.
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY and OPTIONAL are to be interpreted as described in RFC 2119 and RFC 8174 when, and only when, they appear in bold capitals.