The type 1 UUID that I proposed earlier would act more as a timestamp and authenticator than as URI.<br><br>The type 4 (random) UUID is better suited for many purposes since it is inherently anonymous, but the idea here is to act as a verification of content creator (IM or whatever) as they existed at a particular point in time. This can also be useful for unambiguous identification of freinds and IM originations - certainly not foolproof, but useful all the same.<br>
<br>I don't think the inherent privacy issues would impact any foreseeable use in the context of a public identifier such as this.<br><br>The fact that the user/organization later changes domains after creating the identifier, computer/MAC addresses is really irrelevant since (as I understand it) this is intended to identify somehting created at a particular time and place.<br>
<br>Yes the type 1 and type 4 UUIDs are compatible, there is a built in identifier field which tells which type is used. Figuring out which is legitimate (or correct) in a specific situation is a higher level problem.<br>
<br>Karen<br><br><div class="gmail_quote">On Sat, Aug 28, 2010 at 12:48 PM, Dahlia Trimble <span dir="ltr"><<a href="mailto:dahliatrimble@gmail.com">dahliatrimble@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Would it be possible to use just the UUID part and not tie it to a specific domain? I can foresee events where a user and a business/grid/domain owner/whatever make a decision to go separate ways and then any other systems out there that have the global identifier referenced may not be able to use it to contact that user. If only the UUID were used (we already use UUIDs for many diverse applications and the context implies the specific usage) it could be similar to a cell phone number where a user can take it from carrier to carrier. Resolving the current user domain would need to be worked out but several methods might be considered from a P2P network of resolvers to one or more central authorities, and/or simply storing it in a cache in local installations when the UUID is first used.<div>
<br></div><div>If we only use the UUID part then it may have some backward compatibility with existing user UUIDs used to identify content creators.<div><div></div><div class="h5"><br><div><br><div class="gmail_quote">On Sat, Aug 28, 2010 at 11:26 AM, <span dir="ltr"><<a href="mailto:diva@metaverseink.com" target="_blank">diva@metaverseink.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">I'm about to introduce global identifiers, so that I can make friends and IM work on the hypergrid, and would like feedback on the best form of these identifiers. Here are some options:<br>
<br>
<a href="http://myworld.com:8002/7c4450fc-aeaf-468d-b238-d52955dc868b" target="_blank">http://myworld.com:8002/7c4450fc-aeaf-468d-b238-d52955dc868b</a><br>
<br>
<a href="http://myworld.com:8002/7c4450fc-aeaf-468d-b238-d52955dc868b" target="_blank">myworld.com:8002/7c4450fc-aeaf-468d-b238-d52955dc868b</a><br>
<br>
<a href="http://myworld.com:8002/user/7c4450fc-aeaf-468d-b238-d52955dc868b" target="_blank">http://myworld.com:8002/user/7c4450fc-aeaf-468d-b238-d52955dc868b</a><br>
<br>
<a href="http://7c4450fc-aeaf-468d-b238-d52955dc868b@myworld.com:8002" target="_blank">7c4450fc-aeaf-468d-b238-d52955dc868b@myworld.com:8002</a><br>
<br>
...<br>
<br>
In this particular case (for friends and IM) we're dealing with user accounts, but the issue is broader than that. Whatever form we choose should be applicable to all sorts of resources.<br>
<br>
My preference is to use a URI, according to the spec of URIs (<a href="http://www.w3.org/Addressing/URL/uri-spec.html" target="_blank">http://www.w3.org/Addressing/URL/uri-spec.html</a>). The question is: should we add additional specifications on these URIs? Like using the path /user/ for user accounts, etc.<br>
<br>
Thoughts?<br>
<br>
Thanks.<br>
Diva / Crista<br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de" target="_blank">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
</blockquote></div><br></div></div></div></div>
<br>_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br></blockquote></div><br>