 Then let's move on to our diligence task force. So this task force was set up a couple of months ago to take a look, a deeper look into existing implementations and the need by implementers when it comes to implementations of OpenID for verifier potential. It has been mentioned a couple of times in the presentations. I thought it would make sense to just briefly explain what it is, right? So OpenID for verifier credentials is one set of protocols that allows the issuance of credentials and the presentation of credentials. There are others like TITCOM, ISO stuff and so on. OpenID has been emerging during the last two years. It's done by the OpenID Foundation. That's the standardization body that also did or does OpenID connect and FAPI for example. There's a working group associated with that. It's called Digital Credentials Protocols Working Group. I'm one of the co-chairs of that working group and Joseph writes the conformance tests for it. So that's what it is. It was for example chosen by the European Union's expert group for EIDAS as one of the technical underpinnings of EIDAS beside ISO 18 or 13-5. So those are the major technical standards when it comes to protocols. And we are super proud of that and support that initiative with all we do. And one of the new work items we picked on in support of that initiatives and others is the OpenID for VC high assurance interpreter, the profile with SDJOT. It's called HYPE. It was also mentioned by two of the project maintainers. So it elevates or it profiles OpenID for the regulated use cases. And Susie in this presentation already mentioned OpenID for VP over Bluetooth for Energy, something we are really excited about because it extends the family to proximity use cases. And I think that's important because Verifyable Credentials, the unique feature of Verifyable Credentials is you can use them in all different sorts of scenarios online as well as proximity. And that should be seamless. We also have a security and trust document which is maintained by Daniel Fett, who you have seen in the SDJOT presentation before. Yeah. And there is a certification suite on the development. Right now we are able to test presentation interface of a wallet. And it's already being used by Joseph, three wallets? Yeah. Thank you. All right, thank you. Let's go back to the diligence task force. So the goal of the diligence task force is pretty simple. We would like to bring existing a new code that implements OpenID for VC to RWF. That's our goal. So, and in order to really do that, there are lots of other objectives. So first of all, we would like to implement what implementers want. We want to gather that input. And we want to deep dive with all the implementers into specifications. So the last couple of sessions, for example, Christina, or Christina Yazuda, who is the other co-author or co-chair of the DCP working group and one co-author of OpenID for VC, we ask or we answer questions by implementers, which prove to be very useful. But we are still surveying existing implementations. So we have a huge sheet. I'm gonna show it to you where we really have feature sets and the existing implementations so people can really also again, compare what's in it for me. And it also helps implementers to figure out where are gaps? What is missing? What do I need to do next? We also provide implementers of projects that are not necessarily already at OWF. We provide them a space to demonstrate and to show their implementations, clearly with the intent to convince them to come and join the team, right? So, yeah. And we are contacting those implementers and try to figure out whether OWF would be a good place for hosting their work. Yeah, I think the last point, meanwhile, is obsolete because we have inbound implementations of OpenID for VC. But we originally planned also to come up with a plan on what is needed and in the end, yeah, construct a project proposal. Right now it looks like there is the contribution by Ping, Mossap, and also Lizzie and Esato that implement a protocol and there are other implementers we are on discussion with. So those are the implementers that we have been working with. So you see, none of the contributions we proposed today are on the list so there are even more implementers that are interested to come to OWF so it's pretty amazing. Yeah. Just to give you an idea how the sheet looks like, so what we did is, and it was mainly Hakan who runs this group has really broken down the different features of the, for example, OpenID for VP. Specification. And then we have columns for each of the implementations and now we try to figure out what is supported by which of those implementations which again helps implementers to understand what they can do with which project. It's a tremendous work and kudos to Hakan for that. We are hoping that all the implementers use that as a chance to also present their project and their features to interested developers. Yeah, that's the current scope and progress. So for OpenID for VCI we have created 70% of the criteria. As a spec writer, I have to admit there are two people that are really in my neck right now. This is Joseph because he always wants to be, to know in detail what I mean with certain text and it's Hakan because Hakan tries to break down that into the features in the sheet and we realize Christina and I myself, we realized, okay, we need to improve the spec a bit to make their life easier. So that's already really a good feedback loop we have here. So we're not done yet with the implementation criteria for OpenID for Verify Prodentary Issues but we are done with the criteria for OpenID for Verify Presentations and a lot of implementers already filled the table and the cells you have seen already. And there is another protocol I did not mention which is called PSIOP V2. This is a protocol for doing pseudonymous authentication with the wallet. So you can use the wallet, can set up a new connection for a certain relying party and can use that and it's basically a key pair managed by the wallet that is then used for subsequent logins with the wallet. This is also part of the family and it's also being used in the IITUS context. We have already broken down all the criterias and now waiting for the implementers to fill in. For OpenID for BLE, we haven't started yet to work on that. But it's ongoing work. If you want to chimp in, the group meets every other Tuesday, five o'clock CST. But you can also find that on the OpenVollet Foundation calendar. Yeah, bi-weekly meetings. Yeah, I recalled it correctly, five PM CST. We have a GitHub repo, we have the worksheet and we communicate using the Discord of OpenVollet Foundation. Are there any questions on the divisions task force? You like it? Okay, cool. Right, so we are largely ahead of schedule which is due to the fact no one asks questions, I guess. So I would like to sum up the mini-summit. So anyone here in the room wants to share his or her impression about that. Have you gained what you were looking for? That's very important to us. I mean, we need to figure out whether that format makes sense going forward, right? If it is useful for people. What do you think? Mission accomplished, right? We want you to look into the project, yeah. And I took note and what I'm really amazed about is we have seen projects for three different protocols. Didcom, ISO and OpenID, which to me are the main protocols in the credential space today. And there's also one other project inbound for VC API. Unfortunately, somehow the maintainers didn't react on my impulse. So we have four protocols going forward in OWF which really demonstrates we are open to all kinds of contributions, right? And people can get code for the technology they are looking for in decentralized identity. We also have seen credentials from ISO, ISOMDoc. We have seen SDJOT, JSONLD and Anocrats. So at least four different credential formats. So there's really is really, yeah, diversity. We have seen online protocols and we have seen proximity protocols. So the physical world and the online world and most notably almost all projects are production grade. That's really cool. So with that, thank you for coming.