Re: [mmox] Global Object Identification

Christian Scholz <> Mon, 06 July 2009 21:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A350F3A6C9F for <>; Mon, 6 Jul 2009 14:31:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.26
X-Spam-Status: No, score=-0.26 tagged_above=-999 required=5 tests=[AWL=1.739, BAYES_00=-2.599, J_CHICKENPOX_36=0.6]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id XDBWX6UCtCZp for <>; Mon, 6 Jul 2009 14:31:03 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 2B88C3A68A3 for <>; Mon, 6 Jul 2009 14:31:02 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5FDFD1CE030D; Mon, 6 Jul 2009 23:30:53 +0200 (CEST)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id u-os5xkxhSXF; Mon, 6 Jul 2009 23:30:52 +0200 (CEST)
Received: from [] ( []) by (Postfix) with ESMTP id BC1E11CE01C8; Mon, 6 Jul 2009 23:30:51 +0200 (CEST)
Message-ID: <>
Date: Mon, 06 Jul 2009 23:30:49 +0200
From: Christian Scholz <>
User-Agent: Thunderbird (Windows/20090605)
MIME-Version: 1.0
To: Jon Watte <>
References: <> <> <1245446801.9567.12.camel@mdickson-laptop> <> <1245601755.7174.3.camel@mdickson-laptop> <> <> <1246813317.4532.48.camel@mdickson-laptop> <> <1246820675.4532.55.camel@mdickson-laptop> <> <1246833222.4532.83.camel@mdickson-laptop> <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "" <>, Dave CROCKER <>
Subject: Re: [mmox] Global Object Identification
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Massively Multi-participant Online Games and Applications <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 06 Jul 2009 21:31:04 -0000

Jon Watte schrieb:
> Mike Dickson wrote:
>> I'm not at all convinced that your DNS example is a non-problem.
>> Companies merge all the time and how name spaces migrate or merge is a
>> real problem.   
> My question to you is: Do you think that it is a technical problem to 
> keep a DNS domain alive, if there were an incentive to do so? My 
> assertion is that it isn't. Thus, if you structure your URL well 
> (typically use a custom DNS for all your asset URLs) then they can 
> survive for as long as you want them to.

I think here there is also the general topic of data portability which 
is important. If I own some stuff I might want to take it with me which 
might mean to change URLs. As long as an asset is always copied into a 
context IMHO there shouldn't be a problem with URLs.

Now it is a policy decision if you always copy it or just use it by 
reference (which IMHO makes no difference in non-copyability btw) but if 
you use the latter you already have that problem on the web today. On 
social networks though more stuff seems to be copied (or actually 
re-uploaded all the time) so even if the first place you put it goes 
down the others still have it (and you yourself should be able to copy 
your own stuff around as you wish to anyway).

> Assuming I want to pay the $10/year for 
> "" then this will survive forever.
> Admittedly, my main concern with the handle system is not technical, but 
> the fact that it costs $100 to get started, and then $50/year, which is 
> 5x-10x more than it costs with a DNS based solution (both solutions need 
> additional web hosting, too).

I agree here. As long as this is not a free service it won't get 
traction and we actually see this with XRI. Besides that you'd need to 
explain all this to people and too many levels of indirection are not 
too easy to understand in general.

The question IMHO is if we need to care today if they will be popular 
tomorrow as long they are URIs. Then it should be easily replaceable 
without even changing any specs.

-- Christian

COM.lounge GmbH
Hanbrucher Strasse 33, 52064 Aachen
Amtsgericht Aachen HRB 15170
Geschäftsführer: Dr. Ben Scheffler, Christian Scholz

fon: +49-241-4007300
fax: +49-241-97900850

personal email:
personal blog:
personal podcasts:,