For example, I am developing a community site, where users come across various content and which they then end up placing into various categories on my site. In most cases, I end up storing just the URL to the original content. In cases of RSS news feeds, I store the headline part of the news story and the URL to the originating publisher's story page. In all cases, I take the end user to the original URL page, via Adobe AIR's built in WebKit browser. So, I do not even iFrame nor in any other way camouflage the originating site's page.
Now, I would like to use GOOG translate on some of these RSS news headlines. I might even want to translate the whole originating page. In addition, I might want to build a chat with translation capabilities. Here, I have no sense of what may or may not be TOS compliant. Furthermore, I could cache some of the translations and even get them re-translated, only if the original content changes. I do not have to do this caching but would rather be able to do it, if it turned out to be a more efficient and preferred way. Finally, in my use cases, I have not yet even looked at AdWords nor any other form of advertising because I have a specific revenue model. So, there are no ads being displayed on the same page that the content is displayed on - unless, I take the user to the originating site's page, on which they would likely have their own ads. Up to now, none of the content is "discovered" via GOOG API's of any sort. In case of YouTube, I use GData to search specific videos and I cache only the 11 character VideoId. From what I can tell, and from what I have been told on YT API dev forum, this is YT TOS compliant. So, I am trying to figure out what additional GOOD Searching API's I could use, where I could cache the most basic info - like the URL or whas it GID? for the content that is returned. P.S. While I am relatively new to web development, I have tons of legacy software development experience or rather tons of different real life use cases experience. As such, my strengths are in creativity and the whole idea of "if you can not have it the way you wished it, wish it another way". However, I am learning too many different technologies and can not afford to be guessing nor developing cool things without having a good sense that they may be copliant *before* I develop them. Any help in interpreting the above use case examples would be immensely appreciated. Regards, Zdravko On Tue, Mar 1, 2011 at 7:41 PM, Zdravko Gligic <[email protected]> wrote: > Hi folks, > > I am deep into using YouTube API (player and gdata) as well as > translation v1. I have been lurking on this v2 stuff and for most > part it seems to be so much and so deep into javascript, while I am > under an impression that it is a REST based API. I am using Adobe > Flex and AIR for all of my development and mostly as a shield from all > of the browser incompatibilities, being an old timer (: from COBOL and > PUNCHED CARD days :). > > So, what are all of the different links that deal with TOS and where > one can get a sense of what is and what is not allowed and/or > welcomed. I am actually quite in tune with YT TOS. > > Thanks, > Zdravko > The Web 0.2 Guy > -- You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-ajax-search-api?hl=en.
