epcis20

GS1 EPCIS repository written in .NET 10. Supports v1.x and v2.0 of the specification.

Generate valid EPCIS 2.0 and CBV 2.0 test events in JSON/JSON-LD or XML; GS1 Digital Link and EPC URIs, randomized serials and timestamps, event hash IDs. Available as a Java/Quarkus library, a REST API and a free online tool.

Java models for GS1 EPCIS 2.0 and CBV 2.0 supply chain traceability: documents, events, master data, queries and subscriptions, with Jackson (JSON/JSON-LD) and JAXB (XML) bindings, GS1 Web Vocabulary classes and a Quarkus extension.

Convert GS1 EPCIS 2.0 documents between XML and JSON/JSON-LD, and upgrade EPCIS 1.2 XML to 2.0. Streaming conversion for large event documents, available as a Java library, Quarkus extension, REST API and native Docker image.

Signing of EPCIS events for tracability and immutability within COPPA and beyond

Java library and Quarkus extensions for GS1 identifiers: convert EPC URN to GS1 Digital Link Web URI and back, validate against GS1 rules (check digit, GCP length), and generate Digital Link QR codes. Covers SGTIN, SSCC, SGLN, GRAI, GIAI, GDTI, ITIP, UPUI, LGTIN and more. EPCIS 2.0 ready.

EPCIS 2.0 Repository built in GraphDL, Graph.do and Cloudflare Workers Durable Objects

Classes and parsers for GS1 EPCIS 2.0 subscription callback endpoints. Supports JSON callback format.

This project provides Maven-Bom for all the modules of the openEPCIS project

Validate GS1 EPCIS 2.0 documents and events against the official JSON Schema, and EPCIS 1.2 or 2.0 XML against the EPCglobal XSDs. Reports every schema error with line and location instead of stopping at the first one. Covers capture and query documents. Java library, REST API, servlet and Quarkus extension.

Communication of physical, chemical and microbiological analyzes from LAB/Olive via EPCIS v2

Communication of physical, chemical and microbiological analyzes from LABrys via EPCIS

Java constants for the GS1 EPCIS and CBV standards: EPCIS event field names, version strings, document types and GS1 Application Identifier and URN prefixes. Used across all OpenEPCIS projects so field names are defined once and typos fail at compile time.

Use Case of the EPCIS v2 protocol for sending IoT data from the Olive Sentry program.

Additonal JSON-LD contexts and XML schema for EPCIS in the COPPA ecosystem

Implementation of the EPCIS protocol in Sentinel System