I actually did mean WITH, but may have been clumsy with my selection of
terms. Using OR is basically saying that the content is dual-licensed which
is not the intent (please correct me if my understanding is wrong).
My understanding (based on section 3.2a of the license) is that the intent
with th
On Thu, Aug 17, 2017 at 04:22:51PM -0700, Gary wrote:
> > > > Will that be:
> > > >
> > > > a. GPL-2.0-only OR GPL-3.0-only
> > >
> > > The "ONLY" would be an operator, so I'd expect to see: (GPL-2.0
> > > ONLY OR GPL-3.0 ONLY)
> >
> > That's certainly possible as well, and it would be easier to pa
I think there's something a little odd about the EPL 2.0 opt-in GPL
compatibility feature I hadn't paid attention to before (despite having
reviewed the license closely during its drafting and the OSI approval process).
The way the opt-in GPL compatibility works, the initial licensor of 'the
P
On Tue, Aug 22, 2017 at 2:52 AM, Wayne Beaton
wrote:
> The EPL-2.0 has been approved by the OSI and the Eclipse Board of Directors.
[...]
> The wrinkle, I think, is that there is a provision in the license for
> "secondary license" support. A project team may opt to declare that their
> project co
Kate Stewart:
> Possibly you're using WITH (which is restricted to only refer to exceptions
> when you mean to use AND??
> Does the following look like what you're trying to represent?
> EPL-2.0
> EPL-2.0 AND GPL-2.0
> EPL-2.0 AND (GPL-2.0 with Classpath-exception-2.0)
Those are *syntactically* f
Hi Wayne,
Possibly you're using WITH (which is restricted to only refer to exceptions
when you mean to use AND??
Does the following look like what you're trying to represent?
EPL-2.0
EPL-2.0 AND GPL-2.0
EPL-2.0 AND (GPL-2.0 with Classpath-exception-2.0)
EPL-2.0 AND (GPL-2.0 with Assembly-excepti
Hi Wayne and Richard,
The syntax for the license expressions specify that the left side of the with
must be a “simple-expression” and the right side must be a license exception.
A simple expression is a license reference or a license ID. See
https://spdx.org/spdx-specification-21-web-version