"for those that celebrate" should be offset by commas on each side, https://www.grammarly.com/blog/punctuation-capitalization/comma-with-interrupters/. The draft is correct in this regard.
I think many readers, however, will read "celebrate ABNF" (missing the trailing comma) and get confused because they ended the interrupting phrase in the wrong place. On Fri, Oct 25, 2024 at 9:22 AM Warren Parad <[email protected]> wrote: >> >> Little attempts at satire, like this one, that poke fun at the occasional >> absurdity involved in standards development work help me keep it together in >> the face of the occasional absurdity. > > > I totally agree, I've always found the opportunities to add enjoyment to the > consuming of the specs to be appreciated. I will say that I can't actually > decide if the comma belongs or not though. > > On Fri, Oct 25, 2024 at 1:11 AM Brian Campbell > <[email protected]> wrote: >> >> The phrase "for those who celebrate" there is a subtle attempt at a little >> bit of good-natured humor. ChatGPT explains the general phrase thusly: >> >> The phrase "for those who celebrate" is often used to acknowledge that not >> everyone may participate in a particular holiday, event, or tradition. It's >> a way of being inclusive and respectful of diverse beliefs, practices, and >> customs. For example, saying "Happy Holidays to those who celebrate" >> recognizes that while some people may be celebrating a specific holiday, >> others may not observe it or may celebrate different holidays. >> >> The meaning in the context of this document is to playfully acknowledge that >> some people really like ABNF while others aren't readily familiar with it >> and/or don't find it particularly useful. The former are those who >> celebrate. The latter are those who do not. The document is inclusive of all. >> >> This lighthearted reference also reflects the journey of how ABNF came to be >> included in the document. Seen here: >> https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/393, there >> was initially a suggestion that including ABNF would be helpful for >> implementers. Even though this was met with some skepticism about how many >> people would actually find it useful, it was added to the document anyway. >> >> Of course, if a joke requires explanation, it tends to lose its humor. >> Nevertheless, I remain partial to the text. Little attempts at satire, like >> this one, that poke fun at the occasional absurdity involved in standards >> development work help me keep it together in the face of the occasional >> absurdity. >> >> >> >> >> >> On Thu, Oct 24, 2024 at 1:54 AM Travis Spencer >> <[email protected]> wrote: >>> >>> Section 4 of draft 13 of the SD-JWT WG document says: >>> >>> As an alternative illustration of the SD-JWT format, for those who >>> celebrate, >>> ABNF [RFC5234] for the SD-JWT, SD-JWT+KB, and various constituent parts >>> is provided here: >>> >>> Who are those who celebrate? Those that celebrate birthdays, >>> Midsummer, Halloween? I don't understand and think that phrase should >>> be deleted. >>> >>> Suggested alternative: >>> >>> As an alternative illustration of the SD-JWT format in ABNF [RFC5234] for >>> the SD-JWT, SD-JWT+KB, and various constituent parts is provided here: >>> >>> HTH! >>> >>> _______________________________________________ >>> OAuth mailing list -- [email protected] >>> To unsubscribe send an email to [email protected] >> >> >> 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 -- [email protected] >> To unsubscribe send an email to [email protected] _______________________________________________ OAuth mailing list -- [email protected] To unsubscribe send an email to [email protected]
