Kim Hamilton Duffy: Co-chair of CCG, steering committee of Decentralized Identity Foundation (DIF), board of Rebooting-the-web-of-Trust [scribe assist by Markus Sabadello] ✪
Kim Hamilton Duffy: Working at MIT on a credentialing scheme, based on standards and principles of this group [scribe assist by Markus Sabadello] ✪
Kim Hamilton Duffy: In the past, created blockcerts, earlier version of the standards we're discussing here [scribe assist by Markus Sabadello] ✪
Topic: Announcements and reminders
Joe Andrieu: Regular call to work on DID Spec work every Thursday [scribe assist by Markus Sabadello] ✪
Kim Hamilton Duffy: #44 And #43, issues around security model / threat model of DIDs, requesting clarity on correlation [scribe assist by Markus Sabadello] ✪
Kim Hamilton Duffy: Have been lingering for a while... if no progress soon: propose to turn them into DID spec issues so they can be addressed in the DID WG [scribe assist by Markus Sabadello] ✪
Christopher Allen: Maybe use new GitHub move issue feature. ✪
Kim Hamilton Duffy: I.e. close them in a week or so [scribe assist by Markus Sabadello] ✪
Kim Hamilton Duffy: We've been having breakout sessions to work on DID WG charter, triage issues [scribe assist by Markus Sabadello] ✪
Kim Hamilton Duffy: Closed about half of the issues (many editorial), still some remaining [scribe assist by Markus Sabadello] ✪
Kim Hamilton Duffy: This is a good opportunity to get involved! [scribe assist by Markus Sabadello] ✪
Kim Hamilton Duffy: If you want to help, click on above link to see the issues and feel free to contribute. Ask kimhd if you have any questions. [scribe assist by Markus Sabadello] ✪
Kim Hamilton Duffy: This is our list of work items [scribe assist by Markus Sabadello] ✪
Kim Hamilton Duffy: Both ongoing and completed ones. [scribe assist by Markus Sabadello] ✪
Kim Hamilton Duffy: We try to capture the efforts the group has done historically, so we can look and find historical work items. [scribe assist by Markus Sabadello] ✪
Kim Hamilton Duffy: You can help here too, help to update the list [scribe assist by Markus Sabadello] ✪
Joe Andrieu: We identified 5 work items in that issue, what's the current status? [scribe assist by Markus Sabadello] ✪
Christopher Allen: These work items were approved in previous meetings, but we don't have solid progress or editors or idea where things are going [scribe assist by Markus Sabadello] ✪
Christopher Allen: We'd like to get an idea if we continue to put time into these [scribe assist by Markus Sabadello] ✪
Christopher Allen: Suggest we try to find a new editor for this [scribe assist by Markus Sabadello] ✪
Christopher Allen: Idea of this work: Who and where and how do various parties use DIDs? [scribe assist by Markus Sabadello] ✪
Christopher Allen: Get an inventory of things; if we can't find an editor, we should close [scribe assist by Markus Sabadello] ✪
Joe Andrieu: Will reach out to see if someone is interested to move this along. [scribe assist by Markus Sabadello] ✪
Joe Andrieu: Volunteers? [scribe assist by Markus Sabadello] ✪
Joe Andrieu: Item 2: Digital Verification Specifications [scribe assist by Markus Sabadello] ✪
Christopher Allen: This is a separate task force, haven't done a great job keeping track of status [scribe assist by Markus Sabadello] ✪
Christopher Allen: Perhaps we should move this and list it as a "Draft Note", or other work item path, and officially list it [scribe assist by Markus Sabadello] ✪
Christopher Allen: Has reached some level of completion, may be close to final [scribe assist by Markus Sabadello] ✪
Christopher Allen: There's been some work on reconciling names [scribe assist by Markus Sabadello] ✪
Christopher Allen: Where are the specs for these? [scribe assist by Markus Sabadello] ✪
Markus Sabadello: We've known for a while this needs work. [scribe assist by Joe Andrieu] ✪
Joe Andrieu: ... We've done an update recently where we introduce ecda secp2561, but still need the specification written ✪
Joe Andrieu: ... The implementations here are various. ✪
Joe Andrieu: ... Agree with Christopher that how it works right now, process-wise needs work ✪
Markus Sabadello: Recently we just added "EcdsaSecp256k1Signature2019" (with no complete spec), simply to get alignment on Bitcoin-based and Ethereum-based DID methods ✪
Joe Andrieu: Where are we with Credential Handler API? [scribe assist by Markus Sabadello] ✪
Dave Longley: Spec is under CCG right now, right? People are implementing against the spec. But the spec needs to be updated and re-published. [scribe assist by Markus Sabadello] ✪
Dave Longley: Are planning to put more effort into updating this over the summer. [scribe assist by Markus Sabadello] ✪
Joe Andrieu: Is the polyfill also under CCG or under Digital Bazaar? [scribe assist by Markus Sabadello] ✪
Dave Longley: Digital Bazaar, since that's an implementation (open source) [scribe assist by Markus Sabadello] ✪
Christopher Allen: This is a spec, but is it planning for a concrete WG to take this on? [scribe assist by Markus Sabadello] ✪
Dave Longley: Not at the moment, way forward would be for more implementations to happen against that spec, to build up ecosystem around it [scribe assist by Markus Sabadello] ✪
Dave Longley: Then in the future it would go into WG for browsers to implement. [scribe assist by Markus Sabadello] ✪
Christopher Allen: Could it be on a "Commentary" track right now? so it can be listed as a Community Report? [scribe assist by Markus Sabadello] ✪
Joe Andrieu: Longer term, where would it go? [scribe assist by Markus Sabadello] ✪
Dave Longley: Long term: Move it into WG (similar to what Web Payments did: first CG, then WG, then implemented in browsers) [scribe assist by Markus Sabadello] ✪
Joe Andrieu: Sounds like "specification" track, not "commentary" [scribe assist by Markus Sabadello] ✪
Christopher Allen: Right [scribe assist by Markus Sabadello] ✪
Joe Andrieu: How does this interface with other related efforts, e.g. the various flavors of DID Auth that are happening [scribe assist by Markus Sabadello] ✪
Dave Longley: This API can be used to do DID Auth [scribe assist by Markus Sabadello] ✪
Dave Longley: Some politics around when is the right time.. Need broader support by people who implement. Want to make sure it remains generic and open [scribe assist by Markus Sabadello] ✪
Christopher Allen: Perhaps we should include another editor added, from another community that supports this work [scribe assist by Markus Sabadello] ✪
Christopher Allen: Should add it into CCG Github, then publish it as a draft report, with versioning [scribe assist by Markus Sabadello] ✪
Joe Andrieu: This was proposed before we had simplified work items [scribe assist by Markus Sabadello] ✪
Joe Andrieu: @OR13 hasn't found a 2nd editor; this could be an "informal" work item, we don't need to officially approve it [scribe assist by Markus Sabadello] ✪
Joe Andrieu: We should support it and accept as an "informal work item". What exactly does this entail? [scribe assist by Markus Sabadello] ✪
Christopher Allen: Without 2nd editor, it doesn't qualify as official work item. So we should close and invite to resubmit when there is a 2nd editor. [scribe assist by Markus Sabadello] ✪
Joe Andrieu: But still, how can we support "informal" work items? Perhaps give them a chance to introduce it as part of the agenda of weekly CCG call? [scribe assist by Markus Sabadello] ✪
Christopher Allen: My advice is, once it's more mature and has a 2nd editor, it should be officially announced. [scribe assist by Markus Sabadello] ✪
Christopher Allen: We can still list it as an adjacent resource, not everything has to be an "official" work item. [scribe assist by Markus Sabadello] ✪