Closed David-Chadwick closed 8 months ago
For what it's worth, I think this would be useful. This is not an official position etc :)
This issue should be closed, this is covered in vc-jose-cose
The issue was discussed in a meeting on 2023-12-06
This issue should remain open until the following issues are fixed
Thanks for your comments, @David-Chadwick . Here are my thoughts:
Per 2, [SD-JWT-VC] was actually referenced several places, but using the wrong Markdown syntax. https://github.com/w3c/vc-jose-cose/pull/198 fixes this.
Per discussion on the 20-Dec-23 working group call, I don't think there's consensus to do 1.
We can take up 3 after CR, but given it doesn't change the meaning of the spec, it's not critical to go to CR.
Please re-open this issue as it has not been completed yet. It can be marked post-CR if you like, but until point 3 has a PR prepared for it, then this issue should not be closed.
@David-Chadwick I opened a separate issue to track this https://github.com/w3c/vc-jose-cose/issues/199
I have raised PR#212 to address the title issue. This does not make the title any longer, and furthermore it accurately reflects what the spec is about. Furthermore it is consistent with the Introduction section of the specification, which the original title no longer is
Apologies if this topic has already been discussed in the VC WG and I missed it.
The current work on SD-JWT is being carried out in the IETF. A profile of SD-JWT is also being created for "verifiable credentials" but this draft contains the following note "This specification does not utilize the W3C's Verifiable Credentials Data Model v1.0, v1.1, or v2.0."
This poses the following questions. Q1. Does this working group think that there should be a specification of how to use SD-JWT to create W3C VCDM conformant VCs? If the answer to Q1 is yes, then Q2. Is it within the scope of the current WG to create a profile of SD-JWT that does utilise the W3C VCDM? Q3. If not, does W3C have any other mechanism for creating such a profile?