On 27/03/13 09:19, Sergio Fernández wrote:
Attached the current dependencies; I can't see json.org either.
(using json.org as an example)
json.org is often included as included source - it's small, the official
distribution is source code and any central maven artifact has been
second-class - the most currently looking one seems to be 3rd party
generated. This is a reason why NOTICE is so important.
There is a clash of cultures, between informal and formal views of open
source.
Where each component of some other system all falls under one overall
license, then the whole license applies. If you dig into the bits you
use you can discover there are recursive dependencies you don't inherit.
But while the overall license/notice names a system, the check is
going to have to be every version.
With java (JVM languages) that's easier to check but just packaging
isn't enough. Copied in source code is often repackaged so as to avoid
clashes with other uses from libraries e.g. com.sun.org.apache.xerces
(and quite a lot of other things) in the Java runtime.
Andy
Kudos to Bertrand Delacrétaz for the trick: http://goo.gl/8NJ90
On 27/03/13 10:15, Sebastian Schaffert wrote:
Hi Peter,
funny, we don't have any dependency to the json.org module left in
Marmotta. Where is Sesame actually using it? The SPARQL JSON writer seems
to write directly to the output stream.
Maybe the beta2 does not yet include this code anyways? If you have a new
release with more SPARQL JSON support, we would be very happy, because
then
we can throw away our own code :)
:-)
2013/3/27 Peter Ansell<ansell.pe...@gmail.com>
On 26 March 2013 23:04, Andy Seaborne<a...@apache.org> wrote:
On 26/03/13 12:47, Sergio Fernández wrote:
Hi,
On 26/03/13 12:33, Andy Seaborne wrote:
On 25/03/13 16:50, Sergio Fernández wrote:
On 25/03/13 17:02, Andy Seaborne wrote:
The license for json.org has the linethat makes it in contradiction
with the definition of open source:
This is no longer an issue, since we managed to rewrite some code
and
completely removed such dependency (commit
bdb25fedcbb38c311ffb4f08e84505163109718d) with other with better
licensing and performance.
I would point out that by shipping any system, you take on the
responsibilities from the license of that system system, not the part
you happen to use.
Sure. In this case the system is Jackson, which was already in use in
Marmotta: I've just replaced the single usage of json.org by the
equivalent in Jackson.
Thanks for the remark; we really appreciate your toil as mentors :-)
In this case, having any system like Sesame mention in their NOTICE
file,
recursively brings it in. json.org is particular fiddly as so many
systems
include it by source (and forget to be explicit about it).
I have it on my todo list to replace org.json with Jackson in Sesame.
I wrote a Talis RDF/JSON parser and writer using Jackson the other day
and it works famously, so it should be fairly simple to convert the
Sesame Workbench and the SPARQL Results JSON module when I have time.
Cheers,
Peter
