Capture cold-chain temperature sensor readings as EPCIS 2.0 SensorElement events using the standard GS1 capture interface
domain: gs1.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Model each temperature reading as part of an EPCIS event with a sensorElementList
Populate a SensorElement with sensorMetadata (time, data source) and one or more sensorReport entries carrying type (e.g., gs1:Temperature), value, and uom (e.g., CEL for Celsius)
POST the event(s) to your EPCIS repository's capture endpoint, following the GS1 EPCIS 2.0 REST bindings OpenAPI spec (async batch capture, or a single-event POST)
Set the GS1-Capture-Error-Behaviour header to control how the repository handles partial failures in a batch capture
Test end-to-end against an open-core reference implementation such as OpenEPCIS before pointing at a production repository
Known gotchas
EPCIS 2.0's REST binding is a formal spec, but exact capture endpoint behavior (sync vs. async, precise paths) can vary by repository vendor - confirm against your specific EPCIS server's docs, not just the abstract spec
uom codes follow UN/CEFACT unit codes (e.g., CEL) rather than free text - repositories may reject events with an incorrect code
This is a data-modeling/integration standard, not a single vendor's live API - you need an EPCIS-conformant repository (self-hosted OpenEPCIS or a commercial one) to actually capture or query against
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?