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

[David Booth <[e-mail]>]

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
http://thing-described-by.org/
(or the shorter version http://t-d-b.org/ ), except that
http://thing-described-by.org/ 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:
http://dbooth.org/2006/urn2http/
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.
]]

David