15 <m:name/> are something that should be released about twenty years ago. But real work started in 2018. |
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. |
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. |
17 We understand the <em>release early, release often</em> rule. |
18 But it fits better to application software than to standards and APIs. |
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 backward compatibility in future. |
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 backward compatibility in future. |
|
20 </p> |
|
21 |
|
22 <p> |
|
23 <strong>When the project started?</strong> |
|
24 <br/> |
|
25 The first commit was in the July 2018. Before that, there was nonpublic prototype which started in the April 2018. |
|
26 But the original ideas are much older. |
|
27 Predecessors of <m:name/> were <a href="https://sql-api.globalcode.info/">SQL-API</a> (September 2014) and <a href="https://alt2xml.globalcode.info/">alt2xml</a> (January 2012). |
|
28 The SQL-API was a prototype of an API for operating systems – it allowed SELECTing users, processes, fstab etc. |
|
29 This prototype was based on PostgreSQL and Perl and is being replaced by particular modules of <m:name/>. |
|
30 The alt2xml uses different data model (tree instead of relational) but despite that, it is based on the same ideas as <m:name/>: converting data from various formats to a uniform model, streaming and processing through reusable transformations (filters). |
|
31 This tool might be developed in the future and can be used together with <m:name/> (e.g. read INI, JSON or Java properties files using alt2xml and pass them to the <code>relpipe-in-xmltable</code> and continue with the processing in the relational way). |
20 </p> |
32 </p> |
21 |
33 |
22 <p> |
34 <p> |
23 <strong>How can I help you?</strong> |
35 <strong>How can I help you?</strong> |
24 <br/> |
36 <br/> |