Layers
Part of the Stack documentation (overview). Not yet endorsed by NDE.
The NDE network architecture distinguishes four layers. This chapter consolidates per-layer Stack guidance: each layer’s patterns, standards, and components. Bottom-up:
| Layer | Scope | Who runs it |
|---|---|---|
| Data management | Source-internal handling: collection management systems, internal catalogues, cleanup at source. Out of scope for this Stack documentation; see Requirements. | Data Provider |
| Publication | Source-side externalisation: RDF dump, SPARQL endpoint, IIIF, LDES. | Data Provider |
| Data Layer | Service Platform internals. | Service Platform |
| Presentation Layer | User-facing presentation. | Service Platform / consumer application |
The NDE Stack covers all four layers. It is positioned around the full Linked Data lifecycle the same way Linked Data Elements (LDE) is (Discovery / Ingestion / Transformation / Analysis / Publication / Serve).
LDE is a toolkit of small, composable @lde/* packages that handle generic linked-data plumbing:
discovering datasets, downloading distributions, running pipelines, serving SPARQL and RDF. It is data-model-agnostic and network-agnostic.
The NDE Stack composes LDE’s packages with NDE-specific configuration (@ndes/*) and operated network services to produce the NDE approach of the lifecycle.
In this chapter
- Data Provider side – what Data Providers do (Publication Layer; Data management out of scope).
- Service Platform side – what Service Platforms do (Function mapping, Data Layer, Presentation Layer).
Related
- DERA – the network-wide architectural reference; the four-layer model is being added there.