Future better UUID binary-to-text encoding #769
Labels
No labels
breaking
bug
dependencies
good first issue
help wanted
unstable
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-uuid-rs/uuid#769
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@KodrAus
The authors of RFC 9562 have resumed discussion about a better UUID binary-to-text encoding
Proposal for OOXML Extension to Support Interactive UUID Widgets
In
uuid, we can support more encodings through additional types in thefmtmodule. Ideally anything we add there should have a unique length, so we can tell what encoding we're looking at without having to attempt to parse it first.The most popular encoding for UUID is Crockford's Base32 (5 bits per character). It has become a de facto standard. It is also used for ULID.
UUID is encoded in a 26-character string.
See an example