14:02:12 RRSAgent has joined #did 14:02:12 logging to https://www.w3.org/2021/08/17-did-irc 14:02:14 RRSAgent, make logs Public 14:02:15 please title this meeting ("meeting: ..."), ivan 14:03:14 Meeting: DID WG Telco 14:03:14 Chair: brent 14:03:14 Date: 2021-08-17 14:03:14 Agenda: https://lists.w3.org/Archives/Public/public-did-wg/2021Aug/0011.html 14:03:14 ivan has changed the topic to: Meeting Agenda 2021-08-17: https://lists.w3.org/Archives/Public/public-did-wg/2021Aug/0011.html 14:31:44 TallTed has joined #did 14:51:27 justin_r has joined #did 15:00:00 JoeAndrieu has joined #did 15:00:10 present+ 15:00:15 present+ 15:00:16 present+ 15:00:23 present+ 15:00:28 present+ orie 15:00:30 Orie has joined #did 15:00:36 present+ 15:00:37 drummond has joined #did 15:00:42 present+ justin_r 15:00:43 present+ 15:00:59 present+ TallTed 15:01:12 present+ 15:02:00 present+ manu, markus 15:02:01 I can't scribe today unfortunately -- must multitask 15:02:19 present+ 15:02:30 present+ 15:02:55 present+ 15:03:10 Geun-Hyung has joined #did 15:03:18 markus_sabadello has joined #did 15:03:21 present+ 15:03:26 present+ identitywoman 15:03:28 scribe+ 15:03:34 identitywoman has joined #did 15:03:36 present+ Geun-Hyung 15:03:37 present+ 15:03:45 brent: We begin with an agenda review. 15:04:23 brent: We'll talk about press release, next charter, DID Rubric, Implementation Guide, then covering issues+PRs for DID Spec Registries. 15:04:32 brent: Anything else folks want to talk about? 15:04:43 present+ agropper 15:04:47 manu: One announcement about historical PR, want to get some ideas on it. 15:04:50 brent: We'll get to that. 15:05:01 brent: Any introductions from the group? 15:05:11 present+ 15:05:23 agropper has joined #did 15:05:26 present+ by_caballero 15:05:32 present+ 15:05:48 q+ 15:05:55 brent: We are working with W3C public relations to work on press release, which will be about DID specification announcement, plus next steps. 15:06:29 brent: We will be reaching out directly to you and some companies regarding contributions, when we have a draft press release (probably end of this week) 15:06:30 ack manu 15:07:14 manu: I'm working on coordinating some testimonials from groups outside of W3C. We should speak holisticly on DIDs + VCs, rather than separately. Speak about concrete deployments rather than just how great it is. 15:07:26 +1 to manu about deployment 15:07:29 brent: I second all of that. 15:07:43 topic: Charter of the next DID WG. 15:07:54 -> charter https://w3c.github.io/did-wg-charter/ 15:07:54 brent: This has been sent to the W3C strategy group. 15:08:27 ivan: There have been a number of reviews that the charter has to go through. I think I got all of them signing off on the charter. 15:08:55 ivan: I've also sent a note to the strategy team on issuing an advanced notice to the AC, 3 or 4 hours ago. I presume they will look at it and it will go to AC today or tomorrow. 15:09:23 ivan: I don't expect the vote to officially start before mid-September, which means we will have to formally extend this WG after September. 15:09:58 ivan: So far, everything is going as it should. 15:10:23 ivan: There is one small addition for the charter that Brent and Joe and I are discussing, but otherwise the charter text seems stable. 15:10:28 brent: Any questions about the draft charter? 15:10:29 q+ 15:10:33 Nope, great job on it Ivan. 15:10:57 ack manu 15:12:29 manu: We are discussing relations with other groups. 15:13:08 Topic: historical PR 15:13:09 brent: Anything else on this topic? 15:13:34 brent: Manu has written a PR about the historical context of the DID spec 15:13:39 https://github.com/w3c/did-core/pull/790 15:13:47 scribejs, pr 790 15:14:06 q+ 15:14:21 brent: It's to acknowledge past work, people, and efforts. 15:14:49 ack manu 15:14:49 brent: Please review if you want to tweak this and add suggestions 15:15:12 manu: It's currently written as the editors writing this, I'd like to upgrade it to the WG writing it. 15:15:24 bumblefudge has joined #did 15:15:27 +1 for speaking "from the WG" 15:15:28 present+ 15:15:35 manu: I don't think there is anything controversial, we'd like to acknowledge the work before there was a DID WG. 15:15:44 +1 15:16:01 I went back and looked up past IIW Sessions that forshadow the group - they are there in 2015 - https://iiw.idcommons.net/index.php?title=Special%3ASearch&search=blockchain&go=Go 15:16:12 manu: We'd like to give people an understanding that this work started long ago. 15:16:35 q+ 15:16:35 +1 to that change. 15:16:41 manu: Would anyone object to change this from "the editors acknowledge" to "the WG acknowledges", or similar 15:16:50 +1 to "The Working Group acknowledges" 15:16:51 ack ivan 15:17:02 agree, Ivan -- the only reason we put "Editors" is to avoid process objections... 15:17:06 ivan: It's more appropriate if it says "the WG" rather than "the editors" 15:17:09 whatever those might be 15:17:10 +1 spread the love to as many of the shoulders on which we stand as we can recall 15:17:14 +1 15:17:21 +1 15:17:26 q+ 15:17:31 ack ivan 15:17:36 q+ to ask for a proposal? 15:18:07 ack manu 15:18:07 manu, you wanted to ask for a proposal? 15:18:10 ivan: This is only editorial, so I don't think anyone would object from a process point of view. 15:18:22 manu: Should we document a WG resolution, to make absolutely sure? 15:19:11 brent: Any changes to the proposal? 15:19:15 PROPOSAL: The WG will add editorial text to the acknowledgements section of the Proposed Recommendation that gives some historical context for the work and thanks those who were involved. 15:19:18 +1 15:19:18 +1 15:19:19 +1 15:19:19 +1 15:19:19 +1 15:19:20 +1 15:19:22 +1 15:19:26 +1 15:19:28 q+ 15:19:28 +1 15:19:34 +1 15:19:36 +1 15:19:37 +1 15:19:48 RESOLVED: The WG will add editorial text to the acknowledgements section of the Proposed Recommendation that gives some historical context for the work and thanks those who were involved. 15:19:53 ack ivan 15:20:08 ivan: Do we say somewhere in the document that all appendices are non-normative? 15:20:26 ivan: If not, then we should mark acknowledgements as being explicitly non-normative. 15:20:44 manu: It doesn't say that, I can add it. We have it for all other sections. 15:21:05 Yes, Appendix A says non-normative explicitly. 15:21:26 manu: I'm going to raise an issue. 15:21:43 brent: Anything else on this topic? 15:21:50 Topic: DID Rubric 15:22:03 brent: Status update from Joe? 15:22:10 https://w3c.github.io/did-rubric/ 15:22:14 JoeAndrieu: We have a draft that is ready for publication. 15:22:17 Whohoo!! 15:22:21 https://github.com/w3c/did-rubric/blob/main/FPWD/2021-08-26/index.html 15:22:30 JoeAndrieu: This is the static version 15:22:46 JoeAndrieu: Targeting Aug 26th, does that work? 15:23:16 ivan: I have to issue a Transition Request today, which I can do. That should work. 15:23:48 q+ 15:23:49 JoeAndrieu: I sent a note to the group that we will propose to transition this to a Registry. 15:24:25 brent: I think it would be appropriate today that we want to publish this static copy as a note, combing the "objection week" with the "review week", to move the process forward, if folks are not opposed to that. 15:24:39 brent: I'd love to put a proposal forward if process allows us to do that. 15:24:46 +1 to publish as a NOTE today 15:24:49 ack ivan 15:25:12 ivan: This group is usually very formal about it. If we vote today, does the vote mean that the WG instructs me to send the request for transition to the management today? 15:25:26 ivan: Or is it a vote that says the WG wants to publish. 15:25:28 You can view the FPWD Rubric here -- https://w3c.github.io/did-rubric/FPWD/2021-08-26/ 15:25:52 ivan: For Recommentations, usually the 1 week cooling period is better. Not sure if it's necessary for a Note. 15:26:01 brent: If anyone thinks this is necessary, let us know. 15:26:20 JoeAndrieu: If anyone has a concern, please speak up. This has been worked on for a while, hopefully concerns have been voiced. 15:26:34 ivan: The resolution should make it clear. 15:26:45 ivan: Has the final document cross-checked with pubrules? 15:26:45 JoeAndrieu: No 15:26:53 ivan: Then please do it as quickly as possible. 15:27:24 ivan: I usually speed up thing.. I ask the webmaster to do a preliminary check so it doesn't get done at the last minute 15:27:30 JoeAndrieu: I need some guidance on how to do that. 15:27:39 manu: I can help, Joe just ping me. 15:27:48 JoeAndrieu see https://github.com/w3c/did-imp-guide/issues/10 15:27:56 ivan: The same will be true for the other Nore. 15:28:09 s/Note/Note/ 15:28:12 s/Nore/Note/ 15:28:34 brent: Anything needs to be added to the proposal? Manu, Ivan? 15:28:42 ivan: It's fine 15:28:44 PROPOSAL: the WG will ask W3C to transition the DID Rubric (https://w3c.github.io/did-rubric/FPWD/2021-08-26/) to a WG Note, and set up echidna for automatically updating the Note. 15:28:47 +1 15:28:48 +1 15:28:50 +1 15:28:50 +1 15:28:50 +1 15:28:51 +1 15:28:53 +1 15:28:53 +1 15:28:56 +1 15:29:10 +1 15:29:32 JoeAndrieu: Thanks to Daniel Hardman, he put a lot of work into this. 15:29:35 +1 15:29:35 +1 15:29:41 RESOLVED: the WG will ask W3C to transition the DID Rubric (https://w3c.github.io/did-rubric/FPWD/2021-08-26/) to a WG Note, and set up echidna for automatically updating the Note. 15:29:47 Joe, you and Daniel both rock for completing this. 15:30:01 brent: Anything else on this topic? 15:30:07 Topic: Implementation Guide 15:30:14 q+ 15:30:17 See https://w3c.github.io/did-imp-guide/FPWD/2021-08-26/ 15:30:23 brent: Orie can you give us a status update? 15:30:43 ack Orie 15:30:44 Orie: There has been an Implementation Guide for some time. Recently, there have been some contributions. 15:30:59 Orie: We have run pubrules on a static version, there are still some pubrules errors. 15:31:15 Orie: I thought Respec was supposed to deal with those, I'm now working on fixing them. 15:31:32 Orie: It's ready for review, still being contributed to do on the editorial side, and pubrules side. 15:31:45 brent: Sounds like similar cleanup as the DID Rubric work, getting ready for publication. 15:31:50 brent: Any comments or questions? 15:32:06 Sounds great 15:32:36 brent: Any recommendations for changes to the proposal? 15:32:41 PROPOSAL: the WG will ask W3C to transition the DID Implementation Guide (https://w3c.github.io/did-imp-guide/FPWD/2021-08-26/) to a WG Note, and set up echidna for automatically updating the Note. 15:32:44 +1 15:32:46 +1 15:32:47 +1 15:32:47 +1 15:32:49 +1 15:32:49 +1 15:32:51 +1 15:32:52 +1 15:32:54 +1 15:32:57 +1 15:32:57 +1 15:32:58 +1 15:33:12 RESOLVED: the WG will ask W3C to transition the DID Implementation Guide (https://w3c.github.io/did-imp-guide/FPWD/2021-08-26/) to a WG Note, and set up echidna for automatically updating the Note. 15:33:13 q+ to discuss pubrules result for the rubric 15:33:38 thanks for all the folks to contributed to it 15:33:52 brent: I believe that there is more work that could be done in the Implementation Guide. 15:34:01 brent: This also helps to set up the next WG, so that they can maintain the Notes. 15:34:03 ack JoeAndrieu 15:34:03 JoeAndrieu, you wanted to discuss pubrules result for the rubric 15:34:23 JoeAndrieu: We ran pubrules, there were no errors, only warnings. 15:34:35 brent: Anything else on these topics? 15:34:40 Topic: DID Spec Registries 15:34:53 https://github.com/w3c/did-spec-registries/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-asc+-label%3Aneeds-contact-info+ 15:35:01 q+ 15:35:04 brent: We'll spend the remaining time going through issues 15:35:08 ack manu 15:35:27 q+ 15:35:36 manu: I think I requested that we close all the issues that say "needs contact information", because we have a solution to that. 15:35:36 ack JoeAndrieu 15:35:47 Can we close all "needs-contact-info" issues -- https://lists.w3.org/Archives/Public/public-did-wg/2021Aug/0013.html 15:36:02 q+ 15:36:09 JoeAndrieu: Yes let's close them all. They were created by Daniel and I to solicit input for the Rubric. I think it served its purpose. 15:36:11 ack Orie 15:36:31 Orie: There's language about an email address that is a recommendation, not a requirement. 15:36:43 Orie: I created a PR for label mechanisms. 15:37:12 Orie: If we will have a label "needs contact info", then it would be helpful to keep the issues open. 15:37:34 subtopic: did-spec-registries @pr 29 15:37:38 https://github.com/w3c/did-spec-registries/pull/329 15:38:25 Orie: I was absent from the call when we discussed labels, but my understanding is we want to support labels in registry entries. 15:38:28 s/29/329/ 15:39:16 brent: Any opinions on this? 15:39:26 brent: No opposition to this plan. 15:39:37 Orie: I will open a PR to apply these labels to all the DID methods. 15:39:38 great. Thanks, Orie 15:40:03 brent: Should we go through issues, or PRs, what is more valuable now? 15:40:04 Orie: Issues 15:40:32 subtopic @issue did-spec-registries#156 15:40:38 https://github.com/w3c/did-spec-registries/issues/156 15:41:05 brent: Anyone on the call can let us know what needs to be done to address this issue? 15:41:21 q+ 15:41:21 brent: I believe some work was done for this, but I may be mistaken. 15:41:28 ack manu 15:41:51 manu: I believe we did add unacceptable things as examples in the registration criteria. 15:42:09 manu: E.g. no racist language, etc. 15:42:24 q+ 15:42:31 manu: I'll cite the exact text that addresses it. 15:42:45 We added it in step 3 here -- https://w3c.github.io/did-spec-registries/#the-registration-process 15:42:48 ack JoeAndrieu 15:43:13 JoeAndrieu: I think this language is great. This was originally an issue I raised because we didn't have any process, so we were open to abuses. I think this addresses my concerns. 15:43:22 I agree with Joe. 15:43:32 ivan: I think we discussed this in staff, and we were fine with it. 15:43:34 +1 to close it 15:44:04 subtopic @issue did-spec-registries#267 15:44:11 https://github.com/w3c/did-spec-registries/issues/267 15:44:26 brent: I raised this issue, regarding future changes 15:44:31 s/subtopic/subtopic:/ 15:45:00 q+ 15:45:07 brent: If people think this is a good idea, I can create a PR to address this. It means a maintenance group can make changes to the registration process. 15:45:08 ack TallTed 15:45:29 TallTed: I think the general idea is good, but I'd prefer to have something about ratification by the larger group. 15:45:33 q+ 15:45:37 ack ivan 15:46:09 ivan: The maintenance group is a WG. Any change we propose to do must go through the same process as any other WG. 15:46:32 This is the new Registries process -- https://www.w3.org/Consortium/Process/Drafts/#registries 15:46:51 q+ to ask if the maintenance charter address this 15:47:02 ivan: If any process changes, in the future it will be more stringent in the sense that the registry maintenance policy must have some vote through AC. 15:47:09 ack JoeAndrieu 15:47:09 JoeAndrieu, you wanted to ask if the maintenance charter address this 15:47:43 JoeAndrieu: Does the maintenance WG charter address this, is the WG empowered to change the rules? 15:48:19 brent: I do not believe that the wording would enable the editors to unilaterally change the registration process. 15:48:22 IMHO the maintenance WG should be the ones to make any changes to the registration process. 15:48:43 JoeAndrieu: So I think this would be covered by the language in the charter. The WG can change the registration process. 15:48:45 ivan: correct 15:49:31 q 15:49:36 q+ to normative 15:49:45 q+ 15:49:47 brent: Part of my concern was that.. We've been treating the registration process as fundamentally normative. In order to normatively add something to the specification, we would have to explicitly add language to the specification. The WG voted against that. 15:49:50 ack JoeAndrieu 15:49:50 JoeAndrieu, you wanted to normative 15:50:10 ack ivan 15:50:11 JoeAndrieu: Since this is a Note, I'm not sure if the distinction normative/non-normative applies here; 15:50:39 ivan: Yes, but exactly this point that brent was taking is the reason why the new process establishes a new type of document (Registry Document). It's somewhere in between. 15:51:09 ivan: I think it is exactly what brent is looking for. The registry process is as stable as if it was a Recommendation, but the registry contents of course change. 15:51:34 brent: If we can make necessary changes, then I'm good and I will close this. Thanks for feedback. 15:52:01 subtopic @issue did-spec-registries#272 15:52:25 https://github.com/w3c/did-spec-registries/issues/272 15:52:35 brent: I think this is just to track work, Orie what can you tell us? 15:53:14 Orie: We had some resolutions a while ago on how we want to label older DID methods. My understanding of this issue is that we had a resolution to create a new table after the spec is published. 15:53:43 Orie: Subsequently I saw comments that tables are hard to use, and labels are preferable. Therefore the resolution is no longer to be implemented in its current wording. 15:53:57 brent: Should we have another resolution that labels are preferred? 15:54:05 ivan: Shouldn't matter so much 15:54:10 Editor's choice 15:54:42 thanks ivan 15:54:42 subtopic @issue did-spec-registries#271 15:54:50 https://github.com/w3c/did-spec-registries/issues/271 15:55:04 Orie: Similar scenario, this was about status and dates 15:55:15 Orie: We can do status with labels, not sure what to do about dates 15:55:28 q+ to wonder if dates are useful. 15:55:34 Orie: Either we need new proposals for handling dates, or decide that we will not implement the resolution 15:55:34 ack manu 15:55:34 manu, you wanted to wonder if dates are useful. 15:55:55 manu: We have a resolution for first registered date, and last reviewed date 15:56:08 brent: Seemed like a good idea at that time 15:56:16 manu: Not sure if this is very useful 15:56:19 q+ 15:56:26 ack drummond 15:56:44 q+ 15:56:47 drummond: I still think "first registered" is a good idea, but "last reviewed" doesn't seem to make sense 15:56:51 ack TallTed 15:56:59 This can be reconstructed from Git history? 15:57:02 q+ to propose using git for managing dates 15:57:14 TallTed: This is also overtaken by events. 15:57:33 ack Orie 15:57:33 Orie, you wanted to propose using git for managing dates 15:57:44 q+ to suggest a note about link permanence 15:57:44 TallTed: We registered DID methods before we had even finalized the requirements for DID methods. 15:57:58 Orie: We should just use Git, and resolve to not implement this resolution 15:58:02 ack JoeAndrieu 15:58:02 JoeAndrieu, you wanted to suggest a note about link permanence 15:58:35 JoeAndrieu: The link that people click on may not be the one that was reviewed (unless we use hashlinks) 15:59:03 brent: There was a lot of conversation on liveness, and how up-to-date DID methods are. 16:00:10 PROPOSAL: We are not going to add dates in a table to the DID Registry 16:00:15 +1 16:00:18 +1 16:00:20 +1 16:00:21 +1 16:00:21 +1 16:00:22 +1 16:00:22 +1 16:00:24 +1 16:00:25 +1 16:00:39 RESOLVED: https://github.com/w3c/did-spec-registries/issues/271 16:00:42 +1 16:00:51 RESOLVED: We are not going to add dates in a table to the DID Registry 16:01:24 Thanks Brent. Big high five to Joe and Daniel and also Orie. 16:01:25 rrsagent, draft minutes 16:01:25 I have made the request to generate https://www.w3.org/2021/08/17-did-minutes.html ivan 16:01:26 brent: Thanks everyone, we got through a lot of items. Cu next time. 16:01:52 JoeAndrieu has left #did 16:02:11 zakim, end meeting 16:02:11 As of this point the attendees have been ivan, brent, JoeAndrieu, shigeya, orie, justin_r, drummond, TallTed, manu, markus, dlongley, cel, markus_sabadello, identitywoman, 16:02:14 ... Geun-Hyung, agropper, by_caballero, bumblefudge 16:02:14 RRSAgent, please draft minutes 16:02:14 I have made the request to generate https://www.w3.org/2021/08/17-did-minutes.html Zakim 16:02:16 I am happy to have been of service, ivan; please remember to excuse RRSAgent. Goodbye 16:02:19 rrsagent, bye 16:02:19 I see no action items