EPCIS and Intelligent Transportation Systems: An Introduction

EPCIS 2.0 is the GS1 standard for supply-chain event data, and epcis.dev is a capture gateway for it: post an event and the door validates it against GS1's own schema, stamps the capturing account — capturedBy, the warrantor, kept distinct from who, the attested observer — hashes it by CBV 2.0, and appends. That is the ground the topic above stands on.

Start with the model. An EPCIS 2.0 event answers five questions about one observed moment: what objects were seen, when, where, why (the business step and disposition, drawn from the CBV — the Core Business Vocabulary), and how (sensor data, where instruments were involved). Events are captured over one standard interface, queried over another, and identified by the CBV 2.0 §8.9 hash of their own content. That is the whole standard in one paragraph; almost everything else is vocabulary, and the CBV is that vocabulary.

Ten years of vendor XML has a path forward: EPCIS 1.1, 1.2 and 2.0 XML in, EPCIS 2.0 JSON-LD out, with a round-trip fidelity report per job so the translation is something you review rather than something you trust. That translator answers at POST /translate on this origin.

The same door answers people and agents. Capture, query, get_event, trace and translate are exposed over MCP, so a logistics agent captures and queries with the same key a person would use, without a human copying values between two systems.

Provenance: an aged epcis.dev page, kept at its original URL and refreshed into the current design on 8 September 2026.