- From: Richard Tobin <richard@inf.ed.ac.uk>
- Date: Mon, 7 Jan 2008 23:58:42 +0000 (GMT)
- To: jeni@jenitennison.com, public-xml-processing-model-wg@w3.org
> > I though no, because of the likely difficulty of representing > > sequences on the command line. > If I were implementing a command-line processor, I'd allow people to > specify "*.xml" to create a sequence of XML files (for example). I'm using directories for sequences (though of course I could have it handle command line inputs specially). I'd been imagining that the declaration of the pipeline determined whether it used files or directories, and that would imply that all abbreviated pipelines used directories, which would be unreasonable. I'd like to be able to use standard input and output too, which I only expect to work for non-sequences. I suppose I can just make it some kind of dynamic error if you try to send a non-singleton sequence to a file. -- Richard
Received on Monday, 7 January 2008 23:58:40 UTC