> There is still great ambiguity regarding logins to sites using the > maps API.
They must, I hope, allow some things to change when people log in. For example, you will probably want to only allow people to edit their own data, like Google's My Maps does. You might also want to allow people to keep some data private, such as incompleted and unpublished routes, etc. And the Estate Agent example suggests that you can restrict some features of your API application, such as editing points, to logged-in people who aren't general public. The other issue is of whether the rules govern the API (the slippy maps and controls) or the API plus all data displayed using it. I have a site where the general public can see the maps for free, along with some useful additional data. Members of an organisation can log in and see more detail about the same data. I consider that to be fair, as the Maps API, and the basic data, is "generally accessible to users without charge". There is additional data displayed for some users, who belong to the organisation, but they haven't paid anything to access the additional data, seeing it is a very minor additional benefit of their organisational membership. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
