The age old question of the restrictive terms of service...
RickB
there are many, many situations for security and physical connectivity
reasons that a client device/browser does not have internet access.
Yet Google has maintained a very restrictive TOS that prohibits
offline use of the Google Visualization API. I've yet to hear a
legitimate reason why this remains the case.
The issue of "you get the most up-to-date code" is a non-issue and
easily dealt with. In fact, in enterprise apps, particularly those in
regulated industries, constantly changing the code is a huge
governance risk, so it isn't even desirable.
It would be helpful to know who the executive(s) in charge of both the
Visualization API TOS and the enterprise customer offerings are, so
that we can begin a meaningful dialog to move Google closer to
understanding the needs and realities of the enterprise.
Kind regards,
Rick Bullotta
CTO/Co-Founder
Burning Sky Software
OG
I am wondering about the same thing. We'd like to use Google
Visualization API, but can't send the data (may not even be ours) to
Google. Here are some links to threads on this topic from 1 -1 1/2
years ago. "VizGuy (Google)" hinted at ToS possibly changing back
then to allow more liberal use of the GV API:
Is there any way to use the library without sending data to Google and
being dependent on Google at "run-time"?
It's even OK to fetch the (versioned) JavaScript files from Google
servers at run-time, but agreeing to ToS that say that Google can
limit access or set request limits doesn't work for business. Plus,
what happens if Google decides to discontinue the API? The ToS
doesn't guard against that.
Would it be possible to get the official word/update from Google?
Thanks,
Otis
On Feb 19, 7:36 am, RickB <rbullo...@gmail.com> wrote:
> Google has aspirations to deliver solutions into the enterprise, but
> there are many, many situations for security and physical connectivity
> reasons that a client device/browser does not have internet access.
>
> Yet Google has maintained a very restrictiveTOSthat prohibits
> offline use of the Google Visualization API. I've yet to hear a
> legitimate reason why this remains the case.
>
> The issue of "you get the most up-to-date code" is a non-issue and
> easily dealt with. In fact, in enterprise apps, particularly those in
> regulated industries, constantly changing the code is a huge
> governance risk, so it isn't even desirable.
>
> It would be helpful to know who the executive(s) in charge of both the
> Visualization APITOSand the enterprise customer offerings are, so