On Wed, May 11, 2016 at 11:56 PM, Wheeler, David A wrote:
> In the Linux Foundation CII “best practices” badge effort I’m noticing an
> interesting problem. Some projects have *different* license situations for
> their source code and documentation, but there’s no simple way to express
> that usi
ech-
> boun...@lists.spdx.org] On Behalf Of Philippe Ombredanne
> Sent: Wednesday, May 11, 2016 3:13 PM
> To: Wheeler, David A
> Cc: spdx-tech@lists.spdx.org
> Subject: Re: Proposal: Add "(IF THEN
> [ELSE ])" to License expressions
>
> On Wed, May 11, 2016 at 11
Philippe Ombredanne [mailto:pombreda...@nexb.com]>
>Could this be simplified?
> I can see two use cases:
> 1. at the file or directory level, this is unlikely needed: just provide the
> expression that applies there only e.g. to a doc or source directory in an
> SPDX doc or a simple expression.
On Thu, May 12, 2016 at 6:06 PM, Wheeler, David A wrote:
> Philippe Ombredanne [mailto:pombreda...@nexb.com]>
>
>>Could this be simplified?
>> I can see two use cases:
>> 1. at the file or directory level, this is unlikely needed: just provide
>> theexpression that applies there only e.g. to a do
Philippe Ombredanne:
> I suggest instead to change this application design and data model to track
> several license expressions, one for each of your "keywords".
> For instance, by storing a list of expressions and what they apply to or by
> breaking down top level packages in sub-packages each
