The new search API returns results in both JSON and XML. There is also a new BOSS mashup framework that provides SQL-like syntax for web data sources, like BOSS.
In my online experience, I typically visit a variety of sites: Techmeme, Digg, Techcrunch, eBay, Amazon, del.icio.us, etc... The biggest goal of Boss is to help bootstrap sites like these to get comprehensiveness and basic ranking for free, as well as offer tools to re-rank, blend, and overlay the results in a way that revolutionizes the search experience... I think users should be confident that if they searched in a search box on any page in the whole wide web that they’ll get results that are just as good as Yahoo/Google and only better...The next couple of milestones for Boss I think are even more interesting and disruptive - server side services, monetization, blending ranking models, more features exposure … so stay tuned.
My first plan is to try it with RecipeComun, my recipe search engine, to add a spell-checking ability. Ideally, I'd also like to backfill recipe results with web search results. However, I want to only return results from a slice of Yahoo's index, the food section. I can do something like this with Google Custom Search Engine, but I'm not keen on Google's restrictions. Perhaps I will start by adding site: restrictions, but I'm not sure how far I'll get with that.
Also, one observation is that the restriction on 50 results is very limiting if you want to perform any kind of significant reranking. Will multiple queries at different start offsets be throttled if you try and get around this? (Answer: you can get up to result 1000 by paging. This seems inefficient, why not allow this in fewer queries?)
- What is that max "start" position possible? (Answer: 950)
- What is the maximum supported query length? (for query expansion and site restrictions)
- In the future, would it be possible to get result metadata from the Webmap?