--- a/relpipe-data/faq.xml Tue Nov 27 00:22:01 2018 +0100
+++ b/relpipe-data/faq.xml Tue Nov 27 17:03:54 2018 +0100
@@ -7,9 +7,73 @@
<pořadí>16</pořadí>
<text xmlns="http://www.w3.org/1999/xhtml">
+
<p>
- The world is relational!
+ <strong>When the stable version will be released?</strong>
+ <br/>
+ We don't know – there is no exact date.
+ <m:name/> are something that should be released about twenty years ago. But real work started in 2018.
+ So it is not a big difference whether it will be released this month or the next one.
+ We understand the <em>release early, release often</em> rule.
+ But it fits better to application software than to standards and APIs.
+ Of course, we expect some evolution after the v1.0.0 release, but we need to stabilize and verify many things before the release in order to be able to maintain hackward compatibility in future.
+ </p>
+
+ <p>
+ <strong>How can I help you?</strong>
+ <br/>
+ ...
+ </p>
+
+ <!--
+ <p>
+ <strong>?</strong>
+ <br/>
+ ...
+ </p>
+
+ <p>
+ <strong>?</strong>
+ <br/>
+ ...
</p>
+
+ <p>
+ <strong>Why don't build on XML? It is a standard since 1998 and there are many tools and libraries for it.</strong>
+ <br/>
+ XML is a great and mature (meta)format and its ecosystem is respectable and inspiring.
+ But the XML does not conform to our <m:a href="principles">principles</m:a>, especially the ability to concatenate multiple files/streams and to append new records to an already existing relation.
+ XML is also not concise.
+ And the implementation of the XML parser in various environments would be <em>a bit more complex</em>.
+ </p>
+ <p>
+ We prefer XML as an input and output format and look forward to cooperation with XML ecosystem (XSD, XPath, XSLT, XQuery etc.).
+ Such steps might be at the beginning, at the end, or even in the middle of the relational pipeline.
+ </p>
+
+ <p>
+ <strong>?</strong>
+ <br/>
+ ...
+ </p>
+ -->
+
+ <p>
+ <strong>Have you seen <a href="https://xkcd.com/927/">XKCD 927</a>?</strong>
+ <br/>
+ Yes. And we liked it so much that we followed their instructions and created <m:name/>.
+ </p>
+
+ <p>
+ <strong>Are <m:name/> compatible with cloud, IoT, SPA/PWA, AI, blockchain and mobile-first? Should our DevOps use it in our serverless hipster fintech app with strong focus on SEO, UX and machine learning?</strong>
+ <br/>
+ Go @#$%& yourself. We are pretty old school hackers and we enjoy our green screen terminals!<br/>
+ Of course, you can use <m:name/> anywhere if it makes sense for you.
+ <m:name/> are designed to be generic enough – i.e. not specific to any industry (banking, telecommunications, embedded etc.) nor platform.
+ Its native data structure is a relation (table) but it can also handle tree-structured data (i.e. any data).
+ It is designed rather for streaming than for storage (but under some circumstances it is also meaningful to use it for storage).
+ </p>
+
</text>
</stránka>