Hello,
There was a request to add media type parameters to application/sd-jwt
and +sd-jwt made here:
https://github.com/w3c/vc-jose-cose/issues/184#issuecomment-1827973403
TLDR; TallTed believes that the convention in the JWT BCP is not correct:
https://datatracker.ietf.org/doc/html/rfc8725#nam
An afterthought... we could also punt on the impact of multiple suffixes by
following the convention activity pub used:
https://www.w3.org/TR/activitystreams-core/#media-type
application/ld+json; profile="https://www.w3.org/ns/activitystreams";
For W3C Verifiable Credentials that could be:
appl
If you are interested in how this `profile` parameter might be related to
other credential formats at W3C, for example anonymous credentials built on
top of data integrity proofs, see this issue:
https://github.com/w3c/vc-data-model/issues/1363
Regards,
OS
On Mon, Nov 27, 2023 at 9:00 AM Orie S
On 2023-11-27, at 15:55, Orie Steele wrote:
>
> application/jwt; profile=secevent
>
> This is a general form of the challenges associated with using multiple
> structured suffixes with JWTs.
Anything that reduces our need to extract semantics from complex nested
structured suffixes is good.
