My Personal Fork of the YQL Datatables
This is my personal fork of the original YQL open data tables. If you want to find the latest version of the YQL tables, please go to the original.
What is YQL?
From the Yahoo's YQL website:
The Yahoo! Query Language is an expressive SQL-like language that lets you query, filter, and join data across Web services. With YQL, apps run faster with fewer lines of code and a smaller network footprint.
Why do you have a personal fork?
I am a YQL enthusiast. I love the general idea and also the current implementation (for the most parts). The Open Data Tables are great but sometimes a bit slow when it comes to incorporating recent updates. Therefore I am using this repository as my personal playground. I pull the latest changes from the YQL Community tables as I need them but at the same time I can always do random experiments here without being depended on the original repository.
As I said, YQL is great. As any piece of software it also has some flaws (as in bugs) and some other things that I just don't like that much, which is more a matter of personal taste. Also there are some areas of YQL that I just don't understand.
Therefore I am sometimes collecting some thoughts about YQL on Twitter. See some examples below. I am happy to learn more about them or discuss with anybody who is interested in YQL.
- How to keep a given API and the corresponding datatable in sync as API gets updated?
- How to measure the "coverage" of a datatable, meaning how many calls of an API are implemented by the datatable? #in
- How to introduce and maintain naming conventions for the naming of "keys" across different datatables?
- Would be great to access usage stats for datatables that I did, to see how people use them. #optimization #motivation
- How to search for existing community datatables? The console is fine but could be better.
- Why can I not access/use values from a Sub-Select besides using the IN-syntax? Would allow for richer queries.
- How to test datatables, e.g. to be notified when the underlying API changes or gets deprecated like
- The error messages are just not clear :( Except this one of course "Yahoo! - 999 Unable to process request at this time"