I can't definitely answer this.
You don't include any source code from Sesame?
1/ Where you link to it, via maven dependencies, no problem.
2/ Where you bundle and ship it, you have redistribution responsibilities.
That said, it clearly says "Source code contributions" and reads to me
like an acknowledgement list rather than a strict NOTICE requirement.
There is nothing in LICENSE so do we presume those contributions are
BSD-ish?
Sesame also has an assignment system - if those contributions are under
that, then there was no need to include in NOTICE.txt.
Let's hope someone else has been here before.
Andy
FYI - no action needed -
But it gets messy:
"""
Parts of this product use software developed by JSON.org
(http://www.json.org/). License: http://www.json.org/license.html
"""
and we get into *much* controversy.
Good news is that this has be clarified for Apache:
http://www.apache.org/legal/resolved.html#json
The license for json.org has the line:
"""The Software shall be used for Good, not Evil."""
that makes it in contradiction with the definition of open source:
http://opensource.org/docs/osd
Item 6. "No Discrimination Against Fields of Endeavor"
unless you get an exemption
http://java.dzone.com/articles/jsonorg-license-literally-says
https://news.ycombinator.com/item?id=3693108
(This is why Jena does not use json.org - easier to replace that dela
with it. The fact we have a simpler faster parser is no bad thing
either but the real reason was the rewrite was much less work than the
legal side. It uses the fast I/O but otherwise is independent of the
rest of Jena.)
Andy
On 25/03/13 15:02, Sebastian Schaffert wrote:
Hi Andy, and other mentors,
while trying to figure out what should go into the NOTICE file and what
not, we realised that the Apache license says that derivative works need to
contain a copy of the NOTICE of included project. So in case of our binary
releases that include the Sesame libraries, this would mean we need to
include the contents of the following file:
https://bitbucket.org/openrdf/sesame/src/master/core/NOTICE.txt
What we are not sure about is whether it would be ok to only mention Sesame
as we do now, or whether we need to include all the NOTICE content of the
dependency. What is your opinion on this?
For reference, the Apache license says:
4d)
If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
2013/3/25 Andy Seaborne <a...@apache.org>
On 25/03/13 12:03, Sebastian Schaffert wrote:
restart
the release candidate
Sebastian,
As Release Manager, could you send a [CANCELLED] message on this thread so
that when looking back, the list archive makes it clear as to status?
Andy
