On 4/14/2011 11:24 PM, Maps.Huge.Info (Maps API Guru) wrote: > As for terms documents, everything we need to know is in the > document. If you need to have more information or clarification, the > answer is always the same: consult a lawyer. I believe both are > appropriate although the terms documents can be somewhat cryptic and > even conflicting.
If we consulted 4 lawyers on the term documents, I bet we would end up with 8-10 interpretations, with a lot of caveats and a huge bill at the end. The fundamental problem is that, for all intents and purposes, it's NOT interpreting the terms from the perspective of a lawyer that is relevant. I'm not going to sue Google even if they do violate any of these terms, and they're not going to sue me if they consider me to have violated them (they'll just kick my app(s) out of the store). What I want to know is what they intend (or don't intend) for applications to do in the store. In plain English. And in more detail than what's in the terms. I want clear guidance on some of the more subtle points. I've seen long debates, held between smart people, that pretty much prove that portions of the terms are too vague. SOMEONE inside Google knows what they were intending to say, or should know that. That's the person I'd like to be talking to -- the person that says, if you do X in your app, that's OK, but if you do Y, that's a problem. Tim -- You received this message because you are subscribed to the Google Groups "Android Discuss" 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/android-discuss?hl=en.
