22:01:00 RRSAgent has joined #did 22:01:00 logging to https://www.w3.org/2021/08/31-did-irc 22:01:35 rrsagent, make logs public 22:01:42 rrsagent, draft minutes 22:01:42 I have made the request to generate https://www.w3.org/2021/08/31-did-minutes.html brent 22:01:54 drummond has joined #did 22:01:57 Meeting: Decentralized Identifier Working Group 22:02:01 present+ 22:02:04 Chair: Brent Zundel 22:02:36 brent has changed the topic to: DID WG Agenda 2021-08-24: https://lists.w3.org/Archives/Public/public-did-wg/2021Aug/0021.html 22:02:52 present+ 22:02:56 brent has changed the topic to: DID WG Agenda 2021-08-31: https://lists.w3.org/Archives/Public/public-did-wg/2021Aug/0021.html 22:02:59 JoeAndrieu has joined #did 22:03:10 present+ 22:03:19 present+ 22:03:23 Agenda: https://lists.w3.org/Archives/Public/public-did-wg/2021Aug/0021.html 22:03:31 present+ 22:03:46 scribe+ 22:04:56 Topic: Agenda Review, Introductions 22:05:43 brent: agenda is press release, DID Core, notices for TPAC, plan for the next meeting, next charter, DID rubric, and DID Spec Registries 22:06:03 Topic: Press Release 22:06:36 brent: Work is underway. Coralee is working on draft text but not quite ready yet. Should be available for our next meeting. 22:06:44 Topic: Upcoming SRI Report on DID Core 22:07:13 ...our next meeting will include the report from SRI. They were waiting until they had approval to release openly. 22:07:27 ...there was an email with the documents. 22:07:37 ...ACTION: Brent will send the report again. 22:08:01 ...they will not have time to go over all the material before the call, so please read beforehand, so the bulk of the call can be Q&A. 22:08:05 Topic: Short videos for TPAC 22:08:19 https://www.w3.org/wiki/TPAC2021/Demos_and_Group_updates#Best_Practices_for_Recording_Videos 22:08:40 ...W3C has asked us if we want to prepare a short video for TPAC 22:09:00 ...it should demonstrating use of the spec, examples, etc. 22:09:09 ...if anyone is interested, reach out to the chairs for more info. 22:09:14 Topic: Notice about vote for Recommendation on 7th 22:09:50 ...we are operating under process 2020 that has a change in procedure. Previously WGs voted on PR and that was it. 22:10:17 kdenhartog has joined #did 22:10:24 ...the process has changed so that now, once the PR goes through the call for review, the WG still votes on moving to a final recommendation. 22:10:40 ...so this is just a heads up that this will be done at the next meeting. 22:10:57 ...the soonest the public announcement is planned is Sept 23. 22:13:17 q+ to talk about PROVISIONAL 22:13:39 ack JoeAndrieu 22:13:39 JoeAndrieu, you wanted to talk about PROVISIONAL 22:14:14 agropper has joined #did 22:14:19 present+ 22:14:22 q+ 22:14:34 ack drummond 22:16:17 Topic: Next DID WG Charter 22:16:30 https://github.com/w3c/did-wg-charter/issues 22:16:46 brent: the reason this is a longer topic is due to issues that have been raised that we should discuss 22:17:06 https://github.com/w3c/did-wg-charter/issues/11 22:17:17 ...the goal is to go through them briefly, then I encourage WG members to respond in the issues 22:17:43 ...the first issue is "one foundational key representation please" from Microsoft. 22:18:04 ...this has received extensive discussion in the WG already 22:18:43 https://github.com/w3c/did-wg-charter/issues/12 22:18:46 drummond: folks are still encouraged to reply in the issue, especially with citations to our earlier discussions of those topics. 22:19:19 brent: Microsoft is recommending non-normative guidance on cross-compatibility between JSON and JSON-LD 22:19:43 ...this sort of non-normative guidance would, in Brent's opinion, be in scope under the new charter 22:19:55 ...but would also retrod well-trodden ground 22:20:04 https://github.com/w3c/did-wg-charter/issues/13 22:20:40 ...Microsoft would also like the WG to take the challenge to define a universal, mandatory-to-implement DID method 22:20:58 ...this would take the WG out of maintenance mode 22:22:13 q+ 22:22:17 JoeAndrieu: There was a proposal to include did:web and did:key in the charter, but that was not done in order to keep it a maintenance WG 22:22:18 ack kdenhartog 22:22:24 ...so this could be a chance to do that 22:22:40 q+ 22:23:01 q+ 22:23:15 ack brent 22:23:26 kyle: did:key could work, but worried that did:web would derail the conversation 22:23:34 ...and not sure what would be the third 22:24:07 brent: The question of what DID methods could reach concensus would be challenging 22:24:16 ack TallTed 22:24:22 ...did:peer might also be a candidate that could reach consensus 22:24:55 TallTed: Going through the exercise of determining which DID methods could become normative could be a work item for the W3C Credentials Community Group 22:25:13 ...but the DID Rubric might be a better tool for evaluating this 22:25:15 q+ 22:26:10 ack drummond 22:28:10 scribe+ 22:28:18 drummond: likes the idea of looking at the DID Rubric and taking an evolutionary path 22:28:22 Topic: DID Rubric 22:28:46 https://github.com/w3c/did-rubric/pull/49 22:29:18 JoeAndrieu: This is the PR that has the proposed registry rules for the DID Rubric registry 22:29:32 brent: is there a link to this presentation? 22:29:45 JoeAndrieu: I will share a link with the mailing list 22:30:05 ...and I will share my screen to convey the key points 22:31:06 ...the slide deck first covered what has been done 22:31:27 ...then an evaluation of the rubric was done on the Veres One method 22:31:39 ...this report was then shared with the community 22:32:02 ...next they are evaluating did:web and did:ion. Both of these will be published when they are ready. 22:32:24 ...SBA research also did some evaluations 22:32:39 ...the main points we learned is that the Rubric is still in its infancy 22:33:09 ...some questions were too academic 22:33:37 ...also, structure-variable questions are needed 22:34:04 ...also, enforcement was needed 22:34:23 ...design was also not included 22:34:40 ...implementations may also need to be evaluated separately 22:34:58 ...and adversaries need to be evaluated 22:35:05 These changes are glorious. I'm very happy about how you have been doing this, and the direction Rubric things are going! 22:35:17 ...all of these were gaps in the Rubric 22:35:27 ...we also need better tools for community engagement 22:35:44 ...we also need more discussion about these criteria 22:36:10 ...the Rubric also proposes that each evaluator essentially create their own custom rubric with the criteria they need 22:36:37 ...shared evaluations also would help 22:37:06 ...the Rubric also needs permalinks and persistent identifiers so that references to the Rubric criteria will not break 22:38:06 ...the proposal is to turn the Rubric into a registry where criteria can be added, updated, and curated 22:38:14 ...updates can be done with a simple PR 22:38:50 ...the desire is that the current DID Rubric authors recommend a starting set of rules 22:39:23 ...so the net net is that it becomes a mechanism for continuing to improve the criteria for evaluating DID methods 22:39:56 ...there are a number of questions about how to proceed 22:40:30 brent: RE deadlines, as a WG, we have 4 more WG meetings that we can use to have this conversation 22:40:48 ...there is a possibility the WG could be extended to address any objections 22:41:15 ...so the last opportunity is by the end of Sept for the existing WG to approve the Note to be taken on by the new WG 22:41:41 ...please review the proposed rules 22:42:09 JoeAndrieu: The proposal follows the template of the DID Spec Registries doc 22:42:22 ...criteria must be identified and versioned 22:42:41 ...subcomponents do not need to be versioned and permalinks 22:43:26 ...use cases, methods, and evaluations all need to be cited 22:44:32 q? 22:44:43 ...the proposal defines what is needed in a criteria. Each proposed criteria needs at least 3 examples. 22:44:56 ...then, for all of those fields, what is required for each field 22:45:21 ...it also defines identifiers and how they need to work 22:45:42 ...there is a way to provide a TR permalink 22:46:24 ...prior criteria will still be retained in future versions in a "Retired" section so that the permalink will still work 22:46:53 ...the versioning rules are also defined 22:47:46 q+ to ask about evaluations vs. criteria 22:48:31 ...there is also an escalation path for disputes. However the key difference here, the editors retain the ability to curate the content 22:49:16 ...that gives the editors more responsibility to maintain the list of curated criteria PLUS a few example evaluations 22:49:59 ...that was done in the original Rubric, but that gave excessive visibility to six specific DID methods that they should not have 22:50:10 brent: we have 10 mins left to discuss 22:50:11 ack drummond 22:50:11 drummond, you wanted to ask about evaluations vs. criteria 22:50:58 q+ 22:51:33 drummond: Looking for some clarification here, I originally understood from the last call that this is about the registering of evaluations, but it seems this is about registering criteria. Is this about one or both? 22:52:04 ack TallTed 22:52:14 drummond: examples would be cited for showing how to evaluate a criteria, but not for registering the evaluations directly 22:52:49 TallTed: I am really happy about how the Rubric is evolving. I very much like this path, and I hope it continues evolving forever. 22:52:53 q+ 22:53:06 ack kdenhartog 22:53:27 JoeAndrieu: I'm very glad to see that. The work of evolving the Rubric has taught us a great deal, and it will continue. 22:53:57 kdenhartog: I also want to second its usefullness. We learned a lot when evaluating did:key. 22:54:19 ...it was possible that my misunderstanding led the WG members astray on the last WG call 22:54:30 q? 22:54:34 ...but now that this is clarified, I think this is a great tool 22:55:25 drummond: what are next steps? 22:55:36 drummond: what are we considering as the next steps to take for this to fit it within the working group time we have left? 22:55:42 brent: Next steps are to review the PR ASAP 22:56:16 ...the sooner we have feedback on that, the sooner we can have the Rubric in a state where the new WG can take it over as a registry 22:56:31 MacTed has joined #did 22:56:42 JoeAndrieu: I will send out an email to the list with the PR and ask for feedback. 22:56:53 ...it is seven pages and it has a lot of detail 22:57:17 ...Daniel Hardman already caught several improvements that were needed 22:57:29 q+ 22:57:32 brent: That looks great. Looking forward to the feedback. 22:57:35 ack kdenhartog 22:58:15 kdenhartog: Wanted to say thanks for accommodating this time zone for one meeting a month 22:58:40 +1 for kdenhartog. it works for me well too! 22:58:40 brent: Thanks to everyone, and especially Joe for the Rubric registry PR, and to scribes, and to wrapping it all up in Sept. 22:58:59 ...also, please jump into the DID WG Charter issue and "make your feelings known" 22:59:12 zakim, who is here? 22:59:12 Present: drummond, cel, brent, shigeya, TallTed, kdenhartog 22:59:14 On IRC I see MacTed, agropper, JoeAndrieu, drummond, RRSAgent, Zakim, brent, stevegt, dmitriz, Travis, hadleybeeman, dlehn4, ChristopherA, dlongley, manu, bigbluehat, wayne, 22:59:14 ... asocrt, etropea73101, damian77, shigeya, cel, rhiaro 22:59:20 present+ agropper 23:00:24 zakim, end the meeting 23:00:24 As of this point the attendees have been drummond, cel, brent, shigeya, TallTed, kdenhartog, agropper 23:00:26 RRSAgent, please draft minutes 23:00:26 I have made the request to generate https://www.w3.org/2021/08/31-did-minutes.html Zakim 23:00:29 I am happy to have been of service, brent; please remember to excuse RRSAgent. Goodbye 23:00:33 Zakim has left #did 23:00:42 rrsagent, please excuse us 23:00:42 I see no action items