Hi Brian,
please note that this is a working group item and you cannot make decisions in a small group with off-line discussions. Hence, I suggest to propose the changes to the list and get support for it. As you know, we need to follow this approach to give everyone in the group a chance to get their voice heard. Ciao Hannes Am 13.06.2023 um 20:58 schrieb Brian Campbell:
Following some offline discussions and feedback there's a plan to make some small simplifying changes to the SD-JWT draft to consolidate the format and associated terminology. Basically the terms "Combined Format for Issuance" and "Combined Format for Presentation'' will go away and the whole structure, issued or presented, can simply be called an SD-JWT. To align the two formats, the last Disclosure will always be followed by a `~` (tilde) character (currently the Combined Format for Issuance does not have the trailing tilde). When holder/key binding is required for presentation of a SD-JWT, a holder/key binding JWT will be appended to the end of the whole thing after the trailing tilde. That's all there is to it, which isn't much, but I think the result will be shortening and simplifying the spec text. And also make the terminology easier and more natural when talking about uses or applications of SD-JWT. /CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you./ _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
