14:23:48 RRSAgent has joined #did 14:23:48 logging to https://www.w3.org/2021/06/15-did-irc 14:23:50 RRSAgent, make logs Public 14:23:51 please title this meeting ("meeting: ..."), ivan 14:24:00 Meeting: DID WG Telco 14:24:00 Chair: brent 14:24:00 Date: 2021-06-15 14:24:00 Agenda: https://lists.w3.org/Archives/Public/public-did-wg/2021Jun/0003.html 14:24:00 ivan has changed the topic to: Meeting Agenda 2021-06-15: https://lists.w3.org/Archives/Public/public-did-wg/2021Jun/0003.html 14:24:01 Regrets+ burn 14:50:21 TallTed has joined #did 14:55:43 burn has joined #did 14:58:03 regrets- burn 14:58:07 present+ burn 14:58:11 justin_r has joined #did 14:58:11 present+ 14:58:39 present+ 14:59:32 present+ 15:01:25 markus_sabadello has joined #did 15:01:37 present+ identitywoman 15:01:41 by_caballero has joined #did 15:01:42 present+ markus_sabadello 15:01:46 present+ 15:01:58 present+ 15:02:26 present+ 15:02:29 present+ drummond 15:02:30 identitywoman has joined #did 15:03:00 agropper has joined #did 15:03:03 present+ 15:03:03 present+ TallTed 15:03:05 drummond has joined #did 15:03:15 present+ 15:03:16 present+ agropper 15:04:23 brent has joined #did 15:04:27 present+ 15:04:32 dbuc has joined #did 15:04:43 present+ 15:04:45 Brent: starting with agenda review 15:04:48 present+ dmitriz 15:05:12 present+ brent 15:05:13 dbuc has joined #did 15:05:13 brent has joined #did 15:05:13 drummond has joined #did 15:05:13 agropper has joined #did 15:05:13 identitywoman has joined #did 15:05:13 by_caballero has joined #did 15:05:13 markus_sabadello has joined #did 15:05:13 justin_r has joined #did 15:05:13 burn has joined #did 15:05:13 TallTed has joined #did 15:05:13 tzviya has joined #did 15:05:13 dlehn has joined #did 15:05:13 dlongley has joined #did 15:05:13 cel has joined #did 15:05:13 faceface has joined #did 15:05:13 wayne has joined #did 15:05:13 manu has joined #did 15:05:13 ChristopherA has joined #did 15:05:13 Travis has joined #did 15:05:13 shigeya has joined #did 15:05:13 bigbluehat has joined #did 15:05:13 hadleybeeman has joined #did 15:05:38 And congrats on publication of CR2! 15:05:41 brent: agenda modifications? 15:06:14 brent: 2nd CR for DID core has been published - no more changes - confeti in other chat from Juan. 15:06:18 Did the service param get dropped? 15:06:34 brent: until further notice no special topic calls 15:06:58 brent: upcoming meetings - canceled next week. Neither chairs nor staff content is avalibe. 15:07:10 brent: July 6th canceled - near to American 4th of July. 15:07:36 Topic: Status of Implementations 15:07:38 topic: status of implementations 15:07:40 Brent: status of ipmlemetnation by Manu 15:07:46 Geun-Hyung has joined #did 15:07:49 manu: implementation report was just run 15:08:27 manu: we have marked almost everything - marked many of things at risk that are at risk - changes 15:08:54 manu: all of a sudden - reporting mechanism is broken - now counting exmaple implementations working with Chea on fixing that. 15:09:00 present+ 15:09:43 manu: if we see relative ref and service and HL might be removed because not implemented 15:10:28 manu: had a regression of some kind in test suite - two things not showing up - equivalent ID and connonical ID 15:11:15 manu: still remain a number of things in resolution and de-referencing and no one seems to be implementing so can't test everything in the syntax 15:11:41 manu: but other things insufficent implementations we will see things like the deactivated property doesn't have enough implementations. 15:12:14 Aren't those essentially error messages? 15:12:23 manu: a couple of other ones - an invalid DID - not enough implementations. 15:12:24 Don't we want to keep them? 15:12:27 q+ 15:13:03 ack markus_sabadello 15:13:42 Markus: talking about some of the missing things. 15:13:46 Manu: timeline? 15:14:08 Markus: if we have the next call then probably have them anything further then that will be problematic. 15:14:30 manu: couting on uinversal resolver to provide those implementations 15:15:13 Brent: anyone else providing resoultion and dereferencing features - will it be sufficient. Ceramic submitted own resolver implementation. 15:15:46 manu: are you using ceramic implementaiton 15:15:55 Markus: no 15:16:09 Manu: not sure how many other implementations exist outside of ceramic. 15:16:55 Topic: Publishing CBOR Note 15:17:05 brent: about publishing a note 15:17:28 chriswinc has joined #did 15:17:36 Manu: an e-mail went out to the mailing list on saturday - saying there was a date stamped CBOR representation. 15:17:50 ManU: publication date is 29th of June 15:19:07 Manu: intro - words on conformance, IANA consideration rules, short and suite. Good example for the length of what a representation spec could look like. We still need to register this as a note. 15:19:11 present+ 15:19:12 q+ 15:19:48 Drummond: Manu has done a huge amount of work to turn this into stand alone document 15:19:52 seconded 15:19:56 q+ 15:19:58 ack 15:20:01 ack drummond 15:20:05 ack ivan 15:20:20 did-cbor-representation 15:21:26 Ivan: administrative, must have - short name must be part of resolution, other thing just to make life easier 15:21:39 PROPOSAL: We will publish The Plain CBOR Representation v1.0 as a WG Note with the shortname did-cbor-representation, use echidna to publish updates automatically, and register the CBOR representation in the DID Spec Registries. 15:21:56 +1 15:21:56 +1 15:21:56 +1 15:21:59 +1 15:22:00 +1 15:22:08 +1 15:22:09 +1 15:22:10 +1 15:22:24 q+ 15:22:39 RESOLVED: We will publish The Plain CBOR Representation v1.0 as a WG Note with the shortname did-cbor-representation, use echidna to publish updates automatically, and register the CBOR representation in the DID Spec Registries. 15:22:43 ack ivan 15:23:15 Ivan: resolutions become resolved after a week. Is that the understanding. 15:23:22 Brent: yes this is my understanding. 15:23:31 Ivan: will submit official publication request a week from now. 15:24:26 Totally agree -- Jonathan did a huge amount of work on this. 15:24:58 brent: next topic trying to do similar thing for rubric - none of the editors are ont eh call at this point. 15:25:09 present+ chriswinc 15:25:11 q+ 15:25:14 present+ 15:25:15 Topic: Publishing Rubric Note 15:25:19 ack ivan 15:25:29 q+ 15:25:42 ivan: from my POV we can take the resolution if we feel the content is there. but why Manu has gone through trouble to get document publication ready 15:26:06 ivan: work to get document ready - uneasy to submit request to director - unease 15:26:07 ack manu 15:26:16 Brent and manu share unease 15:26:21 https://w3c.github.io/did-rubric/ 15:26:43 manu: have not had chance to review latest rubric - weary of publishing without them. 15:26:48 We should see if the editors can attend a call and give us an assessment. 15:26:49 I agree. The editors did not prepare this before today, and have not prepped the group for a vote today. 15:26:50 Manu: two errors can be seen. 15:27:03 Brent: continue working with the editors 15:27:23 Topic: Next Steps for DID WG 15:27:28 ... and for the record, I think it's a really good document in concept, and probably close to in execution, it would be a real shame to not publish it. 15:27:51 q+ to suggest a six month rest period... maintenance... possibility of other items after. 15:27:52 Brent: next steps for DID working group - 20 min timebox conversation to explore options for continuing DID spec dev work developed. When this group ends in Sept of this year . 15:28:00 Brent: Q is open 15:28:06 ack manu 15:28:06 manu, you wanted to suggest a six month rest period... maintenance... possibility of other items after. 15:28:29 Manu: I would like to not do did work until this is done - 6 months to a year. 15:28:45 q+ 15:29:39 Manu maybe extra work in VC credentials work - so we don't have capacity to run all the stuff in parallel. 15:29:58 Manu: Secure data store work in DIF. 15:30:17 Manu: natural for us to work on something like DID Key - potential standard we could all get bheind. 15:30:35 ack ivan 15:30:43 manu: could get behind DID:Web - methods that are non-controversal into perview. 15:31:51 q+ 15:32:10 Ivan: something that didn't exist when VC spec went to Rec - could be defined as "living standard" we must decide when we submit a proposed recomendation whether we want to empower the new working group to add substative new features to the spec without going down path of working draft. If we want that we have to declare when we move to prposed recomendation. Might be a good thing to have in this case. Doesn't mean we must jump to do t[CUT] 15:32:26 Ivan: we could say working group is dormant for a year. 15:33:15 Ivan: fait of rubric document - publish a note. We know that joe plans to do some other things - more complicated things which we don't have the time for in this working group - put something in charter further development on rubric is in-scope. 15:33:22 Ivan: have it part of a new charter 15:33:33 q+ 15:33:40 q- 15:33:45 q+ 15:33:47 ivan: question for manu - did key and web that you would plan to publish these as recomendations or as separate notes. 15:33:49 ack manu 15:34:01 manu: we would publish them as separate representations. 15:34:25 manu: as the DID working gorup we need some exampler DID methods as a review and did methods. 15:34:26 q+ 15:34:37 ack manu 15:34:38 q+ 15:34:40 manu: something many different companies can get behind. 15:34:43 q+ manu 15:34:46 ack brent 15:34:51 ack manu 15:35:02 brent: option of doing nothing 15:35:50 brent: maintainace of registry 15:36:03 brent: full new working group defining resolution and DID methods 15:36:10 q+ to note that "Living Standard" creates concerns of feature pressure... would like to stay that for a year. 15:36:22 Brent: I'm not sure would it work to add DID methods to a maintainace type charter. 15:36:26 ack ivan 15:36:55 Ivan: to answer your question - maintainacne working group is not a specific thing - the only thing hte group does is maintain the recomendation 15:37:18 ivan: how we do the timeline - these are the things we develop - for first year we don't do anything we let thigns rest. 15:37:38 Ivan: we crate one liner charter - last for a year - then after that make a more complex charter. 15:37:49 ivan: that is answer to question. 15:38:24 ivan: yet another work item is possible. process 2021 - more formal notion of registry. Take up registry document as we have and turn it into a technical registry. 15:38:58 ivan: way we extend registry might be considered 15:39:07 ack markus_sabadello 15:39:45 Markus: I want to mention did resolution specification in CCG right now it is out of date and needs more work - and gaps in DID Core - define service - don't define did parameters and how to implement those. 15:39:59 Markus: somethings that are in did resolution that would help in long run. 15:40:03 ack manu 15:40:03 manu, you wanted to note that "Living Standard" creates concerns of feature pressure... would like to stay that for a year. 15:40:22 +1 for resolution spec 15:40:37 Manu: +1 for did resolution needs to be moved forward sooner rather then later - did key vs did web methods and resolution. could move forward in parallel. 15:41:04 Manu: living standard option that is good - if we move right to living standard would put feature presure on did standard - I don't think that is good. 15:42:19 manu: would like like to take breather for a year. Did key and core forward - people are spread thin. 15:42:25 q? 15:43:02 q+ on doing nothing 15:43:23 ack ivan 15:43:23 ivan, you wanted to comment on doing nothing 15:44:05 ivan: better to have a group that exists that "does nothing" then nothing and start again. 15:44:24 ivan: work maintained at CCG - maintains IPR 15:44:54 Topic: DID Core issues and PRs 15:45:05 https://github.com/w3c/did-core/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-asc+-label%3Adefer-v2 15:45:41 https://github.com/w3c/did-core/pull/764 15:45:49 Manu: not need to do PRs first - was waiting for CR publication - need review 764 15:45:57 manu: everything else is ready to go in. 15:46:19 subtopic: Diagrams need SVG and detailed description @issue 625 15:46:28 Brent: issue 625 15:46:29 q+ 15:46:38 ack markus_sabadello 15:47:02 markus: recomendation didn't work 15:47:36 q+ 15:47:58 ack ivan 15:48:12 Brent: other aspect of this issue - anyone can jump in and contribute. 15:48:19 If it were me, I'd just recreate everything in Google Draw :) 15:48:28 ivan: might be able to import from open office into google doc 15:48:36 Charles: also open to helping 15:48:43 Fantastic 15:48:56 q+ 15:49:22 ack manu 15:49:35 manu: to make job easier - all of the other issues already have PRs waiting - or have gone in. 15:50:11 Brent: PRs need reviews. 15:50:20 q+ 15:50:32 subtopic: Add link to DID use cases document @issue 766 15:50:35 brent: 766 add link to DID use-cases document 15:50:51 Manu: Phil reminded me this morning - I have failed to put a link into it. will do it. 15:51:19 Brent: look at PR 764 15:51:36 subtopic: docs: add notes to nudge implementors towards common DID URL patterns @pr 764 15:52:11 q+ 15:52:24 https://github.com/w3c/did-core/pull/764/files 15:52:35 q- 15:52:36 ack manu 15:52:51 Ted: review: simple changed a bunch of shoulds - non-normative texts 15:53:13 ack markus_sabadello 15:53:19 ted: he you DID implementor you should look at this thing to understand how resolution is going to happen so design DID to go along with it. 15:53:37 Markus: has non-normative pointer to did resolution 15:53:57 Markus: kyle wanted to add some of that to the language - 15:54:03 Markus: I think it is fine the way it is. 15:54:49 Brent: Thanks - see you all in two weeks - next week's meeting is canceled. 15:54:51 thanks to Kaliya! 15:54:58 thanks all! and kaliya extra 15:55:38 rrsagent, draft minutes 15:55:38 I have made the request to generate https://www.w3.org/2021/06/15-did-minutes.html ivan 15:56:46 zakim, end meeting 15:56:46 As of this point the attendees have been burn, ivan, justin_r, identitywoman, markus_sabadello, by_caballero, manu, cel, drummond, TallTed, agropper, brent, dbuc, dmitriz, 15:56:49 ... Geun-Hyung, chriswinc 15:56:49 RRSAgent, please draft minutes 15:56:49 I have made the request to generate https://www.w3.org/2021/06/15-did-minutes.html Zakim