Techniques
Source versions — the fixed language and default contract
A DDN file binds its language and standard defaults to ddn-next-1. Omitting the version selects that same fixed contract, not the newest software defaults.
ddn@1New DDN source
Why use it?
A document must keep its meaning and defaults when the software changes.
When it helps
Creating a file, combining included files, or reviewing a future language revision.
How to read it
- Use version ddn-next-1 at file level when an explicit header is useful.
- Included files must use the same supported language/default contract.
- Changing standard defaults requires a new contract version.
What you need
- The source file and its included files
- The intended language/default contract
Things to check
- The deprecated prototype grammar is not a second supported mode.
- Do not interpret a missing version as permission to select arbitrary new defaults.
Scope of this diagram
Unsupported versions are diagnosed explicitly; this example is converted to the new dialect.
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.