Closed OR13 closed 1 month ago
@TallTed wrote:
As noted many other places, just as there is no such thing as
application/jpg+zip
, theapplication/vp+ld+json+sd-jwt
media type should not exist; this media type should be simply application/sd-jwt. The described reasoning behind wanting media types likeapplication/vp+ld+json+sd-jwt
would be well satisfied and better conform to RFC history by specifying profiles for theapplication/sd-jwt
media type.
I sent a few messages to both the OAuth and Media Types lists at IETF:
Tracking the potential impact to application/vc+...
in https://github.com/w3c/vc-data-model/issues/1363
PR is up here: https://github.com/w3c/vc-jose-cose/pull/186
Categorizing as post-CR, per decision on 20-Dec-23 working group call.
Please use ISO 8601 date format, or at least 4-digit years. Ambiguous date formats cause endless trouble.
20-Dec-23
==> 2023-12-20
or 20-Dec-2023
We are using "typ" in the spec at this point. Therefore, I believe this can be closed, unless I'm missing something.
Per the comment here: https://github.com/w3c/vc-jose-cose/pull/183/files#r1405326097
This would still have the core data model taking a dependency on multiple suffixes, but it would make it so that there was no specific typ for W3C JSON-LD SD JWT VCs, which would counter the guidance from the IETF OAuth WG and the JWT BCP.
If we can't get consensus on the use of
typ
at W3C, we can remove references to it, such that profiles can lock down the behavior / comply with the JWT BCP... I am leaning towards that approach.