- From: Shawn Butterfield <sbutterfield@salesforce.com>
- Date: Wed, 30 Mar 2022 17:11:34 -0700
- To: James Chartrand <jc.chartrand@gmail.com>
- Cc: David Waite <dwaite@pingidentity.com>, Credentials Community Group <public-credentials@w3.org>
- Message-ID: <CADtMrnDjybOmpdRtU+-4DEK2UGq5sB2dE8VEF5mCOYfFXh6GUA@mail.gmail.com>
Really interesting, thanks for the explanation of your use-case, James. I'm curious: *The letters, which are PDFs, include a QR that encodes (via CBOR-LD) a > complete Verifiable Credential (all using the wonderful libraries from > Digital Bazaar - thank you!) Again the QR is NOT a link to a VC, but > rather contains the entire VC. The VC confirms the information that > appears as text in the PDF. * Is it truly just the CBOR-LD VC Doc or is it a CBOR-LD Verifiable Presentation (wrapped VC) that was serialized into a QR? I'm admittedly "new here" so still learning, but wouldn't interoperable verification software need the bundle as a verifiable presentation, not the standalone credential? Butters @ Salesforce | Software Architect On Wed, Mar 30, 2022 at 5:01 PM James Chartrand <jc.chartrand@gmail.com> wrote: > Hi David, > > Apologies for following up on this so late. McMaster University has got a > pilot underway (as part of our work with the DCC - Digital Credentials > Consortium - https://digitalcredentials.mit.edu) in which we dynamically > generate letters for students. The letters confirm things like: > > - the student is registered for the current term > - the student has graduated > - the student's current course list > > The letters, which are PDFs, include a QR that encodes (via CBOR-LD) a > complete Verifiable Credential (all using the wonderful libraries from > Digital Bazaar - thank you!) Again the QR is NOT a link to a VC, but > rather contains the entire VC. The VC confirms the information that > appears as text in the PDF. > > The idea is that the student can use the PDF in various ways: > > - upload the file (PDF), say as part of an online application for a > student bank account, to prove they're a current student. > - email the file (PDF) to someone, say a company recruiter, to prove > they’ve graduated. > - print out a paper copy and present it in-person, say to the immigration > officer when arriving at the Canadian border and applying at that moment > for a student visa. > > I’m guessing it's the paper scenario that you’d be interested in, although > you could also imagine the student sitting across the desk from a bank > employee when opening a new bank account, and air-dropping (or equivalent) > the file to the employee. > > The relying party can either scan the QR with their phone (from a web > browser open to our verification web page), or if they’ve received the full > file, can submit the PDF to the same verification web page (the > verification code actually simply pulls out the QR image and proceeds as > though the QR had been scanned). The verfication web page displays the > information that’s encoded in the VC (thereby confirming what appears in > the text of the PDF). > > Happy to present a live demo of the system if that would be of interest > (and if I’m not too late with this). It is a fully functional pilot that > uses the campus authentication system (Azure OIDC) and the campus student > info system (PeopleSoft). > > James Chartrand > > On Mar 3, 2022, at 2:40 PM, David Waite <dwaite@pingidentity.com> wrote: > > The Interoperability Open Group at the Decentralized Identity Foundation > is focused on education across communities on technologies, solutions, and > interoperability efforts. > > We are planning for a multi-part series on in-person exchanges of > credentials, also referred to as ‘attended’ use cases in the Mobile Drivers > License community. We are seeking implementers who have created or deployed > approaches to solve this problem using Verifiable Credentials. > > If you’ve worked on such an implementation and are willing to give a > presentation to the group, feel free to reach out to me. > > -David Waite > > > *CONFIDENTIALITY NOTICE: This email may contain confidential and > privileged material for the sole use of the intended recipient(s). Any > review, use, distribution or disclosure by others is strictly prohibited. > If you have received this communication in error, please notify the sender > immediately by e-mail and delete the message and any file attachments from > your computer. Thank you.* > > >
Received on Thursday, 31 March 2022 00:15:54 UTC