-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standardizing MultiKey2021 #46
Comments
support from our side on this |
related issue in DID WG Charter and a comment w3c/cid#115 |
This would support IPFS / IPLD / Multiformat approaches... but the WG could decide that those are an anti pattern that should not be endorsed by standardization in the VC Data Model... we should sort this out before we approve the charter. |
We (Spruce) support the inclusion of |
The issue was discussed in a meeting on 2022-01-26
View the transcript7.4. Standardizing MultiKey2021 (issue vc-wg-charter#46)See github issue vc-wg-charter#46. Brent Zundel: Issue 46. Orie, can you talk about this one?. Orie Steele: Yes. This is a cool one.. Kyle Den Hartog: I like the idea of consolidating around keys within a suite. I'm not sure how well it fits in the VC spec. Maybe it could..
Kyle Den Hartog: Other question: within the DID Core data model, we define two but allow extensions that define any verification method... Creates arbitrariness that may create more complexity at the VC layer.
Kyle Den Hartog: The JSON-LD context... I want to pull that stuff out. Just keep the terms defined by the data model specifications.. David Waite: Multiformats are interesting, but I worry... A spec like JWK has a definition of a key, standardized, has libraries, W3C references it in other specs like WebCrypto. Multiformats does not have a lot of uptake...
David Waite: So I have some concerns. Also about how to profile usage of the crypto, in a working group mostly talking about data models, at least traditionally..
Brent Zundel: Good conversation, please continue in the issue, so we can see if there is consensus.. |
@OR13 what steps need to be taken to address this Issue? Is PR w3c/did#73 sufficient to fix this? |
I believe this issue has been addressed. Marking as pending close. |
no response since marked |
https://w3id.org/security/suites/multikey-2021
https://w3id.org/security/suites/multikey-2021/v1
Support for
publicKeyMultibase
for all existing JOSE kty / crv and RSA... this is thepublicKeyMultibase
mirror ofpublicKeyJwk
.This issue to propose moving it in scope for LD Integrity conversations.
The text was updated successfully, but these errors were encountered: