Standards families
SoaML service architecture
Participants offering and consuming services through service contracts — the architecture of who serves whom.
soaml.services@1New DDN source
Why use it?
Service landscapes rot by assumption; SoaML makes the contracts and their consumers a drawable, checkable graph.
When it helps
Service inventory design, API landscape reviews, consumer-provider onboarding.
How to read it
- Participants are the parties; service interfaces (ball/socket style) attach contracts to ports.
- The choreography variant shows the message order the contract permits.
What you need
- The participants
- The service contracts
- Who provides and who consumes each
Things to check
- Do not draw a consumer wired to a provider without the contract between them.
- A contract with no choreography is underspecified — the variant shows why.
Scope of this diagram
Declared architecture with contract-attachment validation; runtime governance is out of scope.
Work with the converted example
- Open the viewer and select
arch. 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.