14:24:57 <RRSAgent> RRSAgent has joined #vcwg
14:25:01 <RRSAgent> logging to https://www.w3.org/2024/03/27-vcwg-irc
14:25:02 <Zakim> RRSAgent, make logs Public
14:25:03 <Zakim> please title this meeting ("meeting: ..."), ivan
14:25:45 <ivan> Meeting: Verifiable Credentials Working Group Telco
14:25:45 <ivan> Date: 2024-03-27
14:25:45 <ivan> Agenda: https://www.w3.org/events/meetings/0d074559-1457-4540-857b-24b1be7a8d7f/20240327T110000/
14:25:45 <ivan> chair: brent
14:25:46 <ivan> ivan has changed the topic to: Meeting Agenda 2024-03-27: https://www.w3.org/events/meetings/0d074559-1457-4540-857b-24b1be7a8d7f/20240327T110000/
14:55:30 <brent> brent has joined #vcwg
14:58:59 <brent> present+
14:59:43 <ivan> present+
15:00:47 <hsano> hsano has joined #vcwg
15:01:35 <TallTed> present+
15:01:52 <webirc38> webirc38 has joined #vcwg
15:01:52 <manu> present+
15:01:59 <ivan> present+ elfors, bigbluehat, davidc, tallted, hsano, pauld
15:02:03 <webirc38> present+
15:02:15 <dlongley> present+
15:02:59 <pauld_gs1> pauld_gs1 has joined #vcwg
15:03:02 <bigbluehat> bigbluehat has joined #vcwg
15:03:11 <bigbluehat> present+
15:03:11 <webirc39> webirc39 has joined #vcwg
15:03:27 <ivan> present+ jennie
15:03:39 <SebastianElfors> SebastianElfors has joined #vcwg
15:03:46 <DavidC> thanks Dave
15:04:29 <ivan> present+ gregb
15:04:42 <pauld_gs1> present+
15:04:45 <ivan> present+ dlehn
15:05:50 <ivan> present+ dmitriz
15:06:05 <DavidC> scribe+
15:06:17 <TallTed> RRSAgent, draft minutes
15:06:19 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/27-vcwg-minutes.html TallTed
15:06:44 <GregB> GregB has joined #vcwg
15:06:54 <ivan> q+
15:06:57 <TallTed> s/thanks Dave//
15:07:02 <GregB> present+
15:07:08 <brent> ack ivan
15:07:47 <TallTed> s/Date: 2024-03-27//
15:07:47 <DavidC> #ivan still not received approval for the CR
15:08:06 <TallTed> s/#ivan still/ivan: still
15:08:16 <DavidC> ... proposal for canonicalisation spec went out on Monday
15:08:18 <brent> s/the CR/the BBS CR/
15:08:22 <TallTed> RRSAgent, draft minutes
15:08:24 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/27-vcwg-minutes.html TallTed
15:08:40 <ivan> q+
15:08:59 <brent> ack ivan
15:09:28 <brent> Topic: Charter renewal proposal
15:09:45 <brent> https://github.com/w3c/vc-wg-charter/pull/113
15:09:48 <ivan> q+
15:10:17 <ivan> present+ phil
15:10:57 <DavidC> brent: instead of asking for 6 month extension we have been asked to recharter the WG
15:11:21 <DavidC> ... ivan has drawn up a draft in the above mentioned PR 113
15:11:48 <manu> diff-marked copy: https://pr-preview.s3.amazonaws.com/w3c/vc-wg-charter/113/a5ac455...9e11451.html
15:12:14 <brent> brent has joined #vcwg
15:12:25 <brent> q?
15:12:26 <DavidC> ivan. I made the least changes possible to the new charter
15:12:51 <DavidC> ... in maintenance mode WG does not have right to make significant changes to the text
15:13:05 <DavidC> ... except if it is a security issue
15:13:22 <manu> Charter looks good to me.
15:13:23 <manu> q+
15:13:25 <ivan> s/ivan./ivan:/
15:13:33 <brent> ack ivan
15:13:34 <dmitriz> dmitriz has joined #vcwg
15:14:09 <webirc72> webirc72 has joined #vcwg
15:14:13 <dlongley> +1 to the direction
15:14:16 <brent> ack manu
15:14:20 <DavidC> brent: we should make a resolution on this in week after next
15:14:22 <webirc72> present+
15:14:43 <DavidC> manu: the new version looks pretty good
15:15:23 <DavidC> brent: I have asked Gabe to chair next week's meeting
15:15:48 <brent> Topic: Work Item Status Updates/PRs
15:16:03 <manu> q+
15:16:09 <brent> ack manu
15:16:36 <DavidC> manu: statusList has 26 issues still open
15:16:47 <DavidC> ... try to get them all resolved by mid April
15:16:57 <DavidC> ... there are two normative changes
15:17:40 <DavidC> ... first one is to more strongly assert that verifiers should cache status lists
15:18:04 <DavidC> ... and to use OHTP to retrieve them
15:18:18 <ivan> s/OHTP/OHTTP/
15:18:40 <TallTed> s|statusList has 26 issues still open|bitstring-status-list has 26 issues still open, https://github.com/w3c/vc-bitstring-status-list/issues
15:18:46 <manu> subtopic: https://github.com/w3c/vc-bitstring-status-list/issues/151
15:19:10 <TallTed> RRSAgent, draft minutes
15:19:11 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/27-vcwg-minutes.html TallTed
15:19:40 <TallTed> present- webirc38
15:19:44 <DavidC> ... PING have raised several privacy issues that we should address
15:20:31 <DavidC> ... several issues around I18N that need to be reviewed
15:20:41 <brent> q+
15:21:05 <brent> ack brent
15:21:19 <manu> q+
15:22:06 <DavidC> ... strings may be human readable
15:22:06 <brent> ack manu
15:22:27 <manu> https://github.com/w3c/vc-data-model/pulls
15:22:49 <DavidC> ... will be a massive PR to address Yaskin's comments
15:23:30 <DavidC> ... mostly editorial apart from a few normative statements (but no new implementation requirements)
15:23:35 <manu> subtopic: https://github.com/w3c/vc-data-model/issues/1462
15:24:04 <DavidC> ... mediaType for DM does not have a concensus yet
15:24:14 <brent> q+
15:24:36 <DavidC> ... e.g. multiple suffixes is a bad idea
15:25:07 <DavidC> ... Can the WG members review this issue
15:25:21 <brent> ack brent
15:25:44 <TallTed> s/concensus/consensus
15:26:21 <DavidC> brent: multiple suffixes draft means that the authors did not describe single suffix properly
15:27:14 <manu> q+
15:27:20 <brent> ack manu
15:28:03 <manu> subtopic: https://github.com/w3ctag/design-reviews/issues/922#issuecomment-2019124783
15:28:12 <DavidC> manu: BBS spec, TAG review was OK
15:28:44 <DavidC> ... Martin Thomson said we make unlinkability claims that are not supported by the crypto
15:29:31 <DavidC> ... we dont know what level of independent review will be good enough!
15:29:41 <brent> q+
15:29:46 <brent> ack brent
15:30:29 <DavidC> brent: Martin told me that the way Data Integrity builds on BBS primitives may lead to untested situations.
15:30:49 <manu> q+
15:30:52 <DavidC> ... but the way we are liaising with W3C security folk may be sufficient
15:30:58 <brent> ack manu
15:31:49 <DavidC> manu: I am concerned about statements such as "we feel uneasy about what you are doing"
15:32:49 <DavidC> ... so vague comments are not good enough for us to provide a rebuttal of
15:32:52 <GregB> q+
15:33:16 <brent> ack GregB
15:33:25 <DavidC> ... we need specific comments that can be addressed
15:33:50 <DavidC> GregB: I wrote the sections in the spec about unlinkability
15:34:31 <DavidC> ... I also studied publications on linkage attacks
15:34:53 <DavidC> ... its still a new area of standardisation
15:35:14 <DavidC> ... so needs to be handled with care
15:35:20 <brent> Topic: VCDM Issue Processing
15:35:29 <brent> https://github.com/w3c/vc-data-model/issues?q=is%3Aissue+is%3Aopen+-label%3Afuture+sort%3Aupdated-asc
15:36:06 <brent> subtopic: https://github.com/w3c/vc-data-model/issues/1457
15:36:10 <manu> q+
15:36:22 <brent> ack manu
15:36:42 <DavidC> manu: we should update to the more modern signature suites
15:37:52 <DavidC> ... at least ECDSA
15:38:21 <DavidC> ... and a selective disclosure example
15:38:51 <ivan> +1 to manu on this
15:39:43 <brent> subtopic: https://github.com/w3c/vc-data-model/issues/1359
15:40:30 <DavidC> q+
15:40:44 <dlongley> scribe+
15:40:45 <manu> scribe+
15:40:48 <brent> ack DavidC
15:41:02 <TallTed> RRSAgent, draft minutes
15:41:04 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/27-vcwg-minutes.html TallTed
15:41:12 <dlongley> DavidC: The `issuee` property is one potential, at least semi-solution to this, it's also a solution to this. It's also a solution to some of the text in the status list PRs.
15:41:19 <manu> scribe-
15:41:28 <brent> q+
15:41:31 <dlongley> DavidC: Someone suggested we replace `issuee` as first holder but we should just call it `issuee`.
15:41:43 <brent> ack brent
15:41:52 <TallTed> s/first holder/`firstHolder`
15:42:06 <TallTed> q+
15:42:22 <brent> ack TallTed
15:43:33 <ivan> q+
15:43:39 <manu> q+
15:43:47 <brent> ack ivan
15:43:53 <dlongley> scribe-
15:44:05 <manu> Here's where it was injected: https://w3c.github.io/vc-data-model/#reserved-extension-points
15:44:09 <brent> ack manu
15:44:41 <DavidC> manu: I dont disagree with what DavidC and TallTed said
15:44:54 <DavidC> ... but do we really want to define it
15:45:18 <manu> q+
15:45:20 <manu> q-
15:45:37 <ivan> q+
15:45:47 <manu> +1 to TallTed's suggestion, for those that want "issuee"
15:45:52 <DavidC> TallTed: I suggested that someone create a new issue for this along with appropriate PRs where it should be inserted
15:45:58 <brent> ack ivan
15:46:15 <DavidC> q+
15:46:25 <brent> ack DavidC
15:47:11 <TallTed> RRSAgent, draft minutes
15:47:12 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/27-vcwg-minutes.html TallTed
15:47:21 <DavidC> DavidC: I dont think that adding a definition for issuee is a normative change for implementations
15:48:08 <brent> subtopic: https://github.com/w3c/vc-data-model/issues/1455
15:49:06 <DavidC> brent: this issue can be closed
15:49:35 <brent> subtopic: https://github.com/w3c/vc-data-model/issues/1254
15:49:44 <brent> https://github.com/w3c/vc-data-model/issues/1254
15:50:08 <brent> https://github.com/w3c/vc-data-model/pull/1463
15:50:20 <DavidC> brent: this PR can be merged by the end of this week
15:50:47 <brent> subtopic: https://github.com/w3c/vc-data-model/issues/1462
15:51:07 <manu> q+
15:51:13 <brent> ack manu
15:51:30 <DavidC> manu: can we highlight the options now please
15:51:51 <DavidC> ... and write your opinions into the issue
15:52:11 <DavidC> ... might not be able to use multiple + signs
15:52:26 <brent> q+ to say they offered to grandfather in ld+json, not the rest
15:52:39 <DavidC> 1) application/vc+ld+json
15:53:19 <DavidC> ... 2) application/vc
15:53:51 <DavidC> ... with +json or +jwt added to this
15:54:16 <ivan> q+
15:54:24 <DavidC> ... 3) do not register anything, wait for IETF group to finish its RFC
15:54:49 <brent> ack brent
15:54:49 <Zakim> brent, you wanted to say they offered to grandfather in ld+json, not the rest
15:55:52 <brent> ack ivan
15:56:39 <DavidC> ivan: a variation of 2 or 3 is to put a statement into the new charter saying that we will do the mediaType after the IETF has finished
15:56:57 <manu> I think that's still Option C?
15:57:05 <manu> (but explicitly stating it in our Charter)
15:57:12 <ivan> yes
15:57:41 <ivan> rrsagent, draft minutes
15:57:42 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/27-vcwg-minutes.html ivan
15:58:25 <ivan> rrsagent, bye
15:58:25 <RRSAgent> I see no action items