Re: [Uri-review] Initial inquiry into URI proposal (nym)

David Booth <> Thu, 27 June 2013 19:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9F68821F9EC2 for <>; Thu, 27 Jun 2013 12:06:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jjhIcwn9-YjK for <>; Thu, 27 Jun 2013 12:06:10 -0700 (PDT)
Received: from ( []) by (Postfix) with SMTP id ABA9421F9EA6 for <>; Thu, 27 Jun 2013 12:06:09 -0700 (PDT)
Received: (qmail 57361 invoked by uid 0); 27 Jun 2013 19:06:06 -0000
Received: from (HELO ? ( by with SMTP; 27 Jun 2013 19:06:06 -0000
Message-ID: <>
Date: Thu, 27 Jun 2013 15:06:05 -0400
From: David Booth <>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: DataPacRat <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "" <>, Graham Klyne <>
Subject: Re: [Uri-review] Initial inquiry into URI proposal (nym)
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Proposed URI Schemes <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 27 Jun 2013 19:06:15 -0000

On 06/27/2013 02:43 PM, DataPacRat wrote:
[ . . . ]
> What I'm trying to build with nym (one way or another, and with or
> without other complications thrown in), is to have some sort of
> structure that uses such indirect addressing: to take any given URI,
> such as a webpage or mailto: address, and instead of referring
> directly to whatever is pointed at by that URI, having the nym use
> indirect addressing to be a reference to whatever that URI describes.

That sounds very much like
(or the shorter version ), except that also allows the URI to be dereferenceable 
without requiring clients to implement a new URI scheme or protocol.

You might want to look at "Converting New URI Schemes or URN Sub-Schemes 
to HTTP" also:
The abstract:
New URI schemes or URN sub-schemes are sometimes proposed for resource 
identification in applications where the HTTP protocol is deemed 
unsuitable.  This paper argues that URIs based on specialized HTTP URI 
prefixes would be a better choice in virtually all cases, even if the 
resource resolution or data transfer properties of HTTP are insufficient 
for these applications.   A simple recipe is presented for converting 
proposed URI schemes or URN sub-schemes to HTTP using specialized URI 
prefixes.  This technique cleanly separates the use of the URI as an 
identifier (to establish resource identity) from the use of the URI as a 
locator (to retrieve representations).  The resulting capabilities of 
the HTTP URIs are virtually a direct superset of those of URIs based on 
new URI schemes or URN sub-schemes.