diff -r 3667c8882ebd -r e32e2e308de4 relpipe-data/index.xml --- a/relpipe-data/index.xml Sat Nov 21 20:36:38 2020 +0100 +++ b/relpipe-data/index.xml Wed Dec 30 10:29:29 2020 +0100 @@ -17,7 +17,7 @@
Each running program (process) has one input stream (called standard input or STDIN) and one output stream (called standard output or STDOUT) and also one additional output stream for logging/errors/warnings (STDERR). - We can connect programs and pass the STDOUT of first one to the STDIN of the second one (etc.) using pipes. + We can connect programs and pass the STDOUT of the first one to the STDIN of the second one (etc.) using pipes.
@@ -85,12 +85,12 @@
But the question is: how the data passed through pipes should be formatted and structured.
- There is wide spectrum of options from simple unstructured text files (just arrays of lines)
+ There is a wide spectrum of options from simple unstructured text files (just arrays of lines)
through various DSV
to formats like XML (YAML, JSON, ASN.1, Diameter, S-expressions etc.).
Simpler formats look temptingly but have many problems and limitations (see the Pitfalls section in the