19:57:52 RRSAgent has joined #vcwg 19:57:52 logging to https://www.w3.org/2022/01/12-vcwg-irc 19:58:08 zakim, start the meeting 19:58:09 RRSAgent, make logs Public 19:58:11 please title this meeting ("meeting: ..."), brentz 19:58:28 meeting: Verifiable Credentials Working Group 19:58:41 chair: brentz 19:58:53 zakim, this is vcwg 19:58:53 got it, brentz 19:58:56 markus_sabadello has joined #vcwg 19:59:32 rgrant has joined #vcwg 20:00:10 present+ 20:00:12 present+ shigeya 20:00:33 loganporter has joined #vcwg 20:01:05 present+ 20:01:10 present+ 20:01:27 present+ rgrant 20:02:17 present+ 20:02:33 present+ 20:02:35 JoeAndrieu_ has joined #vcwg 20:02:37 scribe+ 20:02:38 present+ 20:02:53 DavicC has joined #vcwg 20:02:54 brent: We begin with agenda review 20:02:59 Present+ 20:03:25 brentz: Agenda is plan for meetings going forward, then conversations about draft charter, review PR, issues 20:03:29 brentz: Any additions to the agenda? 20:03:35 Topic: Meetings moving forward 20:04:01 brentz: The voting period for changes we proposed for VC Data Model that will result in 1.1, that period is up on 18th January 20:04:11 brentz: This means we have fulfilled the primary purpose of this WG 20:04:19 brentz: So far all votes to my knowledge have been positive 20:04:33 brentz: I anticipate that we will want to determine how much work we as a WG have the capacity for 20:05:03 brentz: My thought is between this week and next, if it works for the editors, we could create the set of editorial changes that we want to fold in as soon as 1.1 spec is released 20:05:14 brentz: Then next week we can make a WG resolution to incorporate changes 20:05:30 brentz: After that, i think it makes more sense to meet less often, and focus on WG charter for the next group 20:05:33 q+ to support what Brent said 20:05:36 brentz: Feedback about this? 20:05:37 q+ 20:05:39 ack manu 20:05:39 manu, you wanted to support what Brent said 20:05:50 manu: Largely supportive of that. I think we fulfilled charter tfor 1.1. update 20:06:05 manu: There are still some 1.1 editorial issues, I will make a pass through to see which ones really need to get in there 20:06:14 manu: I don't think there is anything that can't wait until re-chartering 20:06:21 manu: Also +1 to focusing on charter 20:06:39 manu: Did you say we will have fewer meetings? E.g. once a month? Or similar to DID WG? 20:06:49 manu: I'd be supportive of scaling back to once a month, or ad-hoc 20:06:56 brentz: That was my intention to say 20:07:00 ack DavicC 20:07:08 DavicC: When do we expect 2.0 WG to start? 20:07:22 brentz: Really good question. I had a good conversation with Ivan who is planning to be team contact. 20:07:30 brentz: I also had a good conversation with potential co-chair. 20:08:04 brentz: Best timeline we could come up with was .. Charter gets formally reviewed by AC and voted.. We could see new WG as early as late March, that's a best guess. 20:08:18 brentz: Any other questions about meetings, document status? 20:08:38 DavicC: Another question.. If during next week we do edits, can we still do edits in between now and March? 20:08:49 brentz: There is always more work that we _can_ do 20:09:14 brentz: Speaking personally, with all the DID work and this, it's been a heavy load, and a period without much spec work may be beneficial 20:09:34 DavicC: So we should only concentrate on really pressing issues 20:09:59 brentz: I think officially our charter ends at the end of April. That doesn't mean we have to continue meeting weekly, considering we have met charter demands. 20:10:08 Topic: VCWG Draft Charter 20:10:17 https://github.com/w3c/vc-wg-charter/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-asc 20:10:25 brentz: I believe there are 2 issues and we can close 1 20:10:39 subtopic: https://github.com/w3c/vc-wg-charter/issues/21 20:11:15 brentz: The discussion we had in this meeting, with lack of response from MikeJones who posted the issue, in my opinion this issue has been addressed and can be closed. 20:11:17 +1 to closing, agree with brentz's assessment. 20:11:19 brentz: Any disagrees? 20:11:39 brentz: Going to write a quick note and close it. 20:11:55 subtopic: https://github.com/w3c/vc-wg-charter/issues/38 20:12:51 shigeya: Sometimes we need to select from multiple image files to handle multi lingual text. Images may contain text inside images. 20:13:04 shigeya: This is different from how multilingual text is handled 20:13:25 shigeya: I was thinking about opening a PR, but I could not find a good way to disclose that in a simple text 20:13:38 brentz: Manu posted a comment 20:13:41 manu: But I was wrong 20:13:43 q+ 20:13:50 brentz: Any suggestions for shigeya how to address this? 20:13:52 ack manu 20:14:21 manu: We should reach out to Internationalization folks. We might want to ask them. Nothing is coming to mind, I understand the problem and desired to address it, but I don't know.. 20:14:35 manu: I could think of one way in JSON-LD how to do it, but not in this text approach. 20:14:43 manu: Maybe Internationalization folks have an idea how this can be done 20:14:56 shigeya: I will talk to my friend to find out who is best to talk to 20:15:04 brentz: As you discover things, please add comments to the issue 20:15:12 q+ 20:15:15 brentz: That is the set of issues. There are 2 PRs. 20:15:18 ack DavicC 20:15:53 DavicC: Work Human Colossus is doing on OCA could be a solution for this. They have tables with different tables to represent things. Table could also contain multiple images. 20:16:09 DavicC: I think markus is familiar with this 20:16:15 markus_sabadello: Little bit, but not enough to solve this 20:16:36 DavicC: I'll give you an email address of Human Colossus lead, you can chat to him directly. There are various presentations on Google, Youtube.. 20:16:48 subtopic: https://github.com/w3c/vc-wg-charter/pulls 20:16:48 DavicC: On ESSIF-Lab they did a demo a few weeks ago 20:16:51 brentz: Move on to PRs 20:17:05 subtopic: https://github.com/w3c/vc-wg-charter/pull/37 20:17:08 q+ 20:17:16 ack manu 20:17:41 manu: At a previous meeting we decided we wanted to move some cryptosuites into normative deliverables. 20:17:56 manu: Data Integrity is not a concrete serialization, but Ed25519 and JWP are 20:18:23 manu: This says we will work on concrete cryptosuites, and it lists some preliminary work that the WG could standardize 20:18:32 paul.knowles@humancolossus.org for details of Overlays Capture Architecture (OCA) that should provide a solution to multi-lingual images 20:18:42 manu: Markus raised a good point, what if we want to standardize additional cryptosuites. Current language isn't clear on it 20:19:05 manu: Specifically, we don't directly list NIST curves like P-386, we probably should add some language 20:19:08 +1 to language allowing too add curves 20:19:16 manu: Prefer to not pull in the PR until that language is in there 20:19:32 q+ 20:19:47 s/but Ed25519 and JWP are/but Ed25519 and VC-JWT are/ 20:19:56 brentz: I think we could leave it a bit more open 20:20:01 ack rgrant 20:20:05 q+ on the danger of open language (to argue against what I just said) 20:20:18 rgrant: Is there a requirement to focus only on NIST curves? 20:20:25 ack manu 20:20:25 manu, you wanted to comment on the danger of open language (to argue against what I just said) 20:20:27 manu: k1 curve potentially 20:20:36 bumblefudge has joined #vcwg 20:20:51 hey @shigeya 20:20:51 manu: If we are vague, we might do normative things on all of it. This might be a red flag on charter review, since we're not very clear on concrete realizations we want to do. 20:21:00 manu: Feedback may be we need to specify this exactly. 20:21:10 manu: W3C members don't like very open charters 20:21:11 the oca repo is here: https://github.com/the-human-colossus-foundation/oca-spec 20:21:27 manu: That's the challenge with making it more general. If we can't point to a draft spec, people might push back on it. 20:21:32 they do some overlay/decorator stuff for mapping VC property names to new languages and char-sets 20:21:38 @bumblefudge thank you very much. Will check the repo. 20:21:40 manu: Easiest thing to do would be to point to draft spec. I think there is one for k1. 20:21:47 it may be helpful. i believe it's MIT if I remember correctly 20:21:55 manu: Before charter goes out for review, someone could create a cryptosuite 20:22:11 described here: https://humancolossus.foundation/blog/cjzegoi58xgpfzwxyrqlroy48dihwz 20:22:17 manu: Safest thing to do would be, if you want a particular type of cryposuite to be standardized, create a draft spec for it that we can cite in the charter. 20:22:22 https://w3c-ccg.github.io/lds-ecdsa-secp256k1-2019/ ? 20:22:26 makes sense here 20:22:56 brentz: How harmful would it be to include a line "an others as determined by the WG" 20:23:08 manu: We can do that, I would expect that to result in a Formal Objection 20:23:11 manu: We could try 20:23:24 manu: If we are tied to it, we probably should be very specific 20:23:30 brentz: So we hold off on merging this PR 20:23:43 brentz: Make comments on the PR if you want additional cryptosuites 20:24:03 manu: If someone wants a NIST curve, we could put together a cryptosuite 20:24:08 brentz: Other comments or questions? 20:24:11 subtopic: https://github.com/w3c/vc-wg-charter/pull/39 20:24:32 +1 to merge. 20:24:38 brentz: Markus fixed a link, appreciate that 20:24:40 brentz: Any concerns? 20:25:23 brentz: That's our draft charter work, like I said we anticipate within a couple of weeks sending it out to the AC. 20:25:34 Topic: Review PRs 20:25:35 brentz: We don't have a lot of time to discuss; if there is any more tweaking, it needs to happen soon 20:25:41 https://github.com/w3c/vc-data-model/pulls?q=is%3Apr+is%3Aopen+label%3A%22v1.1+%28editorial%29%22+sort%3Aupdated-asc 20:26:28 https://github.com/w3c/vc-data-model/pull/847 20:26:28 subtopic: https://github.com/w3c/vc-data-model/pull/847 20:26:53 brentz: By Kyle, this tries to add language to clarify difference between @context and credentialSchema 20:26:58 s/brentz/manu/ 20:27:15 manu: I asked for changes, DavicC asked for changes as well. DavicC you rejected this? 20:27:33 DavicC: I don't know what the results of my proposed edits are. If my edits are accepted, I'd be +1 20:27:48 DavicC: I got -1 from him, he doesn't want to add types, seems he is rejecting all my changes 20:27:57 manu: So we can't do anything with this without more discussion 20:28:07 DavicC: He accepted one of my proposed changes 20:28:21 manu: I forgot to hit my "request changes" button. 20:28:31 manu: We can't pull it in, will pick it up later 20:28:49 manu: Adding a comment to the PR about there still being disagreement 20:28:59 subtopic: https://github.com/w3c/vc-data-model/pull/859 20:29:14 manu: Renaming LD Proofs to Data Integrity, by Markus 20:29:31 manu: I haven't approved it yet, looks like it does what it says, looks good to me 20:29:46 manu: It's a change we've made across the board 20:29:54 manu: Anyone on the call concerned with this? 20:30:34 manu: We had just 1 day period on this PR.. 20:30:48 brentz: I think we need a resolution what we will merge next week 20:30:51 manu: This will go in 20:31:00 bumblefudge has joined #vcwg 20:31:08 subtopic: https://github.com/w3c/vc-data-model/pull/855 20:31:21 manu: Set of hand-optimizations to SVG files by Charles 20:31:32 manu: brentz I think you were concerned about changes you requested? 20:31:40 brentz: I believe requested changes have been made 20:31:46 manu: No objections I can see 20:32:01 manu: If there are no huge problems with it, we should take the PR into the change set for next week 20:32:20 manu: Any objections or concerns? 20:32:23 manu: Charles is basically optimizing and compressing SVGs. 20:32:48 subtopic: https://github.com/w3c/vc-data-model/pull/857 20:32:58 manu: DavicC 5 days ago you opened this, and got changes requested from dlongley 20:33:09 manu: I guess as long as these changes are made, this should go into change set for next week 20:33:23 manu: These are all of our 1.1 editorial PRs 20:33:38 manu: For 847 there's time until next week to try to resolve it 20:33:52 Topic: Triage Issues 20:34:06 brentz: We still have a week to try and get PRs in 20:34:20 https://github.com/w3c/vc-data-model/issues?q=is%3Aopen+is%3Aissue+-label%3Av2.0+-label%3A%22v1.1+%28editorial%29%22+sort%3Aupdated-asc 20:34:25 brentz: It's still worth looking at issues to see if they fit in scope of work that is still before us 20:34:55 q+ 20:34:58 brentz: Support for multiple signatures https://github.com/w3c/vc-data-model/issues/856, appying a v2.0 label now 20:35:06 ack manu 20:35:15 manu: No concerns with the actions. We do have a number of items that are marked as 1.1 editorial 20:35:20 brentz: That's the next topic 20:35:21 Topic: v1.1 Issues 20:35:31 https://github.com/w3c/vc-data-model/issues?q=is%3Aopen+is%3Aissue+label%3A%22v1.1+%28editorial%29%22+sort%3Aupdated-asc 20:35:57 brentz: All v1.1. editorial issues are at this link. Any of them we want to get into the spec? We should sort that out pretty much today 20:36:27 q+ 20:36:29 manu: Maybe just ask everyone on the call to look at them, and scream if one needs to be addressed? 20:36:48 ack DavicC 20:36:56 DavicC: I'm interested in JWT examples 20:37:00 manu: I'll take that action 20:37:07 DavicC: That's a really good beneficial improvement 20:37:20 DavicC: Issues 836 and 838? 20:37:32 manu: I'm talking about 838 20:37:46 DavicC: It's the presigned, which is useful 20:38:00 manu: If I can get to it, I will 20:38:02 DavicC: Can I help you? 20:38:10 manu: Sure, add the features to the software library 20:38:16 DavicC: Can I hand-do it? 20:38:24 manu: No, it's automatically applied, requires software development 20:38:42 manu: I'll try to do it, it will be in the same area of code.. Just depends whether I have enough time to do it 20:38:56 brentz: Is it different code for every example? 20:39:10 manu: Just need to write the code, test it, pull in new version.. Not hard, just takes time 20:39:39 brentz: Anything else people feel needs to happen? 20:39:50 brentz: Otherwise issues will wait for next WG where we can cover them 20:40:18 brentz: Plan is to meet again in 1 week at a slightly earlier time. We will have a recently published revised recommendation 20:40:45 brentz: We will have a set of PRs that we have already merged, and a set of PRs in addition to that, and a proposal to the group to incorporate them 20:41:11 brentz: Kyle should we talk about the PR with you and DavicC ? 20:41:21 Kyle: I can review Github comments 20:41:29 brentz: I think 1-on-1 between you and DavicC would be helpful 20:41:34 Kyle: Makes sense 20:41:58 DavicC: Timezone is challenging.. Should we have a private Zoom call now? 20:42:01 kdenhartog has joined #vcwg 20:42:01 Kyle: Works for me 20:42:09 brentz: Will end this meeting. 20:42:17 DavicC: Can we stay on this Zoom? 20:42:24 brentz: It should stay open 20:42:34 thx all 20:42:43 brentz: Thanks everyone for incredible work, looking forward to working with you in a newly chartered group 20:43:22 zakim, who is here? 20:43:22 Present: brentz, shigeya, markus_sabadello, loganporter, rgrant, manu, dlongley, JoeAndrieu_, DavicC 20:43:24 On IRC I see kdenhartog, bumblefudge, DavicC, JoeAndrieu_, rgrant, markus_sabadello, RRSAgent, Zakim, brentz, tzviya, cel, wayne, hadleybeeman, shigeya, manu, dlongley, stonematt, 20:43:24 ... bigbluehat, cel[m], juancaballero, dlehn, rhiaro, agendabot 20:43:42 present+ bumblefudge 20:44:04 zakim, end the meeting 20:44:04 As of this point the attendees have been brentz, shigeya, markus_sabadello, loganporter, rgrant, manu, dlongley, JoeAndrieu_, DavicC, bumblefudge 20:44:06 RRSAgent, please draft minutes 20:44:06 I have made the request to generate https://www.w3.org/2022/01/12-vcwg-minutes.html Zakim 20:44:09 I am happy to have been of service, brentz; please remember to excuse RRSAgent. Goodbye 20:44:14 Zakim has left #vcwg 20:44:18 rrsagent, goodbye 20:44:18 I'm logging. I don't understand 'goodbye', brentz. Try /msg RRSAgent help 20:44:24 rrsagent, bye 20:44:24 I see no action items