Data structures and meaning
Catalog, database and schema organization
Namespace hierarchy: catalogs, databases and schemas, and where each object lives in it.
ddn@1New DDN source
Why use it?
Ownership and environment boundaries live in namespaces; getting them on paper prevents "it worked in dev".
When it helps
Organizing many objects across environments, teams or catalogs.
How to read it
- Nesting is ownership: an object has exactly one home.
- Cross-namespace references are explicit, annotated contracts.
What you need
- The environments
- Object homes
- Reference rules across boundaries
Things to check
- Do not let objects drift between namespaces without a migration note.
- Do not hide cross-namespace dependencies in names.
Scope of this diagram
Organizational documentation; no deployment is performed from this view.
Work with the converted example
- Open the viewer and select
diagram. 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.