14:55:06 RRSAgent has joined #did 14:55:10 logging to https://www.w3.org/2025/06/26-did-irc 14:55:17 rrsagent, draft minutes 14:55:18 I have made the request to generate https://www.w3.org/2025/06/26-did-minutes.html ottomorac 14:55:27 rrsagent, make logs public 14:55:32 Meeting: Decentralized Identifier Working Group 14:55:43 Chair: ottomorac 14:55:59 Agenda: https://lists.w3.org/Archives/Public/public-did-wg/2025Jun/0013.html 15:03:30 ottomorac has left #did 15:03:49 ottomorac has joined #did 15:05:02 manu has joined #did 15:05:13 present+ 15:05:14 present+ 15:09:25 smccown has joined #did 15:09:46 scribe 15:10:00 scribe+ 15:11:08 Otto: reviewing agenda 15:11:21 Topic: DID Methods Charter - Special Topic Call 15:11:37 TallTed has joined #did 15:11:44 q+ to note we should mention it on the mailing lists. 15:12:07 ottomorac: want to have a joint special topics call with DIF and other orgs to take place on July 9th 15:12:09 ack manu 15:12:09 manu, you wanted to note we should mention it on the mailing lists. 15:12:21 present+ 15:12:51 manu: should give broad notice this week in all the regular DID communities and orgs, so that everyone is aware 15:13:27 Topic: DID Core Issue Processing 15:13:30 https://github.com/w3c/did/issues 15:13:39 Subtopic: need TTL construct? #896 15:13:45 https://github.com/w3c/did/issues/896 15:14:43 q+ 15:14:52 ack manu 15:14:54 ottomorac: previous meeting discussed adding a validity period 15:16:33 q+ 15:16:34 manu: best way is to add a TTL, but may be beyond current charter. We could add a 'heads-up' that a TTL is coming to the DID spec in the next major iteration. This pre-note could describe how it will work, etc. We could re-charter and enumerate the TTL as a coming features 15:16:48 ack ivan 15:17:24 q+ to note we have /3/ potential parallel recharterings :) 15:18:19 ack manu 15:18:19 manu, you wanted to note we have /3/ potential parallel recharterings :) 15:18:24 Ivan: not looking forward to having 2 items that could have different development lengths under the same charter. Can we try to minimize the administrative difficulties? Can we leave CID where it is and not move it into documents? 15:18:28 present+ 15:22:41 manu: we might even have unto 4 recharters. realizes this is difficult. However, there are several specs / projects going to market and we need to coordinate on standardization, so the multiple efforts / communities are in-line and don't conflict. Concerned that "standards divergence" would be a strong negative. CID belongs in this group. 15:22:41 Discussion around CBOR-LD and where it should go. This impacts VC barcode spec. It's going out to 10K's of people and will affect interoperability. Multiple DID methods vs one DID Method discussion, etc. Need to coordinate all of these topics before large scale deployments happen. It would be good to re-charter in order to handle all of these 15:22:41 items under the same umbrella 15:24:28 Ivan: maybe this is a discussion for later with all the key participants. Once we enumerate all the problem issues, lets's minimize the administrative impacts. 15:24:32 +1 to not doing more work than necessary to fix the worst of these issues. 15:24:36 s/10K/10M/ 15:25:31 ottomorac: add a 'block by recharter' label on this PR for now. Then we can address it in the future 15:25:41 Subtopic: Unaddressed denial of service vector #897 15:25:50 https://github.com/w3c/did/issues/897 15:26:34 q+ 15:26:55 ack manu 15:29:38 manu: agreed. if there is a possibility of a cycle then it should be handled using traditional infinite loop detection methods. Some potential loop cases are errors and the resolution step should throw and error. This (& an example) should be added to the DID Resolution spec text under security issues. Should terminate when cycle detected and 15:29:38 return an invalid result. "any DID resolution that detects a cycle must return a cycle error" 15:30:11 Subtopic: Is percent encoding the fragment (#) really conformant with the URI RFC? #898 15:30:18 https://github.com/w3c/did/issues/898 15:30:50 q+ 15:31:08 ack manu 15:33:10 manu: example 6 is correct and don't think it goes against RFC. Changing to a hash mark would be wrong. The fragment must % encode the fragment. This is an esoteric example and will look at some improved descriptive text. 15:33:21 manu: this would be a class 2 change 15:34:04 Topic: DID Resolution PR Processing 15:34:22 Remove language about "graph merge" for equivalentId and canonicalId. #158 15:34:31 https://github.com/w3c/did-resolution/pull/158 15:37:28 rrsagent, make minutes 15:37:29 I have made the request to generate https://www.w3.org/2025/06/26-did-minutes.html ottomorac 15:38:38 m2gbot, link issues with transcript 15:38:39 comment created: https://github.com/w3c/did/issues/896#issuecomment-3008924320 15:38:40 comment created: https://github.com/w3c/did/issues/897#issuecomment-3008924370 15:38:41 comment created: https://github.com/w3c/did/issues/898#issuecomment-3008924396 15:39:56 zakim, end the meeting 15:39:56 As of this point the attendees have been manu, ottomorac, ivan, smccown 15:39:58 RRSAgent, please draft minutes 15:39:59 I have made the request to generate https://www.w3.org/2025/06/26-did-minutes.html Zakim 15:40:05 I am happy to have been of service, ottomorac; please remember to excuse RRSAgent. Goodbye 15:40:06 Zakim has left #did 15:40:26 RRSAgent, please excuse us 15:40:26 I see no action items