14:31:30 RRSAgent has joined #did 14:31:30 logging to https://www.w3.org/2021/06/08-did-irc 14:31:33 RRSAgent, make logs Public 14:31:34 please title this meeting ("meeting: ..."), ivan 14:31:45 Meeting: DID WG Telco 14:31:45 Chair: brent 14:31:45 Date: 2021-06-08 14:31:45 Agenda: https://lists.w3.org/Archives/Public/public-did-wg/2021Jun/0001.html 14:31:45 ivan has changed the topic to: Meeting Agenda 2021-06-08: https://lists.w3.org/Archives/Public/public-did-wg/2021Jun/0001.html 14:31:46 Regrets+ burn 14:47:22 TallTed has joined #did 14:58:06 present+ 14:58:50 justin_R has joined #did 14:58:58 present+ 14:59:37 justin_R has joined #did 14:59:37 TallTed has joined #did 14:59:37 tzviya has joined #did 14:59:37 faceface has joined #did 14:59:37 dlehn has joined #did 14:59:37 dlongley has joined #did 14:59:37 wayne has joined #did 14:59:37 manu has joined #did 14:59:37 hadleybeeman has joined #did 14:59:37 bigbluehat has joined #did 14:59:37 Travis_ has joined #did 14:59:37 ChristopherA has joined #did 14:59:37 shigeya has joined #did 14:59:50 rhiaro has joined #did 15:01:15 present+ 15:01:20 present+ drummond 15:02:10 brent has joined #did 15:02:16 present+ 15:02:21 present+ 15:02:25 present+ 15:02:39 drummond has joined #did 15:02:44 present+ 15:03:22 present+ dmitriz 15:04:48 present+ manu 15:05:00 present+ TallTed 15:06:03 scribe+ rhiaro 15:06:16 scribe+ dmitriz 15:07:01 agropper has joined #did 15:07:22 present+ agropper 15:07:28 present+ 15:07:58 Topic: special topic call 15:08:02 brent: no special topic call this week 15:08:09 ... and meetings for june 22nd and july 6th are cancelled 15:08:25 ... because of no chairs and independance day respectively 15:08:37 Topic: CR snapshot 15:08:50 dmitriz has joined #did 15:08:54 manu: here is the snapshot 15:08:58 present+ 15:09:07 ... more than a week ago we put out a document for review, a CR2, second candidate rec snapshot 15:09:14 ... that has got some review, discussion on calls and on the list 15:09:28 ... we added a couple of at risk markers, specifically for sevice and relative-ref 15:09:30 ... and a few others to be usre 15:09:32 ... that got review 15:09:34 ... no objections 15:09:37 ... no modifications 15:09:44 ... so the latest snapshot for that is here: 15:09:58 Here's the latest 2nd Candidate Recommendation time stamped document: https://w3c.github.io/did-core/CR/2021-06-15/ 15:10:14 ... a frozen version of what was reviewed 15:10:27 ... publication 15th june 15:10:38 ... needs to be voted on, then ivan can start the w3c process for publication 15:11:00 ... the minimum number of days needed for a CR is 28 days 15:11:09 ... july 13th is when the second CR period will end 15:11:17 ... that's the soonest we'd be able to transition to PR 15:11:22 ... we have 18 implementations 15:11:27 ... that number is going up 15:11:34 ... two features we're looking for other implementations of 15:11:53 ... everything else that was at risk either we've already got two indpendant implemenations of, or continues to be at risk until we do 15:11:57 ... did I miss anything? 15:12:03 ivan: no 15:12:06 brent: no 15:12:13 PROPOSAL: Publish https://w3c.github.io/did-core/CR/2021-06-15/ as a Candidate Recommendation Snapshot 15:12:28 manu: do we have to include the date? 15:12:28 ivan: no 15:12:39 ... the 15th is what we want but will not necessarily be the one, it's fine 15:12:53 +1 15:12:54 ... length of time is per process 15:12:56 +1 15:12:58 +1 15:13:00 +1 15:13:01 +1 15:13:02 +1 15:13:03 +1 15:13:03 +1 15:13:07 +1 15:13:32 +1 15:13:32 cel has joined #did 15:13:47 RESOLVED: Publish https://w3c.github.io/did-core/CR/2021-06-15/ as a Candidate Recommendation Snapshot 15:13:50 brent: seeing no opposition 15:14:00 ... this represents a lot of hard work from a lot of people 15:14:13 ... i'd specifically like to call out shigeya's work on test report generation 15:14:15 yes, +1000 to shigeya -- super, super, helpful work done! 15:14:22 ... would have been far more difficult without that, thank you 15:14:26 Thank you for many improvements to the test suite and reporting! 15:14:33 present+ 15:14:44 Topic: Implementations 15:14:53 manu: mattr's implementation went in this morning so Ihaven't had chance to regenerate that yet 15:15:12 ... latest one I have is from a while ago 15:15:28 ... the biggest improvements to the suite is that we now have a summary of conformance by statement 15:15:33 ... and the number of implementations that support it 15:15:48 ... eg. service and relative ref we only had the example impementation. WE've updated it so those ar eno longer counted 15:15:56 ... anyone should be able to go through and look at how we're doing for every statement 15:16:22 ... a couple still not implemented. a number for resolution and dereferencing, hopefully that changed with mattr's submission 15:16:29 ... the biggest things we're looking for feedback on are the did parameters 15:16:37 ... and a number of resolution and dereferencing functions 15:16:41 ... we don't have examples of alsoknownas being used 15:16:47 ... we're looking for implementation feedback on that 15:17:12 ... the super awkward situation we're in with that is the AP community was expecting the DID spec to define it, and it refers to DID, but if we don't get enough eimplementations we weill remove it to the DID spec and the AP thing will point to a nonexistant entry 15:17:16 ... I believe that's problematic 15:17:23 ... it'd be better for implementers that want it to implement it 15:17:27 q+ 15:17:28 ... so we don't have to take that out 15:17:55 ack ivan 15:18:07 ivan: not ideal but we can also keep it in non normatively or something 15:18:11 ... so we don't create a 404 15:18:15 q+ 15:18:19 ack manu 15:18:42 manu: +1, I'm looking at our at risk marker on it, we say if there's not enough interest we will remove it from the spec 15:18:49 ... I don't now if that creates an issue or if we can later decide 15:18:58 ivan: we have a good reason, I think it's not an issue 15:19:26 Topic: https://github.com/w3c/did-core/issues/708 15:19:35 brent: there has been a long discussion in the issue 15:19:36 q+ 15:19:43 ... Mike indicated to me he'd be on the meeting today 15:19:51 ... but perhaps someone can speak on his behalf? 15:20:00 ack justin_R 15:20:09 justin_R: your friendly local deputy here to speak. Mike couldn't make it 15:20:20 ... he told me that having looked over where things landed, secure key is happy with it being a note to implementers 15:20:27 ... markus made a good point that the details of this kind of thing belong in resolution 15:20:30 ... the details of resolution 15:20:42 ... and kyle's proposed text does seem to put things in the right framing 15:20:55 ... by the way you can expect something like this to happen but dont' count on it, is what i might personally add 15:20:58 ... but that's implied 15:21:12 ... mike said that as far as secure key is concerned the issue can be closed with or without that PR, though my recommendation is we take kyle's PR 15:21:15 brent: thanks 15:21:38 https://github.com/w3c/did-core/pull/764 15:22:02 brent: sounds like that PR will resolve that issue 15:22:16 Topic: DID Core issues and PRs 15:22:20 Topic: DID Core issues and PRs 15:22:35 https://github.com/w3c/did-core/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-asc+-label%3Adefer-v2 15:23:01 brent: first 718 15:23:07 subtopic: @issue 718 FAQ Question: Can the DID Subject of a DID Document be updated/changed after the DID Document has been registered? 15:23:15 q+ 15:23:22 ... I believe there is a PR for this 15:23:25 ack manu 15:23:33 manu: there's a PR, ready to go, but merge conflicts that we're waiting on drummond to fix 15:23:43 drummond: okay 15:23:51 https://github.com/w3c/did-core/issues/718 15:23:56 q+ 15:23:57 subtopic: @issue 728 All appendix sections needs to be cleaned up 15:23:59 brent: next 728 15:24:03 https://github.com/w3c/did-core/issues/728 15:24:27 manu: there are 4 remaining PRs, once those are merged all of the appendices will have had all the editorial changes 15:24:30 ... means we're done with editorial work 15:24:35 ... modulo small adjustments 15:24:38 brent: good news 15:24:52 ... next is 729 15:24:54 subtopic: @issue 729 When is the DID URI getting constructed 15:24:54 q+ 15:25:09 manu: still waiting on me, easy one I just havne't done it 15:25:23 https://github.com/w3c/did-core/issues/729 15:25:33 brent: next 625 15:25:44 subtopic: @issue 625 Diagrams need SVG and detailed description 15:25:44 ... the diagrams need descriptions 15:25:56 q+ 15:26:05 ack manu 15:26:13 ack shigeya 15:26:16 shigeya: markus asked me to help find a way to do the convert to svg 15:26:25 ... the tool he's using can be used to export to svg, should be no problem 15:26:31 ... once he has time to do that then done 15:26:36 brent: we'll have the svg 15:26:41 ... descriptions? 15:26:55 shigeya: I think he will work on that 15:26:59 brent: we'll leave that to markus 15:27:15 subtopic: @issue 719 FAQ Question: Can the DID Controller of a DID Document be updated/changed after the DID Document has been registered? 15:27:29 brent: assigned to drummond 15:27:31 q+ 15:27:43 drummond: I've accepted all the suggestions and that's ready to merge 15:27:48 ack manu 15:28:02 manu: it's been merged, waiting on michael to confirm we addressed the issue and we can close it with explicit confirmation 15:28:27 brent: that's all of the issues 15:28:31 ... six PRs 15:28:52 manu: we should discuss one 15:28:56 ... 741 15:29:13 subtopic: @pr 751 Update Verification Method Rotation section 15:29:27 manu: might need more people to look 15:29:30 ... not sure if that would help 15:29:42 ... biggest issue is that it as editorial update and when it was made people are now re discussing the entirety of the text 15:29:46 s/@pr 751/@pr 741/ 15:29:47 ... daniel hardman has concerns 15:29:49 ... orie neesd to respond 15:29:51 ... it's their text 15:30:03 ... but now there's disagreement over the text that they had initially put in there by daniel 15:30:12 ... the default is the PR won't go in and the thing will be editorially messy 15:30:29 ... I don't know if anyone can chat with daniel hardman and say we need him to propose concrete text and we need orie to talk with him to get there 15:30:33 ... I don't have any strong preference one way or the other 15:30:36 ... largely editorial stuff 15:30:39 ... misunderstanding around text 15:30:43 ... need orie and daniel to talk 15:30:51 q? 15:30:54 ... that's what will resolve it, floating for 23 days 15:30:57 ... neither of them are here 15:31:07 ... can anyone take an action to talk with daniel and/or orie to get them to resolve? 15:31:10 brent: i can reach out to daniel 15:31:59 brent: we have completed the agenda in record time 15:32:04 q+ CBOR? 15:32:18 Topic: CBOR? 15:32:22 ack CBOR 15:32:25 manu: sorry to bring this up 15:32:32 ... the chairs had a quesiton around if we're publsuhing the CBOR thing as a note 15:32:38 ... we don't have to talk about it today, but we could kick it off? 15:32:40 brent: we have time 15:32:43 ... it is an appropriate topic 15:33:04 ... We did not have enough support for the CBOR section in the spec to get tests written 15:33:07 ... Which was unfortunate 15:33:17 ... and that resulted in us needing to resolve to move to the CBOR text into its own note 15:33:27 ... Link to note? 15:33:29 https://w3c.github.io/did-cbor-note/ 15:33:58 ... with minor editorial framing, this is the text of the CBOR section as is 15:33:58 q+ 15:34:07 ... any mor ethat needs to happen here before it's ready to publish? 15:34:11 ack manu 15:34:18 manu: the question is would we make another pass or revisions to the doc or do we think we're done? 15:34:28 ... definitely done enough for a first version 15:34:31 q+ 15:34:32 ... the document stands on its own 15:34:37 ... there are two minor editorial fixes i need to make 15:34:39 ... that have to do with broken refs 15:34:48 ... ivan wanted a different title 15:34:52 ... minor things 15:35:03 ... there are some decisiosn to make on that document 15:35:13 ... a lot of people want this there so there's an example of a representation extension and put it in the registry 15:35:17 ... that's a good thing, not controversial 15:35:24 ... we need to understand if jonathan wants to remain an editor on the document 15:35:27 ... he's an author of a lot of the content 15:35:28 +1 to having an example of how to do a representation extension 15:35:30 ... we need to reach out and ask 15:35:35 q+ brent 15:35:40 ... if not I'm happy to do it 15:35:59 ... even though I don't believe in how this format was put together, but I do believe it is what jonathan wanted and is aligned with the ADM in the spec. it is implementable 15:36:17 ... Given we haven't seen any implementations for it today I'm wondering if we want toput in a warning that it's an exmaple without good implementationf eedback on it yet 15:36:28 ... the reason is because there is disagreement on this being an appropriate way to encode the cbor 15:36:35 ... that there are no implementations and nobody has said they will 15:36:43 ... it may serve better as an example instead of a 'real' representation 15:36:49 ... that's the only controversial thing to discuss 15:37:01 ... if all we're doing s a first published note on this we can decide that later 15:37:10 ... one thing we could do today is say modulo thos editorial changes, publish it as a note 15:37:13 ... and start that process 15:37:18 ... an dlater raise an issue about no implementations 15:37:24 ack ivan 15:37:37 ivan: first, as you said, we must have an agreement from jonathan to keep his name 15:37:53 ... the status section is very short in temrs of history of th edocument 15:38:13 ... as a reader who doesn't know the background I might be asking question why the text is having very normative feeling statements 15:38:16 ... capital MUST etc 15:38:23 ... there is even one single normative reference 15:38:57 q+ I can provide a summary of the kind that ivan mentioned in the SoTD. 15:38:57 ... I think it's okay if it still there but maybe it's worth adding a few sentences in the status saying that it uses this language because if it gets implemented a future version of the WG might make it normative 15:39:02 q+ to say I can provide a summary of the kind that ivan mentioned in the SoTD. 15:39:03 ... explains why it sounds like a recommendation 15:39:17 ... I think it's cleaner or better that we as a WG vote on moving this document as a note when it's ready 15:39:18 q+ to end the meeting on a light note, when appropriate 15:39:29 q- 15:39:30 ... even these small editorial changes I'd prefer to have them done an dthen vote rather than the other way around 15:39:33 ack manu 15:39:33 manu, you wanted to say I can provide a summary of the kind that ivan mentioned in the SoTD. 15:39:38 manu: I'm happy to add that text ivan 15:39:44 ... and +1 for not considering it until we're completely done with the edits 15:39:48 ack justin_R 15:39:48 justin_R, you wanted to end the meeting on a light note, when appropriate 15:40:08 brent: I will take the action to reach out to jonathan 15:40:16 ... it's appropriate to keep his name as an author 15:40:27 ... I'll check to see if he wishes to remain as a listed editor 15:40:39 ... anybody else have anything to discuss on this topic? 15:40:49 Topic: a lighter note 15:41:02 justin_R: I'm in the middle of putting together presentations for other stuff, so I was digging through old presentations for slides 15:41:13 ... this is from a talk I gave 5 years ago about standards groups 15:41:25 ... "in the end you don't really run out of time, of money.." 15:41:28 ... "what you run out of is patience" 15:41:38 I love it! 15:41:42 ... congratualations for finally running out of patience and hopefully finishing this spec 15:41:43 Patience out! 15:41:45 brent: ending early, thanks all! 15:42:15 rrsagent, draft minutes 15:42:15 I have made the request to generate https://www.w3.org/2021/06/08-did-minutes.html ivan 15:42:40 +1 15:50:46 markus_sabadello has joined #did 16:00:20 chriswinc has joined #did 17:59:26 Zakim has left #did 18:43:09 shigeya_ has joined #did 20:17:09 cel has joined #did 22:29:29 dmitriz has joined #did