Fabio Lima

I also think the version bits (subtype) are specific to the RFC4122 variant (type), which has many subtypes that must be separated from each other. Variant 3 (111) doesn't even...

I'm still not sure if using half of the future variant is a good idea. I prefer to be conservative in this case. It may be easier to approve the...

How about defining parallel versions in two variants: v7, v8 and E7, E8? Is it an overkill? In **v7** and **v8**, the version bits are kept in the same position...

> One of the main goals here is to make something useful so databases I think UUID v6 and v7 can also be useful for event-driven applications. This specification suggests...

I don't like using 38, 24 and 12 bits for nanos, micros and seconds respectively. I think this could 'waste' a few bits. I prefer to use 30, 20 and...

Sorry, I didn't focus on the main question in my previous answer. I prefer the first case (one-second faction), although the second (specific number of ms/us/ns) is simpler and more...

I would like to show you how to encode and decode in Python, Java and Javascript using the timestamp with **40 bits** and **10-milli** precision. IMO a timestamp with 40...

I think "MAX_UUID" is more appropriate than "OMNI_UUID". Even in Romance languages like mine we no longer use "omnis" as a standalone word. For instance, in my language it is...

Another important thing to keep in mind is how many UUIDs can be generated per unit of time. The more of a type of UUID that can be generated in...

@edo1 Yes. I made a silly mistake in the beginning. All the rest of the calculation is wrong! I will fix this. Thanks for noticing!