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

Reply via email to