It occurs to me that one way the app could be made compliant would be to first write a local HTML page dynamically, containing the customized link to Google. Then that page could be displayed in the embedded browser and the user could click interactively to execute the link. That would be no different than clicking on any embedded link in any other browser.
I don't know if the app actually works that way, and I don't have a copy to test with. However, if the app's front-end is driving the HTTP call directly, I think that could be construed as "automated means" in violation of Section 5.3 of Google's Universal Terms. On Nov 24, 9:40 am, boomerbubba <[EMAIL PROTECTED]> wrote: > My conceri is the "automated means" of constructing the URL to drive > the HTTP request. That same HTTP interface is used by spiders, etc., > and they clearly would be outside the terms of Section 5.3 (I have > previously considered and rejected the idea of building such a wrapper > interface myself around an embedded browser, because I thought it was > coloring outside the lines.) > > And BTW, if this is relevant, the application I saw is not free of > charge. However, the restriction about being generally available > without charge applies in the terms of the API, and the API is not > being used here. > > On Nov 24, 9:13 am, "warden [Andrew Leach - Maps API Guru]" > > > > <[EMAIL PROTECTED]> wrote: > > On Nov 24, 2:56 pm, boomerbubba <[EMAIL PROTECTED]> wrote: > > > > I have always taken that provison to prohibit batch scripts, scraping > > > scripts, etc. Does it also prohibit the interactive use described > > > above? If not, is there any other provision in the Google Maps terms > > > that prohibit it? > > > I don't believe so: presumably the URL could just as easily be reached > > without using the application which constructs it -- the "interface" > > is the HTTP request to the external site and the Javascript API. As > > such, the map is generally accessible without charge (or whatever the > > current wording is) and it doesn't fall foul of Section 10 of the Maps > > Terms. The only issue is whether the browser object can cope with the > > Javascript necessary for the map. > > > If an automatic creation of a map URL is prohibited, it also bars a > > web application from constructing a URL to show in an iframe -- the > > local app is essentially doing the same thing, and local applications > > are now allowed. > > > Andrew > > beginning to despair at the complexity of interacting Terms of Service- > > Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
