Attendees

• Tony Rose
• Rebecca Distler
• Jim Mason
• Marie Wallace
• David Riedel
• David
• David Luchuk
• Jammal Dorsey
• Justin Dossey
• Kaliya Young
• Ramesh Raskar
• Sid Mishra
• Travis James
• Vitor Pamplona

Agenda Items

Presentations -

(PDFs posted)

Recording - Link

Notes

1. Welcome and Linux Foundation antitrust policy

2. JSON Formats (Based on prompt)

• JSON-LD enables a single representation of a credential that could work as both paper and digital (means trade-off on space, but also meant one single credential). Also enables zero knowledge proofs.
  • You never present VC you present proof of the VC - important in that JSON-LD is common denominator and can help unify this across paper and digital
• There will be multiple flavors in payloads and QR codes no matter what we do.
  • Note that GHPs won’t necessarily have massive data elements (can be constrained if we focus on travel, not full use in epidemiology) 
  • QR codes serve two purposes: proof + also something you might use to load credential into wallet (and not every QR code needs to be translated back to digital)

3. Points to gain consensus on (based on prompt)

• There’s never going to be a single set of schemas - we need to design a system that assumes a mess.
  • Group should explore what can we do to address this issue, rather than assuming this needs to be standardized.
  • Group should make a recommendation re: how to distinguish between payloads and codes.
• Need to understand credential vs. pass
• Pass produced not by the original source of a covid test but by some intermediary - a secondary issuer and a secondary credential that is typically used in a specific context for a specific purpose 
• Terminology can be confusing to customers (e.g., IBM had to walk this language back)
• Pattern of recombining credentials into another credential will come up in a lot of discussion (passes derived from credentials)
  • Need to better help people understand that verifiable credentials don’t go on paper, presentations do (will help better understand credentials vs. proofs)

5. Wrap up 

• Next steps

David Janes Thoughts & Notes (Discussion Prompt)

1. Definition of CREDENTIALS and PASSES as per GHPC Interoperability PDF
2. Consensus Needed:
1. Credentials transform into Paper and back again losslessly - e.g. to the GHPC defined W3C VC
2. Passes transform into Paper as a one-way operation (e.g. PathCheck)
3. If we have agreement on (2) and (2a) in particular, what are the ways of encoding the JSON 
1. JSON → QR (lol)
2. JSON → CBOR → QR
3. JSON-LD → CBOR-LD → BASE32? → QR (Mattr is here)
4. JSON → CBOR → ZLIB → QR
5. JSON → CBOR → BASE32 → QR
6. JSON → CBOR → COSE → ZLIB→ BASE32 → QR (EU is here)
7. JSONXT
4. Consensus Needed: how should we select from (3)
1. Ease of Implementation 
2. Readily available and mature libraries in popular languages
3. Best Size of Compression
4. Size of Compress “Good Enough” (say, under 500 bytes - cross check with size GHPC is recommending!)
5. Amount of code required
6. Works in QR Code - Go/NoGo (cross check with size GHPC is recommending!)
5. Consensus Needed: is it OK if there are multiple compression methods - verifiers have a lot of work to do anyway?
6. Note that there are going to be multiple different QR payloads no matter what we do:
1. GHPC in two flavours
2. EU defines a JSON-based but non-W3CVC
3. Multiple other passes now “in the wild”. Variants!
7. Consensus Needed: GPHC should make a recommendation how to distinguish between different payload types on QR codes, even if they are not using GHPC credentials.
8. PathCheck format: 
1. can GHPC credential be transformed into a PathCheck pass?
2. how do the digital signatures / trust frameworks line up?
9. Consensus Needed: is PathCheck format the recommended format for passes, or is it PathCheck + compressed W3CVC. 
10. Question: is GHPC defining a pass payload, or just a credential?
11. Question: How does DIVOC fit in all this?? 
12. Future meetings, but not now: identity binding & for (2a) being able to self inspect payload for personal assurance

Action Items

1. Connect with DIVOCC and MagnaCerta on use of JSON-LD