For Example: select * from html where url=”http://finance.yahoo.com/q?s=yhoo” and compat=”html5″

Please start using this feature and give us your feedback! Eventually the new parser which supports ‘html5’ will be made default, but that will follow an announcement. Even after the new parser is made default, the old one can still be used by having compat equals to ‘html4’.

YQL Table Health is intended to provide a quick general overview of how “healthy” the community OpenData tables are:

When you first arrive to the page, you will see a list of all the tables that can be used by YQL. Clicking on one of the entries in the list will cause it to expand and show additional information regarding where the source of the XML file is, what kind of table it is, sample query information, and lastly any errors that were encountered. You can use the controls on the left-hand side to further filter, sort, and search through all this data. If you see a table that doesn’t work, you can contact the author of the table to fix it via github. You may also fork the yql-tables from github and fix or enhance the table yourself.

YQL Table Health uses a sever-side script to iterate through all the tables. Each table’s XML file is loaded into YQL cloud storage before a series of checks are run against that XML file. The test results are then cached in a database as well as memory to serve this data as fast as possible. Updates to caches are triggered by users visiting the page and only fire if the data is older than thirty minutes; requests for an update are also synchronized to prevent a race condition occurring, where two or more requests might be made simultaneously. Last but not least, the data is served to the user through a user-interface built using HTML5 and the YUI Library.

The next tool we’re going to introduce to you is YQL Lint.

YQL Lint is essentially an XML debugger for individual YQL tables. You can enter either a URL to a XML file, or the contents of an XML file, and it will validate this against our schema for syntax flaws. Once the schema check has been passed, we will use YQL to get a description of your YQL table and check to see if it contains a sample query that returns a valid result. YQL Lint essentially relies on the same core backend as YQL Table Health.

Please experiment with these tools and send us any questions or suggestions you might have.

Daniel Park – YQL/Pipes Intern

For those of you relying on those tables please consider using the community BOSS v2 table (https://github.com/yql/yql-tables/blob/master/boss/boss.search.xml).

Thanks -YQL Team

http://blog.pipes.yahoo.net/2011/06/10/pipes-v2-engine-timeline/

If you do not provide an API key the request will still work but is subject to rate limiting which may be triggered with high use of this table.

Please sign up for a Flickr API key if you haven’t already and use that in your Flickr YQL calls going forward.

For example: SELECT * FROM flickr.places WHERE query=”north beach” and api_key=”your key here”

Thanks -YQL Team

use 'http://www.javarants.com/nyt/nyt.article.search.xml';
use 'http://www.javarants.com/nyt/nyt.bestsellers.history.xml';
use 'http://www.javarants.com/nyt/nyt.bestsellers.search.xml';
use 'http://www.javarants.com/nyt/nyt.bestsellers.xml';
use 'http://www.javarants.com/nyt/nyt.movies.critics.xml';
use 'http://www.javarants.com/nyt/nyt.movies.picks.xml';
use 'http://www.javarants.com/nyt/nyt.movies.reviews.xml';

…and serve it from somewhere on the web. If you want to try this new feature on some useful open data tables in the console, you can use a few of the ones currently in the github open data tables project like this:

http://developer.yahoo.com/yql/console/?env=http://github.com/spullara/yql-tables/raw/ef685688d649a7514ebd27722366b2918d966573/alltables.env


Try it in the console!. If you look to the “table” list on the right of the console, you’ll see an extra 9 APIs and 30 tables to explore!

For example, one of the requests we had when using our weather table was how to get an ID that would work for an international location. We pointed people to the weather.com API, but that needed a URL to be formatted up in a specific way. Now you can make that a table and use it:

use 'http://www.javarants.com/weather/weather.search.xml' as ws;
select * from weather.forecast where location in (select id from ws(1) where query='bonn, germany')

Try it.

While we believe this is a great start, it’s work in progress. We’re already adding more capabilities and adjusting the open data table XML syntax as we get feedback and go forward. You can read more about how to go about creating open data tables in our documentation.