-
Notifications
You must be signed in to change notification settings - Fork 94
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
Add COSE key format example into CBOR section #340
Comments
Work in progress. PR in the works. |
We might want to reserve terms / discuss on key representations call. |
I was waiting to get feedback before submitting PR and to make sure the example is a well formatted COSE with int as keys. |
Having discussed this in more depth, I am understanding the challenges. In essence, in order to express that a verification method has a public key in COSE encoding we will need to either specify an attribute in the DID document or DID spec registries (as @OR13 suggested
I'm not a bit fan of |
I think you need to define a new publicKey type...
Then we would still need to address the other meta data expressed by a |
@OR13, yes. I had started a publicKeyMultiformat.cddl format, but this is blocked until we have resolution regarding other key formats and accepting CDDL to aid in the representations. I'm also on the fence about whether to allow for inline CIDs. something like for linked items:
This will work fine for cbor, but not for JSON. perhaps the follow is a compromise and works for both dagCBOR, CBOR and JSON but I think I can do better:
technically, this will work for both JSON, CBOR and dagCBOR and is the direction I am attempting in the DID core CBOR section, but alas ... politics |
hmm, I can see the value of I would prefer to split that case, so the that field is always by value , and some other field is by reference.... both have their uses.... I can imagine some CBOR DID Methods might choose to only support 1 or the other. |
Propose closing this and not adding support for CWK this round. |
The group discussed this issue on 2021-01-12 and suggested that the added complexity may not be worth it and has also suggested that the issue should be closed. This issue will be closed in 7 days unless there are objections. |
No objections raised, closing issue |
At present the CBOR example demos a public key format in text for easy serialization to/from JSON and JSON-LD without the need for cryptographic libraries.
@jonnycrunch TODO:
The text was updated successfully, but these errors were encountered: