14:05:52 RRSAgent has joined #did 14:05:52 logging to https://www.w3.org/2020/04/21-did-irc 14:05:54 RRSAgent, make logs Public 14:05:55 please title this meeting ("meeting: ..."), ivan 14:06:45 Meeting: DID Working Group Telco 14:06:45 Chair: brent 14:06:45 Date: 2020-04-21 14:06:45 Agenda: https://lists.w3.org/Archives/Public/public-did-wg/2020Apr/0012.html 14:06:45 ivan has changed the topic to: Meeting Agenda 2020-04-21: https://lists.w3.org/Archives/Public/public-did-wg/2020Apr/0012.html 14:56:53 nat_holloway has joined #did 14:57:49 present+ 14:58:34 brent has joined #did 14:58:43 present+ 14:58:46 burn has joined #did 14:59:54 present+ 15:00:20 Orie has joined #did 15:00:21 markus_sabadello has joined #did 15:00:47 present+ 15:01:23 dmitriz has joined #did 15:01:26 present+ 15:01:38 dbuc has joined #did 15:01:39 present+ 15:01:49 paulmadsen has joined #did 15:01:56 present+ 15:01:59 present+ 15:02:00 present+ 15:02:03 present+ 15:02:06 selfissued has joined #did 15:02:21 present+ 15:02:23 phila has joined #did 15:02:25 scribe+ 15:02:45 present+ manu 15:02:49 present+ dlongley 15:02:49 JoeAndrieu has joined #did 15:02:54 present+ rhiaro 15:03:01 justin_r has joined #did 15:03:09 present+ 15:03:17 present+ phila 15:03:36 present+ JoeAndrieu 15:03:37 present+ 15:03:48 brent: Reviewed proposed agenda 15:03:56 present+ 15:04:05 present+ 15:04:07 drummond has joined #did 15:04:09 present+ 15:04:20 timcappalli has joined #did 15:04:47 present+ adrian 15:04:55 present+ timcappalli 15:05:01 timcappalli: Introduced himself. On the Microsoft identity standards team. 15:05:06 present+ 15:05:07 Welcome Tim 15:05:18 brettmcdowell has joined #DID 15:05:21 brent: Next topic call at 6pm US Eastern 15:05:26 agropper has joined #did 15:05:28 ... E-mail sent last week 15:05:30 present+ 15:05:33 Same zoom link 15:05:35 present+ 15:05:42 did-topic is the channel for the topic call 15:05:42 identitywoman has joined #did 15:05:52 The IRC channel will be did-topic 15:06:16 brent: Next topic: Editorial trust 15:06:37 present+ 15:06:41 brent: There have been concerns about whether some editorial actions were taken in a trustworthy way 15:06:50 brent: The chairs have confidence in the editors 15:07:15 present+ 15:07:16 brent: We strive for transparence. Everything is done in public. 15:07:29 i/next topic/Topic: editorial trust/ 15:07:53 burn: I agree 15:07:53 s/transparence/transparency/ 15:08:07 q+ 15:08:12 brent: Next topic: DID Resolution 15:08:17 ack manu 15:08:47 manu: Proposal from Justin on DID Resolution 15:08:47 i/DID Resolution/Topic: DID Resolution/ 15:09:00 manu: PRs by Marcus and Justin refined by Manu 15:09:06 jonathan_holt has joined #did 15:09:10 manu: Special call last week on this topic 15:09:42 manu: The DID Resolution contract is in scope 15:10:08 manu: Goal to get clarity from the WG that this work is in scope 15:10:40 q+ to talk about deleting things 15:10:58 manu: We want to be able to write tests for the resolution contract 15:11:15 manu: Do the chairs want to consider them one-by-one or as a batch 15:11:33 ack justin_r 15:11:33 justin_r, you wanted to talk about deleting things 15:11:39 brent: Let's take them in bite size chunks 15:11:53 justin_r: I have an alternative proposal for testing ones 15:12:18 present+ jonathan_holt 15:12:32 manu: I have three proposals and then Justin has another proposal 15:12:38 So 7 proposals total? 15:12:42 this should be fun 15:12:46 yes, 7 total. 15:13:32 PROPOSAL: It is in scope for the DID WG to normatively define the parameters of a concrete set of processes that take a DID as input and provides a DID Document as output. 15:13:55 +1 15:13:56 +1 15:13:57 +1 15:13:57 +1 15:13:58 +1 15:13:58 What is a process? 15:13:58 +1 15:13:59 +1 15:13:59 +1 15:14:00 +1 15:14:02 +1 15:14:03 +1 15:14:04 +1 15:14:05 +1 15:14:05 +1 15:14:08 +1 15:14:09 +1 15:14:10 +1 15:14:15 @dbuc process is what we define, as I would interpret it, fwiw 15:14:35 present+ 15:14:45 present+ 15:15:13 RESOLVED: It is in scope for the DID WG to normatively define the parameters of a concrete set of processes that take a DID as input and provides a DID Document as output. 15:15:18 PROPOSAL: It is in scope to normatively define the parameters of a concrete set of processes that take a DID URL as input and provide a resource result as output. 15:15:25 for the notes, this is my proposed list: https://lists.w3.org/Archives/Public/public-did-wg/2020Apr/0017.html 15:15:33 +1 15:15:44 +1 15:15:45 +1 15:15:46 No objections heard 15:15:46 +1 15:15:47 +1 15:15:47 +1 15:15:47 +1 15:15:48 +1 15:15:48 +1 15:15:51 +1 15:15:51 +1 15:15:53 +1 15:15:54 +1 15:16:04 -1 15:16:37 q+ 15:16:57 JoeAndrieu: The term "resource result" could have many interpretations, some of which I wouldn't support 15:16:57 ack markus_sabadello 15:17:09 q+ to note it's defined in the spec now. 15:17:10 +1 to markus_sabadello 15:17:15 When this says 'parameters', does it refer to DID URL Parameters, or parameters in some other sense? 15:17:17 q+ 15:17:20 +1 to what Markus is saying 15:17:23 ack manu 15:17:23 manu, you wanted to note it's defined in the spec now. 15:17:27 markus_sabadello: Clarified 15:17:37 +1 to markus's clarification 15:17:41 manu: "Resource" is defined in the spec 15:17:43 q+ to clarify resource result 15:17:56 JoeAndrieu: It's "resource result" that is the issue 15:18:18 q? 15:18:22 ack JoeAndrieu 15:18:29 brent: Asks is there a concrete proposed modification to the proposal 15:18:30 ? 15:18:32 q? 15:18:42 ack justin_r 15:18:42 justin_r, you wanted to clarify resource result 15:18:51 justin_r: This is intended to include dereferencing 15:18:57 q+ 15:19:09 ack dbuc 15:19:10 joel has joined #did 15:19:16 justin_r: It's the thing what comes out the end 15:19:17 present+ 15:19:26 q+ 15:19:50 justin_r: It's explicitly parameters outside the DID URL itself 15:20:02 justin_r: There's a concept called input options 15:20:28 justin_r: It's within our scope to include these input options 15:20:40 q- 15:20:49 brent: I'm giving us 5 more minutes for all of this 15:21:05 q+ 15:21:11 JoeAndrieu: There isn't language including dereferencing that I would support 15:21:26 q+ 15:21:28 JoeAndrieu: But I understand that I'm an outlier on this one 15:21:57 ack drummond 15:22:01 JoeAndrieu: I might consider a formal objection but I'm trying to understand how to avoid the privacy problems we're headed towards 15:22:03 ack ivan 15:22:10 q+ to explain what we're doing now 15:22:20 ivan: We are not defining the contracts at this moment 15:22:32 q- 15:22:33 ivan: Simply, if we go in that direction, is it in scope? 15:23:00 q- 15:23:02 ivan: The only thing we're clearing up here is whether considering this is within scope of the charter 15:23:11 brent: Let's consider the next proposal 15:23:14 FAILED RESOLUTION: It is in scope for the DID WG to normatively define the parameters of a concrete set of processes that take a DID as input and provides a DID Document as output. 15:23:21 PROPOSAL: It is in scope to make these processes take in options and provide back a document along with different classes of metadata (e.g., document metadata and resolution metadata). 15:23:41 What does "take in options" mean? 15:23:49 q+ 15:23:55 ack markus_sabadello 15:23:58 "take in options" => additional parameters? 15:24:39 ok, so URL Params? 15:24:41 markus_sabadello: When dereferencing a URL, there can be additional inputs considered as part of the dereferencing process 15:24:48 no, not URL parameters 15:24:59 "additional" here means beyond just the URL, i believe. 15:25:09 markus_sabadello: For instance, header parameters can influence HTTP URL resolution 15:25:11 +1 15:25:11 +1 15:25:13 +1 15:25:14 +1 15:25:14 +1 15:25:14 +1 15:25:14 +1 15:25:17 +1 15:25:20 +1 15:25:21 +1 15:25:21 +1 15:25:22 +1 15:25:25 +1 15:25:26 +1 15:25:32 +1 15:25:38 +1 15:25:42 +1 15:25:48 q+ for process clarification 15:25:49 RESOLVED: It is in scope to make these processes take in options and provide back a document along with different classes of metadata (e.g., document metadata and resolution metadata). 15:26:04 brent: Seeing no -1s, this is resolved 15:26:18 ack justin_r 15:26:18 justin_r, you wanted to discuss process clarification 15:26:34 s/FAILED RESOLUTION: It is in scope for the DID WG to normatively define the parameters of a concrete set of processes that take a DID as input and provides a DID Document as output./FAILED RESOLUTION: It is in scope to normatively define the parameters of a concrete set of processes that take a DID URL as input and provide a resource result as output./ 15:26:45 justin_r: Pointed out a cut-and-paste error in the notes 15:27:14 justin_r: Back away from language about how things are tested - just that they are tested 15:28:19 selfissued: I asked that Justin paste his language into the chat 15:28:45 manu: I will paste it in 15:29:01 PROPOSAL: It is in scope to add tests to the test suite that exercise these processes to test the inputs (DIDs, DID URLs, and input metadata) as well as the outputs (DID Documents, resources, and output metadata). 15:29:14 +1 15:29:17 +1 15:29:18 +1 15:29:18 +1 15:29:18 +1 15:29:18 +1 15:29:19 +1 15:29:19 +1 15:29:20 +1 15:29:21 brent: I hear no objections 15:29:22 +1 15:29:22 +1 15:29:23 +1 15:29:50 Here's the current test suite -- https://w3c-ccg.github.io/did-test-suite/ 15:29:51 +1 15:29:54 Probably did:key, I would imagine, if we want to really mail it in 15:30:01 Here's the current implementation report -- https://w3c-ccg.github.io/did-test-suite/implementations/ 15:30:02 dmitriz: Which DID methods will we be testing? 15:30:05 RESOLVED: It is in scope to add tests to the test suite that exercise these processes to test the inputs (DIDs, DID URLs, and input metadata) as well as the outputs (DID Documents, resources, and output metadata). 15:30:09 brent: That's still to be determined 15:30:18 brent: Seeing no objections, this is resoloved 15:30:52 brent: We have three more of these, which we will consider even though we are over the time originally allocated 15:31:05 q+ to explain a bit about process 15:31:25 ack burn 15:31:25 burn, you wanted to explain a bit about process 15:31:50 burn: The plan is to get resolutions here and then confirm them on the mailing list - because this has to do with the charter 15:32:09 Q? 15:32:15 PROPOSAL: It is out of scope to normatively define DID Method specific details of implementing DID resolution. 15:32:34 q+ 15:32:41 q+ 15:32:48 ack selfissued 15:32:54 selfissued: I have no idea what this means or how to make it actionable. 15:32:54 Me either 15:32:54 scribe+ manu 15:33:01 selfissued: I do not know what is being ruled in or out of scope. 15:33:19 selfissued: This seems like... inputs and outputs are in scope... how are the details in scope or out of scope. 15:33:19 q+ 15:33:28 ack drummond 15:33:34 brent: I believe it's the details. 15:33:47 s/the details/the details of DID Method details/ 15:34:06 drummond: This wording doesn't necessarily say that. 15:34:13 drummond: I think I know what this means, but that's not what it says 15:34:24 ack burn 15:34:26 q+ 15:34:37 justin_r: The keyword is details 15:34:40 burn: The keyword here is details... the keyword is "DID Method specific details" 15:34:51 burn: What's not is scope would be DID Method-specific details 15:35:03 q+ 15:35:19 ack dbuc 15:35:22 +1 to brent's interpretation 15:35:34 s/The keyword here is details.../Justin said the keyword here was details, but actually/ 15:35:39 dbuc: We're not going to impose on DID Methods - that would create a minefield 15:35:41 q+ to ask about dlongley's proposal 15:35:43 ack selfissued 15:35:56 An alternative wording would be, "It is out of scope to normatively define how any specific DID method implements method-specific details of DID resolution." 15:36:04 selfissued: I would propose that we not consider this proposal because the wording is so ambiguous that it ends up being meaningless. Let's revisit it on another call. 15:36:17 +1 to that wording 15:36:19 q? 15:36:33 ack manu 15:36:33 manu, you wanted to ask about dlongley's proposal 15:36:54 manu: I suggest we consider Drummond's wording 15:37:01 PROPOSAL: It is out of scope to normatively define how any specific DID method implements method-specific details of DID resolution. 15:37:06 +1 15:37:10 +1 15:37:12 +1 15:37:12 +1 15:37:13 +1 15:37:13 +1 15:37:13 +1 15:37:14 +1 15:37:15 +1 15:37:16 +1 15:37:18 +1 15:37:21 +1 15:37:26 +1 15:37:26 +1 15:37:27 +1 15:37:31 +1 15:37:41 RESOLVED: It is out of scope to normatively define how any specific DID method implements method-specific details of DID resolution. 15:37:43 brent: I hear no objections 15:37:50 brent: This is resoluved 15:37:51 PROPOSAL: It is out of scope to normatively define DID Resolution protocols. 15:37:57 What does that mean? 15:38:01 brent: This is resolved 15:38:12 q+ 15:38:14 q+ 15:38:25 ack selfissued 15:38:39 q+ to talk about protocols 15:38:40 selfissued: Again, I do not know what's referred to as "DID Resolution Protocols". 15:38:44 ack markus_sabadello 15:39:06 What is an example of the thing exactly that we won't do? 15:39:10 Can we get an example for how each of these proposals would manifest in a real world implementation (as each proposal is discussed)? 15:39:18 markus_sabadello: We also refer to DID Method Bindings 15:39:24 q? 15:39:25 An HTTP Protocol woudl be one such example (as out of scope) 15:39:27 ack justin_r 15:39:27 justin_r, you wanted to talk about protocols 15:39:48 s/DID Method Bindings/DID resolver bindings/ 15:39:49 present+ brettmcdowell 15:40:00 justin_r: For example, we don't want to define how to do proxy resolution or make a network call to a remote resolover 15:40:19 justin_r: All these are protocol-level things that are up to particular DID method implementations 15:40:23 q+ 15:40:44 Possible alternative wording: "It is out of scope to normatively define bindings between the DID resolution contract and any specific DID resolution protocols." 15:41:15 justin_r: This is creating layers of abstraction 15:41:28 justin_r: We're not going to assume whether you can make a network call or not 15:41:31 ack selfissued 15:41:32 Aside from inputs into the resolution mechanism, all functions internal to it performing that resolution will not be defined by this group? 15:41:48 selfissued: Why don't we reword this to "It is out of scope to specify how DID Methods are implemented" 15:41:53 q+ 15:42:09 justin_r: Again, this isn't charter text, this is interpretation of charter text and specifically it is out of scope to define protocol. 15:42:14 ack markus_sabadello 15:43:09 markus_sabadello: Talked about the relationship between bindings and DIDcomm 15:43:40 q+ 15:43:45 It is out of scope to normatively define the details of invoking the DID resolution process and any protocols associated with that implementation. 15:43:51 ack selfissued 15:44:13 selfissued: WHy don't we make it simple - it is out of scope to define whether protocols are used for DID Method implementations or to define those protocols. 15:44:32 I agree with this wording 15:44:35 PROPOSAL: it is out of scope to define whether protocols are used for DID Method implementations or to define those protocols. 15:44:47 +1 15:44:50 brent: Asked for objections 15:44:51 +1 15:44:54 +1 15:44:55 +1 15:44:55 +1 15:44:55 +1 15:44:56 Are there proposals currently that would be dismissed as out-of-scope as the result of these new "out of scope" statements? 15:44:57 +1 15:44:59 +1 15:45:01 +1 15:45:11 +1 15:45:15 +1 15:45:21 +1 15:45:27 q+ to talk about the last one when we get there 15:45:34 RESOLVED: it is out of scope to define whether protocols are used for DID Method implementations or to define those protocols. 15:45:37 brent: Seeing no objections, this one is resolved 15:46:41 PROPOSAL: It is out of scope to test concrete DID Resolution protocols and data formats beyond the necessary process to demonstrate interoperability between the test suite and an implementation. 15:46:45 q+ 15:46:47 q+ 15:46:51 ack justin_r 15:46:51 justin_r, you wanted to talk about the last one when we get there 15:47:08 q- 15:47:15 ack manu 15:47:35 justin_r: I changed protocols to implementations 15:48:01 +1 15:48:02 +1 15:48:03 +1 15:48:03 +1 15:48:04 +1 15:48:04 +1 15:48:19 JoeAndrieu: I'm still trying to understand it 15:48:24 Looks very woolly to me but OK +1 15:48:29 +1 15:48:30 +1 15:48:34 +0 15:48:42 I agree that this seems wordy 15:48:51 +1 15:48:56 I also agree that it's fairly vacuous, as dlongley wrote 15:49:11 Word of the day: vacuous 15:49:12 q+ to ask a process questiion 15:49:13 RESOLVED: It is out of scope to test concrete DID Resolution protocols and data formats beyond the necessary process to demonstrate interoperability between the test suite and an implementation. 15:49:27 brent: Seeing no negatives, this is resolved 15:49:37 q+ to explain what happens now wrt. PRs. 15:49:38 brent: This took longer than budgeted but it was time well spent 15:49:39 ack ivan 15:49:39 ivan, you wanted to ask a process questiion 15:50:07 ivan: Who is nat_holloway? 15:50:21 ivan: He's not on the member list and yet he voted 15:50:45 Keyser Söze 15:50:55 ivan: At a minimum, I have to remove this vote 15:51:38 ivan: The AC rep of USAA has to add him to the working group 15:52:03 brent: Next topic: Regarding issue #204 15:52:19 brent: This work is closely related to the work that the VC group did 15:52:48 brent: We will use common terminology unless a specific terminology change is approved by the working group 15:52:54 +1 for property, property name, property value 15:52:56 -> https://github.com/w3c/did-core/issues/204 Issue 204 15:52:59 brent: This is the chairs' position 15:53:00 q? 15:53:13 ack manu 15:53:13 manu, you wanted to explain what happens now wrt. PRs. 15:53:28 nat_holloway has left #did 15:53:33 manu: I want us to outline what happens next 15:53:38 https://github.com/w3c/did-core/pulls 15:54:04 manu: I have attempted to take the PR that Justin did using Markus' text and split it into multiple different portions 15:54:13 github appears to be down for me. 500 error. anyone else? 15:54:33 q+ 15:54:42 justin_r's PR: https://github.com/w3c/did-core/pull/253 based on my earlier PR: https://github.com/w3c/did-core/pull/247 15:54:45 https://github.com/w3c/did-core/pull/262 15:54:49 manu: There is a normative section on DID resolution 15:54:58 https://github.com/w3c/did-core/pull/263 15:55:06 https://github.com/w3c/did-core/pull/264 15:55:15 https://github.com/w3c/did-core/pull/265 15:55:18 manu: 264 is blocked 15:55:40 q? 15:55:59 q+ 15:56:01 ack phila 15:56:04 brent: Asked Joe to look at 264 15:56:16 ack markus_sabadello 15:56:23 phila: I made comments on these. I look forward to responses. 15:56:32 q+ 15:56:44 ack justin_r 15:56:55 markus_sabadello: Should we be discussing this in Justin's PR or in the split ones? 15:57:00 q+ 15:57:06 justin_r: I am concerned that these are intertwined 15:57:29 justin_r: There are comments in 253 that are not reflected in the split ones 15:57:53 justin_r: 252 is incomplete 15:58:02 ack manu 15:58:04 my original PR https://github.com/w3c/did-core/pull/247 will be closed soon, any outstanding content from that one can potentially be re-introduced to the new PRs 15:58:04 +1 to working on the split PRs. Thanks to Justin for helping move his PR over. 15:58:14 justin_r: It's going to take effort to ensure that things remain consistent 15:58:36 manu: When I split the PR apart, I made sure that the internal references continue to work 15:58:48 manu: As long as we don't rename sections, things should keep working 15:59:09 manu: If something didn't make it over, let's bring it in 15:59:24 brent: My dream of considering issues has been dashed 15:59:37 phila: Thanks to selfissued for scribing today 15:59:40 Thank you for scribing Mike 15:59:42 brent: Thanks us for the good discussion and thanks Mike Jones for scribing 15:59:55 agropper has left #did 15:59:58 brent: We will continue some of this on the special topic call today 16:00:08 github is down. 16:00:47 JoeAndrieu has left #did 16:01:27 zakim, end meeting 16:01:27 As of this point the attendees have been nat_holloway, brent, burn, markus_sabadello, rhiaro, dbuc, manu, ivan, Orie, dmitriz, selfissued, dlongley, justin_r, phila, JoeAndrieu, 16:01:30 ... paulmadsen, drummond, adrian, timcappalli, brettmcdowell, agropper, chriswinc, yancy, jonathan_holt, identitywoman, joel 16:01:30 RRSAgent, please draft minutes 16:01:30 I have made the request to generate https://www.w3.org/2020/04/21-did-minutes.html Zakim 16:01:32 I am happy to have been of service, ivan; please remember to excuse RRSAgent. Goodbye 16:01:37 Zakim has left #did 16:01:51 rrsagent, bye 16:01:51 I see no action items