BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20260218T183413Z
BEGIN:VTIMEZONE
TZID:Asia/Tokyo
X-MICROSOFT-CDO-TZID:20
BEGIN:STANDARD
DTSTART:20241118T080000
TZOFFSETFROM:+0900
TZOFFSETTO:+0900
TZNAME:JST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:96d25e6c-7b48-4b83-9d17-e6935cfbd164
DTSTAMP:20260218T183413Z
SUMMARY:Why the issuer-holder-verifier paradigm of VCs isn't enough for cro
 ss-border trade
DTSTART;TZID=Asia/Tokyo:20251113T170000
DTEND;TZID=Asia/Tokyo:20251113T180000
DESCRIPTION:https://www.w3.org/events/meetings/96d25e6c-7b48-4b83-9d17-e693
 5cfbd164/\n\nAsk anyone for the use cases for Decentralized Identifiers an
 d Verifiable Credentials and you'll be told about driving licences\, unive
 rsity degrees and digital identities\, all of which are variations on a th
 eme of an authority issuing a credential to an individual who uses it to m
 ake a verifiable presentation to some relying party in a way that preserve
 s their privacy. Those are solid use cases. But the trade use case differs
  significantly.\n\nAn example: there’s no way an exporter in Australia w
 ould make a verifiable presentation to China customs. Instead the exporter
  needs to be able to link their GS1 shipment identifier\, itself part of a
  chain\, and their verifiable Australia Business Number to their DID. Then
  the exporter issues a commercial invoice as a VC. The importer gets the V
 C and passes it to their broker who includes it with the customs import de
 claration. Then China customs verifies the invoice VC\, resolves the issue
 r DID to find the vABN\, and confirms that the subject did of the vABN VC 
 and the GS1 VC is the same as the issuer DID of the invoice VC. \n\nThere 
 may be other technical ways to achieve this traversal of “verifiable lin
 ked data” (IETF [ACDC](https://www.ietf.org/archive/id/draft-ssmith-acdc
 -02.html) perhaps) but a more general method of verifying what is in effec
 t a trust graph is needed. It requires a method to link VCs in a way that 
 generic verification software can check multiple VCs that will be issued b
 y completely unrelated organizations with no business relationship\, all t
 o prove that the data being presented has multiple roots of trust.\n\nIn t
 his session\, Steve Capell from Pyx\, lead author of the [UN Transparency 
 Protocol at UNECE](https://spec-untp-fbb45f.opensource.unicc.org) and Phil
  Archer from GS1\, who co-chairs the Verifiable Credentials Working Group 
 with Brent Zundel\, explore what's needed for trade. They will be joined b
 y Ivan Marin from the Global Legal Entity Identifier Foundation (GLEIF).\n
 \n**Goal(s):**\nGather input towards a possible new charter for the VCWG\n
 \nAgenda\n\n- Introduction & welcome\, Phil Archer\, GS1\n- Why trusted gr
 aphs are needed for trade\, especially cross-border trade\, Steve Capell\,
  Pyx/UNECE\n- ACDC as a possible solution\, Ivan Marin\, GLEIF\n- Discussi
 on\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3
 c/tpac2025-breakouts/issues/84)\n- [Slides](https://docs.google.com/presen
 tation/d/1GrDVpzZPdsvCCkiVHt8UX72zX3ubecZzqzAjX1-FB7A/edit)\n- [Ivan Marin
  slides](https://drive.google.com/file/d/1As0JVSaYICfrKCcj33Sn5Dowk8zvELLY
 /)
STATUS:CONFIRMED
CREATED:20251103T200253Z
LAST-MODIFIED:20260218T183413Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Floor 5 - 505
CATEGORIES:TPAC 2025,Breakout Sessions
END:VEVENT
END:VCALENDAR