equal
deleted
inserted
replaced
82 </m:diagram> |
82 </m:diagram> |
83 --> |
83 --> |
84 |
84 |
85 |
85 |
86 <p> |
86 <p> |
87 Now the question is: how the data passed through pipes should be formatted and structured. |
87 But the question is: how the data passed through pipes should be formatted and structured. |
88 There is wide spectrum of options from simple unstructured text files (just arrays of lines) |
88 There is wide spectrum of options from simple unstructured text files (just arrays of lines) |
89 through various <abbr title="delimiter-separated values e.g. CSV separated by comas">DSV</abbr> |
89 through various <abbr title="delimiter-separated values e.g. CSV separated by comas">DSV</abbr> |
90 to formats like XML (YAML, JSON, ASN.1, Diameter, S-expressions etc.). |
90 to formats like XML (YAML, JSON, ASN.1, Diameter, S-expressions etc.). |
91 Simpler formats look temptingly but have many problems and limitations (see the Pitfalls section in the <m:a href="classic-example">Classic pipeline example</m:a>). |
91 Simpler formats look temptingly but have many problems and limitations (see the Pitfalls section in the <m:a href="classic-example">Classic pipeline example</m:a>). |
92 On the other hand, the advanced formats are capable to represent arbitrary object tree structures or even arbitrary graphs. |
92 On the other hand, the advanced formats are capable to represent arbitrary object tree structures or even arbitrary graphs. |
138 |
138 |
139 <h2>What <m:name/> are not?</h2> |
139 <h2>What <m:name/> are not?</h2> |
140 |
140 |
141 <p> |
141 <p> |
142 <m:name/> respect the existing ecosystem and are rather an improvement or supplement than a replacement. |
142 <m:name/> respect the existing ecosystem and are rather an improvement or supplement than a replacement. |
143 So <m:name/> are not a: |
143 So the <m:name/> are not a: |
144 </p> |
144 </p> |
145 |
145 |
146 <ul> |
146 <ul> |
147 <li>Shell – we use existing shells (e.g. GNU Bash), work with any shell and even without a shell (e.g. as a stream format passed through a network or stored in a file).</li> |
147 <li>Shell – we use existing shells (e.g. GNU Bash), work with any shell and even without a shell (e.g. as a stream format passed through a network or stored in a file).</li> |
148 <li>Terminal emulator – same as with shells, we use existing terminals and we can use <m:name/> also outside any terminal; if we interact with the terminal, we use standard means like Unicode, ANSI escape sequences etc.</li> |
148 <li>Terminal emulator – same as with shells, we use existing terminals and we can use <m:name/> also outside any terminal; if we interact with the terminal, we use standard means like Unicode, ANSI escape sequences etc.</li> |