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

Re: URIs for the standard output and input streams

From: Jeremy Carroll <jjc@hpl.hp.com>
Date: Thu, 17 Jan 2008 12:06:02 +0000
Message-ID: <478F44AA.3020108@hpl.hp.com>
To: Mike Schinkel <mikeschinkel@gmail.com>
CC: "'Dan Connolly'" <connolly@w3.org>, uri@w3.org

Mike Schinkel wrote:
>> How wide is the convention that /dev/stdin is stdin?
>> Wide enough for the IETF to reserve file:/dev/stdin for 
>> standard input?
> 
> Not sure if this matters, but a Windows machine doesn't have a clue what
> /dev/stdin means.
> 


Note

file:/dev/stdin

does in fact not conform with the file uri scheme specification; it 
should be written

file:///dev/stdin

It will likely work immediately with a range of Unices (the 0 line 
implementation!)

For some OSes (including some Unices), the implementation of the file: 
scheme would need modification.

A std: scheme with std:in, would not work in any OS, but a dispatcher 
written in a particular implementation language is likely to be very 
easy to port (e.g. simple recompile) from one OS to another, since the 
underlying concepts of stdin stdout and stderr are supported by most 
programming languages that might be used for writing such a dispatcher.

Jeremy
Received on Thursday, 17 January 2008 12:06:38 GMT

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