- From: Amir Hameed <amsaalegal@gmail.com>
- Date: Sat, 2 May 2026 16:55:16 +0530
- To: "public-vsc@w3.org" <public-vsc@w3.org>
- Message-ID: <CANGYBsxmyxWwBTzaCVN8bnD=VbWV7y6eLR=mQiNM3DcbKi_4nA@mail.gmail.com>
Hi everyone, I’ve just opened a new issue to track the development of the *VerifiableShippingEvent Profile v0.1*. This profile is a key piece of our architecture, bridging GS1 EPCIS 2.0 event data with the W3C Verifiable Credentials ecosystem. *View the full draft and contribute here:* *https://www.google.com/search?q=https://github.com/w3c-cg/vsc/issues/4 <https://www.google.com/search?q=https://github.com/w3c-cg/vsc/issues/4>* This document defines how a shipping business step can be expressed as a cryptographically verifiable claim. It covers everything from field-level mappings to the derivation of DIDs from SGLN identifiers. *Immediate Areas for Feedback:* - *Mapping Logic:* Are the cardinality rules for sourceParty and destinationParty (Section 4.3) consistent with your real-world shipment data? - *DID Derivation:* Does the proposed GLN-to-DID resolution model (Section 5.1) align with your existing identity infrastructure? - *Revocation:* We are mapping EPCIS errorDeclaration to VC revocation/correction. Does this logic hold up for your audit requirements? Our goal is to move this toward a formal Work Item, so your implementation-first feedback is vital. Please post your thoughts, edge cases, or technical critiques directly in the GitHub issue linked above. Best regards, *Amir Hameed Mir* Chair, W3C Verifiable Supply Chain CG
Received on Saturday, 2 May 2026 11:25:34 UTC