Re: [mmox] Global Object Identification

Jon Watte <jwatte@gmail.com> Sun, 21 June 2009 16:56 UTC

Return-Path: <jwatte@gmail.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 31F473A6814 for <mmox@core3.amsl.com>; Sun, 21 Jun 2009 09:56:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 35vpCExep0Up for <mmox@core3.amsl.com>; Sun, 21 Jun 2009 09:56:08 -0700 (PDT)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.240]) by core3.amsl.com (Postfix) with ESMTP id 4756C3A694E for <mmox@ietf.org>; Sun, 21 Jun 2009 09:56:08 -0700 (PDT)
Received: by an-out-0708.google.com with SMTP id c3so1135830ana.4 for <mmox@ietf.org>; Sun, 21 Jun 2009 09:56:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=5jw11LFS73KcTXtCLms18JPpoUyXW46YvEl/2ICu8XY=; b=p/4V+uFXJ3w7s9+7UBDWjM4nfLZch418J8nPL0f5Bt/RktOeCVquJv2hr/mJXK6KQI gAvckWlzkxvN6einu9QnsC77ul0rUTCw8gmpSppeRN9wjLC1DWBI4O7k6CFhhZbbKm7j 2y9BJHNmjCd+V/B8e+1LjjGRUhN7BLNnux5P8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=jN+2d+prSQVibBhOi4yo8SbFwCT9AuCBBdx+LR83DGhnQPMEuHK4A6q24wCxdZgAT0 SzEEkLCd1BYIHOQsJY7QvWkxQgLRf6xXI8uhnEu9VsUKYjbh0FGKkCyonYZ1oDz0AABW 5JwaYwfjqTECcOlo4vdVXpViazsVF6ytofrxo=
MIME-Version: 1.0
Received: by 10.100.9.18 with SMTP id 18mr6729309ani.122.1245603380899; Sun, 21 Jun 2009 09:56:20 -0700 (PDT)
In-Reply-To: <1245601755.7174.3.camel@mdickson-laptop>
References: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com> <3a880e2c0906191408m66e87830w6094987335fb6c16@mail.gmail.com> <1245446801.9567.12.camel@mdickson-laptop> <4A3E1A16.2070509@dcrocker.net> <1245601755.7174.3.camel@mdickson-laptop>
Date: Sun, 21 Jun 2009 09:56:20 -0700
Message-ID: <c7bcbd620906210956l1a05fb81xb3dea005c902a564@mail.gmail.com>
From: Jon Watte <jwatte@gmail.com>
To: mike.dickson@hp.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>
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: Sun, 21 Jun 2009 16:56:09 -0000

I would assume that in an interoperable world, there is no "local
only" object ID. Or, more likely, if an internal ID is needed, it's up
to each host to manage these, and translate when talking to the
outside world.

Also, I'd think that mapping URI to "resource on the internet" is
right -- VWs are internet constructs, by and large.

Sincerely,

Jw


On 6/21/09, Mike Dickson <mike.dickson@hp.com>; wrote:
> I was simply addressing a question about existing technologies for
> resolving digital assets with one I was aware of.  I think the handle
> system is well suited to the problem but I completely agree, having some
> requirements down will help inform that decision.
>
> URI implies to me resources on the web (as opposed to local only where a
> simple UUID might be sufficient).  But yes, again the details are what
> matters and having some guidance vis requirements is really needed.
>
> Mike
>
> On Sun, 2009-06-21 at 11:31 +0000, Dave CROCKER wrote:
>>
>> Mike Dickson wrote:
>> > I mentioned it in a separate message, but have you had a look at the
>> > NCRI handle service for this. It really seems spot on.  There is the
>> > need to address how digital assets map into it and what metadata is
>> > useful to carry around but the handle service was designed specifically
>> > to handle the secure resolution of URI's to "providers".
>>
>>
>> While there aren't many system/paradigm choices, here, there's more than
>> one.
>>
>> So it will probably help to have a brief summary of what the functional
>> requirements and constraints are, and then a mapping to the candidates.
>>
>> (Saying URI, for example, doesn't really answer many technical questions,
>> although it typically means the top of the scoping hierarchy is defined by
>> a
>> domain name.)
>>
>> d/
>>
>
> _______________________________________________
> mmox mailing list
> mmox@ietf.org
> https://www.ietf.org/mailman/listinfo/mmox
>


-- 

--
Americans might object: there is no way we would sacrifice our living
standards for the benefit of people in the rest of the world.
Nevertheless, whether we get there willingly or not, we shall soon
have lower consumption rates, because our present rates are
unsustainable.