On Mon, Feb 27, 2017 at 03:58:38PM -0700, J Lovejoy wrote:
> In the course of implementing the license expression syntax and
> deciding to put license exceptions in their own sub-list, we thought
> we might as well be thorough about it, and a few brave souls set
> about to find as many license
On Mon, Feb 27, 2017 at 02:18:55PM -0700, J Lovejoy wrote:
> Information related to who, when, how, why a license or exception
> was requested to be added is maintained here:
> https://docs.google.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=695212681
> for
t 10:41:50AM -0700, J Lovejoy wrote:
>> The license exceptions have an “extra” field that we don’t use for
>> the licenses, which is “Example of Use”. I think this is from info
>> we captured when collecting exceptions to add to the list.
>
> Potentially more useful informati
On Thu, Feb 23, 2017 at 10:41:50AM -0700, J Lovejoy wrote:
> The license exceptions have an “extra” field that we don’t use for
> the licenses, which is “Example of Use”. I think this is from info
> we captured when collecting exceptions to add to the list.
Potentially more useful in
ject: extra field for license exceptions
Hi SPDX Legal,
The license exceptions have an “extra” field that we don’t use for the
licenses, which is “Example of Use”. I think this is from info we captured
when collecting exceptions to add to the list.
In the initial conversion to XML, this field didn’t
Hi SPDX Legal,
The license exceptions have an “extra” field that we don’t use for the
licenses, which is “Example of Use”. I think this is from info we captured
when collecting exceptions to add to the list.
In the initial conversion to XML, this field didn’t quite make it. We can
add it easily
