-
Notifications
You must be signed in to change notification settings - Fork 16
2022 12 05 Meeting Minutes
Tracy Kuhrt edited this page Dec 7, 2022
·
4 revisions
- DCC's Learner Credentials Wallet - Dmitri Zagidulin, Brandon Muramatsu, Kerri Lemoie
- Dan Bachenheimer introduced the ISO Digital Wallet Advisory Group that is part of ISO/IEC JTC 1/SC 17
- Brandon Muramatsu demoed the Learner Credential Wallet (source code)
- Questions and Answers ensued
11:02:31 From Daniel Bachenheimer to Everyone:
Android | iOS
Join a meeting.
Tap More in the meeting controls.
Tap Enter Host Key to Claim Host.
Enter your host key.
Tap Claim. Once the host key is verified, you will have host controls in the meeting.
11:04:26 From Daniel Bachenheimer to Everyone:
"voluntold" as it were
11:04:51 From Drummond Reed to Everyone:
A long and distinguished management practice ;-)
11:05:13 From Dmitri Zagidulin to Everyone:
lol
11:07:55 From Andreas Freitag to Everyone:
We have all been there 🙂
11:07:56 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
Wait there IS another way?
11:09:09 From Dmitri Zagidulin to Everyone:
shout out to Sam Curren for his excellent 'Wallet Export' session at IIW the other week. the 'Custom' wallet setup option is precisely to /import/ an exported wallet
11:11:20 From Drummond Reed to Everyone:
+1
11:13:50 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
Is that deep link routing the credential display to the holder’s wallet
11:14:08 From Drummond Reed to Everyone:
Wow, that is definitely cool to be able to send the cred directly to LinkedIn
11:14:09 From Dmitri Zagidulin to Everyone:
it is not, it's displaying the credential on a regular web page
11:14:19 From Dmitri Zagidulin to Everyone:
(that was to Phillip)
11:14:34 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
@Dmitri - thanks.
11:14:41 From Dmitri Zagidulin to Everyone:
@Phillip - it's using a regular web page instead of the wallet, so that people can share the VC in like chat, or email, or whatever
11:15:09 From Keith Kowal to Everyone:
Is there a non-public way to share a credential?
11:15:31 From Keith Kowal to Everyone:
i.e. direct share between holder and verifier
11:15:38 From Brandon Muramatsu to Everyone:
non-public share would be “Send credential” send the JSON file to someone
11:16:15 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
@Brandon -and that “send” is not doing so as a VP?
11:16:24 From Brandon Muramatsu to Everyone:
Send is a VP
11:16:32 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
Just checking.
11:18:05 From Brandon Muramatsu to Everyone:
The “Add to LinkedIn Profile” is current state of the art based on what LinkedIn allows… from a mobile phone it has to go through the LinkedIn Mobile app, you have to be logged in, you can add a credential to the “licenses and certifications” section since that’s the only part of LinkedIn that they have provided a shortcut to allow
11:18:17 From Tracy Kuhrt to Everyone:
Couple of questions:
1. Are there tools that have been provided to Canvas to allow for the creation of the credential?
2. You mentioned that Open Source tools for learner credentials is missing. Is this open sourced?
11:18:48 From Brandon Muramatsu to Everyone:
https://github.com/digitalcredentials/learner-credential-wallet
11:18:59 From Daniel Bachenheimer to Everyone:
if not using DIDCOMM, what protocol do you use?
11:19:10 From Kerri Lemoie to Everyone:
https://github.com/digitalcredentials/lti-issuer
11:19:31 From Dmitri Zagidulin to Everyone:
@Daniel - at the moment, VC-API. working on adding CHAPI (Credential Handler API) native support.
11:19:52 From Dmitri Zagidulin to Everyone:
we hope to support all protocols, just a matter of dev bandwidth :)
11:20:15 From Keith Kowal to Everyone:
Does the wallet hold credentials as VCs or VPs?
11:20:27 From Dmitri Zagidulin to Everyone:
@Keith - as VCs at the moment.
11:21:33 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
The MIT License is actually more liberal than the Apache 2 license.
11:22:08 From Daniel Bachenheimer to Everyone:
thanks Dmitri
11:22:19 From Drummond Reed to Everyone:
My question: what features (or categories of features) of an OWF wallet would the DCC team like to see supported that the DCC wallet does not yet support?
11:22:40 From Dmitri Zagidulin to Everyone:
oooh what a great question
11:24:58 From Brandon Muramatsu to Everyone:
we’ve also got some initial work on encrypting the wallet
11:25:01 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
Are you thinking of building a wallet public repository that other wallets could take advantage such that other institutional consortia could install a public repository for their consortium school members?
11:25:29 From Brandon Muramatsu to Everyone:
one wallet or multiple wallets?
11:25:56 From Drummond Reed to Everyone:
Ahh, connection management is indeed cool
11:26:07 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
@Brandon multiple through a standards approach to this repository.
11:26:14 From Brandon Muramatsu to Everyone:
or do you mean repositories of educational records
11:26:36 From Dmitri Zagidulin to Everyone:
@Phillip - do you mean like a trust registry?
11:27:48 From Tracy Kuhrt to Everyone:
Capturing all meeting minutes and recordings under https://github.com/openwallet-foundation/architecture-task-force/wiki
11:28:09 From Dmitri Zagidulin to Everyone:
@Judith - that working group sounds really interesting!
11:28:13 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
What APIs would you want the wallet to support? For example, e.g., allow a ‘service’ to see a set of credentials that are cryptographically signed to selectively disclose only those elements the wallet holder would like to share, so that decentralized wallet holder data could be sampled for patterns of credentials or other collectively useful data sets?
11:28:17 From Drummond Reed to Everyone:
Another question: do learning credentials present any special requirements for a general purpose wallet that DCC thinks the OWF should consider?
11:29:28 From Dmitri Zagidulin to Everyone:
@Drummond - another great question. one thing that immediately comes to mind, is that in education (maybe unlike in some other fields), there's a couple of big kitchen-sink VC "profiles" - like the OpenBadges v3 spec.
11:29:58 From Dmitri Zagidulin to Everyone:
so in education space, support for those would probably be helpful
11:30:10 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
@Dmitry - I take a trust registry as something that has business logic and governance around the acceptance of a credential. That might be a future state, but immediately I’d say the consortium institution members would have a single public site and ‘assume’ their students are qualified with no additional scrutiny of their credentials required.
11:32:13 From Dmitri Zagidulin to Everyone:
@phillip - happy to chat more about this. (we don't really have any plans for /student/-level registry. more like registry for institutions themselves)
11:33:04 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
@Dmitri - yes PLEASE
11:34:18 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
I thought VC-API allowed for queries to be issued from the holder perspective -as well as - from the relying party perspective.
11:35:15 From Dmitri Zagidulin to Everyone:
queries specifically? not sure
11:35:15 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
@centralized decentralized DIDs
11:36:21 From Brandon Muramatsu to Everyone:
the reason we have Custom setup is for the Germans to send their users a profile with a DID the institution has issued to a known individual
11:36:53 From Kerri Lemoie to Everyone:
This is the list of use cases that have been collected by the VC Education Task Force: https://w3c-ccg.github.io/vc-ed-use-cases/
11:37:53 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
@Brandon - as long as the institution issues a DID for a holder where the keys are not managed by them, that’s no different from any SSI issuer allowing a DID to be created for an individual that wants one, or wants many, is?
11:37:56 From Brandon Muramatsu to Everyone:
kerri can you add the plugfest link also
11:38:14 From Kerri Lemoie to Everyone:
Plugfest 1: https://w3c-ccg.github.io/vc-ed/plugfest-1-2022/
11:38:32 From Kerri Lemoie to Everyone:
Plugfest 2 (videos not posted yet): https://w3c-ccg.github.io/vc-ed/plugfest-2-2022/
11:38:56 From Drummond Reed to Everyone:
@Phillip — if the institution doesn’t control the keys for the DID, then the institution doesn’t actually “issue” the DID. It only enables it to be used.
11:39:23 From Dmitri Zagidulin to Everyone:
+1 Harm
11:39:24 From Drummond Reed to Everyone:
I like to point out that DIDs are really never “issued”, only generated by the DID controller.
11:39:32 From Stavros Kounis to Everyone:
I understand a wallet that holds credentials. Is it sustainable to take an extra step and issue them as well? Where is the limit if it goes down this path?
11:39:42 From Kerri Lemoie to Everyone:
I like the idea of an interop party!!
11:40:10 From Dmitri Zagidulin to Everyone:
@Stavros - that's certainly something we'd like to explore (the wallet being able to issue / self-issue VCs)
11:40:20 From Dmitri Zagidulin to Everyone:
and, +1 to everything Drummond is saying
11:40:27 From Brandon Muramatsu to Everyone:
not sure if they plan to hand over the private key in the German case…
11:42:25 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
@Drummond - agreed. The question is when the German institution (our test example) facilitates the obtaining a DID for you, the holder’s SSI uses then I think we’re on the same page. I was concerned about the phrasing you correctly pointed out where institution “issues” you a DID. That is an oxymoron? ;-)
11:44:02 From Brandon Muramatsu to Everyone:
hah, we were going back and forth what to label to “profile” feature since it’s more the DID than anything else, but that wouldn’t necessarily be obvious to a lay user
11:46:11 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
Call Brandon!
11:46:16 From Dmitri Zagidulin to Everyone:
yesssss!
11:46:30 From Kerri Lemoie to Everyone:
😆
11:47:14 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
Another of the big questions is the business model around which this ecosystem can be sustainable?
11:47:35 From Dmitri Zagidulin to Everyone:
mwa ha haaa so as a non-profit, fortunately that's not /exactly/ for DCC to figure out
11:47:46 From Dmitri Zagidulin to Everyone:
but it is a tough question!
11:50:36 From Drummond Reed to Everyone:
+1 to trust registries. There will be thousands of them.
11:50:43 From Brandon Muramatsu to Everyone:
agree
11:51:14 From Brandon Muramatsu to Everyone:
LCW supports a DCC context of VC and OBv3
11:51:17 From Brandon Muramatsu to Everyone:
“quirks”, lol
11:51:33 From Judith Fleenor (Trust Over IP) to Everyone:
The importance of Trust Registries for all ecosystems, is why that is the next major initiative of our Tech Stack Working Group.
11:52:02 From Brandon Muramatsu to Everyone:
yes please @Judith… we’ve implemented a simple version to meet our current needs, but we assume there will be many
11:53:38 From Brandon Muramatsu to Everyone:
I like the “miracle occurs” step
11:54:54 From Judith Fleenor (Trust Over IP) to Everyone:
@Brandon, hopefully you or someone in your team at join that task force as ToIP starts that work shortly. (Meeting time being worked out now.)
11:54:57 From Brandon Muramatsu to Everyone:
“foot in the door” is probably also a good metaphir
11:55:01 From Brandon Muramatsu to Everyone:
or metaphor even
11:55:27 From Brandon Muramatsu to Everyone:
thanks Judith, we’ll keep our eyes out for it
11:55:32 From Judith Fleenor (Trust Over IP) to Everyone:
Thank you for this great presentation and discussion.
11:55:34 From Brandon Muramatsu to Everyone:
volunasked, lol
11:55:36 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
Thanks Brandon and Dmitri - great presentation and very thought provoking for all of us.
11:55:47 From Brandon Muramatsu to Everyone:
would a slide deck that shows what I demo’d be useful?
11:55:57 From Brandon Muramatsu to Everyone:
(I basically already have it, just a couple minor tweaks)
11:56:51 From Phillip Long (Georgetown, T3/LER Network) to Everyone:
+1 to the value of open source efforts!!
11:58:34 From Dmitri Zagidulin to Everyone:
nooooo ISO! :) hahahah not more groups and calls!
11:58:43 From Lucy Yang to Everyone:
Kaliya and I just published an open letter addressing the alignment/compatibility issues regarding VC & mDL https://medium.com/@identitywoman-in-business/where-can-the-w3c-vcs-meet-the-iso-18013-5-mdl-b2d450bb19f8?source=friends_link&sk=8b30d2654a0692a5f471ff2da15bb0fa
11:59:02 From Dmitri Zagidulin to Everyone:
@Lucy - that is a fabulous post btw!
11:59:11 From Lucy Yang to Everyone:
Thank you!
11:59:26 From Judith Fleenor (Trust Over IP) to Everyone:
Oh just what we need another group to monitor LOL