Roadmap
Three horizons — Now, Next, Later. Skeleton awaiting user-confirmed dates.
Three horizons. Items in Now are confirmed and in flight; items in Next are committed but ordered by priority rather than dated; items in Later are directional only.
Dates are deliberately not part of this roadmap. Priority order in Next reflects what closes the most platform narrative — reorder as commitments firm up.
Now
| Initiative | Affects | Status |
|---|---|---|
| 0.9.5 stabilisation across the BOM | all groups | in flight |
openepcis-dpp-ready 0.9.5 — JSON-LD contexts for EU DPP (battery, textile, electronics, EUDR) | Masterdata | in flight |
GS1-Extensions header rollout — three-mode parsing across the validation chain | Formats, Architecture | in flight |
Next (ordered by priority)
The roadmap is strategic — capabilities that change what OpenEPCIS is, not maintenance of what it already does. The technical fixtures (additional storage backends, sundry CLI utilities, specific deploy variants) are present today and listed in the Feature Matrix; they don't earn roadmap slots.
- Named VC schemas + capture-to-issuance pipeline — The protocol layer (Keycloak OID4VCI / OID4VP / SIOPv2,
sd-jwt-vcfirst) is already shipping in every Business deployment; what's next is the named credential schemas —EPCISCommissioningCredential,EPCISCustodyTransferCredential,DPPBatteryPassportCredential,EUDRDueDiligenceCredential,UNTPDigitalConformityCredential— and the bridge that issues a VC the moment the underlying event or attestation is recorded. Includes UNTP Digital Conformity Credential compatibility and the globally-scoped issuer trust list so verifiers across regions and sectors can validate credentials against a single open list. Affects EPCIS Events, Masterdata, and Architecture. - Event → Resolver masterdata promotion — Close the wiring gap so an EPCIS event arriving at
/capturepromotes its identifiers and masterdata into the resolver via the existingMasterDataDomainEventbus. Completes the "masterdata driven by EPCIS events" narrative end-to-end. Affects Masterdata + EPCIS Events. - Sub-tenant row-level scoping — Today access is binary per tenant: a user sees everything in their organisation or nothing. Optional GLN, EPC-range or biz-location scoping would extend OpenSearch DLS role-mappings without changing the application layer. Affects Architecture → DLS.
- RAG corpus for AI assistant — Today the assistant is intent-routed but stateless — context lives per request. A retrieval corpus over EPCIS events, masterdata and GS1 specs would let the assistant answer about historical supply-chain state, not just translate prompts. Affects Integration.
Later (directional)
- GS1 Web Vocabulary OWL-DL reasoning — derive missing masterdata facts from the existing graph.
- Event-replay subscriptions — let subscribers backfill a missed window by replay from a PIT.
- Cross-tenant data-sharing agreements — opt-in linkset visibility between consented organisations.
- Multi-region OpenSearch federation — geo-replicated event store for compliance with data-residency constraints.
How to read this page
Every initiative is tagged with the module group(s) it affects so the page reads as a coordination map, not a wish list. When a Next item moves to Now it picks up a date; when it ships, the Feature Matrix gains a ✓ and the matrix's roadmap cell is removed.
The platform's discipline rules (Digital Link at rest, masterdata to the resolver, no embedded epcisHeader.epcisMasterData) are not roadmap items — they are constraints, applied to every new feature.