5 <nadpis>FAQ</nadpis> |
5 <nadpis>FAQ</nadpis> |
6 <perex>Frequently asked questions</perex> |
6 <perex>Frequently asked questions</perex> |
7 <pořadí>16</pořadí> |
7 <pořadí>16</pořadí> |
8 |
8 |
9 <text xmlns="http://www.w3.org/1999/xhtml"> |
9 <text xmlns="http://www.w3.org/1999/xhtml"> |
|
10 |
10 <p> |
11 <p> |
11 The world is relational! |
12 <strong>When the stable version will be released?</strong> |
|
13 <br/> |
|
14 We don't know – there is no exact date. |
|
15 <m:name/> are something that should be released about twenty years ago. But real work started in 2018. |
|
16 So it is not a big difference whether it will be released this month or the next one. |
|
17 We understand the <em>release early, release often</em> rule. |
|
18 But it fits better to application software than to standards and APIs. |
|
19 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. |
12 </p> |
20 </p> |
|
21 |
|
22 <p> |
|
23 <strong>How can I help you?</strong> |
|
24 <br/> |
|
25 ... |
|
26 </p> |
|
27 |
|
28 <!-- |
|
29 <p> |
|
30 <strong>?</strong> |
|
31 <br/> |
|
32 ... |
|
33 </p> |
|
34 |
|
35 <p> |
|
36 <strong>?</strong> |
|
37 <br/> |
|
38 ... |
|
39 </p> |
|
40 |
|
41 <p> |
|
42 <strong>Why don't build on XML? It is a standard since 1998 and there are many tools and libraries for it.</strong> |
|
43 <br/> |
|
44 XML is a great and mature (meta)format and its ecosystem is respectable and inspiring. |
|
45 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. |
|
46 XML is also not concise. |
|
47 And the implementation of the XML parser in various environments would be <em>a bit more complex</em>. |
|
48 </p> |
|
49 <p> |
|
50 We prefer XML as an input and output format and look forward to cooperation with XML ecosystem (XSD, XPath, XSLT, XQuery etc.). |
|
51 Such steps might be at the beginning, at the end, or even in the middle of the relational pipeline. |
|
52 </p> |
|
53 |
|
54 <p> |
|
55 <strong>?</strong> |
|
56 <br/> |
|
57 ... |
|
58 </p> |
|
59 --> |
|
60 |
|
61 <p> |
|
62 <strong>Have you seen <a href="https://xkcd.com/927/">XKCD 927</a>?</strong> |
|
63 <br/> |
|
64 Yes. And we liked it so much that we followed their instructions and created <m:name/>. |
|
65 </p> |
|
66 |
|
67 <p> |
|
68 <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> |
|
69 <br/> |
|
70 Go @#$%& yourself. We are pretty old school hackers and we enjoy our green screen terminals!<br/> |
|
71 Of course, you can use <m:name/> anywhere if it makes sense for you. |
|
72 <m:name/> are designed to be generic enough – i.e. not specific to any industry (banking, telecommunications, embedded etc.) nor platform. |
|
73 Its native data structure is a relation (table) but it can also handle tree-structured data (i.e. any data). |
|
74 It is designed rather for streaming than for storage (but under some circumstances it is also meaningful to use it for storage). |
|
75 </p> |
|
76 |
13 </text> |
77 </text> |
14 |
78 |
15 </stránka> |
79 </stránka> |