Re: [MINUTES] CCG Weekly 2025-07-15

In response to this week's meeting, the editors of the Verifiable 
Issuers and Verifiers draft report believe that it is now ready to 
progress to becoming a VC Working Group work item.

The editors are pleased to answer any questions from the CCG about the 
latest draft report, which can be found here

https://w3c-ccg.github.io/verifiable-issuers-verifiers/

Kind regards

David and Isaac


On 15/07/2025 23:07, meetings@w3c-ccg.org wrote:
>
>
>   CCG Weekly Meeting Summary - 2025/07/15
>
> *Topics Covered:*
>
>  *
>
>     *Introductions/Reintroductions:* Jonathan Bryce (new attendee)
>     introduced himself and his background in data analytics and
>     full-stack application development. Erica Connell reintroduced
>     herself and her work with Legendary Requirements.
>
>  *
>
>     *Announcements:* Will Abramson proposed APAC-friendly CCG calls in
>     October, leading up to the W3C technical plenary in Japan. Kaliya
>     Identity Woman announced upcoming IW events. Erica Connell shared
>     a link to her DID-focused podcast.
>
>  *
>
>     *Work Item Updates:*
>
>       o *Verifiable Credential Barcodes:* No update due to the absence
>         of editors.
>       o *Verifiable Credential Rendering Method:* Ready for promotion,
>         likely moving to the Credentials Working Group. Discussion of
>         its purpose to render verifiable credentials in a
>         human-readable format.
>       o *Confidence Method:* Not yet ready for promotion, lacking an
>         owner and requiring further work.
>       o *VC API:* Significant progress, aiming for completion of
>         outstanding issues by August. Discussion of interoperability
>         and the test suite. 25+ implementations at varying
>         interoperability levels.
>       o *Data Integrity 2.0:* Ongoing work on quantum-safe
>         cryptographic suites, with an effort to refactor the core data
>         integrity spec for better parameterization. Discussion of
>         integrating MLDSA, SHS, Falcon, and S2I algorithms.
>       o *Leroa:* Integration into cryptovm zen room demonstrated in
>         Android and microservice environments. Work underway on an SDK
>         for multiple languages.
>       o *VC Test Suites:* No changes to specs, but new implementers
>         are being added. Discussion of creating a similar test suite
>         for DID resolvers.
>       o *Verifiable Issuers and Verifiers:* Version 0.2 of the data
>         model updated, addressing feedback and aiming for promotion;
>         seeking community feedback on mandatory and optional attributes.
>       o *DID Linked Resources:* Update awaited from Alex and Anker.
>         Discussion of related work integrating DID traits into the Rubric.
>       o *Proposed Work Items:* "Verifiable Credentials over Wireless"
>         is nearing acceptance as a work item. "Cryptographic Event
>         Logs" was recently proposed and will be discussed further next
>         week.
>  *
>
>     *Website Change:* A new CCG website was proposed, offering
>     improved features and organization. Community feedback is encouraged.
>
> *Key Points:*
>
>   * Several specifications are nearing completion or ready for promotion.
>   * Significant effort is being put into improving interoperability
>     and testing.
>   * New work items are being proposed and reviewed.
>   * A new website is under development.
>   * The CCG encourages community involvement and contributions.
>
> Text: https://meet.w3c-ccg.org/archives/w3c-ccg-ccg-weekly-2025-07-15.md
>
> Video: https://meet.w3c-ccg.org/archives/w3c-ccg-ccg-weekly-2025-07-15.mp4
>
>
>     *CCG Weekly - 2025/07/15 11:57 EDT - Transcript*
>
>
>   *Attendees*
>
> Alex Higuera, Andrea D'Intino, Benjamin Young, Chandima Cumaranatunge, 
> Dave Lehn, Denken Chen, Dmitri Zagidulin, Erica Connell, Hiroyuki 
> Sano, Isaac Henderson, JeffO - HumanOS, Jennie Meier, Joe Andrieu, 
> Jonathan Bryce, Kaliya Identity Woman, Kayode Ezike, Mahmoud 
> Alkhraishi, Parth Bhatt, Phillip Long, Rob Padula, Ted Thibodeau Jr, 
> Will Abramson
>
>
>   *Transcript*
>
> Erica Connell: Hey guys.
>
> Will Abramson: …
>
> Mahmoud Alkhraishi: Hello We're just giving everyone another two or 
> three minutes and then we'll get started.
>
> Will Abramson: Hi, Bryce. then, I'll let you introduce yourself in a 
> minute, but I'm glad to see you here, man.
>
> Jonathan Bryce: Yeah, it will. no problem.
>
>
>       00:05:00
>
> Mahmoud Alkhraishi: All right. let's get started. thank you all for 
> joining us today. It is Tuesday, July 15th. IPR note, please make sure 
> that you have signed our community license agreement that you adhere 
> to our code of ethics and that you have joined our community 
> credentials group. That is wonderful. today's meeting is going to be 
> about an update on the status of all the current work items where we 
> are and what we want to do. Before we get to that though, 
> introductions and reintroductions. Do we have anybody new or do we 
> have anybody returning who would like to reintroduce themselves to the 
> broader group?
>
> Will Abramson: So, if Bryce isn't going to say anything, I'm going to 
> introduce him for him. I'd love to hear him say, " yeah. Bryce, you go 
> for a minute.
>
> Jonathan Bryce: No problem. All right. good morning everybody. my name 
> is Jonathan Bryce. but as will has been calling me, he can call me 
> Bryce. so my experience would be for 5 years I would have been working 
> as a data analyst at the National Commercial Bank in Jamaica. So right 
> now I'm kind of transitioning from strictly data analytics and 
> reporting leveraging the AI tools currently to generate full stack 
> applications.
>
> Jonathan Bryce: So that would be my introduction in a nutshell. Yeah.
>
> Will Abramson: Great. Thanks,…
>
> Will Abramson: Ryce. Yeah, I'll just say I met Bryce in Kingston, 
> Jamaica, and we've been chatting since it seems like there's a lot of 
> interesting stuff going on in ma So, I'm delighted to have some 
> Jamaican representatives in this group. Thanks for coming, Jeff Bryce.
>
> Mahmoud Alkhraishi: Thank you for joining us, Jeeoff. Erica, I think 
> you had your hand up. Would you like to introduce yourself or did I 
> misread that
>
> Erica Connell: I didn't,…
>
> Erica Connell: but I'm Erica Connell. I work with Legendary 
> Requirements. I have been in the space for some time and I'm currently 
> working leading up our media division to tell the stories about 
> decentralized identity out in the world. That's it.
>
> Mahmoud Alkhraishi: Thank you and sorry for calling on you, I guess. 
> announcements. Does anybody have anything they would like to share 
> with the broader community? Go ahead.
>
>
>       00:10:00
>
> Will Abramson: Yeah, I have something which is kind of a note that I'm 
> working on. I would love to have some help or if anyone's interested 
> in this, please, reach out to me afterwards. But as probably most 
> people know, the W3C technical plenary and advisory council, I think, 
> is happening in Japan in November. And I've been talking to a few 
> people who are APAC, associated or in that part of the world. And 
> obviously these call times aren't APAC friendly as most calls aren't. 
> I would like to explore how we host a series of events that are APAC 
> friendly up to TAC. And I think I have some people who kind of help me 
> find some potential candidate speakers. So we'll be looking for APAC 
> folk doing interesting stuff in the technologies that we work on. 
> Right. maybe like four weeks.
>
> Will Abramson: I'm looking at the month of ctober. Depending on what 
> the group thinks, we could either move this call completely to an APAC 
> friendly time zone or probably where I'm leaning currently is just 
> running another set of calls I would be happy to do that in my 
> mornings in the UK mornings. they're pretty available at the moment. 
> so just making sure that there's a call time that, we can try and 
> build some momentum and some community in the Asia-Pacific region, 
> especially in the run-up to this event that is part of this community, 
> And it is in Apac. So, if that sounds like a great idea or if you have 
> ideas for how we could make that even better, do reach out to me. I'm 
> exploring as
>
> Mahmoud Alkhraishi: There's always the option of running different 
> call times on different weeks. I know a few other groups do that and 
> that may be something that we'll have to look into.
>
> Will Abramson: Yeah, I will just add to that briefly. I agree that is 
> an option. I think I've in the did working group for example, we have 
> tried that and struggled. So we could experiment with that again and 
> see how the CCG does and if that works maybe we can do that. But yeah, 
> we'd have to see in the didwork group for example, we don't get much 
> APAC participation still. But I guess did working group you have to be 
> a member, right? I paid W3C numbers.
>
> Mahmoud Alkhraishi: Yep, makes sense. all right. Does anyone else have 
> any announcements or anything they'd like to share with the broader 
> group? Please.
>
> Kaliya Identity Woman: Hi. yeah, just to share IW is happening the 
> last week of October and the European event we had planned with our 
> partners in early September was unilaterally moved without our 
> knowledge really sometime in November and we're still trying to figure 
> it out. So, yeah, I'll put a link to IW in the chat.
>
> Mahmoud Alkhraishi: Awesome. Thank you,
>
> Erica Connell: Yeah, I did raise my hand this time, I guess. Also, 
> thanks for calling on me. I just wasn't quite all the way awake yet. I 
> put in the chat a link to the Rubric podcast, which is a podcast I 
> produce that's specific to conversations about DIDs and DID methods. 
> And so, that's applicable here and you can check it out at the link I 
> put in the chat. That's it.
>
> Mahmoud Alkhraishi: Thank you for sharing that. does anyone else have 
> any other things they would like to share? Any other announcements? 
> then let us get started with the week. give me one second. Let me 
> start presenting. Can you all see my screen?
>
> Erica Connell: Yes.
>
> Will Abramson: Yeah, exit.
>
> Mahmoud Alkhraishi: Okay. this is Please
>
> Will Abramson: Wait. Did I just say something for moment? Yeah. So, 
> this is just a flag to everybody on this call. we try to run these 
> Every quarter. And the real flag I wanted to highlight is usually Manu 
> takes a lot of these slides, right? Because he's very involved in a 
> lot of these work items. But if you haven't noticed already, Mano is 
> not on the call today. So it'd be great to hear some other voices from 
> other people,…
>
>
>       00:15:00
>
> Will Abramson: particularly obviously if you are familiar with the 
> current state of any of the work items we are going to discuss. So 
> thank you.
>
> Mahmoud Alkhraishi: Yeah, thank you.
>
> Mahmoud Alkhraishi: So the specs that we have heard are ready for 
> promotion which are the the verifiable credential rendering method and 
> the confidence method specs. And then there's a number of specs that 
> are not yet ready for promotion. and we're going to go through them 
> one by one. so the verifiable credential barcodes, do we have anybody 
> from that editor's team that's able to talk about the spec and it 
> current state I suppose.
>
> Will Abramson: I don't see any digital people unfortunately.
>
> Mahmoud Alkhraishi: So, normally this would be Manu, but again he's 
> not here. Wes, Dave, or either of them on that they can talk to it. 
> then let us move on and then hopefully we can get an update on it next 
> week. The render method. I think I saw Dimmitri on, but I'm not sure. 
> Dimmitri, would you be able to talk to it? You're Yes,…
>
> Dmitri Zagidulin: Yeah can you okay so yeah render method is 
> proceeding mostly in GitHub issues right now I think we need to 
> schedule a special purpose call to do some issue triage there …
>
> Mahmoud Alkhraishi: we can hear you fine.
>
> Dmitri Zagidulin: but yeah lots of interest but lots of work needs to 
> be done That's it.
>
> Will Abramson: So I have a question Dinci this is ready for promotion 
> right there is a plan or…
>
> Will Abramson: a hope to bring this into a working Right,…
>
> Dmitri Zagidulin: Yes, yes, yes, yes. Okay. ready for promotion. 
> possibly into the credential working group. but I don't know the 
> details. Man would know.
>
> Will Abramson: right, right. I think my understanding, it could be 
> wrong, is that the hope is probably at TAC they'll try to recharter 
> the verifiable credentials working group and…
>
> Will Abramson: bring in a bunch of these things, right? Cool.
>
> Dmitri Zagidulin: Yeah, that's the most likely route.
>
> Mahmoud Alkhraishi: And that's the Q2 2025 start of standardization work,…
>
> Mahmoud Alkhraishi: right? we are doing weekly meetings on Wednesday 
> for the incubation meetings. I unfortunately have a conflict with 
> those. Is there anybody else who is on those calls that can speak to 
> it a little bit more or is this all we have on? Yep.
>
> Will Abramson: I'm not on these calls,…
>
> Will Abramson: but at least I know Bryce won't have a clue what's 
> going on. So, I'll just speak to what the verifiable credential render 
> method is as I understand it. Maybe Dimmitri could correct me. So 
> basically, right, a verifiable credential is a digitally signed 
> credential your passport, right? has some information, some attributes 
> that are signed over by an issuer. And that's all fine for a machine. 
> But what about when you want to actually render it for a human so they 
> can look at and go like, " yeah, that's the human face." I'm looking 
> at a human, and I can see all that information in a nice human 
> readable way.
>
> Will Abramson: And the VCU render method tries to not be specific 
> about how you might render it but provide a extension point where 
> people can define different render methods. So you might render it as 
> a PDF for example or some other ways. Maybe Demetri can add some other 
> approaches. The basic thing is we're trying to render some signed data 
> in a way that a human can read it friendly…
>
> Will Abramson: if that makes sense.
>
> Jonathan Bryce: All right.
>
> Jonathan Bryce: Thanks. I do have a question though. this project 
> seems a bit similar to a governmentbacked initiative called NIDS which 
> would be the national ID program what they're trying to do is to 
> combine passport driver's license and…
>
> Jonathan Bryce: I guess any other supporting document into one ID. So, 
> that's been going on for some years now. So, definitely that I think 
> would be beneficial in trying to get that project off the ground.
>
> Will Abramson: Cool. Yeah,…
>
> Will Abramson: thanks for sharing. Maybe you've got a link. That'd be 
> great.
>
> Mahmoud Alkhraishi: Moving on, we have the confidence method, which I 
> don't believe we have any text for. but we do have the spec link and 
> as is always fun, we don't have any editors on for it.
>
>
>       00:20:00
>
> Mahmoud Alkhraishi: Is anyone working on this confidence method that 
> can speak to it a little bit? Yeah.
>
> Will Abramson: Yeah. Yeah.
>
> Will Abramson: And maybe even if not like I'd be interested if 
> anyone's been going to the calls that Manu has been hosting I think on 
> Wednesdays around moving some of these specs ready to production ready 
> to done because I mean in the first place you shared my mood right the 
> confidence method I was quite surprised to see the confidence method 
> is ready for promotion because it doesn't have an owner at the moment 
> it is work we want to be ready for promotion but it's not quite there 
> yet. That's my opinion. I haven't been attending these Wednesday 
> calls. So,
>
> Mahmoud Alkhraishi: Okay, I guess we don't have anyone on who's 
> working on it. VC API. This one we should have someone who can speak to.
>
> Mahmoud Alkhraishi: Parth, please go ahead.
>
> Parth Bhatt: So there are 25 issues at the moment on the VC API spec and…
>
> Parth Bhatt: I am tackling one by one. so far eight PRs are there 
> already and I think we based on Manu's comments during the meeting I 
> think we are targeting to tackle all those issues by August and make 
> it ready for moving this back to VC working Sure.
>
> Mahmoud Alkhraishi: Awesome.
>
> Will Abramson: And can I ask either you pass or…
>
> Will Abramson: somebody else to just give us a short synopsis of what 
> the PC API is trying to do?
>
> Parth Bhatt: So VC API basically it's list of all the APIs that all 
> verifier coordinator all those based on the API specs can issue VC. So 
> it's kind of VC management service related APIs that supports issuance 
> verification presentation and…
>
> Will Abramson: Great. Thanks.
>
> Parth Bhatt: status modification which is mentioned in this slide in 
> short. Mhm.
>
> Mahmoud Alkhraishi: Thank you for that. does anyone else have anything 
> they would like to add on the VC API? And I believe just the other 
> two, this is intended to be brought up at TAC. Jonathan
>
> Jonathan Bryce: Yeah. I have a question. I'm seeing 25 + 9 which be 34 
> implementations. varying levels of inter oper yeah that line. could 
> you go a bit deeper in terms of the tech that is currently being used 
> for it to be inter operable.
>
> Mahmoud Alkhraishi: So yeah, if we go to the VC API itself, which is I 
> believe there's a VC API test suite. I don't know from this or if it's 
> linked to externally. I think there's a whole slide on the test suite, 
> unless I'm mistaken. Yeah, it's on slide 11. where we go through and 
> we have an implement list and these are the different impleers and 
> their current level of support. Again, these vary at different times. 
> Sometimes I know for the Mavenet site, sometimes we're always green, 
> sometimes It just depends on if we have the service up or not.
>
> Mahmoud Alkhraishi: And again most people turn it on for a specific 
> point, make sure tests are all passing, publish the report, etc. What 
> we mean is for the current state on the implementers and varying 
> levels interoperability is we had nine new impleers be added since the 
> last call.
>
> Mahmoud Alkhraishi: So this was for March. I believe that number's not 
> changed. So we currently I believe have 25 influencers and the varying 
> levels of interoperability just means they are varying levels of 
> compliance with the different spec texts. and again yeah sorry go ahead
>
> Will Abramson: And I was just going to add yeah so right the VC API is 
> a specification right…
>
> Will Abramson: which is just a document that defines how to implement 
> a thing and in particular defines a bunch of must specific statements 
> which are spec statements that an implement should be passing 
> particularly the implements must pass the must statements to be 
> compliant with the specification and the test suite is how implement 
> mentors can demonstrate that they have implemented this specification and…
>
>
>       00:25:00
>
> Jonathan Bryce: All right. thank you, Will. And my home
>
> Mahmoud Alkhraishi: Yeah. No worries.
>
> Will Abramson: some obviously don't implement all the must statements 
> and some don't implement all the should. So that means you have 
> interoperability issues when they are implementing different
>
> Mahmoud Alkhraishi: Are there other notes on the VC API work? I think 
> the biggest thing that we heard that's a new update is a lot of PR 
> work is now being done and they're no longer lagging and the 
> expectation is sometime around August. Is that right part?
>
> Parth Bhatt: Based on the last couple of meetings. Yeah.
>
> Mahmoud Alkhraishi: A data integrity 2.0.
>
> Mahmoud Alkhraishi: So I believe these are currently occurring on 
> Friday morning calls. is there anyone on who can speak to it please?
>
> Will Abramson: I can…
>
> Will Abramson: unless somebody else wants to I can at least pick this 
> up. yeah, so I don't always attend these calls. I'm mostly involved in 
> the quantum safe crypto suite and also there's this schnore on here 
> which I guess theore integrity suite is really not a CCG work item yet 
> but I would like to make it one. I just haven't got around to doing 
> it. I do have some other editors or proposes I think Marcus said he 
> would be on it. And this basically is a crypto suite that uses the 
> same signature algorithm that the Bitcoin community uses. So shore 
> signatures over the cryptographic curb seps you can use that in the 
> same data integrity proof way to construct a valid proof and verify 
> proofs that are signed in that way. the quantum safe one is kind of 
> interesting.
>
> Will Abramson: So it started off using just a single algorithm MLDDSA. 
> This is all crypto suites or cryptographic algorithms that are 
> hopefully secure in a world with quantum computers. postquantum 
> cryptography. So it started off with just MLBSA and now just on the 
> side Mood if you look at all these algorithms. So I recently added a 
> whole bunch of other ones based on feedback right away. There's SSA, 
> SHS, there's Falcon, and there's S2I. So these are all different 
> cryptographic algorithms that kind of do the same crypto suite data 
> integrity process. And what's come out of this is kind of clear to us 
> and I think to anyone that really data integrity is there's a lot of 
> repeating itself right across the specs it's the same kind of thing.
>
> Will Abramson: Typically what you do is you fork a spec and you just 
> change a few minor things and then you publish it and you're like 
> there's my crypto suite right that's what I did when I developed sep 
> and that's bad right we don't repeat ourselves in code why are we 
> repeating ourselves in spec so there is an effort underway that I'm 
> going to try and work with manu and some others to refactor the core 
> data integrity spec or at least to look at what that refactoring would 
> look like because we can't change the core data integrity spec until 
> it's in a new working group but we want to make it much more 
> parameterized so that if you're de developing a new crypto suite, all 
> you need to do is specify some parameters really rather than writing a 
> whole new document that is basically repeat stuff all over the place. 
> it seems silly.
>
> Mahmoud Alkhraishi: Mhm. That makes a lot of Yeah,…
>
> Will Abramson: So that is exciting. Yeah. But yeah, please.
>
> Andrea D'Intino: and maybe I can also add something about the quantum 
> safe.
>
> Mahmoud Alkhraishi: that makes a lot of sense. Sorry about that.
>
> Andrea D'Intino: Yeah, because I think it was last week we presented 
> something to the W3CVC CCG and what we did show was our implementation 
> of W3C 2.0 that includes also a revised MLDDSA 44 W3C credential. And 
> I actually promised to update the file, but I haven't got to there 
> yet. I think I need some help. So, I'd be very happy if I can meet up 
> with someone and we can have a look at this together. But as of today, 
> what we can do and I can post you a link to that is a canonicalized 
> debut CVC with MLDDSA 44 signature and multibase public keys.
>
> Will Abramson: And Andre, if you want to reach out to me, I think you 
> were saying you need some help updating the spec, the quantum.
>
>
>       00:30:00
>
> Andrea D'Intino: Yes. All right.
>
> Will Abramson: Yeah, I'd be happy to help you with that. I'm sure I could.
>
> Andrea D'Intino: I'll drop your line.
>
> Andrea D'Intino: Thank you very much. I will post the link to the 
> stuff that we show last time.
>
> Will Abramson: Yeah, no worries. Okay.
>
> Mahmoud Alkhraishi: We did talk about Leroa last time. Has there been 
> any updates on this?
>
> Andrea D'Intino: Yeah, we did. That's also part of what we showed last 
> time two weeks ago.
>
> Mahmoud Alkhraishi: Awesome.
>
> Andrea D'Intino: We did integrate longfellow into our cryptovm zen 
> room and we demonstrated it working in a native Android app written in 
> Java as well as in the microser. We're now working on an SDK for 
> multiple languages to run it easily. So if anyone is interested in 
> that, you're most welcome to ping me. should I say a couple of words 
> about…
>
> Mahmoud Alkhraishi: Thank you so much, Andrea. That sounds wonderful. 
> Please
>
> Andrea D'Intino: what that is? So December last year a paper was 
> started floating around the internet from two guys at Google Matteo 
> FGO and Abby Shalat and this paper was presented around Europe a 
> couple of time at various conferences. We got in touch with them. They 
> told us that they were about to release some code which is written in 
> C++. So we got early access to that and we integrated into our 
> cryptovm. What does it do? It does it does zero knowledge proof for 
> identity starting from an mdl using circuit technology.
>
> Andrea D'Intino: So it starts from a regular M do credential and the 
> credential is run through a circuit and a 400 kilobytes proof is 
> produced and this proof is not only zeal proof…
>
> Will Abramson: Okay.
>
> Andrea D'Intino: but it also appears to be quantum safe. Welcome.
>
> Mahmoud Alkhraishi: Thank you, And Appreciate that. does anyone have 
> anything else they would like to share on the data integrity 0 All 
> right. On the VC test suites, normally this would go to Ben, but I do 
> not believe he's on the line. I know there's a lot of work that was 
> done last time for the test suites for March and this was because we 
> had to get a lot of it done for the VC working group. I don't believe 
> there's been any work done…
>
> Mahmoud Alkhraishi: but this is based on my limited knowledge. I do 
> not think there's been any shared out. I know there are regular office 
> hours for people who need access to this house. Yes.
>
> Will Abramson: Yeah, I don't see Benjamin on the call,…
>
> Will Abramson: but I will use this as an opportunity to shout out the 
> fact not the VC working group test, but working group is starting to 
> spin up an effort to create a similar thing for decentralized 
> identifiers and particularly for the DID resolution specification. So 
> if anyone on this call is or knows implementers of DID resolvers, we 
> would love to talk to them and we would love to work together to 
> figure out how do we create a test suite that your implementations can 
> demonstrate conformance against right like that would be excellent.
>
> Andrea D'Intino: We do have one.
>
> Will Abramson: There is a proto one in the CCG group, but the data 
> group is going to take that up and evolve it a bit, I think. Unless 
> you're talking, Andrea, about your company having one. That would be 
> great to know.
>
> Andrea D'Intino: Yeah, we actually have one. Perfect.
>
> Will Abramson: Okay, wonderful. Yeah, we can chat when we chat about 
> the quantum safe thing. That would be great.
>
> Mahmoud Alkhraishi: Thank you all. does anyone have anything else they 
> want to share on the working group testes?
>
> Mahmoud Alkhraishi: right. the CCG test. So this is did key one that I 
> think you were just talking about where it's going to be migrated to 
> the did working group and I'm assuming evolved to not just read key 
> but rather a generic did resolver test suite right?
>
> Will Abramson: Yeah. Yes.
>
> Will Abramson: Yes. I think so.
>
> Mahmoud Alkhraishi: Yeah. this is the VC API issuer one that I linked 
> to earlier and…
>
> Mahmoud Alkhraishi: this is a verifier as well. VC education are calls 
> that happen on Monday mornings.
>
> Mahmoud Alkhraishi: I don't know if anybody here is on from those 
> calls please.
>
>
>       00:35:00
>
> Will Abramson: Maybe Demetri or Phil.
>
> Dmitri Zagidulin: Hi. Yes,…
>
> Dmitri Zagidulin: I'm one of the chairs. and what's the question about it?
>
> Mahmoud Alkhraishi: So just a question is what are the big things that 
> have occurred since last March on the VC education and what are things 
> you want to share with the broader group and what are you currently 
> working on?
>
> Dmitri Zagidulin: Yeah, right so the group in general is a combination 
> of implementation demos but also basically dev teams in the education 
> realm implementing verifiable credentials coming across stumbling 
> blocks and so we present those stumbling blocks to the group and 
> discuss. So during the previous years we had a demonstration of using 
> render method for PDF talked about internationalization and 
> localization since a lot of the projects in that realm sort of involve 
> those. So it's that sort of thing.
>
> Dmitri Zagidulin: So over the past year we've had a issuer registry 
> project that was done jointly by credential engine MIT's digital 
> credentials consortium and a handful of other companies right where it 
> was a review of issuer registry specs including CCG's verified issuers 
> and verifiers and there was an implementation and sort report out for 
> implementing a registry using open ID federation specification. So 
> it's a lot of stuff like that.
>
> Dmitri Zagidulin: the current sort of main project is just gathering 
> together a gallery of verifiable credentials used in education as well 
> as trying to in build an informal matrix kind of like with the VC API 
> test suite except instead of a test suite this is more of a manual 
> okay We've been able to get credentials out of this issuer into this 
> wallet and here's the protocols that this wallet speaks. Here's the 
> data models that it displays that sort of thing. So surveys of the 
> field with an eye towards interoperability.
>
> Mahmoud Alkhraishi: Thank you,…
>
> Mahmoud Alkhraishi: Demetri. Alex, I believe you wanted to add something.
>
> Alex Higuera: No.
>
> Alex Higuera: I just unmuted myself in case Demetri wasn't going to 
> answer the question.
>
> Mahmoud Alkhraishi: Is there anything else anybody would like to add 
> on the VC education calls or specs in general? I see we have Ben, 
> sorry to put you on the spot, but would you be able to talk a little 
> bit about the VC test suites? Have there been any changes since last 
> time we walked through them?
>
> Benjamin Young: Sorry, double muted. yeah, there have been no new 
> changes as the specs are not themselves changing for the working group 
> at the moment. so the test suites continue the same, but we are still 
> adding new implementers. So if you are out there and have not yet 
> integrated with these, you can start with the VC implementations link, 
> which is not on that list. I'll paste it in the chat. and it has 
> instructions on how to join the list of implementations.
>
> Mahmoud Alkhraishi: Awesome. Thank you.
>
> Benjamin Young: That's it. Yep.
>
> Mahmoud Alkhraishi: Verifiable issuers and…
>
> Mahmoud Alkhraishi: verifiers. We have David or Isaac on.
>
> Isaac Henderson: Yeah, I'm Isaac.
>
> Isaac Henderson: So I'm here to give an update on it so we addressed 
> the comments and the feedbacks from the last meeting and also with 
> five issues in GitHub and the version 0.2 two data model of issuer and 
> verifier list has been updated. So you can see the data model of the 
> list with two use cases as education use case and also driving license 
> use case and we also provided the security recommendation how the 
> integrity of the list can be ensured using W3C data model at the end.
>
>
>       00:40:00
>
> Isaac Henderson: With the version two of the files actually so that's 
> also being there and updated actually currently so it is almost ready 
> for the promotion consideration as we have addressed the feedbacks and 
> so we would like to get any comments or feedbacks from the community 
> so that we could align ourselves towards the next step.
>
> Mahmoud Alkhraishi: Can I ask you to send out a message to the mailing 
> list saying that you believe the spec is ready for promotion…
>
> Mahmoud Alkhraishi: if that's where you think it is and you're looking 
> for feedback just so that because a lot of people aren't able to show 
> up on these calls…
>
> Mahmoud Alkhraishi: but they do respond to the mailing list.
>
> Isaac Henderson: Okay. Sure.
>
> Isaac Henderson: That we can do that Yeah. Yeah.
>
> Mahmoud Alkhraishi: Thank you so much.
>
> Will Abramson: And sorry,…
>
> Will Abramson: did I heard ready for promotion are you pl wanting to 
> get it through to a working group? Because obviously the CTG work item 
> does have a life cycle and the life cycle is you start it, you're 
> working on it, maybe you disband it, but also ideally you get to a 
> final product. Maybe that's where you want to get to, right? 1.0 
> version that we can publish, stamp on and get the WCC to put on their 
> website. these are our finished products if you like.
>
> Isaac Henderson: So the idea what David mentioned because I was not in 
> the last call as a part of the promotion meeting but he was there and 
> he said that actually yeah so the next step would be to go into this 
> working group model and…
>
> Will Abramson: Right. Mhm.
>
> Isaac Henderson: then also do some work there actually because we need 
> some refinements or get feedback from the community regarding which 
> are the attributes like mandatory and optional and these kind of 
> things so that to refine this list but this is a exclus that is part 
> of the next step actually which we are planning to Introduction.
>
> Mahmoud Alkhraishi: Thank you so much, did they link to resources? 
> This is Alex and anchor from checked. I don't believe either of them 
> are on today. last time they weren't on either but they did give us a 
> note saying that they had updated the supporting the alerts in the 
> universal resolver. I don't know if there's been any feedback any 
> sorry progress done since then. does anyone else have any updates or 
> any knowledge about this spec?
>
> Will Abramson: I do not,…
>
> Will Abramson: but I don't know if we can ask Joe to speak to his 
> adjacent work and where that conversation is. Is Joe on the call? I 
> think it's
>
> Mahmoud Alkhraishi: We can't hear you,…
>
> Mahmoud Alkhraishi: You're off mute, but there's no audio.
>
> Joe Andrieu: Yeah, there's a hardware mute. Sorry about that. I can't 
> speak to where Alex Nanker are with the DDL linked resources. we've 
> been working with them tegrate the DID traits stuff into the rubric. 
> So, that's sort of adjacent to this. there is a effort at the 
> decentralized identity foundation that is sort of a companion or…
>
> Mahmoud Alkhraishi: What are the trait stuff?
>
> Joe Andrieu: a competitor to the rubric which was designed to be a 
> simpler way to sort of programmatically evaluate whether or not a 
> given method has a particular trait. and it was just simple booleans 
> so that you could for example filter the DID method extensions to see 
> which particular did methods meet the criteria that you care about.
>
> Mahmoud Alkhraishi: That makes sense.
>
> Joe Andrieu: So we're working on integrating that with the did rubric 
> in a way that the two of those can play nicely together. Sure.
>
> Mahmoud Alkhraishi: Thank you, I believe that is all we had for today. 
> Does anyone have anything I know there's a couple of proposed work 
> items that are currently being considered to be added to CCG. This is 
> where I would call on Mano to speak to it,…
>
> Will Abramson: Yeah. …
>
> Mahmoud Alkhraishi: but he's not on.
>
> Will Abramson: I think we should talk about them briefly at least.
>
> Mahmoud Alkhraishi: Please.
>
> Will Abramson: Just to flag them. I mean, I'm not prepared to do this, 
> but I will share the links. maybe even you could open them.
>
> Mahmoud Alkhraishi: Yeah. Yeah.
>
> Will Abramson: So, the first one is verifiable credentials over 
> wireless. So this is a proposed work item two weeks ago. I think it's 
> going to get accepted. I' I've not been checking deeply but I haven't 
> heard any complaints right just plus one. I mean it's been open for 
> two weeks. We have shared it last week in the call. So I mean probably 
> this week I'm going to say yeah this is now a work item. So it's 
> becoming a work item and it is all about how do we transmit verifiable 
> credentials over wireless over NFC or Bluetooth or things.
>
>
>       00:45:00
>
> Mahmoud Alkhraishi: The last thing I heard about this was Brent raised 
> a similar u spec that is currently being worked on and man responded 
> with a list of differences between them.
>
> Will Abramson: Okay. Right.
>
> Mahmoud Alkhraishi: I haven't heard anything since. I think that's the 
> only quote unquote holdup to actually adopting this work item. If 
> there's any actual objections to it on that front.
>
> Will Abramson: So, that must have been in the mail list.
>
> Mahmoud Alkhraishi: Yeah. Yes.
>
> Will Abramson: It's not in the comments or anything. Yeah.
>
> Mahmoud Alkhraishi: That was in the mailing list, not in the comments.
>
> Will Abramson:
>
> Will Abramson: Right. Right.
>
> Mahmoud Alkhraishi: Yes. …
>
> Will Abramson: Yeah, we can talk about that. Maybe we'll wait to talk 
> with Manu, but I didn't get the sense that Brent was like holding it.
>
> Mahmoud Alkhraishi: I didn't get that either. I think it was just 
> asking a clarification question.
>
> Will Abramson: Yeah, great.
>
> Mahmoud Alkhraishi: Does anybody have anything they want to share on this?
>
> Will Abramson: Yeah. …
>
> Mahmoud Alkhraishi: Any other information on it?
>
> Will Abramson: if no I will just add I mean this is my sense from 
> digital bazar is that this spec is in pretty good shape and it is 
> implement like they've been using it is my sense so I don't know what 
> that means but it has been implemented it's not just an idea now 
> there's this other one…
>
> Mahmoud Alkhraishi: So was there any other spec? I think that's the 
> only spec that I know of that is currently being proposed.
>
> Will Abramson: which is more recent and I think we haven't shared it 
> with the group so 252 Yeah.
>
> Mahmoud Alkhraishi: The cryptographic event logs. Yeah, this one.
>
> Will Abramson: Yeah. I think Manu has shared this on the mailing list 
> before just the digital bazaar spec that is linked there.
>
> Mahmoud Alkhraishi: Is there Yeah.
>
> Will Abramson: But I guess it's the next step to bring it into under 
> the CCG.
>
> Mahmoud Alkhraishi: And I haven't seen any push back at all towards 
> this, I don't believe.
>
> Will Abramson: Maybe we give that till next week because I think that 
> was only raised this week.
>
> Mahmoud Alkhraishi: No. No. all right. Does anyone else have anything 
> they would like to raise or anything'd like to flag? Anything they'd 
> like to talk about with regards to current work items or future work 
> items?
>
> Mahmoud Alkhraishi: I know there's the website change that I think is 
> tangentially related to this which is Yeah.
>
> Will Abramson: Yeah, we can talk about that in a sec.
>
> Will Abramson: I'll just say one last thing about these work items. 
> So, this is for Bryce and also anyone else who is new and doesn't 
> really understand the W3C TCCG process. So, we're a community group at 
> the W3C which is pretty flexible like a working group is much more 
> rigorous in its approach. And in our community group, we accept Work 
> items is work done under the credentials community group banner and 
> has the credentials community group logo on it. And basically we have 
> the rule that anybody can propose a work agent. The only sort of 
> requirement is that you signed up to the W3C's IPR agreement.
>
> Will Abramson: which is pretty lightweight but it just means you're 
> not like trying to get a work item through our process that locks into 
> some IP that you've already got hold of basically. and the idea is 
> anyone can propose a work item. Obviously it should be loosely related 
> to digital interaction, decentralized identifiers that sort of genre. 
> And basically you propose a work item like this process as a template 
> issue that you can fill out. we like to have owners from at least two 
> different organizations. So hopefully Digital Bizarre because Kalia 
> says they are the ones who do a lot of the implementing. but I think 
> they managed to pull in other organizations too because we don't want 
> just one organization doing all the work. We want to make sure it's a 
> community effort, and what else was I going to say? Yeah. and 
> basically we accept any work. if people want to do the work, we accept it.
>
> Will Abramson: the only way we might reject or ask for that a change 
> to happen is if people can object to say no I don't want this in this 
> community right and then we'd have to work through that objection 
> hopefully to satisfy all parties if possible so basically that the bar 
> is quite low right we're not looking for 10 plus ones or whatever it's 
> just no minus ones basically I think that's everything I don't…
>
> Mahmoud Alkhraishi: Yeah.
>
> Will Abramson:
>
> Will Abramson: if anyone has anything else to add the W3C CCG 
> processes. And maybe that's a good segue to go on to the website that 
> Man's created because it does show a lot of the work items that we do 
> currently have ongoing in various forms.
>
> Mahmoud Alkhraishi: So I believe this is the currently proposed 
> website. This was shared on the community mailing list. Please make 
> sure that you review it. You get your feedback. It's a lot nicer than 
> the old website…
>
>
>       00:50:00
>
> Will Abramson: Could you drop a link to that in there? Yeah.
>
> Mahmoud Alkhraishi: which I'm not even going to show because the new 
> one. Yes. here it's a lot cleaner. It's a lot nicer. There's a lot of 
> nice little features like a list of all the current meetings and you 
> can join them and it makes it a lot easier for you to work through. 
> There's a list of use cases. This might need some work. If anybody 
> here wants to review specific re use cases and…
>
> Will Abramson: Totally. Yeah,…
>
> Mahmoud Alkhraishi: again this doesn't have to be perfect.
>
> Mahmoud Alkhraishi: It just has to be better than what we currently 
> have before we adopt it, And it's always a work in progress and we're 
> always happy to improve. And a huge thank you to Manu for, starting 
> jump starting this effort.
>
> Will Abramson: Yeah. I mean, I don't know. I'd love to hear what the 
> rest of the community thinks, but I'm inclined to just say, "Let's 
> ship it, it's good enough." the one point that I'm wary of is we 
> should ship it but we should ship it in a way that Manu is not the 
> owner of this thing right it needs to be a community effort and 
> ideally not Manu because he does a lot of work right just because he 
> created this first effort to change the website doesn't mean that he 
> should be the one you go to when you see an issue or need a change 
> request and I guess the last thing I would shout is like please anyone 
> on this call take some time five minutes 10 minutes whatever just
>
> Will Abramson: read over it and see if there's anything that you would 
> suggest to improve or any mistakes. Right. Cool.
>
> Mahmoud Alkhraishi: I think that concludes our call for the week. 
> Thank you for participating. And we'll see you all next week. Have a 
> great rest of your week.
>
> Will Abramson: Yeah, thanks.
>
>
>       Meeting ended after 00:52:10 👋
>
> /This editable transcript was computer generated and might contain 
> errors. People can also change the text after it was created./
>