DID — Diagram Definition Language
Contents of DID 0.2
Specification, version 0.2 (Working Draft)
| Date | 2026-09-30 |
| Definition schema | did.schema.json (JSON Schema, draft 2020-12), $defs/Definition |
| Specification language | DISL, the Diagram Specification Language, in ../disl/ |
| Media types (provisional) | application/vnd.did.definition+json, application/vnd.did.fragment+json |
| File extension | .did |
| Licence | Apache License 2.0 (Apache-2.0) |
This is a working draft. DID, the Diagram Definition Language, specifies how a diagram a user created is stored. It is complete enough to implement a conforming reader, writer and validator of stored diagrams together with DISL, but individual constructs may still change before version 1.0. Sections and paragraphs marked (informative) explain intent and give guidance; everything else is normative.
DID 0.2 adds to DID 0.1 what DISL 0.2 needs of a stored diagram: tolerant reading of ids, findings instead of refusals, ephemeral and derived elements, suppressions by subject, enum stored forms, fixed attributes, optional relation targets and time value forms. Every valid DID 0.1 definition is a valid DID 0.2 definition and means the same; section 12 lists every change. DID continues the document format of the earlier combined format (DEDL became DISL and DID); section 11 lists the old identifiers that readers still accept. The abbreviation DID here always means ADP's Diagram Definition Language, not the W3C's Decentralized Identifiers.
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.