Ce #RFC normalise les #UUID, une famille d'identificateurs uniques, obtenus sans registre central. Il remplace l'ancienne norme, le RFC 4122, avec pas mal de nouveautés et un RFC complètement refait.
Of geek interest: UUIDs have been around for a long time and they work well and interoperate fine, but the specification space is a mess. So the IETF just shipped RFC9562; it has a fine consideration of the history and the trade-offs involved in all the different flavors of UUIDs, and is well-written and I think, as of now, the place to start looking if something UUID-flavored is puzzling you. Strong work! https://www.rfc-editor.org/rfc/rfc9562.html
@timbray
“UUID should be represented by the "hex-and-dash" string format consisting of multiple groups of uppercase or lowercase alphanumeric hexadecimal characters “
Every time I’m handling uuids in code I need to remember to think about case. I have seen resource IDs in azure recently consisting of multiple uuids in the one resource ID string. where some UUIDs are in caps and others are lower case. In the same ID string. But if you were building that resource ID string to use in an azure SDK you would have to respect which UUIDs are in caps and which are lc otherwise it will not be useable. It’s an absolute nightmare.
because the standard allows both and some library code has not implemented the standard correctly, we get issues with case. #Azure#UUID
I recently knocked up a VERY simple tool that generates a UUID and puts it in your clipboard. The way I use it is to set a global keyboard (Win+U) then I can paste it. https://github.com/asgrim/uuid2clip#rust#uuid#tool
OC Here is some code to generate UUIDs/GUIDs in QuickBasic
I couldn't sleep. Also I don't know how to deal with formatting this because of the apostrophes and I don't care that much...