Ga naar hoofdinhoud

Data Provider side

Draft – under review

Part of the Stack documentation (overview). Not yet endorsed by NDE.

Data management and Publication are run by Data Providers. Data management is source-internal and out of scope here. Publication is the source-side externalisation that turns internal data into something the network can consume.

Publication Layer​

Data Providers make their data available via standardised channels so Service Platforms, consumers, and network services can discover, fetch, and process it.

Patterns applied at this layer​

The Publication Layer is the source-side of several cross-cutting patterns defined in the Patterns chapter:

  • SCHEMA-AP-NDE-first: the inter-layer data contract; every Data Provider publishes at least SCHEMA-AP-NDE.
  • Parallel Data Models: publish in SCHEMA-AP-NDE and, where relevant, in one or more domain models (Linked Art, RiC-O, RDA, EDM) alongside.
  • Enrichments-as-Datasets: when a Service Platform publishes its own enrichments back into the Dataset Register, those enrichments enter this layer as new published datasets.

Standards used at this layer​

The Publication Layer is built on standards published outside this Stack documentation. Each links to its canonical source.

  • SCHEMA-AP-NDE: the NDE-Schema.org-toepassingsprofiel. Network minimum for heritage data publication.
  • Linked Open Data: dataset publication as Turtle / N-Triples / JSON-LD dump or SPARQL endpoint. See Publish linked data.
  • LDES: incremental change feed. Currently the most mature mechanism for sub-dataset-granularity change detection.
  • IIIF: Image API + Presentation API for image-based heritage. See Publish IIIF.
  • DCAT-AP 3.0 / Schema.org Dataset – the dataset-description vocabularies the Dataset Register accepts. Data Providers publish descriptions in either; Schema.org Dataset is the more common choice in practice, DCAT-AP is the EU-catalog-interoperability standard.

Network services consumed at this layer​