Frank Siebenlist writes:
> There is one more important difference between EPL and GPL/LGPL that
> we should be aware off:
>
> You cannot copy snippets out of Philip's LGPL'ed code and use them in
> your own EPL'ed code.
This is a true and is, indeed, a risk. Most of the code in tawny is not
that
Michael Klishin writes:
> 2013/2/6 Phillip Lord
>
>> You mean "what is the name of this library as maven artifact"? Rather
>> than it's dependencies.
>
> Are you sure people will find it there if it's not in the README? The
> thinking "if I can't even get started with it, why do I need to see
>
There is one more important difference between EPL and GPL/LGPL that we should
be aware off:
You cannot copy snippets out of Philip's LGPL'ed code and use them in your own
EPL'ed code.
For me, one of the great benefits of all the EPL'ed clojure libraries out there
is, that I've freely borrowed
2013/2/6 Phillip Lord
> You mean "what is the name of this library as maven artifact"? Rather
> than it's dependencies.
>
Yes.
>
> I've added this to the documentation; this needs expanding anyway,
> because its poor at the moment.
>
Are you sure people will find it there if it's not in the R
John Gabriele writes:
> LGPL just means that the library itself is copyleft (if you make changes to
> it, and distribute the modified library, you've got to distribute your
> changes along with it (under the same conditions) as well).
>
> Issues of license compatibility generally only come up wh
This should be fine. Both EPL and LGPL are weak copyleft. Clojure code
does not need to be EPL because EPL does not force it. Likewise, Clojure
can call back to this LGPL library because, the LGPL doesn't enforce
derivative works as a whole to be LGPL (although modifications to the
tawny *would* h
On 6 February 2013 05:52, John Gabriele wrote:
> On Tuesday, February 5, 2013 12:08:43 PM UTC-5, AtKaaZ wrote:
>
>> you can release that on LGPL License ?
>> does that work with the EPL of clojure ? or is it only an issue when lein
>> uberjar-ed ?
>>
>
> LGPL just means that the library itself is
Michael Klishin writes:
> 2013/2/5 Phillip Lord
>
>> Although, it's been available for a while, this is the first release
>> that I have announced here. I'd welcome feedback.
>>
>
> Phillip,
>
> Please add dependency (artifacts) information to the README.
> Otherwise beginners won't be able to u
Thank you.
On Wed, Feb 6, 2013 at 4:52 AM, John Gabriele wrote:
> On Tuesday, February 5, 2013 12:08:43 PM UTC-5, AtKaaZ wrote:
>
>> you can release that on LGPL License ?
>> does that work with the EPL of clojure ? or is it only an issue when lein
>> uberjar-ed ?
>>
>>
> LGPL just means that t
On Tuesday, February 5, 2013 12:08:43 PM UTC-5, AtKaaZ wrote:
> you can release that on LGPL License ?
> does that work with the EPL of clojure ? or is it only an issue when lein
> uberjar-ed ?
>
>
LGPL just means that the library itself is copyleft (if you make changes to
it, and distribute t
you can release that on LGPL License ?
does that work with the EPL of clojure ? or is it only an issue when lein
uberjar-ed ?
On Tue, Feb 5, 2013 at 5:57 PM, Phillip Lord
wrote:
>
>
> Tawny-OWL is a clojure library which provides a DSL for the construction
> of OWL Ontologies (http://www.w3.org
2013/2/5 Phillip Lord
> Although, it's been available for a while, this is the first release
> that I have announced here. I'd welcome feedback.
>
Phillip,
Please add dependency (artifacts) information to the README.
Otherwise beginners won't be able to use your project.
Thank you.
--
MK
htt
Tawny-OWL is a clojure library which provides a DSL for the construction
of OWL Ontologies (http://www.w3.org/2004/OWL/). The practical upshot of
this, is that allows a form of logic reasoning over sets of facts about
the world, with strong computational guarantees about decidability.
At it's si
13 matches
Mail list logo
