14:41:25 RRSAgent has joined #vcwg 14:41:29 logging to https://www.w3.org/2026/08/05-vcwg-irc 14:41:29 RRSAgent, make logs Public 14:41:30 please title this meeting ("meeting: ..."), ivan 14:41:40 Meeting: Verifiable Credentials Working Group Telco 14:41:40 Agenda: https://www.w3.org/events/meetings/b1a3e329-74d1-405d-ab47-2934b41c2ab4/20260805T110000/ 14:41:40 chair: brentz 14:41:40 ivan has changed the topic to: Meeting Agenda 2026-08-05: https://www.w3.org/events/meetings/b1a3e329-74d1-405d-ab47-2934b41c2ab4/20260805T110000/ 14:59:27 present+ 14:59:40 phila has joined #vcwg 14:59:43 hsano has joined #vcwg 15:00:14 michaelshea has joined #vcwg 15:00:32 present+ michaelshea 15:00:36 present+ 15:00:40 present+ phila 15:00:59 present+ saad 15:01:22 present+ olvis 15:01:26 Elaine has joined #vcwg 15:01:26 dmitriz has joined #vcwg 15:01:36 brent has joined #vcwg 15:01:43 present+ brentz 15:01:57 present+ 15:02:03 present+ 15:02:05 present+ 15:02:08 present+ 15:02:38 Saad has joined #vcwg 15:02:56 present+ 15:03:01 present+ denkeni 15:03:58 hsano8 has joined #vcwg 15:04:13 denkeni has joined #vcwg 15:04:49 wes-smith has joined #vcwg 15:04:52 present+ 15:04:52 scribe+ Elaine 15:04:59 present+ kezike 15:05:08 present+ wes-smith 15:05:20 present+ manu 15:05:27 present+ 15:05:33 present+ tallted 15:06:28 @brentz covers admin and agenda 15:06:42 q+ 15:06:48 ack manu 15:06:51 q+ 15:07:17 kezike has joined #vcwg 15:07:19 Tracker Doc: https://docs.google.com/spreadsheets/d/1OM-UsLnOZKywcy1eSGZsi_laCHBIy5wmQFOer0a7kYI/edit?pli=1&gid=67467047#gid=67467047 15:07:21 present+ 15:07:36 manu reviews need to proceed with horizontal review - we are behind schedule 15:08:27 s/manu/manu:/ 15:08:54 ack dmitriz 15:09:07 s/manu reviews/manu: reviews/ 15:09:41 present+ 15:10:01 dmitriz asked to review PR1629 15:10:13 TallTed has joined #vcwg 15:10:16 Topic: Task Force Updates 15:10:23 q+ 15:10:32 michaelshea+ 15:10:35 got it 15:10:36 q+ 15:10:40 ack wes-smith 15:10:51 s/dmitriz asked/dmitriz: asked/ 15:10:54 q+ 15:11:12 q+ to provide update for VCALM TF 15:11:21 present+ jennie 15:11:50 wes-smith: progress on barcode spec, threat models is good 15:11:50 q+ 15:11:55 ack michaelshea 15:12:08 q+ 15:12:25 ack denkeni 15:12:25 https://github.com/w3c/vc-confidence-method/issues/30 15:12:54 https://w3c.github.io/vc-confidence-method/#assurance-levels 15:13:08 q+ 15:13:17 q- 15:13:17 present+ 15:13:17 denkeni: issue whether to quote ISO or other policies 15:13:23 s/got it// 15:14:06 I have made the request to generate https://www.w3.org/2026/08/05-vcwg-minutes.html TallTed 15:14:13 pdl-asu has joined #vcwg 15:14:13 qq 15:14:15 present+ 15:14:24 brent: guidance from council is to avoid it unless necessary - just because there's a cost doesn't mean others can't obtain it 15:15:00 q+ 15:15:09 ivan: is there a public text? answer is yes 15:15:19 ack kezike 15:15:19 kezike, you wanted to provide update for VCALM TF 15:16:31 kezike: VCALM - threat model merged / new test suite repo just merged in yesterday - over last month, worked to classify issues - will proceed with focusing on issues that are blockers for candidate rec 15:16:39 ack manu 15:16:43 https://github.com/w3c/vc-data-model/pull/1638 15:18:17 I found the W3C Council Report on the Formal Objection to the use of Normative References to ISO/IEC 18013-7 Annex C in the Digital Credentials API specification which is at https://www.w3.org/2026/06/council-digital-credentials-report.html 15:18:25 manu: re vc data model - there's now a threat model - please review. Will speak to status list and some post quantum stuff. There's also a data integrity threat model that is hoped will work for other related specs. Large number of threats will layer on top of that base. The threat models have broken the preview mode. working with Ivan to fix 15:18:26 it. 15:18:31 ack dmitriz 15:20:05 FO Council Report related to referencing ISO specs: https://www.w3.org/2026/06/council-digital-credentials-report.html 15:20:10 q+ 15:20:12 dmitriz: render method - have compressed road map to get to horizontal review - consensus on 3 categories - asks group for feedback about meeting frequency which is currently every other week - proposes each week to get to review 15:20:13 Yes, let's please meet every week for Render Method -- we need more time on spec to get it to horizontal review. 15:20:20 ack olvisgil 15:21:25 @zakim: regarding deliverables tracker - suggests new item - verifiable credential for payment rails 15:21:44 ack phila 15:21:57 wrong person - olvisgil 15:21:58 s/@zakim/olvisgil/ 15:22:35 q+ 15:22:52 ack ivan 15:23:07 group agrees every week is available for render method - dmitriz can update calendar 15:23:17 We really need to move the render method forward faster, would prefer not to delay until after August. 15:23:22 +1 15:23:24 q+ 15:23:32 q- 15:23:58 @ivan: perhaps wait until September to change render method meeting frequency / group agrees weekly is needed sooner 15:24:06 Topic: Placing the new terms in vocabularies and context files 15:24:19 https://github.com/w3c/vc-wg/pull/15 15:24:34 brent: next topic new terms in vocabulary 15:24:39 https://github.com/w3c/vc-wg/blob/main/vocabs/newvocabularies.md 15:25:35 q+ 15:26:34 I have made the request to generate https://www.w3.org/2026/08/05-vcwg-minutes.html TallTed 15:27:34 ivan: number of TFs need update of context file - render method (already exists as a class), also confidence method Bitstring is here because there may be a new version due to barcode TF work. Current situation is that bitstring status list has its own vocabulary. 15:28:26 Agree with Ivan's proposal for render, confidence, bitstring... possibly disagree with forgery defense (should probably go in status), recognized entities (should probably go in VCDM), don't have a strong opinion about barcodes, but Wes might. 15:28:42 ivan: for forgery defence - follow the same model 15:28:46 forgery defense could also potentially go into the security vocab 15:28:53 agree ^ 15:30:28 we've previously offered individual contexts and a "batteries computed" context, i think we should probably keep doing that 15:30:41 @ivan: for recognized entities - should have separate context file not just build on VC / same with barcodes 15:30:46 s/batteries computed/batteries included 15:31:24 ivan: other option is to fold into the rest of the VCDM - need to discuss and make a decision 15:32:20 @ivan: once decision is made, then can set up framing and then repository 15:32:49 q+ 15:32:51 brent: reviews manu's IRC comments regarding Ivan's proposal 15:33:02 ack manu 15:33:08 ack dlongley 15:34:14 dlongley: previously had individual contexts - useful for those who need them / not related to vocabularies - need to continue that conversation 15:34:48 q+ 15:35:00 brent: I will trust the experts on this 15:35:06 ack phila 15:35:10 q+ 15:35:14 q+ 15:35:36 phila: checking in re longley - can have the individual contexts PLUS an overarching one? 15:36:01 ack dlongley 15:36:25 dlongley: yes 15:36:25 ack ivan 15:36:47 q+ 15:37:36 ack dlongley 15:37:36 @ivan: I am not sure about this because of messaging - 15:38:42 dlongley: agree with ivan on this piece - if creating specific credentials of different types - that's a new context / using components of existing spec is not 15:39:49 group - discussions will continue 15:40:16 Olvisgil has joined #vcwg 15:40:28 saad has joined #vcwg 15:40:31 q+ 15:40:39 topic deprecate digest sri - but parties are absent 15:40:50 Topic: DigestSIR 15:40:51 s/topic/topic:/ 15:41:07 s/SIR/SRI/ 15:43:13 ack dlongley 15:43:16 dlongley: believe we cannot use a copy of something that's in another spec without processing rules applying 15:45:46 dmitriz: goal for the PR was "now what?" - have reasoning for deprecating digest SRI / manu and shigeya prior conversation - no consensus and Shigeya's concerns are not addressed. 15:45:59 q+ 15:46:12 brent: if not resolved by TPAC - seek consensus there / doesn't feel urgent 15:46:27 ack ivan 15:46:44 hopefully a "this is deprecated and language that says other specs shouldn't use it, but it won't be removed, it will still be in the next context, etc." is a good compromise 15:47:41 q+ 15:47:51 ack dlongley 15:47:55 ivan: brent is now the master of the process - which doesn't have the term "deprecate" as such. This is more like we have it - if you use it, has to be this way - but don't use it. The process is unclear. 15:47:59 pdl-asu has joined #vcwg 15:48:08 present+ 15:48:45 dlongley: idea is to keep it in the next version of the context - keep it around but with clearer guidance 15:48:51 q+ 15:48:55 re deprecation: https://www.w3.org/TR/epub-34/#sec-obs-deprecated 15:49:12 This is issue 1628 15:49:16 ack michaelshea 15:49:39 Topic: TPAC 15:50:36 brent: please register for TPAC / WG meetings thursday and Friday with Friday shorter / Will be a Tuesday joint session with payments and DC API - all invited 15:50:41 https://www.w3.org/news-events/tpac/2026/registration/ 15:51:56 brent: planning to talk about CR and about CR / if there are other topics, let Brent know 15:52:04 q+ Request to amend short URL for confidence method 15:52:05 Topic: Request to amend short URL for confidence method 15:53:05 https://www.w3.org/2026/03/vc-wg-charter.html#confidence 15:53:05 ack denkeni 15:54:33 q+ 15:54:34 Elaine has joined #vcwg 15:54:35 q+ 15:54:44 ack dlongley 15:54:46 ack Request 15:54:46 Request, you wanted to amend short URL for confidence method 15:54:50 sorry - lost power 15:55:04 i am back 15:55:51 q+ to chip in if time allows 15:56:07 ack ivan 15:56:07 dlongley: maybe expand confidence method to include assurance levels - then does the name need to change / need to discuss in task force but there was no meeting last week 15:56:18 +1 to have more discussion in the task force 15:57:48 ivan: WG must have formal resolution to change short name / then need review as if it is an actual new working draft. Used to be a bigger pain. But now still needs to be done manually - requires actions by Ivan and the working group and editors. Extra work. 15:58:06 ivan: the title can be changed - it's the short name that's an issue 15:58:37 ack phila 15:58:37 phila, you wanted to chip in if time allows 15:58:47 brent: new VC overview doc - please review / confidence method TF - come back with decision 15:58:48 q+ 15:58:53 +1 to phil, i feel similarly. 15:59:05 ack michaelshea 15:59:06 phila: confidence is too broad 15:59:07 -> new version of overview https://www.w3.org/TR/vc-overview-1.1/ 15:59:44 michaelshea: mike jones is listed as an owner for the CID repo / if not involved anymore, what needs to happen 15:59:54 brent: I will change it 16:00:05 Jem_ has joined #vcwg 16:00:27 Thank you so much! 16:00:28 brent: good work 16:00:29 rrsagent, draft minutes 16:00:30 I have made the request to generate https://www.w3.org/2026/08/05-vcwg-minutes.html ivan 16:00:36 Thanks all! 16:00:43 rrsagent, bye 16:00:43 I see no action items