21. Some of them get
offered to you in very
easy to use formats.
22. Others need to get
converted to more
useful formats.
(which is a hack in itself that can make a difference)
23. Some very good data
sources:
http://developer.yahoo.com/everything.html
http://data.gov.uk
http://www.guardian.co.uk/world-government-data
http://programmableweb.com/
http://www.guardian.co.uk/news/datablog
24. The trouble with data:
You need to get access to the data sources (API
keys, authentication)
You need to get data in formats that are easy to
use for your use case
You need to filter the data down to what you
really want to have in the end.
All of the above multiplies in annoyance with
the amount APIs you use.
29. select * from query.multi where
queries in (
'select * from nyt.article.search where
query="healthcare"',
'select * from microsoft.bing.news where
query="healthcare"',
'select * from google.news where
q="healthcare"'
)
30. select content from html where
url="http://www.foxnews.com/"
and xpath="//h2/a"
31. select * from google.translate
where q in (
select content from html where
url="http://
www.foxnews.com/" and
xpath="//h2/a"
) and target="fr"
32. Using YQL has a lot of
benefits:
No time wasted reading API docs
Using the console makes creating
complex queries dead easy.
Data filtering down to the least
amount necessary.
Fast pipes.
Caching + converting
Server-side JavaScript