Closed msporny closed 4 months ago
From my point of view, neither of these sections is intended to define formal algorithms, with inputs and outputs. Rather, they are a set of steps for implementers to follow when sanity-checking instances of data structures defined by this specification.
If you want to suggest adding steps that you believe are missing, have at it.
I'll fix the broken SD-JWT reference. Thanks for pointing it out.
From my point of view, neither of these sections is intended to define formal algorithms, with inputs and outputs.
Based on the input from Google, the VCDM now has clear requirements for all securing specifications:
https://w3c.github.io/vc-data-model/#securing-mechanism-specifications
This includes the definition of algorithms w/ inputs/outputs.
If you want to suggest adding steps that you believe are missing, have at it.
That is primarily the responsibility of the Editors of the specification. I don't expect the specification will be able to transition to Candidate Recommendation when it fails to meet the requirements established by the WG and highlighted as a potential to cause a Formal Objection by a W3C Member.
The issue was discussed in a meeting on 2024-01-09
The new VCDM text pertinent to this is at https://w3c.github.io/vc-data-model/#securing-mechanism-specifications. @brentzundel , can you please either tell us that you think this is done or create another PR? Thanks.
The issue was discussed in a meeting on 2024-03-06
PR is here #261
Addressed by https://github.com/w3c/vc-jose-cose/pull/261
The algorithms in Section 11 and Section 12 are poorly defined, do not provide the interface specified in the VCDM, and are generally unimplementable as written.
The following problems exist in Section 11:
The following problems exist in Section 12:
credentialSchema
andcredentialStatus
can be ignored -- which seems like a bad idea. The group hasn't agreed to this being the default validation practice.