Kim Hamilton Duffy: Send last call for additional CG work items before poll DUE FRIDAY MAY 26th [DONE] [scribe assist by Manu Sporny] ✪
Kim Hamilton Duffy: Create poll for priorities on work items, ~3 weeks snapshot poll results for prioritization - DUE TUESDAY MAY 30th [IN-PROGRESS] [scribe assist by Manu Sporny] ✪
Christopher Allen: Create a new proposal for how Digital Verification CG integrates DUE JUNE 6th [ON HOLD re: NAME & MISSION] [scribe assist by Manu Sporny] ✪
Manu Sporny: ALL: Approve New Name and Mission Statement - DUE JUNE 27th ✪
Manu Sporny: Clarifies that only W3C chairs can update community docs ✪
Topic: Community Group Scope and Naming
Christopher Allen: At the last meeting, there was a motion to unite the two community groups ✪
Christopher Allen: The open issue is the name of the unified group. "Credentials" is overused ✪
Manu Sporny: Needs to appear before the US Fed Secure Payments Task Force next week and give them a formal name of this group ✪
Manu Sporny: Proposes "Digital Verification Community Group" ✪
Manu Sporny: Favors that name because it's a "big tent" ✪
Manu Sporny: Wants to avoid the term "Identity" since it is so overloaded ✪
David Chadwick: The term "credential" is more accurate ✪
Ryan Grant: Asks about the term "identity" - why is it overloaded? ✪
Manu Sporny: The W3C has said that it is not a topic they want to tackle ✪
Manu Sporny: The security community got upset about the use of the term "credential" because in their view a credential is strictly a username/password ✪
Manu Sporny: "Decentralized Verification" is another option, but that's also vague. ✪
David Chadwick: "Credential" is broader than username/password ✪
David Chadwick: It would be correct to use "credentials" in the meaning of the term we all understand ✪
Manu Sporny: Agrees, but our opinions on the suitability of the term really don't matter to some of the major players at W3C. They can then block the work behind the scenes. ✪
Manu Sporny: The words "identity" and "credential" are trigger words for that reaction ✪
David Chadwick: The word "verification" is too vague ✪
Joe Andrieu: His concern about "verification" is only about the signature of the issuer, not whether the claim is true. So he'd like to be able to retain that, ✪
Adam Lake: Decentralization is a strategy to achieve Self-Sovereignty--Self-Sovereignty is the goal it seems to me. ✪
Harlan Wood: +1 For "Self-Sovereign Technology Community Group". Inspiring to us, and likely sounds irrelevant to those who might block other names... ✪
Adam Lake: Interesting shift from trying to name the specs to using the name of the goal [scribe assist by Ryan Grant] ✪
Christopher Allen: I love the SS idea (obviously) but it may alienate some, as you can use this tech with centralized as well. ✪
Maria Dubovitskaya: Worked on ABC for Trust, which was all about privacy-preserving credentials and authentication. This was published by Microsoft and IBM. ✪
Manu Sporny: That's true, ChristopherA - SS may alienate large corporates/governments. ✪
Adam Lake: If SS can be centralized then why does it alienate? ✪
Dave Longley: A Web API for verifiable claims will work like other Web APIs like the Payments API. In fact those other APIs are designed to be extended for functions like these. ✪
Ryan Grant: Slide 8's did would be legal as: did:nop:1324 ✪
Dave Longley: Doing this in a polyfill lays the groundwork for browsers to natively implement the API and those APIs will take over from the polyfill ✪
Dave Longley: Digital Bazaar has an implementation of a polyfill that works now. It lets you register a DID, receive a claim, and then share it with another site. ✪
Manu Sporny: Dave's referring to slide 6 - the one with the links ✪
Dave Longley: There are a number of ways we can go with this. The preso includes links to source code of the demo. The last few slides show what the Javascript code looks like. ✪
Dave Longley: The Web API abstracts the digital wallet so that the developer does not need to care where or how the credentials are stored ✪
Joe Andrieu: The work is a prose description of the 15 steps of a user interacting with the system—in this case a Syrian refugee arriving in Greece ✪
Joe Andrieu: Talks through the 15 steps as shown in the use case document ✪
Joe Andrieu: The goal is to present what the user experience would be throughout the lifecycle of the technology without the technical details so one can focus on the actual use and benefits ✪
Topic: Data Minimization and Selective Disclosure Report
Christopher Allen: We have a number of topics around data minimization and selective disclosure, including CL signatures ✪
Christopher Allen: Other approaches do simpler forms of data minimization and selective disclosure, but these have not been expressed in detail, so we need a document that explains and explores the options. ✪
Christopher Allen: Right now he is the lead on this item, and is seeking other champions ✪
Drummond Reed: I can talk about current DID spec on next call [scribe assist by Manu Sporny] ✪
Drummond Reed: This is work that started here with the VCTF and DIDs for Verifiable Claims... we moved it forward under DHS S&T... and Rebooting Web of Trust last year. [scribe assist by Manu Sporny] ✪
Drummond Reed: It's an identifier format that can work with any ledger or decentralized identifier technology. It doesn't rquire centralized registration authority, standardized JSON-LD object/DDO, associated w/ public keys, key rotation control block, service endpoints. [scribe assist by Manu Sporny] ✪
Christopher Allen: Asks that if you know others who are interested in this work, send them email and make sure they know that this is a new Community Group with a big tent. Encourage them to participate in the next few calls. ✪
Kim Hamilton Duffy: A poll is going to come out this afternoon ✪