Meeting minutes
Agenda Review, Introductions
decentralgabe: Anyone want to reintroduce yourself?
decentralgabe: We'll recap abstract data model call, did core issues, might end 10 minutes early.
decentralgabe: any additions to the call?
Abstract Data Model Discussion Summary
<decentralgabe> w3c/
decentralgabe: recap of last meeting, we discussed 855, simplifying abstract data model to be more concrete. We did pass a few resolutions.
<decentralgabe> Align DID Core with the Controller Document specification (https://
decentralgabe: That was the first resolution
<decentralgabe> When profiling the Controller Document for the DID Document specification we will use JSON as a concrete representation, with language describing options for alternative representations.
decentralgabe: That one passed.
decentralgabe: That was the second resolution, that one passed as well.
decentralgabe: That was a good success.
<denkeni> I saw that we shared a common vision for broader inclusion of representations. Great to see things moving forward!
decentralgabe: We plan on having a special topic call on alternate representations, mostly on extensions, that's a part of that discussion. PRs will clean up a lot of language in DID Core that aligns with these resolutions.
<decentralgabe> manu: we had a call in the VCWG earlier in the week on the Controller Document spec and we were able to choose a new name, before Candidate Recommendation. Now we can pick a media type for that document.
<decentralgabe> ... that document can further align with those previous two resolutions (not using the ADM, etc.). We are starting to see some good alignment between the Controller Document spec -- now the 'Controllable Identifier Document' specification (CIDs), with DIDs on top of that.
<decentralgabe> ... things are aligning well!
DID Core Issue Processing (Class 2)
decentralgabe: Ok, onto DID Core issue processing for class 2 changes.
w3c/did-core#170
decentralgabe: Let's go through these in least recently updated.
decentralgabe: This one opened by Mike Jones 4 years ago, comments two years ago.
decentralgabe: suggestion that there might not be an issue.
decentralgabe: Let's mark this as pending close
manu: Agree, this hasn't been an issue in 4 years and is unlikely to become one... kid/kty are different from id/type in JsonWebKey and Multikey.
w3c/did-core#370
decentralgabe: This one was opened by Adrian, four years ago. Suggestion to classify DIDs into Accountable and Voluntary categories. There doesn't seem to be consensus or concrete proposal, suggestion is to ask Adrian to write language and mark them as pending close.
manu: Agreed.
w3c/did-core#530
decentralgabe: Suggestion for DIIPs by jonnycrunch, Manu suggested that other WGs don't really have these. I think that the process we have is sufficient, my inclination is to close this.
w3c/did-core#539
manu: +1 to closing, the current process is to raise an issue, discuss in WG, then Pull Request, then merge if consensus.
<denkeni> +1 for it
decentralgabe: The section on herd privacy, what it means, how it applies to DIDs, good discussion here...
decentralgabe: Seems like we should discuss with Joe. Let's ask Joe if this could be closed.
w3c/did-core#798
manu: The WG is creating data models and APIs, which answers the question, we should mark it as pending close.
<shigeya> +1
w3c/did-core#821
manu: The group should discuss this, maybe special topic call?
decentralgabe: Yes, special topic call.
w3c/did-core#835
decentralgabe: This is broad, asking about verifiable credentials, and was answered. Marking as pending close.
<denkeni> +1 special topic call, i remember there was a discussion about whether DID should be align with URI or not
manu: Agreed
w3c/did-core#837
decentralgabe: This is reminiscent of a controller / subject discussion we had in VCWG.
manu: There was a big discussion in controller-document about this. Joe has written a lot of language around this.
w3c/did-core#839
decentralgabe: This is about how to specify multisig -- need to clarify?
decentralgabe: Doesn't say where logic is defined, keep open and improve language.
<shigeya> +1
manu: Yes, that sounds good.
w3c/did-core#844
decentralgabe: This is vague, let's see if they can provide more input.
w3c/did-core#847
decentralgabe: This is another path parameter thing.
w3c/did-core#849
decentralgabe: This is about service endpoints, Markus has responded, spec registries could e used to help. My instinct is to ask for an update or PR or concrete text.
manu: yes, let's ask them what they want to see.
w3c/did-core#802
decentralgabe: This is another one that was covered in the VCWG in the controllable identifier document specification.
w3c/did-core#803
manu: Yep, agreed -- Ivan had concerns, I think we addressed them with PRs in VCWG.
decentralgabe: difference is concrete representation vs. abstract one. Marking this as pending close.
w3c/did-core#805
decentralgabe: Improving readability is a good goal, hopefully we can take a shot at improving readability.
<shigeya> +1 for ready for PR
w3c/did-core#812
manu: We probably need to specify a more complete example, updated to show verificationMethods.
decentralgabe: want to cover DID Resolution or keep going?
w3c/did-core#831
decentralgabe: long discussion, some agreement w/ Joe's clarification. Sounds like language could be made more clear, but took a bit to understand that what they want is supported. Probably room for improvements.
manu: Maybe ready for PR
decentralgabe: I'm going to tag Joe since he seems to understand what language might be good here.
manu: We might need to move it to CID spec.
decentralgabe: We got through all of those issues.
decentralgabe: Anything else you'd like to discuss?
No other issues.
<denkeni> Thanks!
<decentralgabe> m2gbot, link issues with transcript
<m2gbot> Something wrong happened: Failed loading minutes from https://
<decentralgabe> m2gbot, link issues with transcript
<m2gbot> Something wrong happened: Failed loading minutes from https://