Tour 2 of 3
Lets repeat the test, only this time we will reverse engineer an rss feed and create the OpenQL statements.
Link to Feed
<rss version="2.0">
<channel>
<title></title>
<link></link>
<description></description>
<image>
<url></url>
<link></link>
</image>
<item>
<title></title>
<link></link>
<description></description>
</item>
<item>
<title></title>
<link></link>
<description></description>
</item>
</channel>
</rss>
Lets create our OpenQL statements
 | |rss version="2.0"|channel|title,link,description,image,item| |
 | **|image|url,link| |
 | **|item|1..2|title,link,description| |
Analysis
| Command Type | Channels | Compressed tar.gz | Un-compressed Ascii |
| Open QL | 2 | | 117 bytes |
| Json | 1 | | 210 bytes |
| XML | 1 | 238 bytes | |
NB: The table refers to the above OpenQL statements and compressions were performed on Linux
Using online XML to Json convertor
Open QL is the clear winner on 3 points as follows:
1. Open QL has two channels one for the structural expression and one for data injection.
2. Open QL is the byte size winner.
3. Open QL is still human readable, xml is not.