Talk:UUID

RFC specification website is changed. Link appears to want https://datatracker.ietf.org/doc/html/rfc4122#section-4.1.3

UUIDs are v4... or not!?

This page claims:

SL uses Version 4 UUIDs as defined in RFC-4122, though there are some that are not V4.

Except for NULL_KEY (which is separately defined in RFC-4122), what are those UUIDs that are not V4? Where are they used? When were they generated, and for which purpose? What version do they conform to, if not 4?

The issue is only important for me to validate UUIDs coming from SL and making sure they conform to whatever UUID specification SL uses. The statement on this page implies that SL uses UUIDs from different sources, possibly different versions, and possibly even UUIDs which are not technically UUIDs (as understood by RFC-4122), they just look like UUIDs (humans may not be able to spot the difference visually).

How, then, can we validate if an UUID is valid? :)

Gwyneth Llewelyn (talk) 12:33, 27 January 2022 (PST)

Most, but not all, avatar UUIDs are V4. A few of the earliest ones aren't, like 3de27254-3baa-31fd-2d41-4ff10c86717e.

Most other UUIDs are NOT v4, including groups, animations, textures, sounds, inworld object IDs...

The only way to validate them, besides checking the 8-4-4-4-12 format (if (my_key_value) in LSL comes handy for that), is checking if they exist in the database. A certain UUID may not be valid today and may be valid tomorrow.

Sei Lisa (talk) 16:52, 1 February 2022 (PST)