On Sep 18, 2008, at 4:23 PM, Luciano Resende wrote:
We should be asking license related issues in [EMAIL PROTECTED]
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
<[EMAIL PROTECTED]> 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
