15:03:13 <RRSAgent> RRSAgent has joined #did
15:03:13 <RRSAgent> logging to https://www.w3.org/2020/07/14-did-irc
15:03:25 <justin_r> justin_r has joined #did
15:03:27 <Zakim> Zakim has joined #did
15:03:27 <justin_r> present+
15:04:18 <burn> scribe+
15:04:34 <burn> Topic: agenda review
15:04:42 <rhiaro> present+
15:04:53 <agropper> agropper has joined #did
15:05:05 <burn> brent: any changes to the agenda?
15:05:12 <manu> q+
15:05:18 <brent> ack manu
15:05:26 <rhiaro> RRSAgent, make logs public
15:05:31 <burn> manu: want to close some PRs, specifically justin's open PRs.
15:05:37 <agropper> present+
15:05:47 <burn> brent: right before our issue status check
15:05:53 <Eugeniu_Rusu> Eugeniu_Rusu has joined #did
15:05:55 <rhiaro> zakim, start meeting
15:05:55 <Zakim> RRSAgent, make logs Public
15:05:56 <Zakim> please title this meeting ("meeting: ..."), rhiaro
15:05:57 <burn> Topic: Introductions?
15:06:02 <rhiaro> Meeting: DID WG
15:06:48 <burn> drummond: I'm an editor of our key spec, for a loooong time now :)
15:06:55 <burn> ... chief trust officer at Evernym
15:07:04 <burn> ... have been working on DIDs for close to 4 years now
15:07:05 <jonathan_holt> jonathan_holt has joined #did
15:07:29 <burn> ... also VCs and everything related.  I present DAILY on the importance of DIDs.  Let's get it done!
15:07:42 <selfissued> You should just pick up the pen and finish it, Drummond!
15:08:00 <burn> brent: next topic call scheduled for this Thursday, June 16, noon EDT.  Same zoom link but different irc channel.  Topic will be metadata
15:08:08 <burn> ... if time permits we will move on to key formats
15:08:13 <Eugeniu_Rusu> present+
15:08:15 <burn> Topic: f2f stuff
15:08:17 <drummond> drummond has joined #did
15:08:23 <drummond> present+
15:08:32 <identitiywoman> identitiywoman has joined #did
15:08:33 <manu> present+
15:09:01 <manu> q+
15:09:03 <burn> brent: just completed a virtual f2f meeting.  Several key topics, made good progress.  Any comments or feedback on what went well, was missing, format of the meeting, etc.?
15:09:18 <brent> ack manu
15:09:43 <burn> manu: timing of the sessions was great.  90 minutes on one topic followed by a break was great.  Felt very manageable.  We could easily do 2 of those a year.
15:09:54 <burn> ... not as bad as an all-day meeting.
15:10:07 <burn> ... made good progress but have already forgotten what we discussed :)
15:10:21 <jonathan_holt> present+ jonathan_holt
15:10:24 <burn> ... happy about general structure
15:10:37 <manu> +1 yes, meaningful use of time
15:10:40 <burn> brent: was it a good use of our time?
15:10:43 <JoeAndrieu> thanks, Amy
15:10:50 <burn> ... anyone who thought it wasn't?
15:10:59 <drummond> q+
15:11:06 <brent> ack drummond
15:11:12 <dlongley> +1 was productive
15:11:22 <burn> drummond: really thought the chunks of time helped
15:11:41 <burn> ... hope remaining topic calls will be enough.  Tomorrow's feature freeze is also momentous.
15:11:57 <burn> brent: Yes, feature freeze is TOMORROW.
15:12:20 <burn> ... did anyone miss the f2f and needs info?
15:12:29 <markus_sabadello> q+
15:12:44 <brent> ack markus_sabadello
15:13:05 <burn> markus_sabadello: I particularly remember dmitri's session on the test suite.  Well prepared and something we need to start working on.  What are the next steps there?
15:13:21 <Orie> See the issues! https://github.com/w3c/did-test-suite/issues
15:13:21 <burn> brent: yes, we will have a special topic call on the test suite.  To be scheduled
15:13:46 <burn> ... the repo exists (see Orie's link above)
15:14:53 <burn> ... if anyone has more to report or complaints, please email the chairs
15:15:18 <burn> Topic: PRs from manu (Justin, really)
15:15:24 <manu> https://github.com/w3c/did-core/pulls
15:15:41 <justin_r> q+
15:15:53 <burn> manu: justin, there are some old PRs we think we can close.  Which ones do you think we can?
15:15:56 <brent> ack justin_r
15:16:11 <burn> justin_r: go ahead and close all of them.  They are as far as they will get.
15:16:32 <markus_sabadello> q+
15:16:40 <burn> manu: some have to do with metadata.  editors may raise a new PR around infra, but didn't want to close yours wihout discussing.
15:17:03 <brent> ack markus_sabadello
15:17:08 <burn> justin_r: manage them as you see fit.  Even if closed they are not gone.  But do what you believe is appropriate.
15:17:23 <burn> markus_sabadello: let's keep them open at least until our special topic call this week.
15:17:41 <burn> manu: let's leave the complete one (with metadata), and add a new PR to compare/contrast
15:18:15 <burn> markus_sabadello: others around contract can be closed.  They have been addressed in some way (other than derefer]ncing)
15:19:01 <burn> justin_r: 299 has more content than 300.  close 253, 295, 297, 298, and 300
15:19:08 <markus_sabadello> q+
15:19:31 <justin_r> q+
15:19:42 <burn> markus_sabadello: some of 253 hasn't been incorporated.  We could close it and add a new issue for dereferencing.
15:19:42 <brent> ack markus_sabadello
15:19:48 <burn> manu: will leave it open for now
15:19:49 <brent> ack justin_r
15:20:33 <burn> justin_r: on leaving 253 open, I didn't touch deref in whole series because an objection was raised about the topic itself.  if it showed up again it would need to be very different than whats' in 253
15:20:52 <burn> ... it has not been addressed yet, but 253 doesn't do it and it's not clear if we are even doing it.
15:21:10 <burn> brent: so let's open an issue for deref just to track the discussion?
15:21:19 <burn> manu: there may already be one
15:21:36 <burn> brent: we may not need to decide now.  I trust the editors here to do the right thing.
15:21:50 <burn> Topic: core issue status check
15:21:50 <brent> https://github.com/w3c/did-core/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-asc
15:22:11 <brent> https://github.com/w3c/did-core/issues/176
15:22:28 <wayne> present+
15:22:59 <burn> selfissued: still on my todo list.
15:23:31 <brent> https://github.com/w3c/did-core/issues/85
15:24:00 <burn> selfissued: we should talk about this in the metadata call
15:24:15 <brent> https://github.com/w3c/did-core/issues/203
15:24:40 <burn> justin_r: that's the topic of the call.
15:24:49 <brent> https://github.com/w3c/did-core/issues/95
15:25:02 <burn> s/of the call/of the upcoming call/
15:25:14 <burn> justin_r: we can close this.
15:25:44 <brent> https://github.com/w3c/did-core/issues/94
15:26:18 <burn> brent: dan and I have a plan for this.  we need to act on it
15:26:49 <brent> https://github.com/w3c/did-core/issues/163
15:27:24 <burn> drummond: doing this as we go along, but final cleanup will be for CR
15:27:49 <brent> https://github.com/w3c/did-core/issues/119
15:28:17 <burn> brent: this is waiting on #92
15:28:34 <brent> https://github.com/w3c/did-core/issues/291
15:28:36 <burn> s/92 and 291/
15:28:45 <jonathan_holt> q+
15:28:57 <brent> ack jonathan_holt
15:29:23 <burn> jonathan_holt: questions are about how it's implemented.  Has to do with did resolution.  Which depends on info in DID document.
15:29:24 <gannan> gannan has joined #did
15:29:41 <burn> ... three questions.  Is there a questionnaire where I can submit what I have
15:29:54 <burn> ... I'm not qualified to address the threat models
15:30:13 <burn> brent: not aware of a form, just need to write them up. Can others help?
15:30:37 <phila> phila has joined #did
15:30:40 <burn> jonathan_holt: these questions are about web browser security, in our case we have did browsers, so different.
15:31:00 <burn> brent: may be helpful to look at VC privacy and security questionnaire info
15:31:07 <burn> ... explains what does and doesn't apply
15:31:22 <burn> ... i will email link to jonathan
15:31:45 <burn> jonathan_holt: we are effectively building a did browser.
15:31:54 <burn> brent: but we are not defining resolution
15:32:01 <manu> q+ to note some things w/ PING review
15:32:04 <burn> jonathan_holt: depends on how you implement the contract for a did browser
15:32:17 <burn> brent: can you please add a comment here about the plan?
15:32:22 <brent> ack manu
15:32:22 <Zakim> manu, you wanted to note some things w/ PING review
15:33:02 <burn> manu: typically PING reviews require us to first talk about the spec itself, privacy issues in the core itself, then separately the broader ecosystem it fits into.
15:33:13 <wayne> q+
15:33:20 <burn> ... with VCs most of the text was about pontificating on the broader ecosystem
15:33:46 <burn> ... think about every response with both lenses:  every feature in the spec by itself, then what happens when used in the broader ecosystem.
15:34:15 <burn> ... it's really only what's in the spec that we can be forced to address.  Because we can't stop a determined adversary in the wild
15:34:32 <burn> wayne: would like to help here, jonathan.
15:34:37 <brent> ack wayne
15:34:42 <manu> +1 to wayne's volunteering to work on it! :)
15:34:45 <agropper> q+ Happy to help with PING as well
15:35:08 <brent> ack Happy
15:35:08 <Zakim> Happy, you wanted to help with PING as well
15:35:11 <burn> agropper: also happy to help with PING questions
15:35:31 <jonathan_holt> will do, thanks!
15:35:39 <burn> brent: the three of you should connect directly among yourselves at this point.
15:35:49 <brent> https://github.com/w3c/did-core/issues/58
15:36:16 <dlongley> q+ to comment on #289
15:36:22 <burn> brent: no resolution yet, conversation ongoing
15:36:25 <brent> https://github.com/w3c/did-core/issues/289
15:36:27 <brent> ack dlongley
15:36:27 <Zakim> dlongley, you wanted to comment on #289
15:36:42 <Orie> close it
15:36:46 <burn> dlongley: we can close this.  PR 312 resolved this.  Orie agreed on the PR.
15:37:14 <brent> https://github.com/w3c/did-core/issues/269
15:37:39 <burn> brent: conversation between kyle and joe.  any update, joe?
15:38:31 <burn> JoeAndrieu: not much to report.  With feature freeze this may get closed.
15:38:42 <burn> brent: feature freeze doesn't apply since already brought up
15:39:05 <burn> ... maybe possibilities on what to do, but just waiting on kyle.
15:39:11 <burn> JoeAndrieu: will add a note asking if kyle has any more comments.
15:39:19 <brent> https://github.com/w3c/did-core/issues/23
15:40:10 <burn> Orie: we discussed at f2f.  making sure that you get support for popular formats out of the box.  Still working on JOSE.
15:40:32 <burn> brent: if the metadata conversation goes quickly we can move on to this in our topic call this week
15:40:41 <brent> https://github.com/w3c/did-core/issues/205
15:41:03 <justin_r> q+
15:41:10 <brent> ack justin_r
15:41:42 <selfissued> q+
15:41:44 <burn> justin_r: not aware of any movement on this.  ignored still not fully defined.  editors, has more happened here?
15:41:49 <burn> manu: not yet
15:42:00 <burn> justin_r: needs to remain open until it's clear in the spec
15:42:02 <brent> ack selfissued
15:42:40 <dlongley> q+
15:42:41 <burn> selfissued: not clear that needs to be expanded.  already standard language in a bunch of IETF specs.
15:42:52 <burn> ... not sure what else you want to say.  it's fine as is
15:42:53 <brent> ack dlongley
15:43:03 <burn> brent: please dis9cuss in issue
15:43:37 <burn> dlongley: others have commented on case where things need to be transformed.  here we are supporting other formats.  in that case may need to throw an error.
15:43:40 <selfissued> q+
15:43:45 <burn> ... need to handle ambiguity.
15:43:54 <burn> brent:  a PR would be helpful here
15:43:56 <brent> ack selfissued
15:44:19 <burn> selfissued: throwing an error is not ignoring it.  Otherwise you can't do extenisions.  If you comment in issue I'll respond.
15:44:21 <dlongley> q+
15:44:27 <brent> ack dlongley
15:44:31 <burn> ... you don't throw an error when you ignore, you just ignore.
15:44:39 <burn> dlongley: made my comment in the issue now.
15:45:04 <burn> brent: if anyone has specific text to resolve, please submit a PR
15:45:08 <brent> https://github.com/w3c/did-core/issues/195
15:45:27 <Orie> q+
15:45:45 <brent> ack Orie
15:46:20 <burn> Orie: we've had some discussion.  different did methods handle this differently.  May not be able to say more.  I will add a comment to that effect.  May not be a standard way.
15:46:36 <burn> brent: please also note if you believe the issue can be closed.
15:46:44 <brent> https://github.com/w3c/did-core/issues/137
15:46:53 <burn> s/say more/say more in the spec/
15:47:27 <burn> markus_sabadello: lots of discussion on how params work.  issue was about whether the specific params in the spec now are normative and must be supported.
15:47:38 <manu> q+
15:47:55 <burn> ... there are 4  right now in the spec and registries.  Others have been proposed.  Question still remains.
15:48:26 <brent> ack manu
15:48:26 <burn> ... is it okay to define resolution params without details on how resolution works
15:48:52 <burn> manu: i will add to the issue that the language around the did params has been modified to get us all the way through rec as-is.
15:49:06 <burn> ... we point to an internet-draft, for example.
15:49:26 <burn> ... current weasel wording should be good enough.  The question is whether we want the current wording or not.
15:49:47 <burn> brent: all please review spec text and comment in issue if needed.
15:49:51 <brent> https://github.com/w3c/did-core/issues/325
15:50:41 <burn> manu: we need to discuss as group. commenter is correct.  we should talk about the r1 and k1 values.  already in the issue.
15:51:13 <burn> manu: can be part of keys discussion.  If not, those who care about r and k curves and expression as raw byte string, please comment in issue.
15:51:34 <brent> https://github.com/w3c/did-core/issues/72
15:53:02 <burn> drummond: it's all about GDPR.  Wrote comment in issue.  Wants to wait until close to CR to write this because related info continues to evolve.
15:53:13 <brent> https://github.com/w3c/did-core/issues/327
15:54:12 <burn> Orie: I got it to work.  First time deref ever used for a package manager.  It was basically an experiment and we can close the issue.  By fixing the way DID params are referenced this now works.
15:54:19 <burn> ... I will comment and close
15:54:30 <brent> https://github.com/w3c/did-core/issues/332
15:55:24 <manu> +1 to this PR, I'd like to do this as soon as Gihub pages are fixed.
15:55:31 <manu> s/this PR/this issue/
15:55:38 <manu> Thank you to brent for raising it :)
15:55:41 <burn> brent: this is a relic of our vocab and github tooling.  The tooling is changing such that we should be able to do this eventually without wrecking everyone's work.  We should wait until that point.  I will make a comment and look forward to doing this.
15:55:57 <brent> https://github.com/w3c/did-core/issues/174
15:56:22 <burn> selfissued: no update.  on my todo list.
15:56:42 <burn> brent: related to metadata so may get resolved soon.
15:56:51 <brent> https://github.com/w3c/did-core/issues/118
15:57:07 <rhiaro> brent, same update, waiting for nearer to CR
15:57:55 <phila> present+ (if somewhat late to the party)
15:58:21 <gannan> present+
15:58:57 <burn> rrsagent, draft minutes
15:58:57 <RRSAgent> I have made the request to generate https://www.w3.org/2020/07/14-did-minutes.html burn
16:02:34 <jonathan_holt> jonathan_holt has joined #did
16:15:06 <dmitriz> dmitriz has joined #did
16:21:01 <JoeAndrieu> JoeAndrieu has left #did
18:14:23 <Zakim> Zakim has left #did