Repository navigation
Add DCAT and Dataspace Protocol interoperability #7
Description
🤖 Generated by the Agentic Engineer
User story
As a data-space participant, I want data products to publish interoperable catalog and policy metadata so that independently operated products can be discovered, negotiated, and transferred under explicit usage rules.
Acceptance criteria
- Data-product descriptors map to W3C DCAT 3 resources, datasets, distributions, and data services.
- A provider-neutral adapter exposes Eclipse Dataspace Protocol catalog metadata without coupling the core controller to one connector implementation.
- Identity, policy, contract negotiation, and transfer remain explicit external capabilities; the controller never treats a public endpoint as authorization.
- Interoperability tests round-trip a reference product through the catalog representation.
- A public example documents what is interoperable and what remains deployment policy.
Rough size: XL.
Remaining adoption
DCAT publication and the offline provider-bound DSP catalog representation are delivered by
#122 and #125. #126 remains open for an independent connector/provider to accept the exported
catalog and complete its own negotiation and transfer path before release-gate retirement.
Catalog-format compatibility alone does not establish that integration or authorize activation.
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
No fields configured for Epic.
Projects
- Status
Activity
devantler commentedon Sep 30, 2026
The first discovery slice is delivered: #122 is complete through merged PR #124 and release v1.7.0. Publisher-declared datasets now have an opt-in DCAT 3 JSON-LD catalog, stable identities, distributions and service/contract links, bounded public-metadata projection, independent consumer discovery/query coverage, and real Kubernetes enablement/withdrawal/pagination/rollback evidence.
The Dataset profile and public example are documented in the release. This epic remains open for the provider-neutral Dataspace Protocol adapter and its explicit external identity, policy, negotiation and transfer capabilities. Production activation and release-flag retirement are tracked in #123.
devantler commentedon Sep 30, 2026
The implementation slices are shipped: DCAT discovery in #124 / v1.7.0 and the provider-neutral offline DSP catalog adapter in #127 / v1.8.0. The latter includes runnable examples, pinned-schema and independent JSON-LD validation, and execution of the signed published image.
The descriptor mapping, adapter, explicit external capability boundary and public example criteria are complete. Producer-to-exporter tests verify the reference catalog's identities, offers and service relationships. The interoperability outcome remains open for the actual independent provider/consumer path in child #126, including negotiation and transfer under that provider's access controls. This epic stays open until that adoption evidence and flag decision are complete.
chore: agent-claim #7 nonce=92edf08be74ff74b46fcf6a9dd0c3075
chore: agent-claim #7 nonce=0e44f1fd2c66468f8c86e0939bfb254d
devantler commentedon Oct 1, 2026
The semantic round-trip criterion is delivered in merged PR #149 (
44e23ba837cb13616864ac27771f5312cac0d2a9). Required CI, the real Kubernetes lifecycle test and current-head review passed before merge.The complete independent graph oracle and nine corruption controls protect identity, selected outputs, supported usage rules and text operands. This establishes offline catalog data-model interoperability. This parent remains open while child #126 validates runtime exporter adoption and retires its release flag.