-- Federico Cargnelutti <[EMAIL PROTECTED]> wrote (on Thursday, 08 May 2008, 11:33 AM +0100): > Hi Till, I think you've just made my point, we should try to reduce > assumptions > as much as possible. > > What you said about the API key forcing the user to accept the terms > and conditions sounds great, but it's not always like that. That's why > I mentioned Audioscrobbler.
We provide the tool for accessing the content, but it is up to the individual developer to make sure that they are in compliance with the service's terms of use. Many services do this via an API key, as Till indicates. For those that don't, it's up to the developer to read and understand the terms of service. In all service consumables, we link to the service provider, so that the developer can do so -- you can see this clearly in the first paragraph describing Zend_Service_AudioScrobbler. > On Thu, May 8, 2008 at 10:00 AM, till <[EMAIL PROTECTED]> wrote: > > On Thu, May 8, 2008 at 10:55 AM, Federico Cargnelutti > <[EMAIL PROTECTED]> wrote: > > (...) A user might assume that Zend has some kind (...) > > And that's exactly it. An assumption. > > Many web services forbid commercial usage with the regular API keys > (Flickr, Google Maps, ...). In any way, what you do with the Zend > Framework code is your responsibility, you can't expect warning flags > all over. Those warning flags are at the website when you sign up for > an API key (Terms of Service are usually there for a reason). -- Matthew Weier O'Phinney Software Architect | [EMAIL PROTECTED] Zend - The PHP Company | http://www.zend.com/
