W3C home > Mailing lists > Public > uri@w3.org > January 2008

Re: URIs for the standard output and input streams

From: Noah Slater <nslater@bytesexual.org>
Date: Tue, 15 Jan 2008 12:07:14 +0000
To: Jeremy Carroll <jjc@hpl.hp.com>
Cc: uri@w3.org
Message-ID: <20080115120714.GD12624@bytesexual.org>

On Tue, Jan 15, 2008 at 11:52:54AM +0000, Jeremy Carroll wrote:
> stdin, stdout and stderr are OS provided protocols, and not the network 
> protocol HTTP - hence an HTTP uri seems wholly inappropriate.

STDIN isn't a protocol like http:// is, it's a feature of POSIX
systems that applications can hook into natively without having to
dereference anything. All that is needed is an identifier.

> While say the geoloc vs http argument has merits on both sides - the "HTTP 
> is the only necessary protocol" argument is taken to absurdity with
>
> http://purl.org/std/in

I disagree. URIs are opaque and "http://purl.org/std/in" is just an
identifier for the concept of STDIN, which is it's self a
non-information resource.

The "http://" is not important, it's /just/ a name.

Additionally, by using http:// we get to place a metadata profile at a
network resolvable location so that clients who do attempt to
derefference it will get a description of the resource.

-- 
Noah Slater <http://bytesexual.org/>

"Creativity can be a social contribution, but only in so far as
society is free to use the results." - R. Stallman
Received on Tuesday, 15 January 2008 12:07:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 January 2011 12:15:40 GMT