[MINUTES] CCG Atlantic Weekly 2025-11-04

Here's a summary of the W3C CCG Atlantic Weekly meeting held on 2025/11/04:

*Meeting Summary*

The meeting focused on a discussion and demo led by Andrea D'Intino
regarding EUDIW conformance, interoperability, and the marketplace.

*Topics Covered*

   - *Introductions and Announcements:* Harrison Tang announced the
   upcoming election for the CCG co-chair position and provided details on the
   election timeline. Will Abramson thanked Harrison for his contributions.
   - *EUDIW Interoperability Project Demo:* Andrea D'Intino presented a
   demo of a solution designed to aid in automated end-to-end interoperability
   testing for wallets, issuers, and verifiers. The demo included the use of a
   marketplace, DSL scripting for generating credential offers and
   presentation requests, and integration with testing frameworks like Maestro
   and Temporal.
   - *Discussion on Interoperability Challenges:* The discussion touched
   upon the reasons for the current lack of interoperability, which include
   the loose nature of standards, the various ways in which issuers and
   verifiers can be conformant, and the complexity of protocols.
   - *Future Plans:* Andrea outlined the next steps for the project,
   including completing the GUI for setting up automation pipelines, inviting
   users to test, and potentially offering recurring testing as a paid
   service. The marketplace will remain free.

*Key Points*

   - The project aims to facilitate automated end-to-end interoperability
   testing for wallets, issuers, and verifiers, addressing the current
   interoperability challenges in the EUDIW context.
   - The solution uses a marketplace for wallets, issuers, and verifiers,
   DSL scripting for managing interactions, and integration with automated
   testing frameworks.
   - The project is targeting launch by the end of November and will be
   announced on the W3C CCG email list.

Text:
https://meet.w3c-ccg.org/archives/w3c-ccg-ccg-atlantic-weekly-2025-11-04.md

Video:
https://meet.w3c-ccg.org/archives/w3c-ccg-ccg-atlantic-weekly-2025-11-04.mp4
*CCG Atlantic Weekly - 2025/11/04 11:58 EST - Transcript* *Attendees*

Alex Higuera, Andrea D'Intino, Benjamin Young, Denken Chen, Dmitri
Zagidulin, Erica Connell, Greg Bernstein, Gregory Natran, Harrison Tang,
Ivan Dzheferov, James Chartrand, JeffO - HumanOS, Jennie Meier, Joe
Andrieu, Parth Bhatt, Rob Padula, Ted Thibodeau Jr, Vanessa Xu, Venu R,
Will Abramson
*Transcript*

Harrison Tang: We'll start in about a minute.

Harrison Tang: Hey, Good to see you again.

Harrison Tang: All right.

Andrea D'Intino: Good morning.

Andrea D'Intino: Can you hear me now? Awesome.

Harrison Tang: Thanks. All right. to this week's, W3C CCG meeting. thanks
for joining live again with us every week. today we have Andrea here to
actually lead a discussion and demo for EUDIW conformance interoperability
and marketplace. so u very exciting always like to see new stuff and new
applications of our work here at W3CCG.

Harrison Tang: but before we get to the main agenda, I just want to go
through some administrative stuff. so first of all, just a quick reminder
on the code of ethics and professional conduct. I just want to make sure we
continue to hold constructive respectful conversations here that we always
have. now a quick reminder on the intellectual property. Anyone can
participate in these calls. However, all substensive contributions to the
CCG work items must be member of the CCG with full IPR agreement signed.

Harrison Tang: so if you have any questions in regards to getting a W3C
account or the contributor license agreement please feel free to reach out
to any of the chairs and these calls are automatically recorded and
transcribed and the system will automatically send out audio recordings and
transcriptions in the next few hours. All right, I just want to take a
quick moment for introductions reintroduction. So, if you are new to the
community and want to just say hi, please feel free to just unmute. All
right, just want to take a moment for announcements reminders.

Harrison Tang: So, I'll start with a announcement from myself. So, I just
sent out an email. so, my three-year term as the CCG culture is actually up
at the end of this year. So, yeah, it has been a fantastic three years to
be very frank. I actually didn't realize this has been three years. So, it
has been a very fun educational journey. that every turn right every
banquet has to come to the at the end day we live in a democracy right so
there's no permanent dictatorship or anything like that.

Harrison Tang: so my turn is up. if you know someone who will be interested
in actually run for the W3CG co so please feel free to just reach out to us
or send a email to the list. will I be running for election? we'll see, if
no one else wants to do it and no, I can continue to do I mean, I'll be
very frank.
00:05:00

Harrison Tang: I think while it has been a lot of work it is a pretty good
excuse to meet very interesting thought leaders right in the space. So it
has been a very very educational journey for myself. so I found it very
very fulfilling to be very very frank. But I said, I think if we can have
someone new, right, who can step up and new leadership in the community,
that's always a good thing. So I would encourage other people to
self-nominate or nominate others, right? And then because at the end of the
day, we always want to have new bloods, in the community. But I will always
be here to help. Okay.

Harrison Tang: I sent out in the email there is a instruction on how you
can do it right so at the end it's pretty self-explanatory so you can
self-nominate or if someone who you want to nominate you can do that too or
if you have questions about why I sent out feel free to reach out to any of
coaches but I think the email instruction should be pretty
self-explanatory. Okay. thanks

Will Abramson: Yeah, I just wanted to echo what Harrison said and really
thank you Harrison for all the work you've done for this community over the
last three years. I mean, I think the CCG is a welloiled machine now and
it's in no small part thanks to you. So, I'm sure I'm saying what many
people in this community think, but thank you. and I wanted to also invite
anybody who is thinking about this to reach out like it is a fun,
opportunity to step up and contribute and help this community move
forwards. and if you're interested, just reach out and we can have a chat
about it and no pressure. Thank you.

Harrison Tang: Thanks Will. Yeah, I want to give a quick shout out to my
co-chairs right Will and Mamu as well. They have been a great help. So big
thanks and again biggest thanks to everyone in the community right whether
it's Dimmitri Andrea right Malu I mean I can't name name everyone but I
mean everyone here has been so helpful and also just been teaching me a lot
so I just wanted to say a big thank you as well all right anyway so we're
going to run this election

Harrison Tang: process from November 17th which is till December 10th so
yeah and the goal is that we have the election results by mid December and
the term starts beginning of next year which is January 6 2026. I just
noticed that there's a little typo in my email. The new term actually
starts on not 2025. All right, any questions on the process? All right.
yeah. So, just, if you have any questions, feel free to, reach out to any
of the chairs.

Harrison Tang: and first of all we would welcome and encourage self
nominations or if you want to nominate someone else or know someone who can
help advance our community please do so or just email me, Will and Mamoon
and then we'll try to make All right. So, any other announcements
reminders? So, we have quite a bit of great talks and events coming up we
have so many. It's booked till next March. So, yeah.
00:10:00

Harrison Tang: So I think next week we'll have Frank to talk about VC
implementations in the community resilience project and then the week after
that we'll have Keith en Jensa from DGC to actually talk about digital
trust and interoperability standards and approaches in Canada. so we have
those people coming on and then of course we have great schedules speakers
presentations coming up till actually next March but if you have any
recommendations or things that you think that you would want us to invite
here at W3CCG feel free to just reach out to us.

Harrison Tang: for example, I think last week someone mentioned that Wayne
Wayne Chong has present I think it's Phil shared that Wayne has presented
on the state endorsed visual identity a very good presentation at the IW.
So we actually have him scheduled for next March March 17. So when we'll be
talking about state endorsed digital identities next March you have any
thoughts especially on agentic identities because I think that's one of the
topics that people have been talking about sharing earlier this year that
they want to hear more about if you have those talks that you want to want
us to schedule and put on the calendar just reach out to any of the coaches

Harrison Tang: All Any other announcements, reminders? What item related
stuff,…

Harrison Tang: Let's get to the main agenda. So again, very excited to have
Indra here. he always lead great discussions. I always learn so many new
things. And then to put you on the spot. I heard you're gonna do some demo.
So that's gonna be exciting. So Andrea, the floor is yours.

Andrea D'Intino: Thank you Arizona.

Andrea D'Intino: You're way too kind. I'm very happy to be here. I see a
bunch of people. Very exciting. I really wished he was here. Okay, I'm
going to give him a one to one day soon.

Andrea D'Intino: Okay guys, so we have started working on Audi wallets
three years ago two years and a half three years ago. very soon we realized
that interoperability would be a mess just because the standards are very
loose and the protocols themselves are very open for VP the use there were
very very little definitions of use cases. So the use cases were also very
very very wide we started working on this for Audi but as it is now this
can be used probably in W2C VC and W2C as well.

Andrea D'Intino: I'm gonna explain you how. But after a few months on
working our own wallets, we thought of building something that could help
the community testing performance and interperability. So this software
came out. I think we are 75% done. We have the last major feature. We got
it working last week and we're building the UI around it. Can you all see
my screen? Yes, I think so.

Harrison Tang: Yep.

Andrea D'Intino: So, that's the demo or simply it's going to redirect. if
you just open the page, you will see something very similar.

Andrea D'Intino: you will just see that you're not logged in but you can
create an account here by the usual ways user and password or Google. So
that's the home of the solution. The first thing you see is explore the
marketplace or start a new check beta. Let's first look at the marketplace.
o that's a demo effect. Let me try to Okay, someone is redeploying as we
speak. You have to give me a minute. Hold on a second. Yes, it actually is.
Yes. Yes, right now. Let me just hold on. So, you see no available server
and in here we go. Okay.
00:15:00

Andrea D'Intino: a very nice side feature of the software is that we have a
setup where the software is deployed automatically every time we merge up.
So we started here I clicked on explore marketplace and I land here and we
have wallets credential issuers/credentials verifiers slash case
verification and custom checks. Let me just quickly show you the First I'll
show you the content of the marketplace. Then I will show you how to fill
the marketplace and then I will tell you how to use it. So let's pick this
one. This is the latest version of the wallet from the reference
implementation for Audi.

Andrea D'Intino: So you have metadata here, some text, and then we have a
downloadable APK, and this very weird thing that I'll be talking about for
about half an hour later, actions wallet setup. That's a piece of YAML that
looks a lot like a script. And in fact, it is. Let's go back to the
marketplace. Let's look at r/credentials. So this one is not a real issue.
This is a collection of u issuance use cases that are hacked together from
third party issuers. for example, if you read here, you will see who they
are and what they do. let me pick this one for example. So this is taking
some time to load.

Andrea D'Intino: If you look at this part of the credential offer, so this
is open for VP. It can work for anything else as well. I'll show you how.
if you look at this thing here, I will refresh the page. So, this starts
for 5985. No, or No, maybe this is the unique ID. One of those this one
changed. So, this is 08b. Before it was 50 or something. What are we doing
here?

Andrea D'Intino: We have a script that queries the issuer and based on how
the issue is done it manages to get the credential request and print it out
here. And the very first use you can think about it of this is that I want
to try to use a wallet on this. Let me try to use a wallet. I will use Tala
which is the best that we found so far. So what you see here is my phone.
So I'm going to open a QR code. Try to scan this. Something is happening.
I'm getting a P. Continue. Skip.

Andrea D'Intino: didn't work. Okay, so the intro probably didn't work, but
the whole process got started. So, what did we see so far? we saw this. Let
me move my phone away. So, we saw a script for mobile wallets and a script
for the issuer to pull a credential offer. The same mechanism we can use it
for the verifiers. So here in the same fashion where I separated issuers
from credentials we also did it here. So the verifier here is basically
just metadata while use case verification is a script that pulls offer a
presentation request sorry open for VP. is this clear for anyone in the
room?

Andrea D'Intino: I guess that everyone is familiar with the money for VP.
All right, I'm going to show you how to populate this if you want to add
your wallet, your issuer and your verifier. So you click on developer
dashboard. Here you have wallets, credential issues, credentials, verify
verification, custom check, we leave it alone for now. So in wallets I have
a bunch of wallets.

Andrea D'Intino: where each wallet is basically metadata. You can actually
import the wallet from the store if it's published and you can also add a
version that is tied to an APK. we don't use iOS yet, but we'll get around
it. And for a wallet, you can write an action which is this. I'm going to
show you how this works. If I want to add an issuer, if the issuer has a
static as a static issuance.
00:20:00

Andrea D'Intino: So if the well-known is always the same and doesn't
change. So you don't have any session number, you can simply import the
well-known and it said that it found 24 credentials that you're going to
see. I'm going to save it for now. So that is the one I just imported and
for each of them there is a credential offer that is generated that is
static. you can use it on the marketplace but the vast majority of issuers
do have a session ID inside the credential offer. So what we came up with
is using a DSL called stepci which you can see here.

Andrea D'Intino: So It's a DSL implemented that you can write in YAML that
allows you to do rest calls and do some minimal dec manipulation. So here
there's a script that already works. That's the thing that showed you on
the marketplace before. You press run and it generates secure code exactly
like the one I showed you before. The same thing you do for verifiers and
use case verification. So this is our MISK verifier and this is how you
generate a QR code to start the verification process. So why do we want all
of this? the main purpose of this application is to do automatic automated
end to end interrupt testing.

Andrea D'Intino: meaning that you write a script to set up your wallet or
someone else's wallet. you use a script to generate a credential offer from
some issuer. Then you use another script to generate a presentation request
from a verifier. You put them together and you run all of them in an
emulator or a simulator using a technology called an automated testing wave
from framework called Maestro which you can see here. So we have integrated
one and two into the solution. And what I'm going to show show you now is
the result.

Andrea D'Intino: So one of the nice features of myestro is that it can
capture videos of the scripts running in emulator. So this is an actual
video that is about a week old. I would like you to keep an eye on this
open dollar deep link to see what happens with this. So here first a
certain app is launched on the emulator then something magic happens here
then buttons are pressed on the app and I will show what happens next.

Andrea D'Intino: So you see that this turned into a credential offer
meaning that behind this there is actually something like it is precisely
this one. Now it just enters the pin code otherwise the wallet won't go
further. This part has to be scripted for each wallet. Then you tap on add.
Look what happens now.

Andrea D'Intino: Now the browser is opened. this is the authorization
server So that's the emulator talking to authorization server. We have to
enter user and password. In this case the user is Philippo and password is
Bravo whatever. Then we didn't record the very last step, but basically we
got to the end and pressed the sign in which is what allows you to get the
credential. how is this going to look like? So the stuff that you saw is
executed via a YAML file looking like this.
00:25:00

Andrea D'Intino: And I'm going to give you more informations in a second.
So this temporal we'll skip it for now. Then we have steps on boarding
running on mobile automation which starts a script to the initial setup So
every time you install a wallet on a phone, you have to probably type your
pin. You have to do a little bit of setup. So that is the setup here. We
are calling this I can show you what it is. It's in a different deployment
but it's basically this thing here it has a canonized unique URL.

Andrea D'Intino: So here you have the user which in my case is for Vivian
Andrea digital credential issuers that's the name of the issuer it's
actually this one and then you have the name of the credential which is
this. So first here we fire up the emulator we pass it an APK and we start
an on boarding script. Then we we pass the credential offer to the
emulator. So here we are back on the Android emulator. We pass it the
output of this step and we go on with the flow and we have recorded equal
true.

Andrea D'Intino: What I can show you a work in progress from today because
we got this thing working but right now it works only scripted. We are
working on a GUI to set up automation pipelines. this is the very very
first version. So the pipeline will allow you to choose a wallet action the
credential deep link use case verification. You compose them here and here
you end up with a YAML that will be then used for the automation process.
Are there questions already?

Andrea D'Intino: I've been speaking for 15 minutes and I showed you quite a
lot of things.

Harrison Tang: I don't see any question the queue but I think my question
is earlier you mentioned about DSL domain specific language so my question
is why do a domain specific language as opposed to a standard language
what's the pros and…

Harrison Tang: cons of this design choice

Andrea D'Intino: because we needed to be able to run this in multiple
different places.

Andrea D'Intino: So for Maestro, this is a framework to run testing
automation. There are three or four of them. We picked this because it has
a visual editor. It's pretty easy to use.

Andrea D'Intino: So this one it's part of the framework we use to do mobile
automation. That SECI is something we found that would fit what we do. In
reality, it's not very well maintained. So I think we'll drop it at some
point. But it is something that we need to be able to execute in a safe
environment. it is stored in a database and then passed to an execution
engine later on. So we can't really have you writing Python here. Maybe
TypeScript. We will see. but for now that's a solution we found. we think
we'll integrate multiple scripting frameworks for that.

Harrison Tang: Got it.

Harrison Tang: Cool. Thanks.
00:30:00

Andrea D'Intino: This pipeline that you see will be integrated in the start
and…

Andrea D'Intino: your check part. So here you will have a section called
interrupt automation where you will be able to select a pipeline or to
create one. this section this is already working. It has been working for a
while. what we wanted to do here is allow people to do automated
conformance testing of wallets, issuers and verifiers. So far we only got
this part done because those are the only tests that are around basically.
So if we have to test protocols and credentials inside we only found the
tests from the open ID foundation.

Andrea D'Intino: In reality, something is broken. So, that I cannot show
you because we just merged the PR and things will not work anymore. Anyway,
we have the Open ID Foundation tests and we also have tests from a European
large scale pilot called EWC. Okay, that's the PR that we just deployed.

Andrea D'Intino: Let me tell them. the idea is that you start here and then
you pick a certain standard. let's see. Let's say we pick this one here.
You would have a list of configurations. Then you could go on to set up the
parameters you want and you would land here and this is the heart of the
solution. we integrated in the solution.

Andrea D'Intino: So we need to have a framework to manage tests in a way
that is repeatable so that the whole input and the whole output is
notorized. So what we did is we integrated temporal I don't know how many
of you have heard about this. This is a framework written to do automated
testing. it's used mostly for people purchase cards for ehops. And what you
see here, this is a test I did run before that failed. Those are the logs
from the open ID foundation tests. this was the failure. Here we have the
whole input and the whole output. And those are all the steps in between
which each of them has a unique ID.

Andrea D'Intino: time stamp. So basically vrpi I can rerun a test that has
been run before change any parameters I can just schedule it. So, long
story short, we're working on a composer that allows you to put together
actions to script the wallets along with getting credential offers and
verification flows. All of this is going to end up in tests. Here on the
right side, you will have a button to rerun the tests.

Andrea D'Intino: you will have a button giving you something like a swagger
so that you can call the test with this parameters via rest API and you
will also have a button called schedule where once you have the right setup
so once you have the right actions to do the automated testing you can tell
run it every Sunday at midnight and as I mentioned before you can call it
via rest API

Andrea D'Intino: Iel as soon as you have a new version of your wallet, your
issue of your verifier deployed or as soon as you want to test it, you can
just inject the parameters in the test and run test again. If the test
fails, it will record the video so you can see what failed. And I think
that was my demo. Yeah, this is targeted to people who implemented issuers
and verifiers and are looking to have interoperability. If you ever build
your wallet to work with your issue, your verifier, you want you can use it
to test if things fail.
00:35:00

Andrea D'Intino: But the main purpose of it is introduating and performance
testing. So we were both for the marketplace and the tests we got we were
deeply inspired by what Manu did on VC playground as well as on canivc.com.
this part here this course is something you will see here. We haven't
implemented yet. And the reason we haven't implemented it is that we want
the result the stuff that you can see here. We want it to come from the
test that people run in real time. so first we put this in production. As
soon as people will start writing tests, the output of the test will go in
a scoreboard that will be updated in real time.

Harrison Tang: By the way, Andra earlier so this is question more like for
the QA testing tools that you've used.

Harrison Tang: So earlier you mentioned you use a mash ma maestro and then
the stepci and then also yeah and also the temporal.

Andrea D'Intino: Yeah. Yes.

Andrea D'Intino: Temporal. Yeah.

Harrison Tang: So what are the differences? I'm just curious. Yeah.

Andrea D'Intino: So this is something under the hood. this is managing the
whole automation flow from behind. And you actually may choose not to
interact with it a lot.

Andrea D'Intino: So temporal returns you this kind of things. So This one
failed.

Harrison Tang: So it's kind of like a test registry basically.

Harrison Tang: Is that what it is or

Andrea D'Intino: Yes. Something like that.

Andrea D'Intino: it's a big piece of Go that you can integrate with
different things and it runs several steps and for I mean this is the full
input and the full output and for each step in this case it's only one it
notorizes everything this is temporal myestro is the framework that allows
you to upload an APK and a script to an emulator. So right now we have our
own which is a modified version of ADB but we will also use at some point.

Andrea D'Intino: So this thing you see here is my ro and stepci is what
executes this script and…

Andrea D'Intino: returns this. So right now we're very focused on Audi but
in reality whenever you have a protocol that produces a deep link to offer
a credential to request a presentation this can work exactly the same way.
So this is completely agnostic to what is behind it.

Harrison Tang: Got Cool.

Harrison Tang: Thank you. Any other questions or comments?

Ted Thibodeau Jr: I'll just say what I put in the chat there. I strongly
urge you to have the auto deploy go to a staging point and only replace the
sort of live test when the new build is confirmed to work as well as the
old build.

Andrea D'Intino: Yeah, I know.

Andrea D'Intino: But Jim was still in beta. So this is the beta and…

Ted Thibodeau Jr: Understood. But it keeps demos like this flowing,…

Andrea D'Intino: this is the outcome.

Ted Thibodeau Jr: Not that anything you're doing is bad,…

Andrea D'Intino: Yeah. Yeah. Yeah. That was just No,…

Ted Thibodeau Jr: just it keeps the other things working better.

Andrea D'Intino: but the thing is that normally it's meing PRs, but this
time someone else did. So I was unprepared. But I showed you 80% of What I
want to show you. it's a catastrophe and…

Ted Thibodeau Jr: Fair enough.

Harrison Tang:

Will Abramson: Yeah, I just wondered if you had any insights about the
state of interoperability within the UD context. Have people been exp using
this currently?
00:40:00

Andrea D'Intino: that's why we have a bunch of people that started writing
I mean if I show you here. No, that is the real off. So, this one allow not
to work. But for example, this thing was a This was a third party did it.
we have a bunch of people that started working on it. we have two people
that deployed it in house and people in the Audi world they're very happy
to see something like this because interability is non-existing. so far I
can tell you that we found maybe two instances of issuer working with
someone else's wallet.

Andrea D'Intino: But in 95% of the cases if company XY Z has a wallet issue
verifier that issue and that verifier work only with the wallet and the XYZ
wallet works on doesn't work with somebody else's issue verifier and…

Will Abramson: Okay.

Andrea D'Intino: the other way around. So right now everyone has their own
full solution and they test it by themsel because that's the only thing
they can do. This is Yes,…

Will Abramson: And…

Will Abramson: have you been engaging with at the policy level what are the
EU folks saying about requiring or trying to push people towards being
interoperable so that doesn't

Andrea D'Intino: there are two large scale pilots running. we are in the
largest one which we built there. We are in the architecture working group
plus we are talking with three national authorities that's will be charged
with putting together a wallet accredititation path as well as a credential
catalog.

Will Abramson: Thanks.

Andrea D'Intino: So this should serve both purposes.

Harrison Tang: By the way, I'm curious, Andrea, what are the main reasons
of lack of interpretability? Is it because people are using different
crypto suites or is it because the schema doesn't match?

Andrea D'Intino: so it's a mix of both so first of all in open ID for there
is multiple levels of complexity so the crypto schemes

Harrison Tang: And then if it's because of the issues in different schemas,
couldn't like a gentic AI help, Because LM is actually quite good at
mapping schema.

Andrea D'Intino: are some of it because you can use different kind of
signatures but the transfer protocols are also very loose. there are many
ways for an issuer to work in a way that is conformant. There are many many
ways for a credential format to be conformant. And the same is true for the
verification part.

Andrea D'Intino: So it is just built to be very loose and I believe it's
one of the first time ever that interro is tested as this size among
different countries in so what has been done before historically is that
people did sit down and decide a very strict set of rules to get things
going. But on purpose is left very open to be expandable in the future.

Andrea D'Intino: So this thing that you saw here this composer that I mean
this is the first screenshot ever and…

Harrison Tang: Thank you. what's next on this credini project?

Andrea D'Intino: the screenshot is from today. I think we'll get this
working at some point next week. When we have that working, we can start
inviting people and guiding them to setting up the whole flow for
themselves. So we have already on boarded some people but we did most of
the work for them ourselves. We hope that a little snowball effect will
happen because I mean right now everything is changing but for example the
marketplace works already.
00:45:00

Andrea D'Intino: So if you create your issuer and your verifier here then
other people can come and test with their wallet. So the next step is
getting this to work and then growing this. So our business model is that
some point we will charge for recurring tests because they have to run on
some cloud that we have to pay. But the marketplace will be free forever
and then we'll see how this is shaped in the future.

Harrison Tang: Any other questions or comments? So, last question for me,
Andrea, is like when do you expect this to launch? And then obviously feel
free to send to the W3CTG email list when it's available.

Harrison Tang: But yeah,…

Andrea D'Intino: Yeah. this is the last thing working.

Harrison Tang: when do you expect to launch? Yeah. Mhm.

Andrea D'Intino: So we need this to get up and running and we work a little
bit more testing. till definitely before the end of the year.

Harrison Tang: Sounds good.

Andrea D'Intino: Hopefully the end of this month.

Harrison Tang: That's fast.

Andrea D'Intino: But we've been working on this for two years and a half.
It's been a very very very project. Absolutely.

Harrison Tang: Yeah, yeah, just send it to the list when it's launching and
let us know. I will help promote it too. I think this is very very
critically important for our community.

Harrison Tang: test suites and interoperability. So yeah, thanks

Andrea D'Intino: Yeah. Yes.

Andrea D'Intino: And think we mentioned to man at some point that we can
integrate the VCAPI tests. we haven't done it yet but because we're
focusing on LD but we can definitely integrate the CA VC API tests. I think
I spoke to Will about those ones, but yes, we can definitely integrate them
and we can have people to test automation and also in the W3C world.

Harrison Tang: Sounds good. All right. Last question.

Andrea D'Intino: Thank you. Bye.

Harrison Tang: Thanks, love always loves seeing demos. So, this is,
amazing. Hey, All right. This concludes this week's W3C CCCG meeting. Have
a good one. Bye.
Meeting ended after 00:48:15 👋

*This editable transcript was computer generated and might contain errors.
People can also change the text after it was created.*