You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Dan Becker <da...@gmail.com> on 2008/09/18 21:52:21 UTC
Google license for JavaScript Client Library
A question for the more legal-wise of the developers. I am investigating
Tuscany-2568 (https://issues.apache.org/jira/browse/TUSCANY-2568)
which is to provide a Tuscany JavaScript client model for Atom data.
Luciano and I have discussed the issue a bit, and at this point I am
investigating two possibilities:
1) Grow an Atom Publishing Protocol JavaScript client from scratch
(which is similar to the Abdera Atom model).
2) Use an existing APP JavaScript client model, such as the model that
exists in the Google GData JavaScript client API. Notice that a few of
the Tuscany projects already use the Google GData API, but none that I
have seen have embedded or loaded the GData library from a JavaScript
client.
My question is, if I go down the second route and use the GData model,
does the Apache Open Source licensing coexist peacefully with the terms
of service of the Google Data APIs?
(http://code.google.com/apis/gdata/client-js-terms.html)
If no one knows the answer right off the bat, I will research the answer
myself, but I just wanted to float the question in case anyone had quick
answers or a person to contact.
--
Thanks, Dan Becker
Re: Google license for JavaScript Client Library
Posted by Kevan Miller <ke...@gmail.com>.
On Sep 18, 2008, at 4:23 PM, Luciano Resende wrote:
> We should be asking license related issues in legal-discuss@.
> Also, FYI, see related discussion thread about GData Java apis [1]
No harm in communities discussing licensing issues. Actually, it's
better than that... I'd say it's a good thing...
>
>
>
> [1] http://apache.markmail.org/search/?q=google+services+license+luciano+resende#query
> :google%20services%20license%20luciano%20resende%20list
> %3Aorg.apache.legal-discuss+page:1+mid:jfjntvez6m6cs6mz+state:results
>
> On Thu, Sep 18, 2008 at 12:52 PM, Dan Becker
> <da...@gmail.com> wrote:
>> A question for the more legal-wise of the developers. I am
>> investigating
>> Tuscany-2568 (https://issues.apache.org/jira/browse/TUSCANY-2568)
>> which is
>> to provide a Tuscany JavaScript client model for Atom data.
>>
>> Luciano and I have discussed the issue a bit, and at this point I am
>> investigating two possibilities:
>> 1) Grow an Atom Publishing Protocol JavaScript client from scratch
>> (which is
>> similar to the Abdera Atom model).
>>
>> 2) Use an existing APP JavaScript client model, such as the model
>> that
>> exists in the Google GData JavaScript client API. Notice that a few
>> of the
>> Tuscany projects already use the Google GData API, but none that I
>> have seen
>> have embedded or loaded the GData library from a JavaScript client.
>>
>> My question is, if I go down the second route and use the GData
>> model, does
>> the Apache Open Source licensing coexist peacefully with the terms of
>> service of the Google Data APIs?
>> (http://code.google.com/apis/gdata/client-js-terms.html)
>>
>> If no one knows the answer right off the bat, I will research the
>> answer
>> myself, but I just wanted to float the question in case anyone had
>> quick
>> answers or a person to contact.
First, I think you need to separate the "code" from the "service".
What is the licensing of the javascript code that you want to use? Do
you have a url for the code?
--kevan
Re: Google license for JavaScript Client Library
Posted by Luciano Resende <lu...@gmail.com>.
We should be asking license related issues in legal-discuss@.
Also, FYI, see related discussion thread about GData Java apis [1]
[1] http://apache.markmail.org/search/?q=google+services+license+luciano+resende#query:google%20services%20license%20luciano%20resende%20list%3Aorg.apache.legal-discuss+page:1+mid:jfjntvez6m6cs6mz+state:results
On Thu, Sep 18, 2008 at 12:52 PM, Dan Becker <da...@gmail.com> wrote:
> A question for the more legal-wise of the developers. I am investigating
> Tuscany-2568 (https://issues.apache.org/jira/browse/TUSCANY-2568) which is
> to provide a Tuscany JavaScript client model for Atom data.
>
> Luciano and I have discussed the issue a bit, and at this point I am
> investigating two possibilities:
> 1) Grow an Atom Publishing Protocol JavaScript client from scratch (which is
> similar to the Abdera Atom model).
>
> 2) Use an existing APP JavaScript client model, such as the model that
> exists in the Google GData JavaScript client API. Notice that a few of the
> Tuscany projects already use the Google GData API, but none that I have seen
> have embedded or loaded the GData library from a JavaScript client.
>
> My question is, if I go down the second route and use the GData model, does
> the Apache Open Source licensing coexist peacefully with the terms of
> service of the Google Data APIs?
> (http://code.google.com/apis/gdata/client-js-terms.html)
>
> If no one knows the answer right off the bat, I will research the answer
> myself, but I just wanted to float the question in case anyone had quick
> answers or a person to contact.
> --
> Thanks, Dan Becker
>
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Re: Google license for JavaScript Client Library
Posted by Kevan Miller <ke...@gmail.com>.
On Sep 18, 2008, at 4:53 PM, Dan Becker wrote:
> Kevan Miller wrote:
>> On Sep 18, 2008, at 3:52 PM, Dan Becker wrote:
>>> A question for the more legal-wise of the developers. I am
>>> investigating Tuscany-2568 (https://issues.apache.org/jira/browse/TUSCANY-2568
>>> ) which is to provide a Tuscany JavaScript client model for Atom
>>> data.
>>>
>>> Luciano and I have discussed the issue a bit, and at this point I
>>> am investigating two possibilities:
>>> 1) Grow an Atom Publishing Protocol JavaScript client from scratch
>>> (which is similar to the Abdera Atom model).
>>>
>>> 2) Use an existing APP JavaScript client model, such as the model
>>> that exists in the Google GData JavaScript client API. Notice that
>>> a few of the Tuscany projects already use the Google GData API,
>>> but none that I have seen have embedded or loaded the GData
>>> library from a JavaScript client.
>>>
>>> My question is, if I go down the second route and use the GData
>>> model, does the Apache Open Source licensing coexist peacefully
>>> with the terms of service of the Google Data APIs? (http://code.google.com/apis/gdata/client-js-terms.html
>>> )
>> Hmm. Or is it the "service" that you actually need? I'm not sure
>> what you're trying to do...
>
> I am trying to provide some code for a Tuscany client side
> application. That code would load and use the GData JavaScript code.
K. And would access a Tuscany-based service. Correct? Not the Google
Service? At least not without explicit configuration/modification/ by
an end-user of Tuscany.
So, getting back to my initial question about separating the "code"
from the "service". What is the software license of the JavaScript
code that you want to use? That's not clear to me... The Java-based
Google GData API project is AL v2 (an entirely acceptable license by
Apache standards ;-). Is the Terms of Service the "license" for the
JavaScript code (in particular section 10)? If it is, then IMHO it
would not be acceptable for redistribution by an Apache project...
FYI, you can find information about 3rd party licensing for Apache
projects here -- http://www.apache.org/legal/3party.html
--kevan
Re: Google license for JavaScript Client Library
Posted by Dan Becker <da...@gmail.com>.
Kevan Miller wrote:
>
> On Sep 18, 2008, at 3:52 PM, Dan Becker wrote:
>
>> A question for the more legal-wise of the developers. I am
>> investigating Tuscany-2568
>> (https://issues.apache.org/jira/browse/TUSCANY-2568) which is to
>> provide a Tuscany JavaScript client model for Atom data.
>>
>> Luciano and I have discussed the issue a bit, and at this point I am
>> investigating two possibilities:
>> 1) Grow an Atom Publishing Protocol JavaScript client from scratch
>> (which is similar to the Abdera Atom model).
>>
>> 2) Use an existing APP JavaScript client model, such as the model that
>> exists in the Google GData JavaScript client API. Notice that a few of
>> the Tuscany projects already use the Google GData API, but none that I
>> have seen have embedded or loaded the GData library from a JavaScript
>> client.
>>
>> My question is, if I go down the second route and use the GData model,
>> does the Apache Open Source licensing coexist peacefully with the
>> terms of service of the Google Data APIs?
>> (http://code.google.com/apis/gdata/client-js-terms.html)
>
> Hmm. Or is it the "service" that you actually need? I'm not sure what
> you're trying to do...
I am trying to provide some code for a Tuscany client side application.
That code would load and use the GData JavaScript code.
--
Thanks, Dan Becker
Re: Google license for JavaScript Client Library
Posted by Kevan Miller <ke...@gmail.com>.
On Sep 18, 2008, at 3:52 PM, Dan Becker wrote:
> A question for the more legal-wise of the developers. I am
> investigating Tuscany-2568 (https://issues.apache.org/jira/browse/TUSCANY-2568
> ) which is to provide a Tuscany JavaScript client model for Atom data.
>
> Luciano and I have discussed the issue a bit, and at this point I am
> investigating two possibilities:
> 1) Grow an Atom Publishing Protocol JavaScript client from scratch
> (which is similar to the Abdera Atom model).
>
> 2) Use an existing APP JavaScript client model, such as the model
> that exists in the Google GData JavaScript client API. Notice that a
> few of the Tuscany projects already use the Google GData API, but
> none that I have seen have embedded or loaded the GData library from
> a JavaScript client.
>
> My question is, if I go down the second route and use the GData
> model, does the Apache Open Source licensing coexist peacefully with
> the terms of service of the Google Data APIs? (http://code.google.com/apis/gdata/client-js-terms.html
> )
Hmm. Or is it the "service" that you actually need? I'm not sure what
you're trying to do...
--kevan
Re: Google license for JavaScript Client Library
Posted by Dan Becker <da...@gmail.com>.
After hearing the good points brought up in many replies, I agree that
the Google license is problematic for Tuscany. I am going to pursue the
alternate route which is implementing the framework from scratch. As
mentioned in my original comment on the JIRA, the set of classes is not
overwhelming.
Additionally, from a technical perspective, there were problems using
the Google JavaScript client with non-Google services. It is obvious
that the API is geared toward the Google services. When I pointed the
framework to other Atom feeds I ran into several errors which were not
publicly documented. So the JavaScript client appears to require
specific, non-published info for the services it contacts.
Mike Edwards wrote:
> First the disclaimer: I'm not a legal expert ;-)
>
> However, the terms that Google lay down in the page which you reference
> make me very uncomfortable with the idea of using this code in Tuscany.
>
> It is clear that Google expect their code to be used in conjunction with
> their services - since those services are at the core of the legal
> agreement on that page. In the case of Tuscany, I am sure that the
> intended use of the code is to access *any* service using this client
> side library, which is not what Google have in mind.
>
> Second, the agreement requires *each user* to agree to those license
> terms - and I can't see this meaning anything other than each and every
> user of anything built using Tuscany. This has me heading for the hills
> - it is not in any way reasonable for Tuscany to require this.
>
> There is also this scary requirement:
>
> "You agree that if you use the Client Library to develop a service for
> other users, you will protect the privacy and legal rights of those users."
>
> -- this is squarely in the middle of what Tuscany does. I think Tuscany
> cannot and should not force a term like this onto its users.
>
> As far as I can see, this is not an open source license, so if there are
> any bugs in this library, I don't think you have any rights to go
> messing with the code. Not a good plan for an Apache project.
>
> OK, that's enough. If what I've said doesn't put you off, then you're a
> braver man than I am ;-)
>
>
> Yours, Mike.
>
> PS If you'd like some help building a library from scratch, count me in.
>
> Dan Becker wrote:
>> A question for the more legal-wise of the developers. I am
>> investigating Tuscany-2568
>> (https://issues.apache.org/jira/browse/TUSCANY-2568) which is to
>> provide a Tuscany JavaScript client model for Atom data.
>>
>> Luciano and I have discussed the issue a bit, and at this point I am
>> investigating two possibilities:
>> 1) Grow an Atom Publishing Protocol JavaScript client from scratch
>> (which is similar to the Abdera Atom model).
>>
>> 2) Use an existing APP JavaScript client model, such as the model that
>> exists in the Google GData JavaScript client API. Notice that a few of
>> the Tuscany projects already use the Google GData API, but none that I
>> have seen have embedded or loaded the GData library from a JavaScript
>> client.
>>
>> My question is, if I go down the second route and use the GData model,
>> does the Apache Open Source licensing coexist peacefully with the
>> terms of service of the Google Data APIs?
>> (http://code.google.com/apis/gdata/client-js-terms.html)
>>
>> If no one knows the answer right off the bat, I will research the
>> answer myself, but I just wanted to float the question in case anyone
>> had quick answers or a person to contact.
>
>
--
Thanks, Dan Becker
Re: Google license for JavaScript Client Library
Posted by Kevan Miller <ke...@gmail.com>.
On Sep 19, 2008, at 5:10 PM, Dan Becker wrote:
> Very intriguing idea. I definitely would like to solve this in the
> short term to help with the Tuscany JIRA (2568), but long term I see
> the appeal of this to a wider audience.
Speaking as a relative newcomer -- seems like you should definitely be
talking to the Abdera community about this...
--kevan
Re: Google license for JavaScript Client Library
Posted by Dan Becker <da...@gmail.com>.
Very intriguing idea. I definitely would like to solve this in the short
term to help with the Tuscany JIRA (2568), but long term I see the
appeal of this to a wider audience.
Paul Fremantle wrote:
> I'm sure some others will help if you want to start an AtomPub JS
> library at Apache. We could start it in Apache Labs or we could kick
> it off in the Abdera. I think from a committer situation it might make
> more sense to do it in Labs and then move it over to Abdera, just
> because the participants might not have the right karma in Abdera.
>
> Thoughts?
>
> Paul
>
> On Fri, Sep 19, 2008 at 9:38 AM, Mike Edwards
> <mi...@gmail.com> wrote:
>> Dan,
>>
>> First the disclaimer: I'm not a legal expert ;-)
>>
>> However, the terms that Google lay down in the page which you reference make
>> me very uncomfortable with the idea of using this code in Tuscany.
>>
>> It is clear that Google expect their code to be used in conjunction with
>> their services - since those services are at the core of the legal agreement
>> on that page. In the case of Tuscany, I am sure that the intended use of
>> the code is to access *any* service using this client side library, which is
>> not what Google have in mind.
>>
>> Second, the agreement requires *each user* to agree to those license terms -
>> and I can't see this meaning anything other than each and every user of
>> anything built using Tuscany. This has me heading for the hills - it is not
>> in any way reasonable for Tuscany to require this.
>>
>> There is also this scary requirement:
>>
>> "You agree that if you use the Client Library to develop a service for other
>> users, you will protect the privacy and legal rights of those users."
>>
>> -- this is squarely in the middle of what Tuscany does. I think Tuscany
>> cannot and should not force a term like this onto its users.
>>
>> As far as I can see, this is not an open source license, so if there are any
>> bugs in this library, I don't think you have any rights to go messing with
>> the code. Not a good plan for an Apache project.
>>
>> OK, that's enough. If what I've said doesn't put you off, then you're a
>> braver man than I am ;-)
>>
>>
>> Yours, Mike.
>>
>> PS If you'd like some help building a library from scratch, count me in.
>>
>> Dan Becker wrote:
>>> A question for the more legal-wise of the developers. I am investigating
>>> Tuscany-2568 (https://issues.apache.org/jira/browse/TUSCANY-2568) which is
>>> to provide a Tuscany JavaScript client model for Atom data.
>>>
>>> Luciano and I have discussed the issue a bit, and at this point I am
>>> investigating two possibilities:
>>> 1) Grow an Atom Publishing Protocol JavaScript client from scratch (which
>>> is similar to the Abdera Atom model).
>>>
>>> 2) Use an existing APP JavaScript client model, such as the model that
>>> exists in the Google GData JavaScript client API. Notice that a few of the
>>> Tuscany projects already use the Google GData API, but none that I have seen
>>> have embedded or loaded the GData library from a JavaScript client.
>>>
>>> My question is, if I go down the second route and use the GData model,
>>> does the Apache Open Source licensing coexist peacefully with the terms of
>>> service of the Google Data APIs?
>>> (http://code.google.com/apis/gdata/client-js-terms.html)
>>>
>>> If no one knows the answer right off the bat, I will research the answer
>>> myself, but I just wanted to float the question in case anyone had quick
>>> answers or a person to contact.
>>
>
>
>
--
Thanks, Dan Becker
Re: Google license for JavaScript Client Library
Posted by Paul Fremantle <pz...@gmail.com>.
I'm sure some others will help if you want to start an AtomPub JS
library at Apache. We could start it in Apache Labs or we could kick
it off in the Abdera. I think from a committer situation it might make
more sense to do it in Labs and then move it over to Abdera, just
because the participants might not have the right karma in Abdera.
Thoughts?
Paul
On Fri, Sep 19, 2008 at 9:38 AM, Mike Edwards
<mi...@gmail.com> wrote:
> Dan,
>
> First the disclaimer: I'm not a legal expert ;-)
>
> However, the terms that Google lay down in the page which you reference make
> me very uncomfortable with the idea of using this code in Tuscany.
>
> It is clear that Google expect their code to be used in conjunction with
> their services - since those services are at the core of the legal agreement
> on that page. In the case of Tuscany, I am sure that the intended use of
> the code is to access *any* service using this client side library, which is
> not what Google have in mind.
>
> Second, the agreement requires *each user* to agree to those license terms -
> and I can't see this meaning anything other than each and every user of
> anything built using Tuscany. This has me heading for the hills - it is not
> in any way reasonable for Tuscany to require this.
>
> There is also this scary requirement:
>
> "You agree that if you use the Client Library to develop a service for other
> users, you will protect the privacy and legal rights of those users."
>
> -- this is squarely in the middle of what Tuscany does. I think Tuscany
> cannot and should not force a term like this onto its users.
>
> As far as I can see, this is not an open source license, so if there are any
> bugs in this library, I don't think you have any rights to go messing with
> the code. Not a good plan for an Apache project.
>
> OK, that's enough. If what I've said doesn't put you off, then you're a
> braver man than I am ;-)
>
>
> Yours, Mike.
>
> PS If you'd like some help building a library from scratch, count me in.
>
> Dan Becker wrote:
>>
>> A question for the more legal-wise of the developers. I am investigating
>> Tuscany-2568 (https://issues.apache.org/jira/browse/TUSCANY-2568) which is
>> to provide a Tuscany JavaScript client model for Atom data.
>>
>> Luciano and I have discussed the issue a bit, and at this point I am
>> investigating two possibilities:
>> 1) Grow an Atom Publishing Protocol JavaScript client from scratch (which
>> is similar to the Abdera Atom model).
>>
>> 2) Use an existing APP JavaScript client model, such as the model that
>> exists in the Google GData JavaScript client API. Notice that a few of the
>> Tuscany projects already use the Google GData API, but none that I have seen
>> have embedded or loaded the GData library from a JavaScript client.
>>
>> My question is, if I go down the second route and use the GData model,
>> does the Apache Open Source licensing coexist peacefully with the terms of
>> service of the Google Data APIs?
>> (http://code.google.com/apis/gdata/client-js-terms.html)
>>
>> If no one knows the answer right off the bat, I will research the answer
>> myself, but I just wanted to float the question in case anyone had quick
>> answers or a person to contact.
>
>
--
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
Re: Google license for JavaScript Client Library
Posted by Mike Edwards <mi...@gmail.com>.
Dan,
First the disclaimer: I'm not a legal expert ;-)
However, the terms that Google lay down in the page which you reference make me very uncomfortable
with the idea of using this code in Tuscany.
It is clear that Google expect their code to be used in conjunction with their services - since
those services are at the core of the legal agreement on that page. In the case of Tuscany, I am
sure that the intended use of the code is to access *any* service using this client side library,
which is not what Google have in mind.
Second, the agreement requires *each user* to agree to those license terms - and I can't see this
meaning anything other than each and every user of anything built using Tuscany. This has me
heading for the hills - it is not in any way reasonable for Tuscany to require this.
There is also this scary requirement:
"You agree that if you use the Client Library to develop a service for other users, you will protect
the privacy and legal rights of those users."
-- this is squarely in the middle of what Tuscany does. I think Tuscany cannot and should not force
a term like this onto its users.
As far as I can see, this is not an open source license, so if there are any bugs in this library, I
don't think you have any rights to go messing with the code. Not a good plan for an Apache project.
OK, that's enough. If what I've said doesn't put you off, then you're a braver man than I am ;-)
Yours, Mike.
PS If you'd like some help building a library from scratch, count me in.
Dan Becker wrote:
> A question for the more legal-wise of the developers. I am investigating
> Tuscany-2568 (https://issues.apache.org/jira/browse/TUSCANY-2568) which
> is to provide a Tuscany JavaScript client model for Atom data.
>
> Luciano and I have discussed the issue a bit, and at this point I am
> investigating two possibilities:
> 1) Grow an Atom Publishing Protocol JavaScript client from scratch
> (which is similar to the Abdera Atom model).
>
> 2) Use an existing APP JavaScript client model, such as the model that
> exists in the Google GData JavaScript client API. Notice that a few of
> the Tuscany projects already use the Google GData API, but none that I
> have seen have embedded or loaded the GData library from a JavaScript
> client.
>
> My question is, if I go down the second route and use the GData model,
> does the Apache Open Source licensing coexist peacefully with the terms
> of service of the Google Data APIs?
> (http://code.google.com/apis/gdata/client-js-terms.html)
>
> If no one knows the answer right off the bat, I will research the answer
> myself, but I just wanted to float the question in case anyone had quick
> answers or a person to contact.