Solid-OIDC client
DPoP-bound access tokens for reading Pods; short-lived, cached, fail-closed on expiry.
Open-data integration
A decoupled microservice between the Solid Databox and a CKAN data portal. It lets agencies publish governed Pod data while preserving the natural person’s agency over personal information.
Pipeline
Solid Pod layer CKAN Bridge CKAN registry
(Solid-OIDC / DPoP) --> SHACL + RDF→tabular --> Action API
webhook / HMAC datastore upsert
reconciliation metadata fields
correction propagate
DPoP-bound access tokens for reading Pods; short-lived, cached, fail-closed on expiry.
Fail-closed validation before any data reaches CKAN; non-compliant payloads are quarantined.
Program-profile-driven field mapping with PII anonymisation (strip, hash, generalise) and evidence recording.
Idempotent via sha256(podIri:contentDigest); bounded retries with quarantine on max-retries-exceeded.
HMAC-SHA256 signature verification, idempotent event deduplication for dataset lifecycle events.
Periodic sweeps detect editor drift and orphaned datasets; Databox dispositions propagate back into CKAN.
CKAN plugin
databox_bridge is enabledRelated