I really like the Yahoo Webservices, one reason is that the guys their are really helpful. I asked a general question and they were kind enough to spend plenty of time explaining some parts of the Yahoo Term Extraction API.My basic question was how does the "query parameter" that you pass to the Term Extraction help parse the context parameter.Their general answer was that their is a semantic network in the background that relates words and phrases to a general term. The general term I assume can be controlled by the basic query that you pass as a parameter.So it got me thinking, how can you determine the correct query parameter to use so that the results you get will be the most relevant. It turns out that the results of the term extraction are ordered by relevance, so the most important term is first in the results [kind of obvious when you think about it]. Therefore, if you Term extract your context without a query, choose the first result and then term extract the context again with the query being the first term, you might have a system that will best guess the gerneral topic of the context and then use this topic to filter the results better.I am going to try this in my DeliTag and AjaxTag applications, because a lot of the terms that it generates have little relevance to the actuall topic that I am talking about.Obviously, this method will half the number of requests that your system can run against the Yahoo API's (because two requests are being made).
I lead the Chrome Developer Relations team at Google.
We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.
Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.