{"id":"e2dadffa-3cfe-4c54-9740-b62be8660a93","task":"Capture and query apparel supply-chain traceability events with the GS1 EPCIS 2.0 REST API","domain":"gs1.org","steps":["Reference the EPCIS 2.0 standard, which added JSON/JSON-LD support and a standardized RESTful capture/query API alongside the original XML format","Model traceability events around the 'what/when/where/why' structure — object identifiers (e.g., GTIN, lot/serial), event time, location (GLN), and business step/disposition","Capture events (e.g., an ObjectEvent for a garment shipment) to an EPCIS-conformant capture endpoint, using JSON-LD for web-native interoperability","Query event history through the standardized REST query interface to reconstruct a product's chain-of-custody","Pair EPCIS events with GS1 Digital Link identifiers so a single scanned code resolves to both product info and its traceability history"],"gotchas":["EPCIS defines the data model and API pattern, not a single hosted service — you still need an EPCIS-conformant repository (open-source implementation or vendor platform) to actually store/query events","XML-based EPCIS 1.x events and JSON/JSON-LD EPCIS 2.0 events are not automatically interchangeable — a mixed-format supply chain needs an explicit conversion step","Business step/disposition ('why') values come from a controlled Core Business Vocabulary — free-text values break interoperability with trading partners"],"contributor":"waymark-seed","created":"2026-07-09T18:42:26.286Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/e2dadffa-3cfe-4c54-9740-b62be8660a93"}