15:49:21 RRSAgent has joined #vcwg 15:49:25 logging to https://www.w3.org/2024/01/10-vcwg-irc 15:49:25 RRSAgent, make logs Public 15:49:26 please title this meeting ("meeting: ..."), ivan 15:49:49 Meeting: Verifiable Credentials Working Group Telco 15:49:49 Date: 2024-01-10 15:49:49 Agenda: https://www.w3.org/events/meetings/ae05a21b-c065-4e69-8d5e-352a0d391513/20240110T110000/ 15:49:49 chair: brent 15:49:50 ivan has changed the topic to: Meeting Agenda 2024-01-10: https://www.w3.org/events/meetings/ae05a21b-c065-4e69-8d5e-352a0d391513/20240110T110000/ 16:00:16 present+ 16:00:21 present+ TallTed 16:00:22 present+ 16:00:41 brent has joined #vcwg 16:00:50 DavidC has joined #vcwg 16:00:50 present+ davidc 16:00:55 present+ 16:00:58 present+ brent 16:01:03 cabernet has joined #vcwg 16:01:05 present+ 16:01:11 present+ msporny, selfissued 16:01:37 present+ 16:03:26 pauld_gs1 has joined #vcwg 16:03:34 present+ 16:03:54 scribe+ 16:04:21 present+ 16:04:25 q+ 16:05:08 pdl_asu has joined #vcwg 16:05:08 present+ 16:05:32 ack manu 16:05:47 present+ 16:06:16 Manu: need to publish vc specs directory as a note 16:06:56 ... make it so that any updates are automatically published 16:07:43 q+ 16:07:48 q- 16:07:59 JoeAndrieu has joined #vcwg 16:08:22 selfissued has joined #vcwg 16:08:28 present+ 16:08:39 brentz has joined #vcwg 16:08:42 present+ JoeAndrieu 16:09:07 Topic: VCDM 2.0 Candidate Recommendation Proposal 16:09:11 q? 16:09:39 The prepared CR-ready draft is here: https://w3c.github.io/vc-data-model/CR/2024-01-30/ 16:09:51 brentz: just 2 PRs maked before PR 16:10:00 and the corresponding vc-specs-dir is here: https://w3c.github.io/vc-specs-dir/NOTE/2024-01-30/ 16:10:10 maked -> marked 16:10:54 q+ 16:11:09 Any changes to 1397 not merged should not affect the published CR technical content 16:11:19 ack selfissued 16:11:35 q+ 16:11:49 Kevin-Dean-GS1 has joined #vcwg 16:11:58 present+ Kevin-Dean-GS1 16:12:00 s/PRs maked before/PRs marked before/ 16:12:00 s/maked -> marked// 16:12:04 selfissued: waiting for 1404 to be merged before resolving some PRs in JOSE-COSE 16:12:12 ack ivan 16:13:02 ivan: diagrams have been updated but waiting for comments from manu 16:13:21 manu: this looks fine 16:13:39 q+ 16:14:10 whilst 1404 is editorial selfissued's changes are not 16:14:35 ack TallTed 16:14:55 TallTed: has issues with long media type 16:15:20 ... image that says the media type has a typo 16:15:27 https://github.com/w3c/vc-data-model/pull/1404/files?diff=unified&w=1#diff-a243d1366958acf1007436feb951d911ac6cf5c489a8deff49a8fd125a32d85f 16:16:21 andres has joined #vcwg 16:16:37 selfissued: one minus sign should change to a + 16:17:15 ivan: I cannot do it today sorry, can someone else? 16:17:47 TallTed: I will do a change suggestion on the PR 16:18:01 selfissued: either I or manu should merge it 16:18:10 manu: I will merge it 16:19:13 brentz: after 1397 is merged or closed we will begin the process of moving VCDMv2 to CR 16:20:06 q+ 16:20:27 q+ 16:20:38 ack manu 16:20:46 q+ 16:21:00 manu: do we need to say that we can update this at any time? 16:21:18 ack DavidC 16:21:29 DavidC: We said we're going to publish with a date, but then update, what do we do about the date? 16:21:53 q+ 16:21:55 q- 16:22:03 ack ivan 16:22:28 ivan: publish wont happend before next Friday 16:22:45 ... initial publication date will be 23 Jan 24 16:23:08 ... once it is in the system the automatic publication process automatically updates the date 16:23:26 ... its only the first version that we have to specify a date 16:23:40 PROPOSAL: We will publish VC Specs Directories located at https://w3c.github.io/vc-specs-dir/NOTE/2024-01-30/ as a Note as soon as it is ready and we plan to update the Note as needed.. 16:23:49 +1 16:23:50 +1 16:23:59 +1 16:24:05 +1 16:24:05 +1 16:24:06 +1 16:24:06 +1 16:24:12 +1 16:24:12 +1 16:24:13 +q 16:24:20 whoops 16:24:21 +1 16:24:23 +1 16:24:23 q- 16:24:24 +1 16:24:32 +1 16:24:43 RESOLVED: We will publish VC Specs Directories located at https://w3c.github.io/vc-specs-dir/NOTE/2024-01-30/ as a Note as soon as it is ready and we plan to update the Note as needed.. 16:24:56 brentz: resoved unanimously 16:25:13 typo fix suggestions on 1404 -- https://github.com/w3c/vc-data-model/pull/1404#pullrequestreview-1813608389 16:25:41 gkellogg has joined #vcwg 16:26:43 +1 16:27:03 PROPOSAL: We will transition Verifiable Credentials Data Model v2.0 located at https://w3c.github.io/vc-data-model/CR/2024-01-30/ to Candidate Recommendation after either merging or closing PR 1397 16:27:06 present+ andres 16:27:08 +1 16:27:10 +1 16:27:10 +1 16:27:11 +1 16:27:12 +1 16:27:12 +1 16:27:14 +1 16:27:15 +1 16:27:17 +1 16:27:17 +1 16:27:34 +1 16:27:50 q+ 16:27:53 +1 16:28:13 +1 16:28:20 RESOLVED: We will transition Verifiable Credentials Data Model v2.0 located at https://w3c.github.io/vc-data-model/CR/2024-01-30/ to Candidate Recommendation after either merging or closing PR 1397 16:28:28 brentz: resolved unanimouslu 16:28:43 s/unanimouslu/unanimously/ 16:29:06 ack ivan 16:29:10 https://github.com/w3c/verifiable-credentials/blob/main/admin/CR-vcdm/Approval_request.md 16:29:57 ivan: will update and cross check the approval request text with the URL I published 16:30:09 Topic: VC Spec Directories Volunteers 16:30:13 s/will/will manu/ 16:30:39 q+ 16:30:48 ack manu 16:31:11 https://lists.w3.org/Archives/Public/public-credentials/2024Jan/0010.html 16:31:25 manu: sent out a request for volunteers to maintain registeries and got 16 volunteers 16:31:48 ... 5 are from the general community, rest are not 16:32:22 ... are explaining work to volunteers to see if they are still interested 16:32:57 ... we should be able to put 6 volunteers on each registry (DIDs and spec directory) 16:33:40 ... I do not want to share the emails of the volunteer, but will share their linked in pages 16:34:12 q+ 16:34:20 ack manu 16:34:27 ... if anyone objects to anyone in this list they can notify the group 16:34:58 Topic: Bitstring Status List 16:35:14 PRs for Bitstring Status List -- https://github.com/w3c/vc-bitstring-status-list/pulls 16:36:40 q+ 16:36:47 ack manu 16:36:49 brentz: 20 PRs but majority are almost ready for merging 16:37:14 manu: the plan is to merge them all this weekend 16:37:49 subtopic: https://github.com/w3c/vc-bitstring-status-list/pull/100 16:38:31 ... we had 3 status purpose values: revocation, suspension and status 16:38:41 ... we have changed status to message 16:39:13 ... we have pre-pended the word status to some of the property names 16:39:24 https://github.com/w3c/vc-bitstring-status-list/pull/105 16:40:00 subtopic: https://github.com/w3c/vc-bitstring-status-list/pull/110 16:40:07 ... these affect existing implementations, but not technically difficult 16:40:22 ... request to change base64 to base64url 16:40:56 ... but there is no type for base64url yet 16:41:08 subtopic: https://github.com/w3c/vc-bitstring-status-list/pull/112 16:41:27 ... request to retrieve historical status list 16:41:47 ... so option to add date-time to the request 16:42:16 ... some discussions about what to do if the issuer does not have the status list at the requested date-time 16:42:58 ... nobody has implemented this feature yet, so should we fully specify this feature or wait for implementation experience 16:43:11 q+ 16:43:29 ack DavidC 16:44:15 DavidC: We would like implementer feedback, but we shouldn't have a spec that has multiple options on the reply - that might be confusing to implementers. Select one option for the reply (when you don't have one, we should say you MUST/SHOULD return an error) vs. "it's up to implementers" 16:44:40 subtopic: https://github.com/w3c/vc-bitstring-status-list/pull/118 16:44:41 manu: we can make this change 16:45:15 ... we should not mix and match the security mechanisms on the status list and the vcs that it contains 16:45:46 ... they should all use the same mechanism e.g. JWT or data integrity 16:46:05 subtopic: https://github.com/w3c/vc-bitstring-status-list/pull/119 16:46:23 ... adds an at risk marker to the bitstring format 16:46:48 ... because there is parallel work in the IETF, so we might wish to align 16:46:57 IETF work https://datatracker.ietf.org/doc/draft-ietf-oauth-status-list/ 16:47:49 subtopic: https://github.com/w3c/vc-bitstring-status-list/pull/121 16:48:02 ... renames herd privacy to group privacy 16:48:39 subtopic: https://github.com/w3c/vc-bitstring-status-list/pull/123 16:49:03 ... adding an at risk marker to the multiple status list feature 16:49:37 I believe we intend to implement it 16:49:38 ... if there are insufficient implementors of this feature it will be removed 16:50:20 ... we will need a test suite for it as well as implementations 16:50:34 q+ 16:50:52 ack ivan 16:51:06 subtopic: https://github.com/w3c/vc-bitstring-status-list/pull/105 16:51:15 ivan: pr 105?? 16:51:33 manu: what is the vocabulory URL for the status list? 16:51:54 ... several proposals for this 16:51:58 This could be one of the vocabulary URL prefixes: https://www.w3.org/ns/credentials/status-list# 16:52:10 gkellogg has joined #vcwg 16:52:27 This could be one of the vocabulary URL prefixes: https://www.w3.org/2018/credentials/status# 16:52:47 manu: we need to pick one and go with it 16:52:57 q+ 16:52:58 This could be one of the vocabulary URL prefixes: https://www.w3.org/ns/credentials/status# 16:53:41 ... but does not align with 2118 existing terms 16:53:56 ack ivan 16:54:12 ... should there be a date in the terms or not? 16:54:53 q+ to note that V2 context is: https://www.w3.org/ns/credentials/v2 16:54:54 s/2118/2018/ 16:55:15 ack manu 16:55:15 manu, you wanted to note that V2 context is: https://www.w3.org/ns/credentials/v2 16:56:19 q+ 16:56:26 brentz: do we want to have a poll on the name? 16:56:50 ack TallTed 16:57:30 POLL: What should the status list vocabulary URL be Choice A) https://www.w3.org/ns/credentials/status# and Choice B) https://www.w3.org/2018/credentials/status# ? 16:57:38 B 16:57:39 A 16:57:48 A 16:57:55 A 16:57:56 A 16:58:00 B 16:58:08 A 16:58:12 B 16:58:46 q+ 16:58:50 A 16:58:55 ack DavidC 16:59:24 DavidC: The reason I wanted the date is if you want to change a definition, if you have date in there, change in definition could have a new date. I see how you can append/remove, but changing them is not possible. 16:59:42 I don't fully grok the pros and cons. A `ns` vs B `2018` (which is when the original VCWG started) 16:59:43 ivan: There might be a version in the vocabulary, but URL does not change. 17:00:10 rrsagent, draft minutes 17:00:12 I have made the request to generate https://www.w3.org/2024/01/10-vcwg-minutes.html ivan 17:01:14 rrsagent, bye 17:01:14 I see no action items