DSO Integration¶
Overview¶
The Linked Data Explorer integrates with the Digitaal Stelsel Omgevingswet (DSO) — the national catalogue and registry stack underpinning the Dutch Environment and Planning Act. This integration lets process designers link BPMN subprocesses directly to their authoritative DSO activiteit, browse the Stelselcatalogus and werkzaamheden registry from inside LDE, and verify references against live DSO data.
The integration spans three DSO APIs:
- Stelselcatalogus — the conceptual model (concepts, properties, value lists)
- Zoekinterface — search interface over werkzaamheden (the citizen-facing tasks like "boom kappen")
- RTR (Registratie Toepasbare Regels) — the activity registry where each authority's activiteiten and rule types live
A toggle in Settings selects between the pre-production and production DSO environments independently of the LDE environment.
DSO environment toggle¶
The DSO environment is set in Settings → DSO environment and persisted to localStorage. It is independent of the LDE environment toggle — pre-production LDE can talk to production DSO and vice versa, which matters because some authority data is only available in one environment.
| LDE setting | API target |
|---|---|
| Pre-production | service.pre.omgevingswet.overheid.nl |
| Production | service.omgevingswet.overheid.nl |
A coloured badge in the DSO Explorer header reflects the active environment — amber for pre-production, green for production.
Concepts tab¶
Full-text search over the Stelselcatalogus. Returns concepts with their URI, label, definition, and source. Useful for discovering the canonical conceptual reference behind a citizen-facing term.
Works tab — werkzaamheden¶
Search the Zoekinterface for werkzaamheden (the citizen-facing tasks that anchor a permit application — "boom kappen", "Bed & Breakfast starten"). Autocomplete fires after two characters with 300ms debounce.
Each result shows:
- The human-readable omschrijving (e.g. "Bed & Breakfast starten")
- The full
functioneleStructuurRefURI — the pivot to STTR files for the upcoming Phase 4 import - The short werkzaamheid URN
Selecting a result opens a detail panel with the current version's metadata, validity period, and full version history (each version showing start/end dates and a "current" badge).
Default sort order is meestGekozen — the most-used Omgevingsloket werkzaamheden appear first.
Activities tab — activiteiten¶
Browse the RTR (Registratie Toepasbare Regels) for activiteiten. The default view lists recent activities; the authority presets (Lelystad, Flevoland) filter the list by authority OIN (Organisatie-identificatienummer) using POST /activiteiten/_zoek with bestuursorgaan.oin as the body filter.
The date input above the list defaults to today; changing the date and clicking Load re-fetches the authority list valid on that date.
Each activity card shows badges for the rule types declared on the activity:
- Conclusie — full DMN decision content available
- Indieningsvereisten — application requirements (questionnaire-style DMN)
- Maatregelen — measures (textual content, structured per maatregel)
These badges flag which downstream LDE assets can eventually be derived from the activity in Phase 4 (DMN, form, document template).
Activity Detail panel¶
Clicking an activity row opens the detail panel. It shows:
- omschrijving and full URN
- bestuursorgaan (authority) — bestuurslaag, organisatieType, code, OIN
- validity (begindatum / einddatum)
- parent activity link (if any)
- child activities — names fetched in parallel after the parent loads
- rule types present, with download links
If an activity is queried from the wrong DSO environment (e.g. trying to view a production-only URN while the toggle is on pre-production), the detail panel shows a clear "not available in this environment" message rather than a raw 404.
Linking a BPMN subprocess to a DSO activiteit¶
The BPMN Modeler footer panel has a DSO Activity selector. Pasting a URN and clicking Verify queries the live DSO RTR — on success, the panel shows the omschrijving, authority, and a direct link to the public RTR viewer. The URN is then persisted on the BPMN process element as ronl:dsoActiviteitUrn.
The verified URN survives saveXML round-trips and follows the same pattern as other ronl: extensions (RoPA, language, organization).
Phase plan¶
The integration is delivered in phases. The detailed plan, current status, confirmed test anchors, and remaining work for each phase are tracked in DSO Integration Phase Plan. Phases 1–3 are live as of v1.5.3; Phase 4 (STTR → DMN/form/document import) is the next development cycle.
Related documentation¶
- DSO Explorer user guide — step-by-step search and link workflow
- DSO Integration Phase Plan — phase status, test anchors, implementation order
- BPMN Modeler — DSO activiteit linkage
- Backend API reference — DSO routes