How.
The How is the path an observation takes to the door: an interface, a migration from legacy formats, and the hardware that produces the reads in the first place.
You POST an EPCIS 2.0 document; the gateway validates it against GS1's official JSON schema, stamps the fields it owns, computes the CBV 2.0 event hash, and appends. The same interface answers over MCP, so an agent captures with the same key a person would use. The calculators — POST /translate, /validate, /hash — answer on this origin with no key; the write half opens with a capture key.
The pages below are the capture methods the old tree carried. Two business documents it deep-linked to keep their anchor IDs.
POST /capturePOST /translate
Proof, not adjectives. The gateway's conformance tests pass against GS1's normative artifacts; POST /translate, /validate and /hash answer on this origin. The dated ledger is What ships today.
How, page by page.
-
01
APIs
The capture and query interfaces are built against GS1's official EPCIS 2.0 OpenAPI description, pinned by digest and re-checked in CI. A capture that does not validate is refused as RFC 7807 problem+json carrying the standard's own exception types. The write half opens with a capture key; the calculators answer on this origin without one.
-
02
EDI
Legacy exchange lives in XML. The gateway's translator takes EPCIS 1.1, 1.2 and 2.0 XML in and returns EPCIS 2.0 JSON-LD, with a round-trip fidelity report per job so the translation is reviewable rather than trusted. That translator answers at POST /translate on this origin. A hosted EDI-exchange product is not something this site claims; the migration path is what ships.
-
03
Tags
RFID and barcode tags carry the GS1 identifiers an event observes. The tag is where the identifier originates; the event is what the gateway validates, stamps and hashes once that identifier reaches the door.
-
04
Scanners
Barcode and Digital Link scanners produce reads at a point in a process. Those reads become the epcList of an EPCIS 2.0 event; the gateway does not read the tag, it accepts and validates the event the read produces.
-
05
Readers
RFID readers generate high-volume observation data at fixed and handheld read points. EPCIS 2.0 is the layer above the reads: the standardized event, not the raw stream. The gateway accepts the events, stamps the warrantor, grades the asserted observer, and appends.
-
06
Printers
Label printers commission new serialized identifiers at the start of an object's life. A commissioning event records that origin; the gateway validates and appends it like any other, so the object's history begins at the print, not at first scan.
The documents it ties to.
Each is a business transaction an event references, with the deep-link IDs the old tree carried preserved.
Shipping notice
An advance shipping notice is a business transaction shipping events reference. EPCIS 2.0 links the observation to the notice; the translator handles the legacy XML form of it on the way to JSON-LD.
Bill of lading
A bill of lading is the transport document a shipment event can reference. The event carries the reference in bizTransactionList; the document itself is not replaced by the event log.