Time, composition and linked documentation
Subdiagrams and inline views
A view that links to another view, and an embedded view that keeps its own composition inside the host diagram.
ddn@1New DDN source
Why use it?
Detail-on-demand without leaving the page: the overview stays readable while the detail is one declared hop away.
When it helps
Layered documentation: estate overviews with per-area details, poster diagrams with magnified insets.
How to read it
- Linked elements open their target view; the inline variant draws the embedded view's own layout inside the host.
- The embedded view keeps its composition — moving the host does not rearrange it.
What you need
- The host view
- The linked/embedded target views
- The declared link between them
Things to check
- Do not nest inline views more than the composition rules allow — one level deep, by rule.
- A link target that does not exist fails validation, not silently.
Scope of this diagram
Declared links and embedding with composition validation; no interactive navigation is shipped in the static SVG.
Work with the converted example
- Open the viewer and select
overview. 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.