Techniques
Connector presentation — color, weight and pattern
Registered line and stroke properties change presentation while a connection retains its semantic role and endpoints.
ddn@1New DDN source
Why use it?
Emphasis that lives in a viewer's session-preview CSS vanishes on export; declared in the model, a thicker dashed boundary or a coloured flow survives publication and hand-off.
When it helps
A de-emphasised or highlighted flow (dotted, coloured), a heavier element boundary, a tinted card fill — paint distinctions that are not registry semantics.
How to read it
- Read the relation role and endpoint markers before relying on color.
- View and occurrence settings can change presentation within their property contract.
- Routing geometry and semantic endpoint selection are distinct from stroke styling.
What you need
- The connection role
- Source and target definitions
- Applicable presentation properties
Things to check
- Color alone is an unreliable semantic distinction.
- A heavier or dashed line must not silently change the relation type.
Scope of this diagram
Use only the applicable codex properties; the profile still controls legal connections.
Work with the converted example
- Open the viewer and select
main. 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.