Re: [mmox] Global Object Identification

Infinity Linden <infinity@lindenlab.com> Sat, 20 June 2009 01:03 UTC

Return-Path: <infinity@lindenlab.com>
X-Original-To: mmox@core3.amsl.com
Delivered-To: mmox@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A264F3A6BC8 for <mmox@core3.amsl.com>; Fri, 19 Jun 2009 18:03:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.363
X-Spam-Level:
X-Spam-Status: No, score=-1.363 tagged_above=-999 required=5 tests=[AWL=0.614, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fWQY66b0zId8 for <mmox@core3.amsl.com>; Fri, 19 Jun 2009 18:03:31 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by core3.amsl.com (Postfix) with ESMTP id A75EC3A6849 for <mmox@ietf.org>; Fri, 19 Jun 2009 18:03:31 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so902656ywj.49 for <mmox@ietf.org>; Fri, 19 Jun 2009 18:03:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.208.9 with SMTP id f9mr4723333ang.55.1245459822892; Fri, 19 Jun 2009 18:03:42 -0700 (PDT)
In-Reply-To: <4A3C20B5.4060602@gmail.com>
References: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com> <4A3C20B5.4060602@gmail.com>
Date: Fri, 19 Jun 2009 18:03:42 -0700
Message-ID: <3a880e2c0906191803o1da1305bh35759421fcb71fe9@mail.gmail.com>
From: Infinity Linden <infinity@lindenlab.com>
To: Imaze Rhiano <imaze.rhiano@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: mmox@ietf.org
Subject: Re: [mmox] Global Object Identification
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Massively Multi-participant Online Games and Applications <mmox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmox>
List-Post: <mailto:mmox@ietf.org>
List-Help: <mailto:mmox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Jun 2009 01:03:32 -0000

nothing's wrong with GUIDs if you have one asset service. that way
when you get a GUID/UUID for an asset, you go to that one asset
service and say "okay.. gimme the (meta)data for this asset." it's a
little more difficult if you have more than one asset service cause
the UUID itself doesn't tell you what service to go to in order to
find an asset's (meta)data.

in order to find asset (meta)data from a GUID, you either have to have
a global registry where you can do UUID to asset service mapping or
you ship around the UUID and the location of the asset service. The
latter is essentially what we're talking about in OGP where asset caps
will probably look something like
http://example.com/assets/EBBD86E3-A274-4CD1-A86A-405AABCB7BF9 , where
"http://example.com/assets/" is the location of the service and
"EBBD86E3-A274-4CD1-A86A-405AABCB7BF9" is the UUID of the asset.

On Fri, Jun 19, 2009 at 4:35 PM, Imaze Rhiano<imaze.rhiano@gmail.com>; wrote:
> Hi!
>
> Sorry about noobish question, but what is wrong with GUID?
>
> Tommi Laukkanen kirjoitti:
>>
>> Dear All
>>
>> Anyone have suggestion how we can achieve indisputable universal
>> identification of objects. It would be a good start for
>> interoperation.
>>
>> Respectfully,
>> Tommi of bubblecloud.org
>> _______________________________________________
>> mmox mailing list
>> mmox@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmox
>>
>>
>
> _______________________________________________
> mmox mailing list
> mmox@ietf.org
> https://www.ietf.org/mailman/listinfo/mmox
>