14:31:51 RRSAgent has joined #vcwg 14:31:55 logging to https://www.w3.org/2026/05/06-vcwg-irc 14:31:55 RRSAgent, make logs Public 14:31:56 please title this meeting ("meeting: ..."), ivan 14:32:15 zakim, start meeting 14:32:15 Meeting: Verifiable Credentials Working Group Telco 14:32:15 Agenda: https://www.w3.org/events/meetings/d811d954-dd65-4cce-844a-53dfd95e75c7/20260506T110000/#agenda 14:32:15 RRSAgent, make logs Public 14:32:17 chair: brentz 14:32:17 ivan has changed the topic to: Meeting Agenda 2026-05-06: https://www.w3.org/events/meetings/d811d954-dd65-4cce-844a-53dfd95e75c7/20260506T110000//#agenda 14:32:17 please title this meeting ("meeting: ..."), ivan 14:58:15 Olvisgil has joined #vcwg 15:00:25 brent has joined #vcwg 15:00:32 present+ 15:00:49 present+ 15:00:50 hsano has joined #vcwg 15:00:57 present+ eva 15:01:12 present+ ivo 15:01:15 PDL-ASU has joined #vcwg 15:01:17 ted has joined #vcwg 15:01:23 present+ 15:01:27 present+ ted 15:01:32 present+ 15:01:36 IvoLadenius has joined #vcwg 15:01:43 present+ 15:02:23 kezike has joined #vcwg 15:02:23 present+ susanne 15:02:26 present+ 15:02:34 present+ 15:03:02 present+ schmittner 15:03:07 dppSusan has joined #vcwg 15:03:18 Sebastian has joined #vcwg 15:03:27 Wip1 has joined #vcwg 15:03:27 present+ wip 15:03:35 present+ 15:03:39 present+ bigbluehat 15:03:57 present+ tallted 15:04:07 present+ joe 15:04:21 wes-smith has joined #vcwg 15:04:22 present+ 15:04:24 scribe+ 15:05:18 brent: welcome everyone to the VCWG meeting. We are meeting under the IPR agreements folks have signed as members. If you are here and are not yet a member of the WG or W3C, please let us know how we can help. 15:05:43 ... Today we will discuss the face to face meeting, vocabularies, the Data Integrity task force, and VCDM maintenance. 15:06:16 q+ 15:06:43 jandrieu: We have the first meeting of the confidence method task force tomorro 15:06:45 JoeAndrieu has joined #vcwg 15:06:48 s/tomorro/tomorrow. 15:06:49 bigbluehat has joined #vcwg 15:06:55 present+ 15:07:05 Olvisgil has joined #vcwg 15:07:07 https://lists.w3.org/Archives/Public/public-credentials/2026May/0006.html 15:07:15 manu: The CCG has published the final CG version of the post-quantum cryptosuite. 15:07:41 present+ carolynn 15:07:44 ... Another general announcement on groups like VCALM, recognized entities, etc is that we are preparing to do a bunch of threat modeling work for horizontal review. 15:08:15 ... the VCALM work will probably have the most involved threat model. 15:08:55 present+ 15:09:19 present+ 15:09:25 Ok then: present + dppSusan :) 15:09:26 Topic: F2F Meeting 15:09:43 present+ dppSusan 15:09:53 brent: We are having a face to face meeting in Brussels at the beginning of next month. We are building an agenda and anticipating talking about threat modeling and each task force. 15:10:23 present+ 15:10:28 ... If there are other topics folks would like to cover please let us know. 15:10:36 q+ to invite folks to the after party 15:11:10 carolynn: is there an agenda yet? 15:11:24 brent: We are in the process of building the agenda. 15:11:34 q+ 15:11:38 carolynn: There was discussion of a vocabulary meeting but I would prefer to cancel that. 15:11:56 Carolynn has joined #vcwg 15:11:57 brent: There is an option to do a vocab meeting on Thursday afternoon. 15:12:04 carolynn: That does not work for me either. 15:12:07 q- 15:12:08 ack manu 15:12:09 JoeAndrieu 15:12:12 ack JoeAndrieu 15:12:12 JoeAndrieu, you wanted to invite folks to the after party 15:12:26 JoeAndrieu: Friday morning some of us are playing disc golf, if you can fit that into your schedule we would love to have you. 15:13:07 brent: Let's do some introductions, if you are on the call and have not said hello we invite you to do so. 15:13:09 q+ 15:13:16 ... Let us know who you are and what you are hoping to work on. 15:13:23 ack ted 15:13:59 ted: I work for GeoTab, heavily involved in automotive standards. I used to work for W3C. We are working on vehicle specific Verifiable Credentials with COVESA. 15:15:12 Olvisgil: Pleasure to be here. I'm an invited expert, member of ISO and do standards work in European groups, excited to be part of this work, especially related to DIDs and PCs for payments. 15:15:19 s/PCs/VCs 15:15:24 q+ 15:15:30 ack ivan 15:15:49 ivan: If anyone would like to join any of the task forces please send me an email. 15:16:18 brent: Currently the process to join a task force is manual and needs ivan, we are hoping to automate this. 15:16:22 Topic: PQ Data Integrity Task Force 15:16:31 ... The next topic is the post-quantum Data Integrity task force. 15:16:57 For Ted, DPP vocab meetings are Mondays 16h30-17h30 Paris time. 15:16:59 https://lists.w3.org/Archives/Public/public-credentials/2026May/0006.html 15:17:00 q+ 15:17:00 ... The CCG release a CG final report, using the DI framework with post-quantum algorithms. This is within the charter if there is interest. 15:17:08 ... Do we want to form another task force for this? 15:17:09 ack manu 15:17:26 manu: The good news is that we do not have to, the VC Barcodes/Data Integrity call already contemplated including the post-quantum work. 15:17:41 ... There is crossover there in post-quantum security over physical barcodes. 15:18:25 ... It's possible that the work will expand such that we need a separate task force, but should be fine for now. 15:18:43 q+ to ask when that might be 15:18:48 brent: When there is something to share or a FPWD we will get that on the agenda. 15:18:53 ack manu 15:18:53 manu, you wanted to ask when that might be 15:19:56 manu: A question is, in theory we could move the document over to FPWD, typically we want to see IPR agreements from major committers, largely right now it's Greg Bernstein and folks from Digital Bazaar. I think we're waiting for 4-5 signatures to establish the main IP, and at that point we can pull it over. Question to the group: once we get those 15:19:56 signatures, should we work with ivan to migrate it over to the WG? 15:20:00 ... We already resolved to move it. 15:20:24 brent: yes, that makes sense since we have already resolved to do so. 15:20:38 ... Next up we will discuss vocabularies. 15:20:53 Topic: What to do with Vocabularies 15:21:10 subtopic: https://github.com/w3c/vc-wg/issues/12 15:21:42 JennieM has joined #vcwg 15:21:46 present+ 15:21:59 ... ivan raised an issue in the VCWG repository. When the VCDM 2.0 was published, the WG decided to consider the vocabulary to be normative, but the context to not be normative. As a result the vocabulary was published at a stable link where it could be retrieved and where folks could look at the normatively supplied hash value of the document. 15:22:43 ... There are a number of task forces that are doing their own vocabularies, with some intention of adding terms to the VCDM vocabulary. It's important that this group have a conversation about how to handle that, since the vocabulary is a normatively defined document. 15:23:11 ... There are some things where it would be straightforward to say additions to the VCDM make sense, where some additions might not make as much sense. 15:23:34 q+ to propose a general direction 15:23:49 q+ 15:23:56 q- 15:23:59 qq+ 15:24:06 ack ivan 15:24:06 ivan, you wanted to react to manu 15:24:11 p+ 15:24:39 q+ Carolynn 15:24:47 s/qq+// 15:25:01 q- 15:25:38 ivan: At the moment the vocabularies are defined in different formats. Three different formats have been copied to a stable place in W3C space. Additionally, in the VCDM spec there is a hash that is generated for the JSON-LD version of the vocabulary and normatively referred to. 15:25:55 ... The hash value is normatively defined. 15:26:49 ... I have been glancing through some of the new specifications, and most of them define new vocabulary terms. VCALM may be separate, since I don't think it defines terms in the JSON-LD sense, terms for a protocol are slightly different. 15:27:09 ... It would be good to make a decision in advance on where these terms will go. 15:27:49 ... Another question is regarding the hash, we are not supposed to change that without changing the version of the rec. 15:28:44 ... We also must make structural decisions about the vocabularies. 15:28:54 ack manu 15:28:54 manu, you wanted to propose a general direction 15:29:42 manu: +1 to everything that ivan said, and we need to be careful about making them. We are probably going to have to decide on a case-by-case basis whether these vocab terms go into the core VCDM or not. A general rule is "are these terms generally applicable to the ecosystem, or are they focused on a market vertical or some other vertical". 15:30:22 +1 to keeping it decentralized 15:30:27 ... For the things related to a specific vertical, those can exist independently and do not need to be merged into the core. The purpose behind the way we built this ecosystem is to encourage decentralized innovation, no need to recentralize here. 15:30:28 +1 to the idea that application-specific vocabs are stand-alone (and can be used outside of VCs !) 15:31:29 q+ 15:32:07 +1 for specialized vocabulary for domain-specific terms 15:32:15 ... The render method work is a good example of the kind of stuff that should be added to the main VCDM, things like the barcodes are less clear and the task forces should discuss individually. 15:32:47 ... The general approach is to do this on a case-by-case basis, if it's per-vertical, leave it out of the VCDM, if something crosses verticals it is a good candidate for putting in the VCDM. 15:32:58 ack ivan 15:33:19 ivan: That sounds good but is only part of the problem, another issue is that we need to have some level of consistency among all the documents and vocabularies. 15:33:49 ... So far, what we did is create a GitHub folder that contains HTML, JSON-LD, and Turtle versions of the vocabularies. 15:34:24 ... We develop this as a document on GitHub without formal status in terms of W3C, then when the document goes to Rec we move it to W3C space to make it stable and provide the appropriate redirects. 15:34:40 ... And we add the JSON-LD hash into the specification. The question is, is this the approach we use for all of them? 15:35:33 ... It would be good if URLs for these things could be consistent and easy to find. 15:36:02 ... An orthogonal question is where are the JSON-LD files and who maintains them. 15:36:12 q+ to note "you say mess", I say "decentralized" :) -- we should have this list of decisions that need to be made somewhere. 15:36:19 ack manu 15:36:19 manu, you wanted to note "you say mess", I say "decentralized" :) -- we should have this list of decisions that need to be made somewhere. 15:36:58 manu: Yes, we need concrete answers to those things. I feel that the way we have answered these questions in the past has been fairly successful. Some of this comes down to allowing innovation outside the group (i.e. decentralization). 15:37:20 +1 to some extra urls being a good trade off to enable innovation and decentralization 15:37:28 ... ivan, you went through a fairly long list of items, perhaps we should have a unified place to make these decisions for all the groups. 15:37:43 q+ 15:37:48 ... I think the approach is unified, but we should write down the results in a single place. 15:38:02 ack ivan 15:38:25 ivan: I'm happy to gather all the material in one space and put it into a markdown document on the WG repo. 15:38:32 That sounds like a great path forward, thank you for taking that on, Ivan! 15:39:25 Topic: VCDM Maintenance 15:39:35 https://github.com/w3c/vc-data-model 15:39:39 brent: next and final topic is VC Data Model maintenance. 15:39:50 q+ 15:39:55 ... There are currently no open pull requests, so we will start with issues. 15:40:06 ... There is one issue with no labels, we will look at that first. 15:40:27 subtopic: http://github.com/w3c/vc-data-model/issues/1627 15:40:49 manu: This feels like an LLM generated issue. I don't quite know what they're asking for. 15:40:53 ... It feels largely editorial. 15:41:05 q+ 15:41:21 ack manu 15:41:24 ack brent 15:41:45 q+ 15:41:46 brent: I had the same experience. It's unclear what changes they are requesting. 15:42:00 ack JoeAndrieu 15:42:03 ... My inclination is to propose closing this, happy to hear other perspectives. 15:42:13 perhaps we need a new github tag "AI Slop" ;-) 15:42:35 q+ to agree with Joe, it's more cordial. 15:42:48 JoeAndrieu: I also think we should close it. This is a request to have a use case added, we have a use case document, we could respond by saying they could propose this over there. If there is a human behind this, maybe there is something here that would fit the use case document. 15:42:49 q+ 15:42:52 ack manu 15:42:52 manu, you wanted to agree with Joe, it's more cordial. 15:42:59 +1 to close with no action ... and we might need to start saying more about our requirements around AI generated issues 15:43:30 manu: +1 to requesting they raise a use case PR. 15:43:39 ack ivan 15:43:42 +1 to requesting they raise a PR 15:44:10 ivan: The person's GitHub profile is inactive. I think it should be closed. 15:44:36 +1 to Brent's comment and action 15:44:37 +1 to brent's suggestion. 15:45:31 q+ 15:45:48 ack bigbluehat 15:47:15 brent: ivan will close the issue, I will add a label and add the discussed comment. 15:47:34 subtopic: https://github.com/w3c/vc-data-model/issues/1628 15:47:39 q+ to speak to digestSRI 15:47:44 ack manu 15:47:44 manu, you wanted to speak to digestSRI 15:48:08 manu: This was raised because in another spec, I think recognized entities, the concept of should we use digestSRI or digestMultibase keeps coming up. 15:48:59 ... The reason we support two digest schemes is because we couldn't agree on a single one. This is impacting downstream specs that build on the core data model. My suggestion is that we deprecate digestSRI because it is the less flexible of the two. We don't need to remove it from the spec, just mark it for deprecation/removal in 3.0. 15:49:30 ... If anyone really likes the feature they can add it into the vocabulary for their use case. 15:50:06 ... There were companies that pushed for digestSRI, we may want to ask them where they are on it currently. 15:50:23 q+ 15:50:30 ... The proposal is to deprecate digestSRI. 15:50:33 ack ivan 15:50:49 ivan: whoever writes the PR should ping me so the term can be deprecated in the vocabulary as well. 15:50:56 manu: I'll take this PR if we have consensus. 15:51:18 +1 to deprecate digestSRI 15:51:35 +1 for the proposal to go forward with standardizing the use of digestMultibase and deprecate digestSRI 15:51:41 brent: I will ping folks that are no longer members of this group that pushed for digestSRI in the past. 15:51:43 q+ to ask if anyone is using digestSRI and cannot live with digestMultibase? 15:51:49 ... I am not hearing any objection from the group here. 15:51:54 ack manu 15:51:54 manu, you wanted to ask if anyone is using digestSRI and cannot live with digestMultibase? 15:52:00 q+ to briefly address iso 15:52:13 manu: I want to know if anyone in this group has implemented and is currently using digestSRI and they will not be able to use digestMultibase. 15:52:49 ... Let me look at the implementation report, to see if it shows who is using this feature. 15:53:25 ... The test was to support either, we did not split them apart. 15:54:02 brent: If we don't hear from the people we reached out to, there is no opposition to moving forward as proposed. 15:54:27 subtopic: ISO PAS 15:55:07 q+ to ask if we can do standards-track WDs on ISO PAS? 15:56:13 ivan: We have a pattern for an explanatory document that has to be produced for the PAS process. Hopefully this conversion will become straightforward. 15:56:19 ack ivan 15:56:19 ivan, you wanted to briefly address iso 15:56:23 ack manu 15:56:23 manu, you wanted to ask if we can do standards-track WDs on ISO PAS? 15:57:01 manu: At what stage can we submit something for ISO PAS? Can we do a preliminary on a working draft that is standards track? Can we submit it as a provisional to ISO PAS, to let them know that we intend to take it through the PAS process? 15:57:12 q+ to add color 15:57:37 ivan: The PAS process means that it is a recommendation. Informally, depending on what contact you have with the related ISO group, there is a possibility to give them a version for pre-review (CR). 15:58:22 ... This can shorten the PAS process. 15:58:28 ack brent 15:58:28 brent, you wanted to add color 16:00:00 rrsagent, draft minutes 16:00:02 I have made the request to generate https://www.w3.org/2026/05/06-vcwg-minutes.html ivan 16:01:07 rrsagent, by 16:01:07 I'm logging. I don't understand 'by', ivan. Try /msg RRSAgent help 16:01:11 zakim, bye 16:01:11 leaving. As of this point the attendees have been ivan, manu, eva, ivo, PDL-ASU, ted, brent, hsano, susanne, kezike, dlongley, schmittner, wip, TallTed, bigbluehat, joe, 16:01:11 Zakim has left #vcwg 16:01:14 ... wes-smith, JoeAndrieu, carolynn, Olvisgil, dppSusan, JennieM 16:15:48 q+ 16:24:10 TallTed has joined #vcwg 16:24:10 shigeya has joined #vcwg 16:24:10 dlehn has joined #vcwg 16:24:10 cel has joined #vcwg 16:24:10 jyasskin has joined #vcwg 16:24:10 manu has joined #vcwg 16:24:10 dlongley has joined #vcwg