- From: Shawn Butterfield <sbutterfield@salesforce.com>
- Date: Thu, 31 Mar 2022 08:00:17 -0700
- To: Manu Sporny <msporny@digitalbazaar.com>
- Cc: public-credentials@w3.org
- Message-ID: <CADtMrnAyWxjVqDhx8mNi_f-2_5JavDW3xwrQbo5RYjq8QZ0dGQ@mail.gmail.com>
Thanks for the extra information, James. I'm very excited about your use case and I'd love to see it demonstrated live sometime! Also, thanks to DigitalBazaar for the great libraries, I agree they are extraordinarily valuable for bootstrapping VC work. Butters @ Salesforce | Software Architect On Thu, Mar 31, 2022 at 7:56 AM Manu Sporny <msporny@digitalbazaar.com> wrote: > On 3/30/22 7:59 PM, James Chartrand wrote: > > 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. > > James, this is amazing; we had no idea! We're glad that you found Digital > Bazaar's open source libraries useful! Please let us know if you hit any > snags > so we can improve any rough edges you experienced. > > I'm particularly interested in the specific VC you encoded and how well it > did/didn't compress; happy to provide some insight if that would be useful. > > > Yes, absolutely right - it is a Verifiable Presentation. We’re using > the > > Digital Bazaar vpqr library: > > Neat! You're definitely using the library for its intended purpose. Some > inside baseball: > > We have committed to CBOR-LD and the use of the VPQR "VP1-*" output format > for > production. We've also committed to the Ed25519Signature2020 suite for > production, though we do expect it's successor "eddsa-2022" (exact same > signature format, but different `type` and `cryptosuite` value) to also > become > ratified in the VC2WG. > > We are also exploring a "VPR1-*" format for purely local, purely optical > (QR > Code) VC exchange, AND for bootstrapping from an optical carrier (QR Code) > into a wireless protocol (NFC, Bluetooth, WiFi, LTE, etc.). > > There are some design decisions that we had to make there that are not > widely > known, like avoiding protocol schemes and App Links in QRCodes (for the > same > reasons they're problematic when used in mobile). I expect the recent CHAPI > conversation to uncover more of those design decisions. > > In any case, really neat work, James -- you made my day! :) > > -- manu > > -- > Manu Sporny - > https://urldefense.com/v3/__https://www.linkedin.com/in/manusporny/__;!!DCbAVzZNrAf4!SCtyUWNfb__fIJkg6NQsjHJLuQZgCCfDejy0XsjLM3wWlVLeq33YNc_4We4harXOZyjhtQ$ > Founder/CEO - Digital Bazaar, Inc. > News: Digital Bazaar Announces New Case Studies (2021) > > https://urldefense.com/v3/__https://www.digitalbazaar.com/__;!!DCbAVzZNrAf4!SCtyUWNfb__fIJkg6NQsjHJLuQZgCCfDejy0XsjLM3wWlVLeq33YNc_4We4harXdo8CBJA$ > > >
Received on Thursday, 31 March 2022 15:02:30 UTC