14:03:25 RRSAgent has joined #vcwg 14:03:29 logging to https://www.w3.org/2024/10/16-vcwg-irc 14:03:29 RRSAgent, make logs Public 14:03:30 please title this meeting ("meeting: ..."), ivan 14:04:06 Meeting: Verifiable Credentials Working Group Telco 14:04:06 Date: 2024-10-16 14:04:06 Agenda: https://www.w3.org/events/meetings/bcd2e026-9621-481e-8ac6-824a71464234/20241016T110000/ 14:04:06 chair: brent 14:04:07 ivan has changed the topic to: Meeting Agenda 2024-10-16: https://www.w3.org/events/meetings/bcd2e026-9621-481e-8ac6-824a71464234/20241016T110000/ 14:58:22 mandyv has joined #vcwg 14:59:15 decentralgabe has joined #vcwg 14:59:19 present+ 15:00:28 hsano has joined #vcwg 15:00:48 present+ 15:00:53 present+ TallTed 15:01:41 chair+ 15:01:53 present+ 15:02:00 present+ manu 15:02:04 present+ mandyv 15:02:07 present+ dlongley 15:02:16 present+ hsano 15:02:17 present+ 15:02:33 JoeAndrieu has joined #vcwg 15:02:46 PL-ASU has joined #vcwg 15:02:53 present+ 15:02:54 DavidC has joined #vcwg 15:03:00 present+ 15:03:07 present+ dmitriz 15:03:17 present+ joe 15:03:29 Topic: Agenda Review 15:03:32 present+ will 15:03:39 q+ 15:03:45 ack manu 15:03:53 scribe+ 15:04:04 Wip has joined #vcwg 15:04:06 Topic: CR2 updates 15:04:08 present+ 15:04:17 https://github.com/w3c/vc-di-eddsa/issues 15:04:38 manu: eddsa spec has zero issues, zero PRs and CRv2 has been prepared 15:04:44 https://github.com/w3c/vc-di-ecdsa/issues 15:05:07 ... ecdsa spec in same shape.CRv2 still to be prep'ed 15:05:11 https://github.com/w3c/vc-data-integrity 15:05:47 present_+ 15:05:50 .... data integrity had zero issues and pull requests, but a new normative PR has arisen that needs to be addressed 15:05:52 present+ 15:06:14 https://github.com/w3c/vc-data-model/issues 15:06:16 .... need to resolve this issue with ivan 15:06:38 .... data model. 2 open PRs but both editorial, so can be done after CRv2 15:06:46 present+ bigbluehat 15:06:56 bigbluehat has joined #vcwg 15:07:01 JennieM has joined #vcwg 15:07:07 present+ 15:07:08 present+ 15:07:13 .... but if we require certain algorithms then this would be a normative change 15:07:27 present+ jennie 15:07:29 q+ 15:07:36 ack ivan 15:07:37 ... will have CR3 ready for Nov 5th publication date 15:08:01 ivan. Manu have you made updates on my requests yet? 15:08:08 manu. Sorry no 15:08:55 s/ivan./ivan:/ 15:09:02 manu: once we do CR2s we need to do final acknowledgements 15:09:08 s/manu./manu:/ 15:09:55 DavidC has joined #vcwg 15:10:02 present+ 15:10:26 Topic: vc jose cose media types update 15:10:33 https://mailarchive.ietf.org/arch/browse/media-types/ 15:10:46 decentralgabe: media types were registered by me last week 15:11:09 If David's IRC connection problem persists I''ll back up scribing. Hopefully that won't be necessary 15:11:22 q+ 15:11:24 .... but not sd-jwt yet because sd-jwt registration has not been done. Needs the ID to go to last call first 15:11:48 ack ivan 15:11:59 .... will this block CR2 for jose-cose? 15:12:27 q+ 15:12:34 ivan: Is sd-jwt to be a standard before the end of the year? 15:12:48 ... when we go to PR it must be a standard 15:13:03 ... otherwise we have to remove reference to it 15:13:24 ack manu 15:13:41 manu: did media type has been registered with IANA 15:14:39 Topic: Controller Document 15:14:46 q+ 15:14:53 ack manu 15:14:53 decentralgabe: 8 PRs outstanding 15:15:20 manu: I went through PING and TAG reviews and raised PRs for almost all of them 15:15:34 q+ 15:15:49 ... one outstanding still, role of subject when controller not there 15:16:12 https://github.com/w3c/controller-document/pull/102 15:16:26 ack JoeAndrieu 15:16:52 JoeAndrieu: the issue about subjects is resolved with PR32 15:17:04 q+ to speak to use cases and requirements 15:17:08 ... DavidC please see if this addresses your issue 15:17:09 s/PR32/PR102/ 15:17:09 ack manu 15:17:09 manu, you wanted to speak to use cases and requirements 15:17:14 subtopic: https://github.com/w3c/controller-document/pull/103 15:17:55 DavidC3 has joined #vcwg 15:19:15 manu: controller doc and did document provide different solutions to ownership 15:19:56 ... did document has twice as many use cases as controller doc 15:20:20 subtopic: https://github.com/w3c/controller-document/pull/106 15:21:08 ... the TAG said a JSON-LD processor might resolve to a different solution to pure JSON processing, so need to make clear that this is not the case 15:21:33 ... so even if @context is not there, the result should still be the same 15:22:09 q? 15:22:19 ... if you get two different results then you have a bug in one of your processors 15:22:34 subtopic: https://github.com/w3c/controller-document/pull/107 15:22:36 +1 to put this into VCDM 15:22:54 ... TAG also asked for Security Considerations for multi format choice 15:23:12 q+ 15:23:17 +1 to putting this in the VCDM for consistency 15:23:47 ... cannot tell difference between base64 and base32 encodings but with multi-encoding you can 15:24:13 ... but we have not done this is the relatedResource property 15:24:55 ack DavidC 15:25:32 DavidC: the way I read this, in order to determine whether its b64, you have to read the spec. in multi-encoding you don't have the issue (have a prefix that tells you what it is); however, you have to go to the spec to understand this too. 15:25:33 q+ 15:25:38 ack manu 15:26:55 manu: multibase encoding has a multibase type so can take the text and you know that the first character will tell you the encoding format 15:27:01 +1 you define the multibase type once, and you can then reuse it across software and specs and if you need to switch anything, the impact can be reduced. 15:27:56 q+ 15:28:03 ack manu 15:29:05 subtopic: https://github.com/w3c/controller-document/issues/100 15:29:35 manu: need to find a better name for the specification. We could run a rank poll on various naming options 15:29:43 present+ selfissued 15:29:50 ... this usually provides good results 15:30:14 +1 to a poll for a better name 15:31:06 q+ to suggest RCV 15:31:21 ack manu 15:31:21 manu, you wanted to suggest RCV 15:31:31 ivan: group can decide what sort of poll to use 15:31:52 manu: there is a web site that does poll rankings for you 15:32:42 ... this shows what the ranking is, and the group can then decide to accept this or not 15:33:19 decentralgabe: I will follow up with Brent after this call to create the poll 15:33:36 manu: please make sure you have included all the name choices 15:33:56 Subtopic: https://github.com/w3c/controller-document/issues/66 15:33:57 q+ 15:34:03 q- 15:34:04 q+ 15:34:37 ack manu 15:35:03 manu: would be great if W3C took over the domain name, but this is not likely 15:35:12 selfissued has joined #vcwg 15:35:20 present+ 15:35:41 q+ 15:35:46 ... issue is still open to see if W3C has an opinion on this 15:36:04 selfissued: I asked Ralf about this at TPAC 15:36:24 q- 15:36:31 ... but I am OK on closing this if W3C will take an action on this 15:38:36 ivan: we have a green light from W3C management for the VCWG 15:38:48 q+ 15:38:53 ack manu 15:39:31 manu: we can close the PING and TAG issues once all the resulting PRs have been merged 15:39:54 q+ 15:39:59 ack ivan 15:40:06 ... I have tagged these people with our PRs so that they can check that all their issues have been resolved 15:40:30 q+ to note "testing" and CR1 transition 15:40:34 ivan: how are we going to do the testing of the controller doc 15:40:36 ack manu 15:40:36 manu, you wanted to note "testing" and CR1 transition 15:41:02 q+ 15:41:30 manu: all the normative statements in controller doc are same as in did core, so we can point to did test suite 15:42:06 ... alternatively we can create a JSON schema for people to check if their controller docs conform to the schema 15:42:39 ack ivan 15:43:11 q+ 15:43:25 ivan: I am afraid that saying DID has done it, then what has controller doc to do with VCs? 15:43:34 q+ to note that the Data Integrity test suite tests it indirectly. 15:43:39 +1 the other verification test suites make use of verification methods that are from controller documents 15:43:56 +1 to Ivan. 15:44:21 ivan: we can say that the data integrity tests also test the controller doc since they conform to it 15:44:26 ack decentralgabe 15:44:52 decentralgabe: text suite for JOSE/COSE also uses the controller doc. 15:45:01 ack manu 15:45:01 manu, you wanted to note that the Data Integrity test suite tests it indirectly. 15:45:06 s/text/test 15:46:08 manu: verification methods are tested and these are also in controller doc 15:46:54 q+ 15:47:07 ... we have a whole set of indirect tests for controller doc even if we do not have a test suite for the doc itself 15:48:13 ack ivan 15:48:23 ... and we are not aware that anyone wants to formally object to the controller doc 15:48:42 ivan: but we also need to worry about W3C management as well 15:49:05 q+ to volunteer to write "how this spec is being tested" section 15:49:21 ... therefore all these indirect tests should be written up and presented with the controller doc when it is sent to be published as a CR 15:49:32 ack manu 15:49:32 manu, you wanted to volunteer to write "how this spec is being tested" section 15:50:41 manu: we have to show two independent implementations of every feature. We can point to DID test suite to show this 15:51:12 ... and DI tests and JOSE/COSE tests 15:51:14 +1 to that text 15:51:22 q+ 15:51:27 ack manu 15:52:25 manu: on the security review, the W3C security group is about to start soon, so we still need a review from it 15:53:03 rrsagent, draft minutes 15:53:05 I have made the request to generate https://www.w3.org/2024/10/16-vcwg-minutes.html ivan 15:54:08 rrsagent, bye 15:54:08 I see no action items