FWIW, after several years dealing w. Lawyers and vendors on the commercial side of the MapQuest Developer products, where there may be restrictive terms that have to be passed on to the user (dev or consumer) that conflict with broader functionality intended to be independent from the restrictive content exposed by default...I managed to get four different lawyers to agree with the following statement:
One is legally required to legally constrain, but one is not legally required to technically constrain. In other words, i can give you a map API that has a removeCopyright function call, as long as in my terms i tell you you can't use if you are displaying OSM data. I'm sure you can easily find 4 lawyers that won't agree...but I think thats the point of being a lawyer? Ant Sent from my iPad On May 5, 2011, at 2:44 PM, Frederik Ramm <[email protected]> wrote: > Hi, > > NopMap wrote: >> I tried Locus on my phone and traced the accesses in the server log. I >> positively is the culprit. >> Needless to say that the program contains no proper attribution and no >> license hint whatsoever. :-( > > From reading their forums, I get the impression that they had initially > hard-coded a number of tile providers, and then dropped these in favour of a > "user configurable" tile URL in order to avoid trouble with Google et al. > > Leaving morality aside for a moment, I wonder what the attribution > requirement actually is in that situation. Say you make an Android app that > has no built-in tile sources but if you enter an URL in some text box it will > try to load tiles from there. > > Does CC-BY-SA require that the application programmer somehow cleverly finds > out that the user has entered the OSM tile server, that this tile server > serves CC-BY-SA tiles, and that the attribution is so-and-so? Probably not, > which means that as long as you don't explicitly support OSM you don't need > attribution, right? > > Bye > Frederik > > -- > Frederik Ramm ## eMail [email protected] ## N49°00'09" E008°23'33" > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/dev _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
