Formats, Validation & Identity
XML ↔ JSON-LD conversion, multi-layer validation, identifier translation, idempotent event hashing.
Before an EPCIS document reaches the event store, this layer parses, validates, canonicalises and hashes it for deduplication, and normalises its identifiers to Digital Link form. XML or JSON-LD goes in, and a validated, deduplicated, canonical event comes out. By the time anything is indexed, the platform has guaranteed that it is standards-conformant, semantically equivalent across XML and JSON-LD representations, and impossible to insert twice.
Two converters ship for two scopes. The open-source edition includes an XSLT-based converter that loads the document, runs the transform and emits the result, which works well for single events, small batches and plain event shapes. The Business edition adds a SAX-streaming converter for production volumes. Multi-gigabyte EPCIS exports stream through at network speed with bounded memory, so the JVM heap stays flat as the document grows. Deep extension trees and sensor payloads survive intact, mixed 1.2 / 2.0 batches pass through cleanly, and the edge cases where load-then-transform struggles or quietly drops information are handled correctly. A streamed conversion feeds into the same validation and event-hash stages, so it lands as a fully canonical, deduplicated event in one pass. For organisations moving production volumes, and especially for those migrating live 1.2 corpora to 2.0, this is the main difference between the editions.
Validation runs in layers: JSON Schema first, then custom-extension shapes at every nesting level of the event (parent, readPoint, bizLocation, errorDeclaration, sensorElement, ILMD, bizStep, disposition), then sensor-element rules. A document that fails any layer is rejected at the boundary. Custom namespaces (battery:, eudr:, textile:, customer extensions) are validated only when the request declares them via the GS1-Extensions HTTP header, and without that declaration the validator passes them through untouched. The header is the explicit opt-in that activates regulation-specific or vendor-specific validation rules.
Event hashes are computed against a canonicalised representation of the event content, with field order, types and whitespace normalised per the EPCIS specification. Two events that differ only in JSON whitespace or attribute order therefore produce the same hash, and re-sends and round-trips through different serialisers produce the same event ID. Canonicalisation is aware of the CBV version, so the rules can evolve with the spec without breaking historical hashes.
EPCIS 1.2 ↔ 2.0 XML migration works in both directions, which matters when an organisation is still receiving 1.2 from upstream partners while shipping 2.0 downstream.
Capabilities by edition
| Capability | OSS | Business |
|---|---|---|
| XML ↔ JSON-LD conversion (XSLT, load-then-transform) | ✓ | ✓ |
| Streaming XML ↔ JSON-LD conversion (SAX, bounded memory) | — | ✓ |
| EPCIS 1.2 ↔ 2.0 XML migration | ✓ | ✓ |
| EPCIS document validation | ✓ | ✓ |
| Multi-level custom-extension validation | — | ✓ |
| Sensor element validation | — | ✓ |
| Pre-canonical event hash (idempotent IDs) | ✓ | ✓ |
| Web UI for format conversion | — | ✓ |
| Hash generator as a service | — | ✓ |
See also
- Architecture → GS1 conformance contract: the rules these modules enforce.
- Modules → EPCIS Events: where the validated, hashed events go next.
- Modules → Testdata: generators that respect the same conformance rules.