Techniques
View profiles — choosing symbols and rules
A view selects a profile that defines its method, projection, palette, legal relationships and verification rules.
flow.documented@2New DDN source
Why use it?
A declared kind turns "this looks wrong" into a coded diagnostic: permissive mode reports each out-of-vocabulary element as DDN-VP03, strict mode fails the check with DDN-VP04 naming the fix.
When it helps
Any view that claims to follow a notation: declare the kind, then choose strict for regulated deliverables and permissive while drafting.
How to read it
- An explicit view declaration uses as followed by its registered profile identifier.
- Native short forms supply a particular recipe; they do not merge rules from different methods.
- Lifecycle status is separate from profile and drawing style.
What you need
- The intended diagramming method
- The selected profile contract
- The definitions and data the view presents
Things to check
- Do not select a profile only because its symbols look similar.
- A draft status permits incomplete design but does not turn illegal references into resolved ones.
Scope of this diagram
Profiles have bounded contracts. Their presence does not imply a complete execution engine for the external method.
Work with the converted example
- Open the viewer and select
flow_strict. 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.