22:00:05 RRSAgent has joined #did 22:00:05 logging to https://www.w3.org/2021/05/25-did-irc 22:00:16 justin_r has joined #did 22:00:31 zakim, this is did 22:00:31 got it, brent 22:01:06 rrsagent, make logs public 22:01:12 chair: brent 22:01:32 Meeting: Decentralized Identifier Working Group 22:01:34 markus_sabadello has joined #did 22:01:48 present+ 22:01:49 Agenda: https://lists.w3.org/Archives/Public/public-did-wg/2021May/0016.html 22:01:51 present+ 22:02:00 present+ 22:02:11 present+ burn 22:02:35 present+ 22:02:47 agropper has joined #did 22:02:48 selfissued has joined #did 22:02:55 present+ 22:02:57 present+ 22:04:30 present+ 22:04:55 drummond has joined #did 22:05:05 present+ 22:05:09 scribe+ 22:05:52 brent: Agenda review 22:06:15 ...special topic call, implementation feedback, testing status, MIME types, DID Core issues and PRs 22:07:08 ...Special topic call: we may or may not have one depending on the outcome today. If we have one, it will be Thursday at noon ET. 22:07:18 Topic: Status of Implementation Feedback 22:07:23 q+ 22:07:36 ack manu 22:07:57 manu: shared screen of implementation report 22:08:26 ...Shigeya has done a great job of providing a report 22:08:58 ...various DID methods are passing the "valid id property" test today. 22:09:28 ...currently there are 150 tests all of which have to be checked manually 22:10:05 Yes, I'm working on summary part of the report. 22:10:10 ...we currently have enough implementations of versionid 22:10:38 ...but hl and service parameters have not been implemented yet 22:10:47 ...these could be cut from the spec 22:11:08 ...removing hashlink could be removed without a new CR 22:11:27 ...but service and relativeRef are not marked as at-risk 22:11:51 ....we do really well elsewhere until we get to the JSON tests 22:12:23 imho, if we drop these from the data model that will be one of the stupidest decisions this group could make :P 22:12:37 ...the data model has all the different data types and they will likely stay even if there are no implementations in JSON 22:13:08 selfissued: Having booleans and numbers should not be controversial. 22:13:21 manu: Agreed. We just need a resolution supporting them. 22:13:52 ...when we get into DID resolution and dereferencing, it gets thin. 22:14:12 ...most of the tests are fulfilled only by the Universal Resolver and Ceramic. 22:15:40 ...is the Universal Resolver going to implement those? 22:15:46 markus_sabadello: Yes, a new PR is coming 22:16:41 manu: there were 2 other features that were concerning: canonicalID and equivalentID 22:17:15 justin_r: Not sure about SecureKey using equivalentID and canonicalID, but they do use service 22:17:43 orie: Manu is showing a local version 22:18:10 manu: Hopefully if we get ION and SecureKey in, then we'll have coverage of those properties 22:18:24 justin_r: Do I have an action item for that? 22:19:39 Orie_ has joined #did 22:19:48 https://github.com/w3c/did-test-suite/blob/main/packages/did-core-test-server/suites/implementations/did-orb.json#L166 22:19:53 manu: looks like a bug in the test suite 22:19:57 https://github.com/w3c/did-test-suite/blob/main/packages/did-core-test-server/suites/implementations/did-orb.json#L146 22:20:10 ^ including examples of cannonical / equivalent and service. 22:20:34 Maybe missing from `default.js` ? 22:20:35 manu: The only concern should be with service and relativeRef. 22:20:38 q? 22:20:42 q+ 22:20:57 ...hopefully that's not a big problem because we just need implementators to submit their examples. 22:21:20 ...so we should go for another week. In the meantime, the pressure is on Markus to get the Universal Resolver in... 22:21:35 ...and for those working on the test suite to see why some results are not showing up 22:21:54 Orie_: We should also be sure the CR system is generating the right report 22:22:14 manu: We are not longer checking in the report 22:22:25 ack brent 22:22:32 ...and the CI system no longer works the way it did before 22:22:54 brent: What are our options going forward? We have asked implementators to submit. 22:22:58 q+ 22:23:20 ack manu 22:23:32 ...we understand there are implementations supporting the service property, but are there any alternatives such as affadavits? 22:24:23 manu: 3 options. 1) people implementation. 2) Affadavits of promising to use it, such as with JSON data model., and 3) remove from spec which forces us into another CR which will take 3-4 weeks minimum. 22:24:50 ...the best option right now is identifying implementators and having them speed up 22:25:15 q+ 22:25:16 https://github.com/w3c/did-test-suite/pulls 22:25:20 brent: we can take a few more mins to discuss if needed 22:25:22 ^ there are a lot of open PRs 22:25:22 ack shigeya 22:25:23 https://github.com/w3c/did-test-suite/issues/132 22:25:53 shigeya: I created a new issue about descriptive text for implementations. 22:26:14 q+ 22:26:18 ...we may need to ask implementators to update their descriptive text. 22:26:19 ack manu 22:26:41 manu: question for Shigeya: what is the description for? 22:27:48 shigeya: There are inconsistent uses of the summaries of the tests in the report. 22:28:07 ...that would better categorize the outputs of the reporting tool 22:28:25 q+ 22:28:26 manu: I think that's something that the test suite curators can add as metadata 22:28:35 ack markus_sabadello 22:29:04 q+ 22:29:11 markus_sabadello: For the Universal Resolver, we are including the file name but we could include the name inside the test submission 22:29:22 ack manu 22:29:42 q+ 22:29:53 manu: The Universal Resolver is submitting DID methods that you didn't author, but you are submitting requests for multiple other live DID methods. 22:30:13 ack markus_sabadello 22:30:15 markus_sabadello: It depends somewhat on the DID method type and how it is implemented. 22:30:45 ...most of the time it is a Docker container that is running code from the DID method authors 22:31:02 ...so in that case, the Universal Resolver is running different code 22:31:06 q+ 22:31:40 manu: I would say it meets the bar for an independent implementation. Does anyone object? 22:31:45 ack drummond 22:31:57 q+ 22:31:59 scribe+ 22:32:15 drummond: I agree with manu, those are separate implementations 22:32:19 ack markus_sabadello 22:32:52 q+ to note when we need to be careful about this. 22:33:03 markus_sabadello: Ironically this sometimes could mean that for certain DID methods the Universal Resolver could be resolving through different resolution paths. 22:33:14 ack manu 22:33:14 manu, you wanted to note when we need to be careful about this. 22:33:21 ...so those might not be considered two implementations. 22:33:53 manu: The only time we need to be careful about this is when we have a normative statement with only two implementations and one of them is the Universal Resolver. 22:34:27 ...for example where a test shows only the Universal resolver and Ceramic may be suspect 22:34:28 Topic: MIME Types 22:34:31 ...but we will check that 22:35:02 brent: We have an IANA Considerations section in DID Core 22:35:36 ...and we specify MIME types there that we have had issues getting registered with IANA due to containing two plus signs 22:35:59 ...option #1: remove all media types from spec and hope there is no impact 22:36:23 ...option #2: we only register did+json 22:36:35 q+ 22:36:39 q+ 22:36:42 ack manu 22:36:55 ...option 3: only register one MIME type and write IANA 22:37:16 manu: We haven't sent IANA a "we really need you to act" email 22:37:22 ack selfissued 22:37:23 ...I will avoid saying anything else 22:37:30 q+ to argue for something. 22:37:50 selfissued: Normally when you ask IANA to register and there's a problem, the experts say what to do 22:37:57 q+ to note what they asked us to do. 22:38:08 ack manu 22:38:08 manu, you wanted to argue for something. and to note what they asked us to do. 22:38:20 ...the double plus issue is understandable - with the JWT work we changed one plus to a dash 22:38:27 ...why aren't we doing that 22:39:03 manu: IANA asked us to write up a spec proposing support for two plus signs 22:39:08 ...we wrote up that spec a year ago 22:39:18 ...there was a robust mailing list discussion 22:39:28 ...but then it died down and there was no decision 22:39:39 ...even though the feedback was mostly positive 22:40:01 ...and ironically the feedback was that a spec was not really needed to register 22:40:07 ...so we have a couple options 22:40:21 ...first we could go back and just ask to register, pointing to the past experience 22:41:06 ...RE "why aren't we changing one plus to a dash", the JSON-LD MIME type already has a plus, so JSON processors would not recognize it if that was changed. 22:41:31 selfissued: The way to force the hand in the IETF process, we just ask for a preliminary registration 22:41:39 ...either they will register it or they won't 22:41:47 ...if they register it, we're done 22:41:53 ...if not, then we can appeal 22:42:07 ...and ask for full registration 22:42:51 manu: Ok, we will go forward with that approach, which means we don't change anything in the spec 22:43:35 selfissued: In the comments, explain what happened, citing the spec you wrote, and say, "W3C as a cooperative standards org requests your help in resolving this". 22:43:42 manu: Ok, we'll do that. 22:43:59 brent: Good. Thanks Mike for the input. 22:44:09 ...any other input about MIME types? 22:44:28 Topic: DID Core issues and PRs 22:44:41 ...based on those last two topics, we will NOT have a special topic call this week. 22:44:42 https://github.com/w3c/did-core/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-asc+-label%3Adefer-v2 22:45:12 ...my hope as we go through these, my hope is we can get volunteers 22:45:54 subtopic: @issue 728 22:46:04 manu: some of the PRs have turned into challenges even though they are all editorial 22:46:19 ....so it may take some back-and-forth on each of these 22:46:45 ...if you have concerns with the language, please make concrete recommendations on new language 22:46:52 subtopic: Diagrams need SVG and detailed description @issue 625 22:46:59 ...using the GitHub change tool would help the most 22:47:19 markus_sabadello: I should have done this much sooner. So far I haven't been able to. 22:47:38 I did the diagrams with an OpenOffice app, but I can't get them converted to SVG. 22:48:03 Please let me know exportable formats, then I may help. 22:48:35 brent: if folks can help, please offer 22:48:57 subtopic: verification method IDs MUST contain a fragment @issue 708 22:48:58 markus_sabadello: Thanks, Shigeya, I will share my source docs and ask for help 22:49:40 manu: George Aristy from SecureKey would like to have normative statements about the structure of DID URLs 22:50:01 ...but I don't know as the WG could agree on anything more than a valid URI 22:50:15 ...however it would be worth a call with George to understand 22:50:42 subtopic: @issue 719 22:51:19 PR that addresses this: https://github.com/w3c/did-core/pull/754 22:51:49 subtopic: Examples might be out of date @issue 734 22:51:54 q+ 22:52:00 drummond: I submitted PRs on that and the next issue; they just need review 22:52:18 PR for this issue: https://github.com/w3c/did-core/pull/748 22:52:20 Orie_: I removed the Ethereum address example 22:52:23 ack Orie_ 22:52:43 ...there is still a potential issue with having a public key multibase example first 22:53:01 ...so I hoped that providing several examples would solve the problem 22:53:16 brent: a link to the PR is in IRC so please review 22:53:26 subtopic: When is the DID URI getting constructed @issue 729 22:53:43 manu: this just requires me to write some text 22:54:15 ...if someone else wants to take a look at that, please do 22:54:25 subtopic: Proving Control sections are wrong @issue 583 22:54:55 manu: The PR is in and has been merged, and I am waiting for Amy to see if it addressed her concern 22:55:07 brent: There are currently 15 open PRs that are all editorial 22:55:26 ...I encourage WG members to go in and review and approve (or improve) 22:55:44 ...the editors rely on our review to know when they can go forward with a merge 22:55:57 ...thank you everyone for your hard work; it is a pleasure to work with you 22:56:03 ...NO SPECIAL TOPIC CALL this week 22:56:10 ...next meeting is June 1 22:56:30 zakim, who is here? 22:56:30 Present: justin_r, shigeya, brent, burn, markus_sabadello, agropper, selfissued, manu, drummond 22:56:33 On IRC I see Orie_, drummond, selfissued, agropper, markus_sabadello, RRSAgent, Zakim, TallTed, brent, tzviya, dlehn2, faceface, Travis_, dlongley, manu, bigbluehat, hadleybeeman, 22:56:33 ... cel, rhiaro, wayne, shigeya, ChristopherA 22:56:43 present+ 22:57:12 zakim, end the meeting 22:57:12 As of this point the attendees have been justin_r, shigeya, brent, burn, markus_sabadello, agropper, selfissued, manu, drummond, TallTed 22:57:14 RRSAgent, please draft minutes 22:57:14 I have made the request to generate https://www.w3.org/2021/05/25-did-minutes.html Zakim 22:57:18 I am happy to have been of service, brent; please remember to excuse RRSAgent. Goodbye 22:57:22 Zakim has left #did 22:57:25 rrsagent, bye 22:57:25 I see no action items