# HG changeset patch
# User František Kučera <franta-hg@frantovo.cz>
# Date 1572001258 -7200
# Node ID 1cdb74e845d08450dbbb977259e7067ec79e3781
# Parent  f7334408c68102bc11e0bed8f96fc5c2fc9139ac
faq: When the project started?

diff -r f7334408c681 -r 1cdb74e845d0 relpipe-data/faq.xml
--- a/relpipe-data/faq.xml	Tue Oct 22 16:48:36 2019 +0200
+++ b/relpipe-data/faq.xml	Fri Oct 25 13:00:58 2019 +0200
@@ -20,6 +20,18 @@
 		</p>
 		
 		<p>
+			<strong>When the project started?</strong>		
+			<br/>
+			The first commit was in the July 2018. Before that, there was nonpublic prototype which started in the April 2018.
+			But the original ideas are much older.
+			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).
+			The SQL-API was a prototype of an API for operating systems – it allowed SELECTing users, processes, fstab etc.
+			This prototype was based on PostgreSQL and Perl and is being replaced by particular modules of <m:name/>.
+			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).
+			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).
+		</p>
+		
+		<p>
 			<strong>How can I help you?</strong>		
 			<br/>
 			<ul>