15:00:53 RRSAgent has joined #did 15:00:57 logging to https://www.w3.org/2024/06/13-did-irc 15:00:57 RRSAgent, make logs Public 15:00:58 please title this meeting ("meeting: ..."), pchampin 15:01:02 shigeya has joined #did 15:01:21 meeting: Decentralized Identifiers WG 15:01:41 JennieM has joined #did 15:01:42 manu has joined #did 15:01:48 present+ 15:02:01 present+ 15:02:08 present+ 15:02:11 chair: burn 15:02:15 present+ 15:02:17 present+ 15:02:28 regrets+ dlongley 15:02:34 present+ 15:03:23 JoeAndrieu has joined #did 15:04:12 Wes-Smith has joined #did 15:04:26 markus_sabadello has joined #did 15:04:26 kevindean has joined #did 15:04:37 bigbluehat has joined #did 15:04:47 danpape has joined #did 15:04:47 Bruno has joined #did 15:04:47 kevindean has joined #did 15:04:47 markus_sabadello has joined #did 15:04:47 Wes-Smith has joined #did 15:04:47 JoeAndrieu has joined #did 15:04:47 JennieM has joined #did 15:04:47 burn has joined #did 15:04:47 rhiaro has joined #did 15:05:00 scribe+ 15:05:05 topic: introductions 15:05:08 present+ 15:05:34 burn: Dan Burnett, involved in digital identity and related standards since 25 years, co-created the DID WG 15:05:41 ... here as backup for Gabe 15:06:05 decentralgabe: with Block; editor of a few specs around VC; author of some DID methods 15:06:11 danpape has joined #did 15:06:11 Bruno has joined #did 15:06:11 markus_sabadello has joined #did 15:06:11 Wes-Smith has joined #did 15:06:11 JoeAndrieu has joined #did 15:06:11 JennieM has joined #did 15:06:11 burn has joined #did 15:06:11 rhiaro has joined #did 15:06:14 present+ 15:06:42 present+ 15:07:04 ... please everyone q+ on IRC for introducing yourself 15:07:22 q+ 15:07:25 kevindean has joined #did 15:07:26 ... we will then review the work that we have to do as a group. 15:07:29 mccown has joined #did 15:07:31 q+ 15:07:33 q+ 15:07:36 q- later 15:07:41 jameseaster has joined #did 15:07:41 ... questions about our work items. 15:07:59 q+ 15:08:03 ack kevindean 15:08:04 q+ 15:08:08 q? 15:08:09 present+ 15:08:10 q- later 15:08:11 q+ 15:08:11 q+ 15:08:24 q+ 15:08:25 q- later 15:08:30 ack markus_sabadello 15:08:31 q+ 15:08:35 kevindean: Kevin Dean, Legendary Requirements; co-editor of the VC use cases document 15:08:48 q+ 15:08:58 ack phila 15:08:58 markus_sabadello: Markus Sabadello, author and editor of the initial DID core resolution, and also DID resolution 15:09:37 phila: Phil Archer, GS1 Global Office. Think of GS1 as "the bar code people", standard body for the supply chain industry. 15:09:50 ... Interested in how and whether GS1 must implement DID. 15:09:56 ack JoeAndrieu 15:10:01 ... Spent 8 years on the W3C team, working on Linked Data 15:10:28 JoeAndrieu: Joe Andrieu, Legendary Requirements, co-author of the DID use cases document, creator and co-editor of the DID rubric. 15:10:32 ack bigbluehat 15:10:33 q+ 15:10:35 ... interested in the DID Resolution spec 15:10:40 wip has joined #did 15:10:50 present+ 15:10:57 ack ivan 15:10:59 bigbluehat: Benjamin Yound, Digital Bazaar. Involved in W3C for 10 years: Web Annotations, JSON-LD (chair of the WG), VC 15:11:09 present+ 15:11:12 q+ 15:11:21 q+ 15:11:29 ack Wes-Smith 15:11:35 ivan: Ivan Herman, W3C, former staff contact of the DID WG. Now staff contact of the VC WG, but still interested in this group. 15:11:42 ack manu 15:11:43 q+ 15:11:45 Wes-Smith: Wes Smith, Digital Bazaar, new to this space. 15:11:49 q+ 15:12:00 ack shigeya 15:12:00 manu: Manu Spory, co-editor of DID and VC specs. 15:12:02 q+ 15:12:09 q+ 15:12:30 ack Bruno 15:12:32 shigeya: Shigeya Suzuki, co-editor of the DID core spec. 15:12:49 ack mccown 15:12:52 Bruno: Brino Vavala, Interlabs. Here to monitor the work of the group. 15:13:20 mccown: Steve McCown, co-chair of the DID-Comm WG at DIF. On the DIF steering committee. 15:13:34 ack wip 15:13:39 ... Background in cybersecurity, approaching problems from that perspective. 15:13:55 ack dlehn 15:14:00 wip: Will Abramson, Legendary Requirements, co-chair of the CCG. 15:14:09 ack jameseaster 15:14:22 dlehn: David Lehn, Digital Bazaar, involved in JSON-LD, VC, DID for quite some time. 15:14:26 ack danpape 15:14:41 jameseaster: James Easter, Digital Bazaar, new to this space. 15:15:04 danpape: Dan Pape, Digital Contract Design. In this space for a few years. 15:15:05 ack pchampin 15:15:30 ack JennieM 15:15:38 pchampin: Pierre-Antoine Champin, W3C, team contact of this group. 15:15:38 pchampin: Hi Pierre-Antoine from W3C, staff contact, relatively new to the space, looking forward to learning. 15:16:08 JennieM: Jennie Meier, Digital Contract Design, alternate AC-rep for DCD, new to this space. 15:16:43 Tim Minard: Digital Bazaar. 15:16:49 s/Tim/Tyler/ 15:17:22 tminard has joined #did 15:17:28 q+ 15:17:30 burn: it's great to see so many people. Please turn on your video if you are willing to. It is nice to get to know people a little better during the initial call. 15:17:36 topic: W3C process 15:18:04 Topic: W3C Process https://www.w3.org/2023/Process-20231103 15:18:20 gabe: the W3C operates under a process of strong consensus. Different from other organizations. 15:19:04 ... If somebody disagrees, we may spend time trying to resolve the objection. It does not always work, but we take time for that. 15:19:47 ... Also, when we ask for scribes, please volunteer. For newcomers, this is a good way to become popular in the group. 15:20:07 ... We will talking more about spec process. 15:20:30 ... I look forward to see you all at the F2F meeting. We will do work in the meantime, but this is an important moment for the group. 15:20:41 ... A standard group is a place where competitors meet. 15:20:42 q+ to ask about f2f meetings 15:21:13 ... Remember that people who disagree with you are not idiots, they usually are talented and knowldgeable. 15:21:39 https://www.w3.org/2023/Process-20231103 15:21:53 https://www.w3.org/2023/Process-20231103/#correction-classes 15:21:57 decentralgabe: +1 to what Dan said about scribing; also a good way to pay close attention to the meeting. 15:22:15 https://www.w3.org/2023/Process-20231103/#rec-track 15:22:25 ... Above links to the W3C process, and to the section about correction classes and the recommendation tracks. 15:22:53 ... We are going to work together as a team; please rely on us chairs and the team contact to resolve conflicts. 15:23:22 TallTed has joined #did 15:24:46 pchampin: two parts to our work 15:25:02 Topic: Charter Review https://www.w3.org/2024/04/did-wg-charter.html 15:25:02 q- 15:25:24 q- 15:26:25 decentralgabe: the group is chartered for two years. We can consider extensions as need be. 15:26:34 RRSAgent, pointer? 15:26:34 See https://www.w3.org/2024/06/13-did-irc#T15-26-34 15:26:36 RRSAgent, draft minutes 15:26:37 I have made the request to generate https://www.w3.org/2024/06/13-did-minutes.html TallTed 15:26:50 ... We plan to meet on a weekly basis. This time is the most probably accepted time, according to the previous survey. 15:27:04 dan: we will talk about that at the end of the meeting. 15:27:11 s/dan:/burn: 15:27:46 decentralgabe: we will maintain the DID core WG; no new features, but class 3 changes may affect compliance 15:27:56 ... we will also maintain the DID registry 15:28:24 s/maintain the DID core WG/maintain the DID core spec/ 15:28:37 ... I talks with people and no one seems interested to take over this deliverable. We might need to deprioritize it. 15:28:45 Just to note that items such as the Plain CBOR representation are maintenance only, so it is not an issue if no one has a desire for changes. 15:28:56 https://w3c-ccg.github.io/did-resolution/ 15:29:08 ... Then we have the DID Resolution deliverable on REC track. 15:29:28 ... It has one input document (link above), but that does not mean that we can not depart from that document. 15:29:30 I really do hope we do adopt the CCG DID Resolution spec -- it's the best starting point :) 15:30:07 ... The charter lists a number of related groups that we may want to liaise with at some point. 15:30:30 ... External organizations are also listed. 15:30:41 q+ to talk about liaisons 15:30:54 q+ to explain external groups/coordination 15:31:17 ... To join meetings you need to be a W3C member, but minutes are publicly available. 15:31:24 ... The mailing list and github repo are also public. 15:31:48 q? 15:31:55 ack phila 15:31:55 phila, you wanted to talk about liaisons 15:32:30 phila: don't overlook the liaison section 15:32:42 ack burn 15:32:42 burn, you wanted to explain external groups/coordination 15:32:57 ... in the RCH WG, which I chaired with markus_sabadello, we had a hard time justifying that we had actually liaised with the groups listed in our charter. 15:33:18 burn: agree; in some cases, it is worth having a proper liaison. 15:33:47 q+ 15:33:53 ack ivan 15:33:56 ... In other cases, it is mostly about having people in both group discussing. 15:34:10 ivan: one more things that people should realize: 15:34:31 ... we have a number of "Horizontal Review" groups (i18n, accessibility, privacy, security, TAG) 15:34:53 ... it is extremely important to get their review before publishing a Candidate Recommendation, 15:35:08 ... it is never to early to contact them; they have requests from many different groups 15:35:12 q+ to add to what ivan said 15:35:18 +1 to Ivan's comments 15:35:21 ack burn 15:35:21 burn, you wanted to add to what ivan said 15:35:23 ... We should draw their attention as soon as we have a First Public Working Draft. 15:35:32 s/never to early/never too early/ 15:35:33 burn: thanks ivan. We will cover this as we go along. 15:36:00 ... If you are new to this process, it is easy to think "we are doing our work, the rest does not matter". 15:36:38 ... Many other groups I've been involved in start without a process, then add those constraints as they go, realizing they are necessary for a standard group. 15:36:51 ... This is what makes a standard good for the world. 15:37:03 Topic: Charter discussion 15:37:30 decentralgabe: we will create 2 distinct task forces. 15:37:42 ... we will need editors for each of our work items. 15:38:06 q+ 15:38:11 ... You may express interest right now, or later. 15:38:17 ack manu 15:38:36 q+ 15:38:39 manu: some comments on the DID-core spec and the DID spec registries. 15:38:47 ... I'm volunteering as an editor for both. 15:39:11 ... DID-core has editorial PRs since 2021, which we didn't address as we were working on the charter. 15:39:15 ... They should be addressed. 15:39:36 ... In the VC WG, we have a new Controller Document spec, which is a generalization of DID-core. 15:39:37 https://w3c.github.io/controller-document/ 15:40:09 ... We has a number of updates, normatively defined. 15:40:27 ... This group will have to decide whether to depend on this spec or not. 15:40:40 ... The two biggest things that I see for DID-core. 15:41:18 ... For the DID-spec registries, a couple of things happened. 15:41:38 ... A group of ~14 people are helping dealing with registration, but I'm behind on managing PRs. 15:41:45 ... A couple more volunteers would be useful. 15:42:17 q+ to suggest some thoughts. 15:42:25 q+ to suggest some thoughts on Registry. 15:43:07 decentralgabe: as we migrate the rubric and spec registries to W3C Registry, what does it mean process-wise? 15:43:42 ack markus_sabadello 15:43:49 pchampin: as they are notes, hence non-normative, I guess the transition will be very similar to starting from scratch 15:44:04 I'm happy to volunteer to help as a co-editor of either document 15:44:10 ivan: we need to check with PLH. This is a special case, hence not covered in the process. 15:44:27 markus_sabadello: interested in being an editor of the DID resolution work item. 15:44:28 ack manu 15:44:28 manu, you wanted to suggest some thoughts. and to suggest some thoughts on Registry. 15:44:29 ack manu 15:44:40 I'm also happy to volunteer to continue editor role with DID Method Rubric and, should we need it, the DID Use Cases document. 15:45:07 manu: regarding registries, my understanding is that the WG sets the rules that govern the registry. 15:45:31 ... by and large, the current criteria that we have works ok. 15:45:46 ... We need to discuss if everyone agrees. 15:45:59 q? 15:46:24 burn: thanks to Steve and Joe for volunteering to help with some documents. 15:46:43 ... We will leave this call for volunteers open for a little while, then we will reach out to people. 15:46:57 Co-editors welcome! 15:47:05 ... We appreciate the volunteering, often we don't get enough volunteers. 15:47:07 Topic: Administiriva 15:47:19 https://www.w3.org/events/tpac/2024/tpac-2024-hybrid-meeting/ 15:47:49 decentralgabe: TPAC is coming up in September. It would be excellent if you could join in person, but that's a hybrid meeting, so online is good too. 15:48:14 ... Our meetings are on Monday and Tuesday; no conflict with VC. 15:48:32 yes, interested in a joint session w/ FedID WG 15:48:36 ... There is a conflict with the Federated ID CG+WG. I contacted their chair about a possible joint meeting. 15:48:42 +1 to a joint session with the federated ID folks. A compare and contrast discussion would be interesting 15:49:04 ... It would be interesting to have presentations/demos of DID uses in the real world. 15:49:16 q+ to talk about TPAC 15:49:28 ack phila 15:49:28 phila, you wanted to talk about TPAC 15:49:57 tminard has joined #did 15:50:14 burn has joined #did 15:50:14 phila: if you can get there, it is good. 10 years ago, there was the 20th anniversary of the Web with TimBL and Vint Cerf. 15:50:27 ... This year will be the 30th anniversary. You will be glad to be there. 15:50:48 there's also DID & FedID overlap/conflict with WebID, which remains a 2014 Editor's Draft, trying to become at least a CG Report. needs proper adoption and shepherding, because LOTS of people treat it as if it were a full TR 15:50:53 decentralgabe: recurring meeting: this slot seems to work. 15:51:03 q+ 15:51:10 JoeAndrieu has joined #did 15:51:21 ... reach out to me if you have remarks, or know other interested people. 15:51:36 burn: the next meeting will not necessarily be next week. Watch your email. 15:51:45 mccown has joined #DID 15:51:46 ... If we need to schedule a different slot, this is goint to take time. 15:52:01 q? 15:52:14 ack pchampin 15:52:26 https://www.w3.org/groups/wg/did/calendar/ 15:52:47 JennieM has joined #did 15:53:49 decentralgabe: please review the charter and list of deliverables; 15:53:56 woo! Thanks everyone! Excited to get started! 15:53:57 ... open issues or comment on existing ones. 15:54:03 RRSAgent, make minutes 15:54:05 I have made the request to generate https://www.w3.org/2024/06/13-did-minutes.html pchampin 15:54:41 chair+ decentralgabe 15:54:43 RRSAgent, make minutes 15:54:44 I have made the request to generate https://www.w3.org/2024/06/13-did-minutes.html pchampin 15:55:01 regrets+ TallTed 15:55:05 RRSAgent, draft minutes 15:55:06 I have made the request to generate https://www.w3.org/2024/06/13-did-minutes.html TallTed 15:56:13 s/Administiriva/Administrivia 15:56:23 RRSAgent, draft minutes 15:56:24 I have made the request to generate https://www.w3.org/2024/06/13-did-minutes.html TallTed 16:21:24 faceface has joined #did 17:01:30 Zakim, bye 17:01:30 leaving. As of this point the attendees have been manu, burn, shigeya, pchampin, phila, decentralgabe, bigbluehat, ivan, JoeAndrieu, mccown, wip, dlehn 17:01:30 Zakim has left #did 17:01:37 RRSAgent, bye 17:01:37 I see no action items