14:51:53 RRSAgent has joined #did 14:51:58 logging to https://www.w3.org/2026/03/26-did-irc 14:51:59 rrsagent, make logs public 14:52:09 Meeting: Decentralized Identifier Working Group 14:52:28 Chair: ottomorac 14:52:37 Agenda: https://lists.w3.org/Archives/Public/public-did-wg/2026Mar/0018.html 14:52:37 clear agenda 14:52:37 agenda+ Agenda Review, Introductions (5 min) 14:52:37 agenda+ DIDWG Status Update \[1\] (5 min) 14:52:37 agenda+ DID URL Dereferencing \[2\] (10 min) 14:52:37 agenda+ DID Resolution Threat Modelling Update \[3\] (10 min) 14:52:40 agenda+ DID Path PR \[4\] (25 min) 14:52:49 previous meeting: https://www.w3.org/2026/03/19-did-minutes.html 14:52:53 next meeting: https://www.w3.org/2026/04/02-did-minutes.html 14:58:10 pchampin has joined #did 14:58:27 REMINDER WE HAVE A DIFFERENT ZOOM LINK 14:58:32 Wip has joined #did 14:58:57 it is 14:59:10 Joe Andrieu: How the auto... 14:59:11 Otto Mora: Hey, how are you, sir?... 14:59:13 JoeAndrieu has joined #did 14:59:14 Joe Andrieu: Good. How you doing?... 14:59:20 transcriber-bot, pause 14:59:20 Otto Mora: Okay, transcriber bot is working. Let me just pause it. There we go crazy... 14:59:21 ⏸️ Transcription PAUSED (Paused by ottomorac) 15:00:20 swcurran has joined #did 15:00:22 dmitriz has joined #did 15:00:29 present+ 15:00:34 REMINDER DIFFERENT ZOOM LINK: https://w3c.zoom.us/j/82107835958?pwd=skqaa9teeNJuNtIKqV1pJjafJRcyA4.1 15:00:45 present+ 15:00:55 transcriber-bot, resume 15:00:57 ▶️ Transcription ACTIVE (Resumed by ottomorac) 15:00:59 Otto Mora: I can just do transcriberbot comma resume... 15:01:04 I think its https://us06web.zoom.us/j/5637387869?pwd=R2lzUXpLUC91VitFajRKRVlpTlphUT09 15:01:08 Otto Mora: And then, like, anything we say after that point is basically… Transcribed. That's the wrong name. Oh, wait... 15:01:09 Joe Andrieu: Interesting... 15:01:12 Otto Mora: Oh, wait, what?... 15:01:23 Otto Mora: Okay, uh, oh my gosh! Yes, I gave the wrong link. Sorry, sorry, this is a… this was an old... 15:01:27 Pierre-Antoine Champin: That's strange, because I did click on the link you sent... 15:01:30 Otto Mora: Oh, I see, I see, because it's just... 15:01:33 Pierre-Antoine Champin: Oh... 15:01:35 Pierre-Antoine Champin: Okay, no... 15:01:38 Joe Andrieu: That's pretty awesome... 15:01:44 Ivan Herman: What's the problem? You want it to resume, it does resume... 15:01:47 transcriber-bot, pause 15:01:47 Pierre-Antoine Champin: No, no, no, no, the… the… the Zoom link that auto... 15:01:48 ⏸️ Transcription PAUSED (Paused by ottomorac) 15:03:02 REMINDER UPDATED ZOOM LINK: https://us06web.zoom.us/j/5637387869?pwd=R2lzUXpLUC91VitFajRKRVlpTlphUT09 15:03:23 transcriber-bot, chair pchampin 15:03:23 ✓ Added pchampin as meeting chair 15:03:35 transcriber-bot, scribe 15:03:35 scribe+ 15:03:41 TallTed has joined #did 15:04:09 REMINDER UPDATED ZOOM LINK: https://us06web.zoom.us/j/5637387869?pwd=R2lzUXpLUC91VitFajRKRVlpTlphUT09 15:05:27 REMINDER UPDATED ZOOM LINK: https://us06web.zoom.us/j/5637387869?pwd=R2lzUXpLUC91VitFajRKRVlpTlphUT09 15:06:00 transcriber-bot, resume 15:06:00 ▶️ Transcription ACTIVE (Resumed by pchampin) 15:06:15 markus_sabadello has joined #did 15:06:15 zakim, next item 15:06:16 present+ 15:06:16 agendum 1 -- Agenda Review, Introductions (5 min) -- taken up [from agendabot] 15:06:27 present``= 15:06:28 KevinDean has joined #did 15:06:31 Otto Mora: Yes, so today we… we're just, um… we have a few updates, uh... 15:06:35 present+ 15:06:35 present+ 15:06:38 present+ 15:06:43 s/``=// 15:06:50 Otto Mora: mainly, uh, regarding some issues that we reclassified, uh, because we're running out of time, so we want to make sure that we get, um, those issues, uh, either labeled as during CR or future... 15:06:50 present+ 15:06:52 bumblefudge has joined #did 15:07:00 REMINDER UPDATED ZOOM LINK: https://us06web.zoom.us/j/5637387869?pwd=R2lzUXpLUC91VitFajRKRVlpTlphUT09 15:07:07 Otto Mora: And then we also have an update on the data URL dereferencing. There's a PR that Joe created on this, so we're trying to get to the bottom of that as well... 15:07:14 Otto Mora: And then, uh, we have a, um... 15:07:23 just gotta get that updated zoom link into the calendar! 15:07:27 Otto Mora: an update on the DIT resolution threat modeling, and then just a continuation of the discussion on the DIT... 15:07:45 Otto Mora: PathPR, so that's essentially what we have. Did I miss anybody? Any other points that people want to raise, or any other issues?... 15:07:50 s/DIT resolution/DID resolution 15:08:08 Otto Mora: Okay, not hearing any, so… let's move to the next one... 15:08:17 Otto Mora: Uh, okay, so on this first, uh, issue, I think, um... 15:08:27 s|REMINDER UPDATED ZOOM LINK: https://us06web.zoom.us/j/5637387869?pwd=R2lzUXpLUC91VitFajRKRVlpTlphUT09||g 15:08:27 Otto Mora: Sorry, before we get into that, I think, Pierre, we wanted to mention that we really want to get into CR, so... 15:08:31 Otto Mora: Uh, we want to make some difficult decisions, I guess, at this point. Um... 15:08:39 Otto Mora: So that we can try to meet the deadline, uh, before the... 15:08:50 Otto Mora: the need for an extension is there, right, Pierre? Maybe you want to talk about that?... 15:09:00 q+ 15:09:05 Pierre-Antoine Champin: Yeah, we… we… so, we do have one month left, I think, on the… on the charter, so I will start, uh… Very soon, to request for an extension... 15:09:09 ack ivan 15:09:09 q+ 15:09:16 Pierre-Antoine Champin: Uh, and yeah, I guess the, the, the, the, the question will be, uh, how far we think we are, uh, how, how… How long do we need the extension?... 15:09:23 Pierre-Antoine Champin: And so, yeah, at some point, we will need to show progress, so we have did core in candidate recommendation... 15:09:27 Pierre-Antoine Champin: Uh, but did resolution still need to get there? So, yes, now is the time to... 15:09:36 Pierre-Antoine Champin: As Otto put it, make tough decisions, because that's what… that's also what standardization is about. Uh, so that we... 15:09:44 Pierre-Antoine Champin: So that we can be credible when we are requesting the extension, that we can actually get this through... 15:09:50 Otto Mora: Okay, perfect... 15:10:00 Otto Mora: Uh, yes, go ahead, Ivan... 15:10:08 agreed, depending on how long we think we need, we will have to work on a new charter in parallel 15:10:13 Ivan Herman: So, my… as far as I know, these days... 15:10:22 Ivan Herman: More than 6 months extension just like that, is pretty much difficult to get... 15:10:27 Ivan Herman: After that, they would ask us to... 15:10:39 Ivan Herman: on re-chartering, even if it is the same charter, but to have an A/C approval for continuing, even with the same charter, so... 15:10:43 Ivan Herman: 6 months is probably the maximum that we can count on... 15:10:44 q?# 15:10:50 ack Wip 15:10:54 Otto Mora: Mm-hmm... 15:10:57 s/A\/C/AC/ 15:11:01 Otto Mora: Interesting. There's, like, a slight delay on the... 15:11:15 q+ 15:11:23 ack swcurran 15:11:27 Otto Mora: On the transcriber bot, okay, well… yeah, okay, well, that's a… that's a fair point. So you think it, like, it would have to be, like, a shorter extension, Ivan, if any at all, like, it would have to be, like, 3 or 4 months at most?... 15:11:30 Ivan Herman: You can try with 6, though you might get 4... 15:11:34 Ivan Herman: But you might get... 15:11:38 Ivan Herman: The 6 months... 15:11:47 Otto Mora: Hmm. Okay. Yeah... 15:11:58 Otto Mora: Alright. Okay, well, something I really have to fix with this bot is... 15:12:02 Otto Mora: How long it takes to collect the... 15:12:10 Otto Mora: I guess it's just… it's just, like, delayed, I don't understand why, but… Alright, thank you... 15:12:17 Otto Mora: And, alright, so let's move to the next topic... 15:12:28 Otto Mora: Oh, yeah. Go ahead... 15:12:31 Will Abramson: I just had a minor thing, um… thanks... 15:12:33 transcriber-bot, pause 15:12:33 ⏸️ Transcription PAUSED (Paused by pchampin) 15:13:59 scribe+ 15:14:04 +1 to continue the experiment 15:14:28 swcurran: if Joe's PR is merged, all the other PRs will be broken, that is going to take time 15:14:51 zakim, next item 15:14:51 agendum 2 -- DIDWG Status Update \[1\] (5 min) -- taken up [from agendabot] 15:14:57 transcriber-bot, resume 15:14:57 ▶️ Transcription ACTIVE (Resumed by pchampin) 15:15:01 Otto Mora: It's a little... 15:15:01 Pierre-Antoine Champin: Yeah, yeah, because it's… it's… it's lagging quite badly... 15:15:04 Will Abramson: Behind... 15:15:09 Otto Mora: Okay, well, part of… part of drawing pains with this. Uh, yeah, we can keep using it or not, I mean… You guys, feel free to... 15:15:12 Ivan Herman: I think we should use it this time, because we need the full experiment... 15:15:12 Will Abramson: Yeah... 15:15:13 Pierre-Antoine Champin: Absolutely... 15:15:16 Ivan Herman: We should not give up right away, and then... 15:15:22 Ivan Herman: The minutes for this time will not be perfect, but there is a lot of potential in this stuff and this approach also, so I would not. Drop it now... 15:15:24 Otto Mora: Thanks for your patience. Alright... 15:15:31 Ivan Herman: Hey, we have been over there with development of software, which was really… Slow or buggy, or… oh no, of course. whatever I did was always perfect, but every 30 years... 15:15:34 Otto Mora: Alright, thank you, appreciate the patience... 15:15:37 Pierre-Antoine Champin: Okay, okay, I try my best to describe from memory what Stephen said and has been... 15:15:37 zakim, next agendum 15:15:37 agendum 2 was just opened, Wip 15:15:40 Otto Mora: Mm-hmm... 15:15:42 present+ 15:15:45 Pierre-Antoine Champin: during the pause, and uh… and Dmitri, and Dmitri said, I kind of missed the exchange between Will and Dimitri, I'm sorry... 15:15:49 Otto Mora: Okay, uh, alright, so next item... 15:15:50 Pierre-Antoine Champin: But yeah. Yep... 15:15:51 zakim, open agendum 3 15:15:51 agendum 3 -- DID URL Dereferencing \[2\] (10 min) -- taken up [from agendabot] 15:15:54 Otto Mora: And I guess, do you want to hit… try to hit transcriber while resume, see if we catch up? I guess it should at this point. Hopefully, let's see, let me just see... 15:15:59 Otto Mora: Oh my god. Okay, now it's like... 15:16:03 Otto Mora: Wow. It's… it's, like, buffered a bunch of stuff. Okay, maybe we do need to pop it... 15:16:03 https://github.com/w3c/did-resolution/issues?q=is%3Aissue%20state%3Aopen%20label%3Aduring-cr 15:16:05 Otto Mora: Um, alright... 15:16:08 Joe Andrieu: Still need some work, Otto, but it's still impressive... 15:16:12 Otto Mora: Yeah. Apologies for this, I guess we hadn't, like, really stress-tested it. Um, to that level. Um… Okay... 15:16:13 Will Abramson: So, I think you weren't behind in the agenda, so I'm just gonna... 15:16:13 Otto Mora: Yeah... 15:16:16 Will Abramson: Need to do that thing... 15:16:22 Otto Mora: And it does… it… why did it buffer? It should have just ignored. Okay, so just be careful with whatever you want off the record... 15:16:25 Pierre-Antoine Champin: Hmm... 15:16:32 Otto Mora: We might have to completely pause it to be gone if you want things off the record. Okay, so we have, um, we have reclassified issues here. You can see this link... 15:16:42 Otto Mora: Um, we have, uh, labeled a bunch of them as either, uh, during CR or future. And, uh, that's just in the spirit of making some progress... 15:16:52 Otto Mora: I don't know, Will, is there anything we want to mention here about this?... 15:16:56 Will Abramson: I think the only thing I would say… sorry, I thought we'd already discussed this, but I guess you're right, we hadn't. The only thing I would say is, like... 15:17:02 Will Abramson: we might advise us to do this, and I think it is a good approach. Basically, anything that isn't adding normative changes to the text can be labeled during CR... 15:17:06 Will Abramson: So if there are issues that we have labeled during CR that you strongly disagree with... 15:17:13 Will Abramson: then do comment on those issues, but bear in mind that we need time to get those issues in. So, one of the things is, if it's not during CR and you think it's normative. Maybe it has to be future?... 15:17:16 Will Abramson: Um, so that's the only flag, you know, there are some new labels on the issue. If you strongly disagree, do voice your disagreement. Okay... 15:17:17 q? 15:17:21 Otto Mora: Mm-hmm. Okay... 15:17:29 Otto Mora: One is raising any issues with that one, so maybe let's move on to... 15:17:32 zakim, next item 15:17:32 agendum 2 -- DIDWG Status Update \[1\] (5 min) -- taken up [from agendabot] 15:17:33 Otto Mora: the Git URL dereferencing, which is the next one... 15:17:42 zakim, next item 15:17:42 agendum 2 was just opened, ottomorac 15:17:43 Otto Mora: Uh, the working group... 15:17:47 zakim, open agendum 3 15:17:47 agendum 3 -- DID URL Dereferencing \[2\] (10 min) -- taken up [from agendabot] 15:17:51 q+ 15:17:53 Will Abramson: Yeah, I think you need to do this, sorry... 15:17:56 https://github.com/w3c/did-resolution/issues/226 15:17:58 Otto Mora: Okay, thank you. Uh, yes, so this one... 15:18:02 https://github.com/w3c/did-resolution/pull/311 15:18:08 Otto Mora: is this particular one, and then I saw that… yeah, Joe, yeah, thank you, you opened a PR for this, which the link is here... 15:18:17 Otto Mora: And I guess maybe I'll let Joe just present it, and then I think we can go into some detailed discussion around it. Uh, perhaps... 15:18:22 Otto Mora: I do see responding. Go ahead, yeah... 15:18:28 Joe Andrieu: Thanks, Otto. Um, so, uh, as I actually say in the PR, I apologize for the size... 15:18:43 Joe Andrieu: Um, this is a little bit like pulling on a thread on a sweater, uh, that included, you know, Jeffrey's request to clarify resolution versus dereferencing. Um, the path work, which included how do we handle properties that conflict... 15:18:49 s/Git URL/DID URL 15:18:51 Joe Andrieu: Um, and in that work, it became clear it was really hard, even for both Steven and I, to figure out how do we adjust just the dereferencing part... 15:19:02 Joe Andrieu: But not the resolution part, because of how the algorithm was described. And as I started working on that, I failed to give Stephen a good revision. I could only get halfway through it... 15:19:09 Joe Andrieu: And so then, when I turned back to Jeffrey's question and looked at the document as a whole... 15:19:26 Joe Andrieu: I think the thing that most clearly came into, um, high contrast for me was that I think I've always thought about resolution and the dereferencer as a client-server relationship... 15:19:37 Joe Andrieu: And, um, in our process, we ended up treating the dereferencer as if it were a server. So we added HTTP endpoints to it, for example, where... 15:19:42 Joe Andrieu: there really… that isn't a standard thing for most URL dereferencers. Like, a dereferencer generally is a browser of some kind... 15:19:46 Joe Andrieu: Um, and browsers don't generally have an HTTP endpoint, they are HTTP consumers... 15:19:50 Joe Andrieu: Um, so, as I wrote up an algorithm that, uh... 15:19:56 Joe Andrieu: made sense to me, which I had gotten some confirmation on, echoing sort of what I had written up for the did resolution threat model... 15:20:04 Joe Andrieu: And that seemed to be right, like, at least the feedback I got was like, yeah, Joe, that you're describing the right process, and so. I rewrote that... 15:20:13 Joe Andrieu: Um, in a way that hopefully is clearer. Um, that was my primary goal, was to just deal with, you know, inconsistencies or clarity issues... 15:20:19 Joe Andrieu: Um, and one of the things I discovered in there is, um, we don't currently have a normative requirement... 15:20:30 Joe Andrieu: that a dereferencer must allow a user to configure the resolvers. I think we should have that, as a matter of fact. Um, it was just something that was left out. I think that's a fairly minor point. The bigger issue is... 15:20:35 Joe Andrieu: I think, do we treat the dereferencer as a server?... 15:20:35 q+ 15:20:48 Joe Andrieu: Um, or is this insight about dereferencing is basically done by clients? You know, how does the rest of the group feel about that? And we can talk about the consequences. It is a huge. change. I don't… I didn't… I couldn't find a... 15:20:57 Joe Andrieu: short way to deal with it. Um, like, I think Steven and I, as we try to work on his PR, you know, we're looking for simpler options, but... 15:21:03 q+ to ask about formatting 15:21:10 q? 15:21:12 Joe Andrieu: Um, I think this was the most coherent way I could respond, and if we want to cherry-pick aspects of this, we could. We could keep the description of the algorithm. Um, in my PR, but also keep the, um, idea of an HTTP dereferencer... 15:21:17 ack JoeAndrieu 15:21:21 Joe Andrieu: you know, with endpoints. So there are options here. I just wanted to get my, uh, thinking and ideas in a proposal and spec text. So that we could consider it as a group... 15:21:26 ack markus_sabadello 15:21:28 Otto Mora: Okay. So, first up is Marcus... 15:21:40 Markus Sabadello: Hey, Joe, thanks for the PR. I haven't had a… I haven't had the time to really look at it yet, but I'm curious why you think that in the... 15:21:45 JennieM has joined #did 15:21:47 Markus Sabadello: current specification, there's an assumption that the reference is a server. I'm very surprised to... 15:21:54 present+ 15:21:57 Markus Sabadello: to hear that, I think we've always had two functions resolve and dereference, and we've always said that those are... 15:22:05 Markus Sabadello: Abstract functions and the algorithm sections in the current specifications, I think, don't imply any kind of... 15:22:12 Markus Sabadello: client-server relationship. It's true that then there is a separate section with an HTTPS... 15:22:17 Markus Sabadello: binding for Resolve and for dereference, but that's completely... 15:22:25 Markus Sabadello: separate from the… from the definition of the resolve function and… and from… from the algorithm, so I don't think... 15:22:32 Markus Sabadello: Does anything in the current specification that implies or requires a dereferencing... 15:22:35 q? 15:22:38 Markus Sabadello: server, and I think there are also some diagrams which, uh, which make that clear that... 15:22:45 Markus Sabadello: Uh, that the referencing after the resolution step can… can and should happen on the client side... 15:22:50 ack Wip 15:22:50 Wip, you wanted to ask about formatting 15:22:54 Otto Mora: Okay. Uh, Will... 15:22:57 Will Abramson: Yeah, thanks. I just wanted to bring up a... 15:23:07 Will Abramson: of that thing, an issue, which is very hard to review this PRGO because of the formatting issues. Like, I don't know. If you know... 15:23:14 Will Abramson: I don't know what the best solution is here, but, um, I think Steven mentioned it, and then I was having a look too, and it... 15:23:24 Will Abramson: you know, there's just a lot of green, and I think it's not clear which bits of that are, because you've changed things versus just line formatting. Issues and edits... 15:23:26 q+ to say that if you expose an endpoint, you're acting as a server. 15:23:30 Will Abramson: I did suggest maybe we do a separate PR that just does a formatting pass... 15:23:31 s/PRGO/PR 15:23:35 Will Abramson: I don't know… I don't know how easy it would be for you to, like, revert the formatting on here, for example, all those... 15:23:39 ack JoeAndrieu 15:23:39 JoeAndrieu, you wanted to say that if you expose an endpoint, you're acting as a server. 15:23:42 Otto Mora: Mm-hmm. Yep, go ahead, John... 15:23:49 Joe Andrieu: Um, I'm not sure what formatting you're referring to, Will. Do you mean in GitHub, how it presents the diffs?... 15:23:52 Will Abramson: Yep... 15:23:59 Joe Andrieu: Like, I think the way to read this is to clone it and read it. Like, I think that the diffs is going to be a very difficult way to get through it... 15:24:01 Joe Andrieu: Um, it's pretty much a rewrite of the whole thing... 15:24:04 Joe Andrieu: I mean, there are sections that are untouched, but... 15:24:08 Will Abramson: Okay... 15:24:11 Joe Andrieu: Um, I wouldn't expect the GitHub UI to be particularly helpful... 15:24:20 Joe Andrieu: Although, I do see you made a bunch of suggestions that should help our terminology links. So... 15:24:27 Will Abramson: Yeah, well, I think that's amazing, you know, like, when I'm making suggest… yeah, I see what you mean. Most of this are just changes, but for example, like, at the top of the index.HTML file... 15:24:36 Will Abramson: There's a bunch of green on the, like, config, and that's definitely just some formatting changes that have been applied... 15:24:41 Will Abramson: that make it kind of confusing, like, I don't think I need to review the, like... 15:24:45 Will Abramson: Script tag contents of the index.HTML... 15:24:53 Will Abramson: But, like, GitHub is indicating that there are changes, so maybe I should be reviewing. for example... 15:24:54 Joe Andrieu: Okay... 15:24:57 Otto Mora: It's it. This stuff here, right? Like, the... 15:25:00 Will Abramson: Yeah, I can't see your screen... 15:25:09 Will Abramson: I take your point, it's a big major rewrite, and maybe you should just be reading it top to bottom... 15:25:15 q+ 15:25:17 Will Abramson: Uh... 15:25:26 ack Wip 15:25:27 Will Abramson: I guess I could keep going. I do have, like, a more substantial comment about the content. Um... 15:25:30 q+ 15:25:30 Will Abramson: Okay. Yeah, go ahead... 15:25:41 Joe Andrieu: I had a quick comment, just to respond to Marcus's question, if you don't mind. Uh, I was waiting to get on the queue to see where new voices might show up... 15:25:41 Joe Andrieu: Uh, the reason, uh, it feels like a server is because there are endpoints... 15:25:41 q+ 15:25:44 Joe Andrieu: Like, for the browser, browsers don't expose endpoints for dereferencing, they just do dereferencing... 15:25:51 Joe Andrieu: Um, so… that's… that's what felt like, why… why do we have this separate piece of software?... 15:25:56 Joe Andrieu: Um, and what we… we do have in the spec, something that's underspecified, something called a client... 15:26:31 q? 15:26:37 ack swcurran 15:27:15 transcriber-bot has joined #did 15:27:16 Transcription bot ready. Type "transcriber-bot, help" for commands. 15:27:24 I think of the resolvers as a kind of "proxy" or "bridge" in terms of standard Web architecture 15:27:38 transcriber-bot, resume 15:27:53 transcriber-bot, chair ottomorac 15:27:53 ✓ Added ottomorac as meeting chair 15:28:01 transcriber-bot, resume 15:28:01 ▶️ Transcription ACTIVE (Resumed by ottomorac) 15:28:15 q+ to say browsers fundamental exercise is to dereference URLs 15:28:22 scribe+ 15:28:33 q? 15:28:39 swcurran: the diff is unusable, this is goint to take a long time to review 15:28:58 ... the server language is correct; browsers only do the fragment thing, the rest is done on the server side 15:29:02 q- 15:29:12 https://www.w3.org/TR/did-resolution/#examples-0 15:29:24 q? 15:29:27 ack JoeAndrieu 15:29:27 JoeAndrieu, you wanted to say browsers fundamental exercise is to dereference URLs 15:29:31 ... it is a logical requirement, not an impl requirement 15:29:56 JoeAndrieu: you took my comment to be about that particular dereferencer 15:30:20 ... I discovered that Chrome can be used on the command line, like curl 15:30:25 q+ 15:30:28 smccown has joined #did 15:30:31 ... but it does not offer an API that any other app can use 15:30:50 q+ 15:31:01 ack swcurran 15:31:04 ... Jeffrey Yaskin's confusion comes from us defining a new pattern 15:31:24 swcurran: are you considering that the processing and display of the content as part of the dereferncing? 15:31:35 q+ 15:31:37 ... that's not how I see it 15:31:40 q+ 15:31:44 q- 15:31:56 ack markus_sabadello 15:31:57 q+ dmitriz 15:32:18 q+ it specifically says it MUST implement a particular interface 15:32:24 markus_sabadello: repeating myself: nothing in the spec constrains the resolver to be a server 15:32:26 q+ to say the spec specifically says it MUST implement a particular interface 15:32:41 ... it is a component used by other components, possibly via an HTTP binding 15:32:53 ... I posted examples in the github issue 15:33:29 ack TallTed 15:34:07 TallTed: I'm surprised to hear programmers talking about "dereferencing" in a way that is different from its meaning in programming 15:34:37 ... values are stored in memory, and referenced by their address in memory; dereferencing is getting the value from the address 15:34:49 ... that's how I see dereferencing on the web 15:35:24 ... sometimes to dereference a URL, you need to resolve it (e.g. make it absolute) 15:35:49 q? 15:36:33 ack dmitriz 15:36:39 ... hopefully, that's helpful to think about DID dereferencing and DID resolution 15:37:06 q+ 15:37:10 q? 15:37:19 dmitriz: +1 to swcurran and TallTed, processing and displaying is not dereferencing 15:37:19 ack JoeAndrieu 15:37:19 JoeAndrieu, you wanted to say the spec specifically says it MUST implement a particular interface 15:37:48 JoeAndrieu: I'm not sure what dmitriz says. dereferencing happens between a client and a server 15:38:12 ... in this interaction, the fragment *has* to be handled by the client 15:38:22 q+ 15:38:50 ... when I write a dereferencer, I don't want to expose an API 15:39:11 q+ 15:39:27 ... what we are proposing here is not the way the web works 15:39:51 ... we are defining classes of conformant software 15:39:51 ack swcurran 15:40:00 swcurran: I agree that fragments are handled by the client 15:40:31 ... I believe that a client passes a URL to a component, whether that component is local or remore, we don't say 15:40:43 q? 15:40:44 ... that component responds to the client with something, and the client goes from there 15:41:13 ack markus_sabadello 15:41:14 ... a piece of software could call a local component, that's a library, not a server 15:41:55 q+ 15:41:57 markus_sabadello: Joe, maybe you can point to the place in the spec that states that you must expose an API 15:42:05 s/API/endpoint 15:42:17 pchampin 15:42:26 ack pchampin 15:42:31 scribe+ 15:42:34 https://w3c.github.io/did-resolution/#dereferencing 15:42:34 All conforming DID URL dereferencers implement the function below, which has the following abstract form: 15:42:34 dereference(didUrl, dereferenceOptions) → 15:42:34 « dereferencingMetadata, contentStream, contentMetadata » 15:42:50 pchampin: yes plus one to what Stephen said... 15:43:15 q? 15:43:18 ack Wip 15:43:40 Wip: we spent a large part of this meeting discussing this 15:43:48 ... maybe we need a special topic call on this 15:43:54 +1 15:44:10 ... regarding the timeline, I agree with swcurran that this PR will cause a lot of delay on other PRs 15:44:12 q+ 15:44:18 ack swcurran 15:44:42 swcurran: we need to think about the concepts that Joe's PR introduces, then try to make it fit more into the existing spec 15:45:02 ... the current PR mixes formatting and content change 15:45:29 ... I'm not agreeing with some thing that Joe said, but I tend to agree that we may need to change the language, 15:45:46 ... from describing as an HTTP interface, to describing as a message exchange interface 15:46:04 I don't agree there are five things that come back. ANY resource could come back. 15:46:13 q? 15:46:15 q+ 15:46:32 ack Wip 15:46:40 https://github.com/w3c/did-resolution/issues/226 15:46:43 q+ to say give this a week. 15:47:05 Wip: this PR stems from the issue raised by Jeffrey, who's confuse with what's currently in the spec 15:47:15 ... we need some changes to address Jeffrey's point 15:47:25 ack JoeAndrieu 15:47:25 JoeAndrieu, you wanted to say give this a week. 15:47:47 JoeAndrieu: I think we should give this a week, let people comment on the PR and see where they are 15:48:02 q+ 15:48:05 ack Wip 15:48:11 ... while the rest of the WG looks at this, I'll focus on the threat modeling, which is the other bottleneck 15:48:24 Wip: we should put a special topic call in the calendar 15:48:40 ... on the 8? 15:49:00 +1 to saving that time slot 15:49:08 waait there's 7 other PRs and you have 4 meetings left? 15:49:32 i'd rather get through the other 7 in next two meetings and topic calls for jeffrey's Issue 15:49:34 Topic: DID Resolution Threat Modelling Update 15:49:57 JoeAndrieu: quick update: we were hosted by the TM CG this week 15:50:01 ... sorry for the short notice 15:50:16 ... this is the first time we did that in the CG, learning as we go, but I think it went very well 15:50:25 Jeffreys issue is the only blocker for moving into CR bumblefudge. 6 of those 7 PRs are ready to merge I believe 15:50:37 ... it was a joint combination of teaching what TM is, and showing how DID resolution works 15:50:48 ... we started a threat ellicitation process 15:51:04 ... some that came up were more VC threats or DID-core threats, but that's part of the process 15:51:42 ... I'm going to add some of these threats in our repo and get a first draft 15:52:03 q+ 15:52:14 ack Wip 15:52:43 Wip: what changes do we expect in the spec text when the Threat Model is out? 15:53:09 JoeAndrieu: we are probably going to publish the Threat Model as a standalone note, 15:53:19 ... then update the security consideration section to highlight the key threats, and point to that note 15:53:37 q+ To talk about the DID URL Path Handling PR after this topic 15:53:38 q+ 15:53:44 ack swcurran 15:53:44