On 6/4/08, Mike Edwards <[EMAIL PROTECTED]> wrote: > Luciano, > > Yes, I'm no lawyer either. > > It just brought me up short to find that the code itself is licensed under > Apache license, but then > there is this other pile of legal stuff which applies to any *use* of the > code. What purpose does > the code have other than to be used??? So I want to make sure that we have > thought through what > this means - I don't want to see Tuscany in general being subjected to any > kinds of legal > limitations just because we decided to include some Google code in our SVN.
Copyright licenses pertain to copying (and performing). Patents pertain to use. Software is a little odd since a copy of the program must be created before it can be used. > I don't know whether we need to ask the wider Apache community about this - > does anyone have the > necessary legal experience to offer advice? I recommend posting this question to the legal-discuss list Robert > > > Yours, Mike. > > Luciano Resende wrote: >> Let me start with a DISCLAIMER that I'm not a lawyer, so all that I'm >> going to say here is my own understanding. >> >> I think that the link you sent, is more towards the usage of google >> services (e.g blogger, calendar, etc)... and GData Java Client API >> would be the Apache Licensed code that could be used to >> programatically access these services. Having said that, I'd compare >> this to using an apache licensed api to access some kind of >> proprietary services from Amazon or any other company. >> >> Based on that, I think the usage of the api should be fine, but >> connecting to actual google services would require a google account >> and also that the user has accepted those license terms. >> >> Well, this is just how I understood. Any other Thoughts ? >> >> On Tue, Jun 3, 2008 at 12:26 AM, Mike Edwards >> <[EMAIL PROTECTED]> wrote: >>> Luciano Resende wrote: >>>> Hey Mike >>>> >>>> What are your concerns with regards to license ? Looking at [1], it >>>> looks like the GData Java Client is Apache License 2. >>>> >>>> [1] http://code.google.com/p/gdata-java-client/ >>>> >>>> On Mon, Jun 2, 2008 at 10:01 PM, Mike Edwards >>>> <[EMAIL PROTECTED]> wrote: >>>>> Douglas Leite wrote: >>>>>> After analyzing the Google Data API and the code of binding-atom, >>>>>> binding-atom-abdera, and binding-feed, I propose an approach to start >>>>>> the >>>>>> development of the GData biding. >>>>>> >>>>>> I propose creating a new type of binding: biding-gdata. Similarly as >>>>>> binding-atom-abdera, that extends the binding-atom, this new kind of >>>>>> binding >>>>>> would extend the binding-atom too. >>>>>> >>>>>> The implementation of the invokers (linke GetInvoker, PostInvoker, and >>>>>> PutInvoker) would be done using the GData Java Client, that provides >>>>>> tools >>>>>> and an abstract layer, abstracting the necessity of handling with HTTP >>>>>> requests/responses and XML's processing. >>>>>> >>>>>> The binding-gdata could extend the binding-rss aiming to allow RSS >>>>>> feeds. >>>>>> >>>>>> This approach looks like the binding-feed, but reusing the >>>>>> binding-atom >>>>>> and >>>>>> binding-rss, and using the GData Java Client to implement the >>>>>> invokers. >>>>>> >>>>>> What do you think about? >>>>>> >>>>> Douglas, >>>>> >>>>> We need to take some care over the idea of using the GData Java Client >>>>> - >>>>> we >>>>> need to check out the legal terms that apply to the client code, since >>>>> it >>>>> does not appear to have a license that is compatible with the Apache >>>>> open >>>>> source license, as far as I can tell. >>>>> >>>>> I'm not saying that you can't use the Google code, but we do need to >>>>> ask >>>>> to >>>>> see what the right way would be to use this code. >>>>> >>>>> >>>>> Yours, Mike. >>>>> >>>> >>>> >>> Luciano, >>> >>> What about this page, linked off the one above: >>> >>> http://code.google.com/tos.html >>> >>> Yours, Mike. >>> >> >> >> > >
