[sldev] Domains & UUID variant/version bits?

[Dzonatas]

Lawson English wrote:
> But....
>
> What if there is a collission between the UUIDs of two different 
> domains? Unless you have the entire cap as the new asset ID, there 
> will be collisions. I guess, at some point before the meta-grid goes 
> live, asset-wise, LL will need to replace all LL-specific UUIDs with 
> llDomain_URL caps. Guess that would actually work out fine, come to 
> think of it, and should be trivial to implement.
>

It's not a bad idea to use the same UUID from one domain in another 
domain. Although, it creates the illusion that both domains are actually 
one or that they depend on each other, but that dependency is what we 
want to avoid -- especially irrational ones. If domain A creates a UUID 
and provides it to domain B, then domain B can validate if the same UUID 
exists already within its domain before it decides it can use the same 
UUID or if it needs to create a new UUID (to avoid collisions or for 
another reason like with Assets below).

This is part of the reason why, when we look a UUIDs and Assets, we need 
to understand the distinction of the states.  Hence, there are 
differences between tangible, transient, referential, abstract, and 
irrational types:

https://wiki.secondlife.com/wiki/User:Dzonatas_Sol/AWG_Asset

With Assets, for example, each system will have to consider the 
properties of an Asset. The Asset of domain A may not be copiable to 
domain B, even if the UUID doesn't exist in domain B, so domain B 
creates a referential or abstract Asset that holds the URI/URL (or 
llDomain_URL) to another domain. That way, the same UUID is used, but it 
means one thing and domain A and means another in domain B. There still 
is a single truth. Furthermore, if there was a collision, the domain B 
can just create a new UUID before it creates the referential or abstract 
Asset in domain B for a non-copiable Asset from domain A. There is still 
a single truth about the Asset, and that is the greater concern than 
UUID collisions (being allowed and accounted for).

We do not have to replace the UUIDs, that now exist, when the domains, 
that also now exist, decompose to newer domains.

ya'cee? =)




-- 
Power to Change the Void