Storing results - Google Translate API Terms of Use
2,738 views
Skip to first unread message
Anders
May 12, 2011, 1:22:25 PM5/12/11
to Google AJAX APIs
According to the current terms for the Google Translate API it's not
allowed to store results in a database. My application needs to search
translated texts. And to store a lot of translated texts. Is there
another API available for this kind of use? Or is it possible to make
a request for an exception?
Also, my application needs to make automated requests.
allowed to store results in a database. My application needs to search
translated texts. And to store a lot of translated texts. Is there
another API available for this kind of use? Or is it possible to make
a request for an exception?
Also, my application needs to make automated requests.
Jeremy Geerdes
May 12, 2011, 1:34:03 PM5/12/11
to google-ajax...@googlegroups.com
The TOS prohibit you from stashing translations in a database for your own purposes, but there are exceptions. If you need to perform "a specific user-requested action," you can cache results for up to 15 days. Since the TOS don't specify what that specific action must be, as long as you're not doing automated processing on the data, you should be fine.
That said, I am not a legal expert. Nor do I play one on TV. So if you have any doubts about this, I would strongly suggest consulting someone who is.
Jeremy R. Geerdes
Generally Cool Guy
Des Moines, IA
For more information or a project quote:
jrge...@gmail.com
If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church!
> --
> You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group.
> To post to this group, send email to google-ajax...@googlegroups.com.
> To unsubscribe from this group, send email to google-ajax-searc...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-ajax-search-api?hl=en.
>
Anders
May 12, 2011, 2:02:07 PM5/12/11
to Google AJAX APIs
Yes, I read the part about temporary caching data. My application
needs to permanently store lots of translated data. The 5000 character
limit is ok for my needs, but I need to make massive amounts of
automated calls to the API. Hmm... I wonder if there is a version of
the API that one pays a certain amount depending on how many calls are
made, or a fixed price for unlimited use. That would work, unless it
would be too expensive. I have already started developing the
application and only checked the terms carefully today. :-(
On May 12, 7:34 pm, Jeremy Geerdes <jrgeer...@gmail.com> wrote:
> The TOS prohibit you from stashing translations in a database for your own purposes, but there are exceptions. If you need to perform "a specific user-requested action," you can cache results for up to 15 days. Since the TOS don't specify what that specific action must be, as long as you're not doing automated processing on the data, you should be fine.
>
> That said, I am not a legal expert. Nor do I play one on TV. So if you have any doubts about this, I would strongly suggest consulting someone who is.
>
> Jeremy R. Geerdes
> Generally Cool Guy
> Des Moines, IA
>
> For more information or a project quote:
> jrgeer...@gmail.com
needs to permanently store lots of translated data. The 5000 character
limit is ok for my needs, but I need to make massive amounts of
automated calls to the API. Hmm... I wonder if there is a version of
the API that one pays a certain amount depending on how many calls are
made, or a fixed price for unlimited use. That would work, unless it
would be too expensive. I have already started developing the
application and only checked the terms carefully today. :-(
On May 12, 7:34 pm, Jeremy Geerdes <jrgeer...@gmail.com> wrote:
> The TOS prohibit you from stashing translations in a database for your own purposes, but there are exceptions. If you need to perform "a specific user-requested action," you can cache results for up to 15 days. Since the TOS don't specify what that specific action must be, as long as you're not doing automated processing on the data, you should be fine.
>
> That said, I am not a legal expert. Nor do I play one on TV. So if you have any doubts about this, I would strongly suggest consulting someone who is.
>
> Jeremy R. Geerdes
> Generally Cool Guy
> Des Moines, IA
>
> For more information or a project quote:
Anders
May 12, 2011, 3:39:59 PM5/12/11
to Google AJAX APIs
With a modification my application can be developed without the
translate API. Phew! :-) Still, in the future I may want to add
functionality that requires language translation. And it's probably
many developers who want to use the API for automated requests and for
storing results in a database. So I think Google could consider
developing such API version.
translate API. Phew! :-) Still, in the future I may want to add
functionality that requires language translation. And it's probably
many developers who want to use the API for automated requests and for
storing results in a database. So I think Google could consider
developing such API version.
Shakya, Subodh
May 15, 2011, 4:48:41 PM5/15/11
to Google AJAX APIs
I didn't realize that we're not allowed to store the results of
translations. This would mean that the API is mostly meant for real-
time client side scripting. For example, if I write a blog post in
English and want to store the translation when say a Russian visitor
visits it would not be allowed with these terms. I do not think its a
scalable solution for a user to do the translation on the fly every
single time. Nor is it good for Google since users will just be doing
the same translations over and over again!
Can someone really shed some light on this?
translations. This would mean that the API is mostly meant for real-
time client side scripting. For example, if I write a blog post in
English and want to store the translation when say a Russian visitor
visits it would not be allowed with these terms. I do not think its a
scalable solution for a user to do the translation on the fly every
single time. Nor is it good for Google since users will just be doing
the same translations over and over again!
Can someone really shed some light on this?
Jeremy Geerdes
May 15, 2011, 5:11:11 PM5/15/11
to google-ajax...@googlegroups.com
You can cache translations for up to 15 days, as long as the caching is the result of user action. I.e., the user must initiate the translation.
Honestly, I think this is actually good because google is constantly tweaking theur machune translation matrix. In other words, you may get a better translation the next time you cache it.
Zdravko Gligic
May 15, 2011, 5:14:01 PM5/15/11
to google-ajax...@googlegroups.com
I would definitely like to hear an explanation as it definitely makes
no sense to me and especially not for cases where our own sites are
the originators of content and where we are in total control of
content changing or not and whether re-translation would need to
happen. While GOOG can do what it pleases with what it owns, I can
not see even a hint of what such terms achieve for them, other than
that they are totally counter productive and lose-lose for both sides.
no sense to me and especially not for cases where our own sites are
the originators of content and where we are in total control of
content changing or not and whether re-translation would need to
happen. While GOOG can do what it pleases with what it owns, I can
not see even a hint of what such terms achieve for them, other than
that they are totally counter productive and lose-lose for both sides.
Anders
May 16, 2011, 2:25:32 AM5/16/11
to Google AJAX APIs
My guess is that, similar to what Jeremy wrote, that Google constantly
changes the translation algorithm, and if we as third party developers
stored translations indefinitely, then Google translations many years
old could pop up later, which would look odd since the translation
algorithm by then most likely would be much better.
changes the translation algorithm, and if we as third party developers
stored translations indefinitely, then Google translations many years
old could pop up later, which would look odd since the translation
algorithm by then most likely would be much better.
Reply all
Reply to author
Forward
0 new messages