Techniques
Authorized export — hiding is not redaction
A private source view next to its allowlisted public export: the public view shows exactly what the allowlist names.
ddn@1New DDN source
Why use it?
Hidden elements still ship in the SVG source unless the export excludes them — hiding is not redaction, exclusion is.
When it helps
External publication of internal models: customer-facing diagrams, tenders, regulatory submissions.
How to read it
- The private view shows everything; the public variant renders only the allowlisted elements and relations.
- Anything not on the allowlist is absent from the export artefact — check the variant, then the export.
What you need
- The full model
- The publication allowlist
- The export path
Things to check
- Do not publish the private SVG because "it looks clean" — inspect the allowlisted export instead.
- Labels on allowlisted elements can still leak: review wording, not just membership.
Scope of this diagram
Allowlist-based exclusion at render/export time; legal review of what may be published remains a human act.
Work with the converted example
- Open the viewer and select
private. Inspect the rendered view and its source. - Open the designer. Keep the selected profile and inspect its legal palette and property controls.
- Change one displayed title or an appropriate data value. Apply the edit and check the resulting diagram.
- Run the verifier and review its diagnostics before moving complete content into review.
- Download your edited DDN source to retain the change.
The example uses the indentation-based ddn-next-1 dialect. The language guide explains reusable definitions, dotted data rows and explicit property blocks.