Hello Martin
Thank you for giving this issue to your Legal team. I see they have made
determinations on many different licences. We could be on the right road
now to getting it resolved one way or the other. It is better that we
get it legally correct before going further.
Kind regards
Rob
On 30/05/2017 18:45, Martin Desruisseaux wrote:
Hello Rob
Thanks for spotting this licensing issue. Yes, Apache has a legal
division. I just created a ticket asking the question:
https://issues.apache.org/jira/browse/LEGAL-311
Alternatively I know the original author of ACDD specification.
Depending on the answer we will get from the legal team, I could send an
email to him asking if he would suggest an approach.
Martin
Le 30/05/2017 à 18:51, Rob Wallace a écrit :
Hello Martin
Thank you for your reply drawing attention to copyright issues, and I
agree with your comments.
I see the ACDD page we use states at the end: "Content is available
under GNU Free Documentation License 1.2
<http://www.gnu.org/copyleft/fdl.html>."
So it seems we must try to re-word everything to not be a copy or,
copy and follow the licence and acknowledge and reproduce it etc. It
would good if we could get a specific release somehow from these
obligations, as all we are trying to do is to implement the very ideas
that have been specified in ACDD. However, the licence does legally
cover their material because they have specified that it does.
In the preamble of the Javadoc we do refer to the ACDD. We could also
add something more specific about the licence that may satisfy it, but
it does get complicated. I have no experience of having to honour a
GNU Free Documentation Licence with material embedded within
modifications. The solution may even be a simple one solved by an
introductory statement of acknowledgement in the licence's terms.
Does Apache have some legal division who could advise us as to best
practice in the circumstances? Other users of such licensed standards
must have come across this and similar problems as well.
Kind regards
Rob
