UC3 Sovereign Dataspace

Participants

Participant	Role	Advertises	Identity (DID / BPN)	Connector	Status

Live discovery — real DSP catalogue requests between connectors

Consumer → Provider	HTTP	Offer	Capacity	ODRL policy advertised with the offer

A catalogue request is a Dataspace Protocol query issued by the consumer's own connector against the provider's DSP endpoint. It is read-only and does not touch the custody path.

Live Dataspace Protocol exchange — issued now, both directions

Request — what the consumer's connector sends

press a button above

Response — the provider's dcat:Catalog

This is a real DSP catalogue request between two live connectors, performed when you press the button — not a recording. The connectors log at WARN, so a catalogue request leaves no trace in their container logs; the exchange itself is the evidence. Read the dcat:dataset entries and the odrl:hasPolicy offer attached to each.

Catalogues — what each participant publishes

Contracts negotiated by the running market

Cycle	Consumer	Provider	Agreement id	Migration

Federated catalogue database — harvested from every connector

Resources by participant — DCAT-AP classes

Participant	Class	Count

ODRL rules and constraints — decomposed, queryable

Policy	Rule	Constraint

Tractus-X removed the Federated Catalog in 0.13, so this harvester is ours: it asks each connector what it publishes and stores it DCAT-AP shaped. Staleness is mark-and-sweep — a missed crawl degrades visibly rather than emptying the catalogue.

Germany as a data provider — metadata and live data points

Topic	Originator	Stream	Access URL

Live data points

loading…

Germany is read-only production and is never written to. France holds a faithful mirror and serves these topics as a declared intermediary: every asset carries dct:publisher = Germany, dct:creator = the real originator, and an explicit provenance statement.

Connector logs — live

select a connector above