... He has contributed a lot (an understatement), he has inspired many of us
Mike Prorock: Thanks for lining up the schedule. Next week will be interesting, bringing in an Advisory Board member from W3C, to talk about what's going on - directorless Formal Objection handling, etc. ✪
... and about role of Community Groups in W3C going forward
... an important meta-conversation
... As W3C goes through changes about how they handle tests in the Advisory Commitee, etc... will help us move technology forward
Kaliya: Thanks. Next week is our last call of the year. ✪
<rgrant> hi everyone, i can't get audio from Chrome stable or Firefox stable today. both want to update. i'll have to come back later and review notes. present-
... Late December: planning to update Jitsi for the new version
... to try to resolve the Chrome build issue
Manu Sporny: If there is extra time, it would be helpful to get a prioritized list from the chairs of long-standing things to fix ✪
Heather Vescent: Great, I didn't mean to suggest to do all of them. We as chairs should be able to collect and prioritize them. Documentation would be good. ✪
<manu_sporny> Happy to see we're having binding elections that people are happy with :)
... Trying to bring VC Edu work to the existing work in other spaces
... Training and achievements. and how to use with VCs
... VCs are complex
... Entrenched systems are bucking against change, but intrigued by blockchain
... We've had to evolve quickly and make changes in our task force
... We've gone beyond education, to say in charter will include training and achievement credentials
... Achievements can cover informal learning
... Bigger scope change: focus on direct alignment with verifiable credentials
... previously using envelope approach from ILR
... that conflicted with existing verification methods
... It may be useful for others, but we agreed it would benefit to align natively with VCs
... IMS global - Open Badges and CLR
... Verification method of Open Badges included an option for signing
... Members of the Open Badges committee offered to write VC examples a long time ago
<manu_sporny> So, true -- Kerri -- OB community was first to understand where VCs were going.
... Open Badges can represent many kinds of things. A good fit because already JSON-LD.
<manu_sporny> ... and were super helpful in the formative stages (and continue to be so today)
... Will link to the public proposal
... New charter at IMS, new working group working towards this
... Hoping to have something early next year to pilot with
... CLR is more complex. Has roles such as publisher and issuer
... Typically represents transcripts from K-12 and post-secondary institutions
... Opens opportunity to discuss VCs in new ways
... Topics, Questions and Issues - a list of things we've been discussing
... Some have expanded into the main CCG community
... Please queue to discuss any
Kerri Lemoie: Accessibility: very critical - we have participants in education without access to smartphones, computers, WiFi, etc. ✪
... Need to think about QR codes for education
Manu Sporny: For accessibility and path-to-paper, that's a requirement in the SVIP as well - there have been proposals for printing QR codes on paper ✪
... Other question about credential refresh and re-issuance
... I wrote to the mailing list about a new spec for refreshing credentials that are going to expire
... Could potentially be for e.g. educational credential that expires in 3 years but has the option to be refreshed depending on additional training
... Has it been discussed?
Kerri Lemoie: Probably exists, but can't think of it right now ✪
... Credential status just came up - seems related
<mprorock> exists for a lot of certifications such PMP that could leverage this work
Kerri Lemoie: Thank you for bringing up the relation of QR codes to accessibility ✪
Heather Vescent: Kerri and I have talked in the past about VC Edu and how to apply this tech for this use case. ✪
... In their inquiry they have found topics important to the broader credentials group
... We've talked about bringing these items to the CCG, in order to have a broad discussion about that use case
... Kerri and VC Edu task force will have the education perspective, but others could flesh out other situations and use cases for collaboration
... I think this is a very useful way to use a task force
... Usually we spun out task forces and they sortof splinter off
... But here they are finding things to bring back
... Back and forth conversation interesting, to splinter off and focus, and then bring back something, new ideas and use cases, to the main group
Kerri Lemoie: Thank you. Even though we have a separate mailing list, we often write to both, to report back. ✪
Ted Thibodeau: +1 VERY good to have things spin out for deeper dives, and spin back with results, discoveries, questions that turn out to be broader interest/scope! ✪
Marty Reed: To comment on the willingness of the VC Edu Task Force to focus... We're really willing to work on informing how to align the ILR and Open Badges / CLR to better interop with these standards. Kerri and this group's leadership cannot be understated. ✪
Kerri Lemoie: Thanks Marty, you're work has been great too. ✪
Kerri Lemoie: I started a thread about using email addresses for identifiers. My background for last decade is in the field of educational credentials. ✪
... In discussion, emails are well-understood, DIDs are not... Many systems will still use OIDC, even while switching to VCs
... credentialSubject id is not required; can use other info
... Seems to be the best approach so far
<tallted> email addresses can be identifiers, but they have their own challenges... e.g., role accounts and distribution addresses, and the like make many addresses non-identifiers in the common meaning
... We discussed briding systems a lot.
... The best way to do it is not always the best way to bridge to existing systems
<heather_vescent> q
... This is an example of such a compromise.
<manu_sporny> Excellent summary of the current state of things, Kerri.
<identitywoman> can you post links from slides into the chat so they are clickable
<manu_sporny> The "transcript / registrar" use case is an argument for VCs embedded in other VCs... not a VP.
Marty Reed: I think there's a lot of really interesting use cases here ✪
... across K-12, licensure systems
... Manu, I would agree 100% VPs are not the solution here
... But what is exciting is that we are tying it together
<manu_sporny> Glad to hear that from Marty...
Juan Caballero: I was wondering about Manu's comment, perhaps the solemonic solution, if presenting a bundle of credentials to some sort of notary or registrar ✪
<manu_sporny> yes, exactly, Juan -- or embedded...
... maybe that event could be commemorated by a VC that represents the others
... rather than freezing the VP and using it as a VC
<manu_sporny> VP is ephemeral... we don't expect people to hold on to them long-term.
... to reference the contents of the presentation.... or maybe that's what you already meant
<manu_sporny> Agree with Marty and Juan.
Heather Vescent: +1 To look at this topic in the main CCG call! ✪
Kerri Lemoie: This topic triggered me asking Heather if we could present on this call - but then realized we are due for an update anyway. Would like to talk about in the new year ✪
Manu Sporny: +1 To "look at this topic together" ✪
... Would be happy to bring questions. Let's see if we can come up with an understanding.
Manu Sporny: One of the things we're trying to do with both the credential status 2021 and credential refresh/reissue 2021 stuff, is to make the simplist process to apply to the broadest number of use cases ✪
<mprorock> /me unfortunately has to drop for a customer call - this is awesome, thanks for the update and great work
... That use case you've outlined, I think we are trying to say, don't do that (trying to convey the small changes) - just revoke their credential or tell that their credential is going to be revoked in some weeks/months - and then give them a mechanism to automatically bring in the new changes
<mprorock> and on the way out the door, +1 to manu, revoke and re-issue
... So the general approach is to revoke and automatically request changes
... Then the new things are automatically pulled in, as long as they've consented to that.
Kerri Lemoie: Thanks. That last step is critical - the update might not be wanted by the learner. ✪
Heather Vescent: That you for the update. We have some great direction for the new year. ✪
Heather Vescent: We also have the two new co-chairs here ✪
... Would they like to say hello
<juan_caballero_(spruce)> ♥
Simone Ravaoli: It's an honor to support this work in the VC Edu, it grows naturally from my background in the higher-education space, working for credential providers for the majority of my professional life. ✪
... Digitary is a player that was acquired by Parchment this summer
... I'd like to see Parchment take on this great work, across different standards organizations
... I look forward to maintaining tight contacts with this group as the "mother" of the VC Edu group
Dmitri Zagidulin: Thrilled to be part of the leadership of the Education Force. You may know me from Digital Bazaar, various specs, DIDs. Recently I've been coming into more and more contact with educational space use cases ✪
... as part of my other work and projects
<kerri> Thanks, Dmitri!
Heather Vescent: Awesome, excited to see it moving forward ✪
... Thanks to Charles for scribing
Manu Sporny: +1 -- VC-EDU has a fantastic leadership team (and group) ✪
<kerri> Thanks, @Manu!
... With that we'll conclude, and see you next week for our final call of the year
<simone_ravaioli> :)
... Happy holidays - past or present - whatever you are celebrating!