14:52:54 RRSAgent has joined #did 14:52:54 logging to https://www.w3.org/2020/06/02-did-irc 14:53:02 Zakim has joined #did 14:53:25 burn has changed the topic to: 02 June 2020 DID WG Agenda: https://lists.w3.org/Archives/Public/public-did-wg/2020May/0038.html 14:54:05 Meeting: DID WG Telco 14:57:30 present+ 14:58:49 chair: burn 14:59:14 markus_sabadello has joined #did 14:59:33 phila has joined #did 14:59:41 present+ 15:00:05 jonathan_holt has joined #did 15:00:21 present+ phila 15:00:21 present+ 15:00:27 Orie has joined #did 15:00:28 present+ jonathan_holt 15:00:31 Justin_R has joined #did 15:00:34 present+ 15:00:35 present+ Justin_R 15:00:39 present+ 15:00:42 present+ 15:00:50 present+ 15:01:33 brent has joined #did 15:01:43 present+ 15:02:21 selfissued has joined #did 15:02:25 present+ 15:02:37 present+ 15:02:56 oliver has joined #did 15:03:01 present+ oliver_terbu 15:03:06 Eugeniu_Jolocom has joined #did 15:03:37 identitywoman has joined #did 15:04:23 chair: brent 15:05:17 drummond has joined #did 15:05:27 present+ 15:05:30 dezell has joined #did 15:05:32 present+ 15:05:38 present+ 15:06:00 scribe+ dezell 15:06:50 Topic: Agenda Review 15:07:00 No requests. 15:07:33 Topic: Reintroductions 15:07:38 scribe+ brent 15:08:17 dezell: I work for a trade association. We work closely with convenience stores. We are very interested in using DIDs in a variety of use cases. Been at W3c for 20 years. 15:08:21 scribe+ 15:08:23 dezell: I'm David Ezell, work for a trade association called Conexxus, and work closely with National Association of Convenience Stores (NACS). I'm not a cryptography expert, but care very much about availability of these technologies and application to our work. I've been at W3C for 23 years. 15:08:35 Topic: Next Topic Call 15:09:07 brent: 6PM today eastern. DID core properties and metadata. 15:09:14 present+ 15:09:16 present+ 15:09:37 ... Seems like the week of June 29 - July 3 works well for being able to have some additional meetings. 15:09:45 ... watch for a doodle poll. 15:10:39 ... each block will be about 90 minutes, with a break of 90 minutes, over the course of 3 or so days. 15:10:51 q? 15:10:58 ... we hope people will give these meetings precidence. 15:11:05 In other words, it's not a face-to-face but should be given the same priority 15:11:06 present+ identitywoman 15:11:44 present+ 15:11:47 ... it will be hard to replicate a face to face, but we'll do our best. 15:11:52 brent can you please repeat the week the meetings will occur? 15:12:01 (for the minutes) 15:12:21 drummond: just trying to get a feel... 15:12:36 brent: June 29 is only 4 weeks away. 15:12:48 ... doodle poll should be out this week. 15:13:01 Topic: registries document status 15:13:20 ... and Amy!!! 15:13:50 ... expecting to publish a FWD note soon. [scribe missed the antecedent] 15:14:38 +1 to publish FPWD of DID Specification Registries document! 15:14:55 DID Specification Registries FPWD NOTE 15:15:04 https://w3c.github.io/did-spec-registries/ 15:15:20 s/FWD note/FPWD note/ 15:15:21 Many thanks to both Orie and Amy for their work on this (and Manu too, but Manu's everywhere ;-) 15:15:23 DID Specification Registries FPWD NOTE [11:15] https://w3c.github.io/did-spec-registries/ 15:15:30 Topic: Editors' issues 15:16:05 q+ 15:16:42 manu: a couple of PRs - especially CBOR. 15:16:53 q+ 15:17:04 ... there's a question about what to do with the PR... pull into spec? 15:17:16 q+ 15:17:17 ... if we do that I'd like a huge warning (experimental). 15:17:22 ack manu 15:17:33 ... we're in a weird place - trying to finish with new things coming in. 15:17:56 ... there is some misalignment with what to do with that section. 15:18:22 ... So, editors' intention is to pull in the section with a big warning, and we'd like to know how the group feels about that. 15:18:32 gannan has joined #did 15:18:47 q+ to talk about "experimental" 15:18:58 ack jonathan_holt 15:18:59 ... we'd also like Jonathan to know that the section >may< come out of the spec if it meets with disagreement from review. 15:19:09 q? 15:19:19 jonathan: would appreciate more eyes on this part of the spec. 15:19:45 ... what's in the PR, it's moving toward "DAG" CBOR (IPID). 15:19:56 [scribe not familiar with terminology] 15:20:28 ... CBOR allows integers, be we constrained to strings. 15:20:39 ... this offering is NOT CBOR-LD. 15:21:02 ack ivan 15:21:14 ... the core data model is not quite mature, and we'll have a better idea of what can be extended with experience. 15:21:43 Ivan: normally we could call this a "feature at risk" signaling that it might be removed. 15:21:44 q+ to comment on labeling as feature at risk 15:22:01 ack Justin_R 15:22:01 Justin_R, you wanted to talk about "experimental" 15:22:11 ... while this kind of thing is good in a near-final publication, it feels out of place in a FWD. 15:22:33 q+ 15:22:49 Justin: it feels like "fear mongering" to be too strong with our worries about the section. 15:23:00 ack burn 15:23:00 burn, you wanted to comment on labeling as feature at risk 15:23:06 ... I think the section belongs without the warning. 15:23:52 ack selfissued 15:23:57 burn: we don't need to out that label on today. There is plenty of time (before end of candidate recommendation) when we need implementation reports from two implementors. 15:24:14 mike: I agree it should go in, with no warning. 15:24:38 manu: I will then merge it in with no warning. I have a worry that I don't know of any implementor planning to use CBOR. 15:24:56 present+ ganesh 15:24:57 I've also not seen a single company this commited to "Pure JSON", so.... same thing applies to that. 15:25:06 ... we could spend a lot of time working on a feature with no second implementer. 15:25:27 ... there are a few change suggestions. Jonathan, please review, and let us know. 15:25:35 present+ yancy 15:25:35 Jonathan: will do. 15:25:45 Good point Orie 15:25:52 manu: Amy put in editorial PRs that deserve review. 15:26:16 ... since Jonathan won't be able to make the special call today, we'll put that discussion on hold. 15:26:41 ... we have other requests we'll talk about on the special call later today. 15:26:51 burn: any other editors' issues? 15:26:57 Topic: Core issue status check 15:27:24 https://github.com/w3c/did-core/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-asc 15:27:31 drummond: I'm working on the terminology section - please send me notes. 15:27:40 https://github.com/w3c/did-core/issues/176 15:28:13 burn: last comment was Mike said he would reread and comment. Any update. 15:28:21 mike: please skip. 15:28:23 https://github.com/w3c/did-core/issues/205 15:28:47 burn: from Justin. Any update. 15:29:13 Justin: sorry I haven't been keeping up. We need to pick something. Consistent across representations. 15:29:44 q? 15:29:50 ... We need to define "if you see a property you don't understand, what should you do?" 15:29:56 q+ 15:30:04 ... JSON systems tend to ignore such properties. 15:30:10 ack selfissued 15:30:37 mike: I thought there was already a statement saying unknown properties MUST be ignored. 15:30:47 dmitriz has joined #did 15:30:51 present+ 15:30:55 justin: I put in text, but it's only one possible solution. 15:31:16 burn: this is a status check only, don't want to go to deeply. 15:31:30 q+ 15:31:40 ack selfissued 15:31:44 ... those interested please go put your opinions in the issue and then we can decide whether to schedule more discussion. 15:32:14 mike: don't we already have text that says unrecognized members should be ignored. What's the issue? 15:32:26 justin: I want to be sure that is the will of the group. 15:33:03 burn: we're still working on it. Text that has been discussed thoroughly has a higher bar for change. 15:33:15 https://github.com/w3c/did-core/issues/176 15:33:40 mike: I need to create a PR - I haven't worked on it yet. 15:33:52 https://github.com/w3c/did-core/issues/199 15:34:51 brent: status started with a question that turned into a broad discussion. A lot of suggestions, including [scribe missed] changes to the document. PR needs to be created. 15:35:22 drummond: I will work with Brent on this PR. 15:35:42 https://github.com/w3c/did-core/issues/154 15:36:32 oliver: I think Orie should give the comments. 15:37:08 orie: we went over the did registry property definitions, and have made changes that should be reviewed. 15:37:24 ... we're ready to make progress so review should happen soon. 15:37:25 q+ 15:37:46 burn: you had said progress was blocked by the registries discussion, so what is the exact status? 15:37:52 q? 15:37:56 ack jonathan_holt 15:38:29 jonathan: I struggled to use the "proof" section of the document in the CBOR section. 15:38:31 jonathan_holt - there's a PR to remove proof.. if that helps? 15:38:48 ... this is where I need some guidance. 15:39:03 burn: is that a question for this issue, or is it a broader question for the group? 15:39:34 jonathan: I think LD proof need not to be the only proof mechanism, and I'll work on that. 15:39:43 jonathan_holt, see https://github.com/w3c/did-core/pull/305 15:39:50 https://github.com/w3c/did-core/issues/198 15:40:13 Eugeniu_Jolocom_ has joined #did 15:40:36 marcus: several iterations of PRs, see 295-300 (PRs). 15:41:11 ... function definition for resolution, my opinion is that we should merge one (296?) 15:41:19 In order: https://github.com/w3c/did-core/pull/295 https://github.com/w3c/did-core/pull/296 https://github.com/w3c/did-core/pull/297 https://github.com/w3c/did-core/pull/298 https://github.com/w3c/did-core/pull/300 https://github.com/w3c/did-core/pull/299 15:41:22 burn: please add the other references. 15:41:37 https://github.com/w3c/did-core/issues/236 15:42:18 q? 15:42:34 https://w3c.github.io/did-spec-registries/#publickeyhex 15:42:55 manu: the registries discussion is leading to more work. Public Key hacks will go into the document. Orie, where will we point from the registry? 15:43:18 q+ 15:43:23 orie: we may end up with a big bucket in git. 15:43:31 manu: we'll put that in the issue. 15:43:33 ack selfissued 15:44:01 yes :) 15:44:14 mike: we're not just defining terms, we're describing the semantics of the identifier and how it's used. 15:44:25 orie: I agree 15:44:27 https://github.com/w3c/did-core/issues/118 15:44:47 burn, I put in a comment for current status 15:45:30 burn: Amy, we need to conform to Accessibility guidelines, but we need an initial review request. 15:45:32 burn, I don't know anything about asking for review, I'm just working through the self checklist 15:45:54 burn: I'm asking about the self-review beginning horizontal review. 15:46:01 https://github.com/w3c/did-core/issues/260 15:46:56 drummond: I think the issue of "more than one controller" is related to "DIDs being identified." Therefore I'll put my name on this issue. 15:47:04 https://github.com/w3c/did-core/issues/178 15:47:06 q? 15:47:48 yancy: I haven't started considering this issue. 15:47:58 burn: do you understand what needs to happen? 15:48:15 yancy: I have in mind the needed wording, but haven't done anything yet. 15:48:35 burn: could you just put a quick idea of what you intend in the issue. 15:48:35 https://github.com/w3c/did-core/issues/195 15:49:35 manu: there is on-going discussion about whether or not what verification methods are authorized to do updates, and should that be in did-core or did methods. 15:50:06 ... IMO did methods will have to specify what verification methods can operate on a DID document. 15:50:19 burn: yes, we still have to establish the rules. 15:50:25 https://github.com/w3c/did-core/issues/8 15:50:51 burn: my name is on here, along with Brent and Mike. 15:51:12 ... anyone like to offer an opinion? 15:51:14 q+ 15:51:21 q+ 15:51:22 ack Orie 15:52:08 orie: verification methods are often a function of the upper level type attribute. 15:52:16 ack selfissued 15:52:25 ... I'm not in favor of adding any language. 15:52:45 mike: public key JWK should be a self-contained description - that was the issue. 15:52:56 burn: doesn't seem there's agreement - so we need a call. 15:53:42 ... "needs special call". I'll remove "discuss". Needs to be flagged as needing more than just comments in the issue. 15:54:16 qL 15:54:19 q? 15:54:25 ... removing myself and brent, since we were only there bec.ause we needed a call, and we have a method for that 15:54:37 https://github.com/w3c/did-core/issues/85 15:55:20 That is what the last comment says, though -- just fwiw 15:55:24 burn: we haven't had a comment for a month. Marcus please add. 15:56:13 justin: says it's addressed in PR 253. Marcus please add that, too. 15:56:20 https://github.com/w3c/did-core/issues/14 15:56:54 burn: Christopher, Daniel, Oliver assigned... 15:57:00 is joe here? 15:57:11 this is mostly blocked by his comments afaik... 15:57:19 ... looking for someone to give a status. 15:57:27 q+ 15:57:53 ack Orie 15:58:09 q+ 15:58:14 orie: mike has a PR request not to allow revoked keys, and I'll follow up. 15:58:42 burn: time to bring this one to a close. 15:58:44 ack selfissued 15:58:57 mike: what's the status of merging the PR to address? 15:59:13 manu: it's merged, but people are saying it didn't address the issue. 15:59:24 q+ 15:59:30 ack dlongley 15:59:35 ... Joe didn't respond, so I merged, but now it seems insufficient. 15:59:52 dlongley: there was a simple suggestion that was not pulled in. 16:00:06 burn: Dave and Mike please address in the issue. 16:00:11 Adjourned. 16:00:17 present+ 16:00:43 rrsagent, make logs public 16:00:47 rrsagent, make draft minutes 16:00:47 I'm logging. I don't understand 'make draft minutes', manu. Try /msg RRSAgent help 16:00:51 rrsagent, draft minutes 16:00:51 I have made the request to generate https://www.w3.org/2020/06/02-did-minutes.html manu 16:03:27 dmitriz has left #did 16:04:55 gannan has left #did 16:05:20 zakim, end meeting 16:05:20 As of this point the attendees have been ivan, burn, phila, jonathan_holt, Justin_R, markus_sabadello, manu, Orie, +, brent, selfissued, chriswinc, oliver_terbu, drummond, 16:05:23 ... dlongley, dezell, Eugeniu_Jolocom, yancy, identitywoman, rhiaro, ganesh, dmitriz, gannan 16:05:23 RRSAgent, please draft minutes 16:05:23 I have made the request to generate https://www.w3.org/2020/06/02-did-minutes.html Zakim 16:05:25 I am happy to have been of service, ivan; please remember to excuse RRSAgent. Goodbye 16:05:29 rrsagent, bye 16:05:29 I see no action items