Alexandria

Introduction

Documentation of Alexandria, the reference implementation of the Vocabulary Hub specification v0.3.0 for dataspaces.

Alexandria Documentation

Alexandria is the reference implementation of the Vocabulary Hub specification v0.3.0: a hub that governs and publishes the vocabularies and policy profiles of a dataspace, and an edge proxy that validates Dataspace Protocol (DSP) traffic against them without contacting the hub on the request path.

The repository is a single Go module with three binaries and a web console:

  • alexandria-server (C-HUB) — namespaces and stewards, vocabulary registry, release lifecycle, signed credentials and immutable publication.
  • alexandria-client (C-CLI) — L7 edge proxy in front of an unmodified DSP connector, with verified synchronization and a dynamic rule set.
  • alexandriac — offline compiler of the alexandria.profiles/v1 profile language.
  • Console (gui/) — browser application for both binaries, optionally embedded in them under /ui/.

Laboratory notice (DP-14). The sample configurations, the fake-idp identity provider, the fake-connector, local signing keys and self-signed TLS certificates are for laboratory and proof-of-concept use. They are not a production deployment.


What the System Does

  1. Governs releases. Stewards author a draft, the hub validates it (N1–N5), freezes it as a candidate and, on approval, computes the lifecycle dates (published_at, new_content_from, enforced_from) and publishes a package.
  2. Signs everything clients rely on. Version listings, version records and package manifests are W3C Verifiable Credentials 2.0 secured with eddsa-jcs-2022.
  3. Publishes immutably. Artefacts under /pub are content-addressed and cacheable forever; only head redirects change.
  4. Validates at the edge. The client synchronizes and verifies packages in the background (S1–S13), then classifies each DSP message as ok, warning or violation and acts according to the rule mode (observe, shadow, enforce).
  5. Migrates without breakage. A breaking release opens a grace window in which both versions are accepted; messages valid only under the old version are forwarded with a VHub-Verdict notice until the new one is enforced.

The implementation covers 81 normative requirements (REQ-SYS, REQ-HUB, REQ-CLI, REQ-DOC) and the closed catalog of 77 error and verdict codes.


Explore the Documentation

On this page