14:23:38 RRSAgent has joined #vcwg 14:23:43 logging to https://www.w3.org/2026/04/01-vcwg-irc 14:23:43 RRSAgent, make logs Public 14:23:44 please title this meeting ("meeting: ..."), ivan 14:23:48 Meeting: Verifiable Credentials Working Group Telco 14:23:49 Agenda: https://lists.w3.org/Archives/Public/public-vc-wg/2026Mar/0014.html 14:23:49 chair: brentz, phila 14:23:49 ivan has changed the topic to: Meeting Agenda 2026-04-01: https://lists.w3.org/Archives/Public/public-vc-wg/2026Mar/0014.html 14:47:17 TallTed has joined #vcwg 14:59:00 phila has joined #vcwg 14:59:50 present+ 14:59:59 present+ shigeya 15:01:30 JoeAndrieu has joined #vcwg 15:01:42 present+ 15:02:01 present+ elaine 15:02:09 brent has joined #vcwg 15:02:13 present+ 15:02:14 present+ JoeAndrieu 15:02:25 present+ 15:02:33 present+ dlongley 15:02:56 present+ xavier 15:03:13 present+ kayode 15:03:42 present+ 15:03:48 present+ susanne 15:04:04 Wip has joined #vcwg 15:04:09 present+ 15:04:29 present+ wip 15:04:50 present+ jennie 15:05:02 scribe+ 15:05:12 present+ parth 15:05:24 brent: Welcome to the weekly VCWG call 15:05:45 ... We are meeting under our new charter. Lots to cover today. Mostly about workmode and how we want to handle all the various specifications 15:05:59 brent: First, anyone want to introduce themselves? 15:06:13 JennieM has joined #vcwg 15:06:24 shigeya: Shigeya from Keio univerity. Was involved previously 15:06:57 q+ Susanne, Patrick, Henrique 15:07:06 Kayode: Hi I am Kayode Ezike, been involved in the CCG specs. Happy to contribute 15:07:21 present+ 15:07:28 ack Susanne 15:08:00 q? 15:08:12 Susanne: Susanne Guth-Orlowski, I am involved with digital product passports. Have brought this concept into european standards work. I hope to contribute to the work 15:09:17 Elaine has joined #vcwg 15:09:24 ack Patrick 15:09:25 kezike has joined #vcwg 15:09:32 hxavier has joined #vcwg 15:09:45 present+ 15:09:52 DPPSusanne has joined #vcwg 15:10:05 ack Henrique 15:10:08 Patrick: My name is Patrick, been involved in CCG work for the last four or five years. Interested in VCALM spec. Also interested in education and other topics like traceability 15:10:22 q? 15:10:26 q+ Elaine 15:10:36 ack Elaine 15:10:42 Henrique: I am Henrique Xavier, from Brazil. I am here to follow up with the age verification discussions going on there 15:11:22 Elaine: I am Elaine Wooton, I am a specialist in design of secure document e.g. drivers licence. I am going to be leading the Verifiable Credential Barcode spec 15:11:33 dmitriz has joined #vcwg 15:11:43 brent: I am often not looking at the hands in zoom, if you are able to join IRC that would be very helpful 15:12:02 brent: moving forward 15:12:28 ... Welcome everyone, I'm Brent Zundel a standards guy at Yubico, I have been chairing this group for a while 15:12:35 Topic: F2F Meeting 15:12:47 My name is Susanne Guth-Orlowski, Expert in Digital Product Passports and Digital Identity Wallets, European Regulation, JTC24 Standards on DPP System and Framework, UN/CEFACT Experts on UNTP and supply chain data exchange. 15:13:00 brent: F2F meeting scheduled. GS1 has offered meeting space in Brussels, we will be meeting June 2nd to the 4th 15:13:17 -> Email with details of F2F https://lists.w3.org/Archives/Public/public-vc-wg/2026Mar/0005.html 15:13:17 ... There will be 2.5 days of meeting with optional side group meetings the day before or after 15:13:25 ... let us know so we can make sure the space is available 15:13:31 https://docs.google.com/spreadsheets/d/1-pdqKbDNeB255x5BTVhoUKnVzXwVVl3fRHfSTWIpccE/edit?gid=138060477#gid=138060477 15:13:44 https://docs.google.com/spreadsheets/d/1Emo_yVt90Z5xnHNBPhShO4B7zYQ7kwMfNcOa6sKAdoc/edit?gid=179611341#gid=179611341 15:13:55 ... There is a spreadsheet available for sign up. See the link above 15:14:14 ... Let us know if you are able to attend 15:14:42 ... We have no set agenda yet, let us know if there is anything you definitely want us to cover and we can do our best to include 15:14:51 I have a full day assignment from the European Commission that week, but I can join in late afternoon or evenings. 15:14:57 Topic: FPWD VCDM 1.1 15:15:26 brent: We are chartered to do maintenance of the VCDM. We will release a 1.1 version of the spec 15:15:29 q+ 15:15:51 Wip: Isn't it 2.1 15:15:55 s/1.1/2.1/ 15:15:56 brent: Yes, it is 2.1 thanks 15:15:58 Vasilis has joined #vcwg 15:16:13 present+ Vasilis 15:16:40 brent: Working on a proposal for the FPWD 15:17:35 PROPOSAL: Publish a first public working draft of Verifiable Credentials Data Model 2.1 using the short name vc-data-model-2.1 15:17:42 +1 15:17:42 +1 15:17:44 +1 15:17:44 +1 15:17:45 +1 15:17:45 +1 15:17:45 +1 15:17:47 +1 15:17:47 +1 15:17:48 +1 15:17:53 +1 15:18:10 +1 15:18:23 RESOLVED: Publish a first public working draft of Verifiable Credentials Data Model 2.1 using the short name vc-data-model-2.1 15:18:37 Topic: New Charter overview 15:18:42 PatStLouis has joined #vcwg 15:18:48 https://www.w3.org/2026/03/vc-wg-charter.html 15:18:56 brent: This is a link to our new charter 15:19:33 ... We are charted through the end of March 2028 15:20:06 ... We have a lot of work to do. Motivation, background and scope are the same. We no longer have protocol work marked out of scope though 15:20:37 q+ to talk about Echidna for render and confidence 15:20:41 ... We have new normative specs - many. See the charter 15:20:43 q- 15:21:13 ... The BBS spec is essentially done, just waiting for a normative spec for the BBS crypto from ietf I think 15:21:14 ack Wip 15:21:25 ack phila 15:21:25 phila, you wanted to talk about Echidna for render and confidence 15:21:40 q+ to respond 15:21:49 q+ 15:22:04 q- 15:22:06 q++ 15:22:09 phila: Related to render method and confidence method, the echidna system does not seem to be properly configured. So from the specs the publication date is not showing latest changes 15:22:16 q+ 15:22:22 ack + 15:22:26 +1 for echidna setup 15:22:36 ack ivan 15:22:36 ... Echida is designed to continously update the published document with the latest text as we push updates to the repo 15:22:55 ivan: For render method, this is not a problem of setting up Echida. It is setup correctly 15:23:23 ... The HTML is incorrect. The extension to ReSpec handling the graphics is creating an error. We need to get the mermaid extension properly working 15:23:37 ack brent 15:23:37 brent, you wanted to respond 15:23:41 ... The confidence method, I havent looked at it. We did setup echida though 15:23:43 q+ 15:23:55 I have made the request to generate https://www.w3.org/2026/04/01-vcwg-minutes.html TallTed 15:24:02 brent: The previous iteration of the WG resolved to always use echida 15:24:10 q+ 15:24:15 ... We are continuing to work under that resolution 15:24:20 ack JoeAndrieu 15:24:25 ... How bad would it be to use something other that mermaid? 15:24:49 JoeAndrieu: I think we might be well setup, we just haven't had any PRs accepted 15:24:55 ack manu 15:24:57 ... I will try the loop and reach out if there are issues 15:25:15 q+ 15:25:25 q+ to help with mermaid 15:25:31 manu: Re using other than mermaid. I will look into that this weekend, if I can't fix the bug then I will export images and use those 15:25:46 q- later 15:25:48 ... Hoping to fix the bug though. 15:26:02 ... Using images means we will have to generate prose for the images 15:26:05 ack JoeAndrieu 15:26:05 JoeAndrieu, you wanted to help with mermaid 15:26:36 JoeAndrieu: manu reach out to me about mermaid stuff, Kevin Dean and I have been working through this plumbing in the past. I might be able to help 15:26:38 ack phila 15:27:10 phila: I know lots of work has gone into the Confidence method. Can you please get a PR in, to see a more recent date than October 2025 15:27:16 JoeAndrieu: Happy to do that 15:27:29 brent: Back to the charter 15:28:20 previous meeting: https://www.w3.org/2026/03/11-vcwg-minutes.html 15:28:20 next meeting: https://www.w3.org/2026/04/08-vcwg-minutes.html 15:28:20 ... In addition to this set of documents, there are also tentative deliverables. These are just as deliverable as other items in are charter pending having people willing and able to do the work. Including people willing to be editors for this work 15:28:27 I have made the request to generate https://www.w3.org/2026/04/01-vcwg-minutes.html TallTed 15:28:36 ... See the charter for the list of tentative deliverables 15:28:46 q+ 15:28:49 ... As long as there are people to do the work, the group can begin work on thesespecs at any time 15:29:20 ... Additionally, we are charted to maintain VCDM, Data Integrity and the existing cryptosuites, CIDs and bitstring status list 15:29:56 ack manu 15:29:57 q+ 15:29:59 s/Henrique:/hxavier:/ 15:30:01 ... Any issues raised against these specs we will triage. Mostly editorial changes will get in. Others will be queued for later work 15:30:36 manu: The quantum safe cryptosuite, is being worked on by Greg. Google have moved up there post quantum timeline by 6 years 15:30:51 ... We may want to nudge this work forwards at a faster rate than expected 15:30:54 q+ 15:31:02 ... May need reprioritizing 15:31:07 ack ivan 15:31:28 s/Patrick:/PatStLouis:/ 15:31:30 ivan: Coming back to the maintenance items. There are some exceptions on the rule for making normative changes 15:31:40 ... Any security issues that require normative changes are allowed 15:31:41 I have made the request to generate https://www.w3.org/2026/04/01-vcwg-minutes.html TallTed 15:32:08 ack phila 15:32:11 present+ hxavier, PatStLouis 15:32:12 ... The VCDM has references to the two extension documents that we already work on, changes to the spec that are related to these are allowed even if normative 15:32:51 phila: I wanted to talk to the product passport work. There are people joining the working group and the W3C to get this work done. 15:33:04 brent: Any questions? 15:33:06 Topic: VCWG Work Mode 15:33:24 brent: We have a lot that we want to accomplish 15:33:34 ... A single weekly meeting is not going to be sufficient 15:34:01 ... The way we have been operating for the last few months, is to have alternative meetings or task forces focused on the individual specifications 15:34:26 ... E.g. render method and confidence method. They meet, discuss and then report back to the main group where they need input and review 15:34:27 Not sure, when I was expected to speak up, but I am ready to work on the Digital Product Passport Vocabulary as editor. 15:34:39 ... The chairs believe this has gone well and propose using this moving forward 15:35:16 ... The W3C process enables us to create task forces. Members of task forces can manage the calendar. Participants of the task force will see these updated calendar events 15:35:24 q+ 15:35:26 ... We feel this maps well with the work mode we are looking to pursue 15:35:36 ... Looking for feedback and input from the group 15:35:49 q+ 15:35:53 ... We were imagining a task force per specification that we are pursuing as a group 15:35:57 ... Open to other suggestions 15:36:00 ack ivan 15:36:42 ivan: A task force gets its own mailing list. It also creates its own github team, that can be used on specific repos 15:36:57 ... This is done automatically. It will take some time to setup each task force 15:37:46 brent: For those who have not been involved with the VCDM, most of the work related to this group happens in Github. Commenting on issues and PRs etc. 15:38:06 ... If anyone is not comfortable with Github, please let us know and I would be happy to help you get up to speed 15:38:16 ... Please dont let unfamiliarity with the tools stop you from engaging 15:38:28 ... Do reach out if we can support you 15:38:32 ack manu 15:38:49 manu: +1 to the work mode plan. It maps well. 15:38:53 I would need a refreshment on GitHub and the best practice on how it is used for W3C standards. Thank you. 15:39:01 ... I want to make sure we don't overdo it in terms of process and mailing list etc 15:39:28 ... Are we moving over the new google meet infrastructure? And could we do that by next week? 15:39:47 ... I think VCALM is ready for this, maybe verifiable issuers and verifiers too 15:40:06 q+ 15:40:06 brent: For the task force calls, yes use the google meet infrastructure and autoscribing 15:40:16 ... We anticipate also beginning to use that in the main call 15:40:23 q+ 15:40:29 ... There are a couple of things it would be nice to tweak here 15:41:02 q+ to talk about TF meeting timing 15:41:10 ... Also, yes you can begin meeting next week. If you already have a meeting time, then I dont have a problem with that group continuing to meet. Please as much as possible use W3C infrastructure etc 15:41:11 I would need a refreshment on best practice on how to use github for W3C standards. Thank you. 15:41:38 ack ivan 15:41:40 ... I am hoping the infra setup will be done by next week. Please meet either way 15:42:00 ivan: I dont have any objections regarding google meet. I have two comments 15:42:28 ... I dont know how to setup google meet entries for all the groups. The W3C infrastructure is based on zoom. 15:43:17 ... The other thing to keep in mind is there might be some competition here. Otto is exploring in the DIDWG, how to use zoom to generate an auto scribing in IRC. This is probably some weeks or months away 15:43:27 q+ to speak to Google Meet details, Zoom details, moving specs over, bundling meetings. 15:43:43 q- later 15:44:01 ivan: Different topic. Presume that many of the documents currently discussed are on the CCG github. These should all be moved across to the W3C github. This is something I can do. 15:44:19 ... At least if they are on the CCG repository. Other github repos, are more challenging 15:44:36 ... This is important, for patent policy approach 15:44:42 ack Elaine 15:45:11 Elaine: I dont think there is an existing home for verifiable credentials barcode. We need to make one, perhaps we could share this time with another work item 15:45:17 ... We need to decide on another time 15:45:30 brent: Hoping we have time today to go into the logistics 15:45:43 ... Otherwise please use the VCWG mailing list to make those arrangements 15:46:00 ... Aternating with other task forces makes sense if groups do not need weekly meetings 15:46:06 ack manu 15:46:06 manu, you wanted to speak to Google Meet details, Zoom details, moving specs over, bundling meetings. 15:46:12 ... The chairs are not going to organize this, just establish guardrails 15:46:32 manu: Responding to ivan, I am aware of the zoom alternatives. I think the zoom tool will be a better solution longterm 15:46:44 ... In the meantime, I wanted to get up autoscribing and autopublishing 15:47:04 q+ 15:47:04 ... +1 to moving the repos over. I set ivan as admin on all these repos 15:47:18 manu: AWaiting a couple of people to sign of on the IPR for the specs 15:47:30 ... +1 to Elaine's suggestion to bundle meetings 15:48:03 ... Suggest bundling the barcode with the data integrity at least. Idea being to rotate agendas. Idea being we meet weekly and progress relative issues 15:48:18 ack phila 15:48:18 phila, you wanted to talk about TF meeting timing 15:48:20 ... One of the concerns here is not getting enough eyes on the work as it progresses, bundling can help 15:48:25 q+ 15:48:48 phila: Please be aware when setting up task force meetings, new people have joined and they do not necessarily live in the EU and US 15:48:57 ... keep this in mind when selecting meeting times 15:49:24 brent: One option is for our main call to also alternate. We have tried this in the past, but have always struggled with engagement 15:49:30 ... Happy to try this again 15:50:00 ... Please self organize as task forces. The chairs will make sure the main meetings have agenda, notes and sit within the W3C process 15:50:13 ... Task forces will also need an agenda shared at least 24 hours before the call 15:50:31 ack brent 15:50:33 ack JoeAndrieu 15:50:35 ... Additionally there needs to be a github repo under the W3C. Sounds like that is in progress. Just being explicit 15:51:01 q+ 15:51:07 JoeAndrieu: manu, I think we might be open to bundling. However, what we are exploring is finding a better time give denkeni is based in Taiwan 15:51:07 ack denkeni 15:51:32 q+ 15:51:57 denkeni: I am starting to setup an APAC series in the CCG. I will try to get momentum in the APAC region. Aim to move people interested in the spec work to the relevant task forces 15:52:00 ack ivan 15:52:00 q+ to note australia time, EU time, ask questions about main call agenda... what are we going to use it for? 15:52:19 https://github.com/w3c/vc-wg/ 15:52:20 ivan: To make these things practical, I need some help. 15:52:57 q+ for editors 15:53:08 ... The WG has its own github repo. Please raise an issue for each task force telling me the name, shortname and responsible people of the task force 15:53:21 ... Also the repository you want me to move across to W3C 15:53:38 ack manu 15:53:38 manu, you wanted to note australia time, EU time, ask questions about main call agenda... what are we going to use it for? 15:53:40 brent: I think using issues in the vc-wg github repo is a great idea 15:53:54 manu: Noting the APAC/EU/US timezone challenges 15:54:17 ... We are already moving the verifiable recognition call to a time that can work with austrailia 15:55:00 elaine has joined #vcwg 15:55:21 q+ to answer manu 15:55:23 ... Wondering about the interplay between the main working group and the task force. How are we going to ensure the main working group is up to speed about the latest decisions being made across the task forces 15:55:39 ack brent 15:55:39 brent, you wanted to discuss editors 15:55:57 q+ to ask about confidence and render method task force logistics 15:56:05 brent: Good question. We have been talking about leaders of task forces. From the chairs perspective, the editors of the specifications are leaders of the task force 15:56:36 ... For each work item, that is going to be a task force, we want to know who is willing to be involved, who is going to be an editor, when are calls going to happen 15:56:40 ack phila 15:56:40 phila, you wanted to answer manu 15:56:47 phila: My view is we will need to discuss with ivan as we go forward 15:57:13 +1 to phila 15:57:22 +1 15:57:23 ... We will need to make best use of the main VCWG call time. I see it as an important coordination role. Whether you are actively taking part in these task forces, you should know what the work involves for each of them 15:57:25 +1 Phil 15:57:32 +1 that sounds good 15:57:35 ack JoeAndrieu 15:57:35 JoeAndrieu, you wanted to ask about confidence and render method task force logistics 15:57:41 +1 15:58:01 JoeAndrieu: On confidence method, I like the idea of the main call having 1 or 2 task forces reporting in per call 15:58:11 ... The aim being to bring people up to speed across the WG 15:58:13 +1 to Joe 15:58:30 q+ 15:58:37 ... The other item, I think both render and confidence method are setup in github and don't need additional logistics 15:58:48 brent: Some logistics are included. Eg. meeting time 15:59:18 ack ivan 15:59:21 ... Additionally, there will actually be a defined task force for these other work items. If you are interested, please join 15:59:57 brent: For confidence and render method, there will be some steps that arent needed. But still some work required to setup the formal task forces etc 16:00:36 ... This will take some time. Ask for patience. Keep working in the meantime. Feel free to use the main mailing list as required 16:00:51 brent: Thanks for your time today 16:01:13 rrsagent, draft minutes 16:01:14 I have made the request to generate https://www.w3.org/2026/04/01-vcwg-minutes.html ivan 16:01:23 bigbluehat has joined #vcwg 16:50:27 dmitriz has joined #vcwg 16:55:53 rrsagent, bye 16:55:53 I see no action items