[Mulgara-dev] License Question.
Ian Boston
ian at caret.cam.ac.uk
Tue Oct 24 19:45:16 UTC 2006
Paul,
Thank you.
All is clear
Ian
Paul Gearon wrote:
> On 10/23/06, *Andrae Muys* <andrae at netymon.com
> <mailto:andrae at netymon.com>> wrote:
>
>
> On 24/10/2006, at 11:44 AM, Life is hard, and then you die wrote:
>
> > On Tue, Oct 24, 2006 at 10:59:55AM +1000, Andrae Muys wrote:
> >> It is certainly our intent and belief that as long as you use the
> >> designated public API's (currently those are the Session API, the
> >> Resolver SPI, and the Security SPI) you can use Mulgara in any
> >> project you like.
> >>
> >> My understanding of the license is that:
> >> Any changes you make to Mulgara are naturally affected.
> >> Any changes that make use of internal API's would make your
> >> application a derivative work and therefore trigger 1c.
> >
> > Ouch! If that's the case, then please list out _exactly_ which
> > methods, which fields, and which classes are considered public.
> > Otherwise it's a legal crap shoot for us users.
> >
> > E.g. the ItqlIterpreter and ItqlIterpreterBean - are the methods in
> > those public or not? (they don't seem to fall unser those three
> API's
> > you mention).
>
> They are one of the client-side interfaces to the Session API.
> Anything that works (or would work) over RMI is definitely a public
> interface. You are right though, we should spend some time
> documenting the interfaces to Mulgara better than they are.
>
>
> ItqlInterpreter and ItqlInterpreterBean (a wrapper on ItqlInterpreter)
> are the accepted mechanisms for a client to connect to a server
> instance. Everything else that you're importing are really just the
> supporting types for communication with those classes.
>
> If you have any concerns about a part of the code that you believe is
> server-side only, but you require it for a client, then please let us
> know. We want as many people as possible to be using the system. By
> all means, write a closed source client program that talks to the server
> (I think everyone agrees on this point). The more people using RDF the
> better.
>
> The only thing we don't want is for people to expand on the
> functionality of Mulgara without providing the source code for what they
> did. We are building something within the community, and we'd like to
> see others contribute to that.
>
> Regards,
> Paul
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Mulgara-dev mailing list
> Mulgara-dev at mulgara.org
> http://mulgara.org/mailman/listinfo/mulgara-dev
More information about the Mulgara-dev
mailing list