… been a couple of weeks since we met last, so this may be out of date
… we use our github community repo to manage issues and plan for our events
… so that's the list of action items for review
… updating ABNF for DIDs. some of that discussion took place at Rebooting, but obv. did not involve the whole community, so any suggestions from there will definitely be discusses on here or on some other public forum
… or we'll schedule a dedicated meeting on it again
… Linked Data Key Format Registry administrivia - Kim?
Kim Hamilton Duffy: I think I ended up tagging manu on that? ✪
Christopher Allen: Manu had commented 28 days ago that we /had/ a registry, but we need to extend it to mention the key format ✪
Manu Sporny: Now is probably not the right time to have this discussion, but I'll take on that task. No eta to when I'll get around ✪
Dmitri Zagidulin: I'm happy to take that item as well ✪
Christopher Allen: Ok, I'm adding dmitri and manu to that item ✪
Joe Andrieu: Regarding ABNF - there were some questions and comments brought up by mhermann about it, ✪
… so I want to invite Drummond to comment
Drummond Reed: <Struggle with the mute button is real> ✪
… I've shared several PMs with mhermann, I think there was a misunderstanding with regards to what we were trying to do there
… which was to have a discussion and brainstorm, and then bring it to the CCG
… nobody is trying to hide it or run around the CCG
… anyways, to complete an actual proposal / draft spec, we'll need several more calls dedicated to the topic
… so that's my report. we made a little bit of progress, but much discussion needs to still happen on calls
Mhermann: I think there was some poor communication; drummond and I have discussed it ✪
… I'd like to advocate a process that starts with DID URL use cases, and use that to drive the ABNF grammar discussion
… whereas we're trying to do it the other way around
… I suggested a couple of initial DID URL use cases
Christopher Allen: I want to encourage you guys to take this to dedicated meetings. ✪
… the chairs were a little concerned about dedicating more meetings of the main group to it
… we certainly would love to hear you report back, about the various challenges and solutions
Jonathan Holt: Just to distinguish between ABNF rules for the "naked did" vs the DID URL spec ✪
… keeping the distinction separate might be helpful.
… plus there's the struggle with each DID method having its own specialized ABNF
Ken Ebert: One of the usecases was my own, which was the need for immutable data references ✪
… so it is definitely usecase driven
Manu Sporny: Just to underscore the usecase driven thing that ken and michael mentioned, ✪
… we did collect a number of usecases for the DID abnf from Rebooting 8
Joe Andrieu: +1 To use cases. Please get them to me either by PR or email for the use case document ✪
Drummond Reed: I would be happy to help organize some dedicated DID spec meetings—I think we will need a few to close on the Community Final Draft of the DID spec. We've held them before on Thursdays. I'll send an email to the CCG list proposing a time. ✪
… so if you go that link, there's a number of cases, and Ken and Drummond chased down a number of other people who had use cases with regards to service urls, etc
… so, we're definitely taking the use case driven approach even now
Christopher Allen: We've created a template in the repo for templates for new Work Items for the CCG ✪
Manu Sporny: Proposal for registries from Dan Burnett ^^^ ✪
… so, if you want to create a new item, please use the template
… <some description of the template>
… it's automatically tagged as a work item (that template), which allows us to schedule a call automatically for it
… we'll have a discussion, then we send a notification to the list, and if there's no objection, it becomes an official Work Item
… this is involved, but necessary
… helps us keep track of who is responsible, whether there is critical mass, etc
Jonathan Holt: How does the idea of these registries scale? ✪
… for example, semantic interop for Credentials for a Bachelors Degree
… how are the expansions going to be handled - just by the registry? the community, or what
Christopher Allen: I absolutely believe there's a role for Schemas, as a work item for the CG ✪
… I'm not sure if that's exactly a registry
… but it's a good question
Joe Andrieu: Somewhere, we have a registry that can link to external work ✪
… I share your concerns about scalability
… Also: we have far too many Work Items than we've been able to facilitate
… all these projects need leads, and we'll start holding the leads accountable (including myself)
… to make sure they're moving forward (or taking them off the list)
… our near-term focus is - chartering the DID Working Group
… I'm concerned about our workload. We need people to step up and help us with these
Dan Burnett: So, this is a bit of a surprise; I sent an email requesting the registry work. Do I also need to fill out this Work Item form? ✪
Christopher Allen: Yes. it should be straightforward though, in your case ✪
Dan Burnett: Ok, the other thing I wanted to say — you mentioned the focus on the DID WG. I want to point out that the VC WG was also spun out of this CG. ✪
… and that's also a crucial component. And this CG needs that work completed /before/ the DID work
… at some point, we may want to add a field to the registries, the Conformance Level
… anybody can do a DID method, just like with Verifiable Credentials, but when it comes to lists of conforming implementations, there should be a higher bar to entry
… so, right now, there is no conformance test for DID methods, everyone is preliminary. as the spec advances, we may add higher criteria, more restrictive
… but that's down the line, it'll evolve
Manu Sporny: Noting that the VC Registry (whatever we'll end up calling it) is critical for the WG's spec to make progress ✪
For example, the Cha-Cha (& someothers) — those specs are evolving, how do we keep them up to date? how do we specify which version of the algorithm we're referencing, etc ✪
… there were a number of orgs that were interested in the Credentials Handler API & interop testing. (For doing DID Auth and Credential Handling in the browser)
… for wallet interop and DID interop, over the next year
… we're currently trying to work with those orgs, bring them into the CCG, figure out what a viable roundtrip testing would look like
… as a heads-up, large orgs are starting to use the Credential Handler API (though they're not part of this community yet)
… so maybe this year, we can focus more on interop testing (between different DID methods, VCs issued by different stacks, etc)
Jonathan Holt: To echo the epiphany I mentioned on the VCWG call ✪
… the IPLD method — you can serialize JSON-LD on top of IPLD, but there's no backwards compatibility
… the whole issue I've been raising about objects and links, and the IPLD "/" usage
… I've a number of issues open with the IPFS community
… about the cbor serialization, and an explicit IPLD mime type
… it'll take a while to go through the IETF. but in the DID spec, we need to ground ourselves in a serialization format
… but in the end, our type is actually CBOR (byte array, deterministic json, binary)
Drummond Reed: Two things. Christopher, when you asked earlier about our papers at Rebooting, I didn't talk about the paper we started there, called Understanding DIDs in Greater Depth ✪
… we wanted something in between the Primer (high level) and the spec (too low-level). so that's the paper we started. it's very early stage
… I want to make sure folks knew that we want this to be a community doc
… the other thing: I've been txting with Markus, there's currently a call on DID Resolution every other week on Thurs, on 1-2pm Pacific time,
… one hour for DID spec related features (ABNF stuff), and the second hour for DID Resolution topics
Christopher Allen: There were quite a few other docs at rebooting ✪
… in particular I want to point out some of the "softer" ones (I wish there was a better word for that),
… but I wanted to highlight them to this community
… for example, the Digital Citizen one
… and how SSI can survive Capitalism
… various failure modes and opportunities
… there was one by Elizabeth and ?, about the legal side of Verifiable Credentials
… looking forward to that one
… there was the Crypto Jurisdiction one. Sam did some interesting work on how to drive adoption of SSI
… through particular scenarios, like Safety and Security, a great usecase
… for why that's a good place to leverage / bootstrap the VC ecosystem
… On the technical side, there was some work on how to use OpenID Connect for DID Auth and VC Presentation
… as the VC WG finishes and has their final doc approved, it'll become more and more the responsibility of the CCG to advance forward things like protocols that use VCs
… so, at some point, a new VC Protocol WG will be chartered
… but until then, that stuff will be shepherded in this community
… there are a lot of paper (25). None of these have the weight of standards, that's not the point,
… the point is incubation
… and it's up to the authors whether to pass it to the W3C groups
… was there to field questions. We had 2 new features we had been talking about for a while in the DID spec, and we were finally able to consult with them on them
… for example, what keys you use to issue VCs, and what keys you use to enter into legal agreements (think DocuSign and EverSign)
… and we were able to run over to their group and ask, to put it on their radar
… that we'd really like that we would love some legal opinion on these features
… so, that's definitely one of the times we absolutely needed legal direction, and there were lawyers right there, we could ask to start thinking about this in the next couple of months
… so, that was really nice to see, this group definitely needs more than just technologists