Nobody is suggesting it's bad, just that it's not necessary and isn't the framework's or Zend's responsibility. All code in the framework merely facilitates an interface to these web services which in no way falls under those web services' terms of use, licensing or copyrighting. The usage of a developer may, but its then their responsibility alone to ensure they meet the requirement of the service in question and that will always involve reading the terms of use and any attached licensing of data.
I don't see what the problem there is... Pádraic Brady http://blog.astrumfutura.com http://www.patternsforphp.com OpenID Europe Foundation Member-Subscriber ----- Original Message ---- From: Federico Cargnelutti <[EMAIL PROTECTED]> To: Bryan Dunlap <[EMAIL PROTECTED]> Cc: fw-general@lists.zend.com Sent: Thursday, May 8, 2008 11:14:55 PM Subject: Re: [fw-general] Web services & licensing issue > Again, it's not ZFs responsibility to spell out license restrictions > that may or may not exist for a given service that it provides a client > for. You make it sound like providing extra and valuable information is a bad thing. I think the more information you provide to the user, the better. At the end of the day, that's what the docblock is for right? On Thu, May 8, 2008 at 8:54 PM, Bryan Dunlap <[EMAIL PROTECTED]> wrote: -------- Original Message -------- Subject: Re: [fw-general] Web services & licensing issue From: "Greg Donald" <[EMAIL PROTECTED]> Date: Thu, May 08, 2008 9:00 am To: fw-general@lists.zend.com On 5/8/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> Personally, I've never been in a position where I didn't check T&C >> and/or license agreement of a service that I was consuming. I've never >> simply "assumed" that I could use at will. <tangent> >Do you also query the webmasters of all publicly available web pages >you encounter before allowing your browser to render them? >A webservice is just a fancy buzzword for "we wrap our content in XML >for your convenience". If it's not supposed to be public then it >should require authentication. </tangent> >-- >Greg Donald >http://destiney.com/ Again, it's not ZFs responsibility to spell out license restrictions that may or may not exist for a given service that it provides a client for. I think providing URLs in the manual and/or the component's docblock is more than enough, and should be considered a convenience for the developer.
