I added a comment to Bugzilla, but will also respond here as well, in case that 
doesn’t get to everyone:

The SPDX License List Matching Guidelines already account for this.  Guideline 
12 states that you should "Ignore any text that occurs after the obvious end of 
the license and does not include substantive text of the license. . ." (see:  
http://spdx.org/spdx-license-list/matching-guidelines).  

Not all guidelines will have markup, and this is one for which you will 
generally not see markup in the license text. Each guideline also includes info 
as to whether you will, may, or will not expect to see markup in the license 
text.  This one states that templates will not have markup for this guideline.

If you have questions about the license list or matching guidelines, you might 
want to cross-post on the spdx-legal mailing list.

Thanks,
Jilayne
SPDX Legal co-lead

> 
> 
> Today's Topics:
> 
>   1. [Bug 1302] New: Apache 2.0 license text includes appendix
>      ([email protected])
>  
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 13 Jul 2015 18:47:05 +0000
> From: [email protected]
> To: [email protected]
> Subject: [Bug 1302] New: Apache 2.0 license text includes appendix
> Message-ID: <[email protected]/>
> 
> https://bugs.linuxfoundation.org/show_bug.cgi?id=1302
> 
>             Bug #: 1302
>           Summary: Apache 2.0 license text includes appendix
>           Product: SPDX
>           Version: 2.0
>          Platform: All
>        OS/Version: All
>            Status: NEW
>          Severity: normal
>          Priority: P2
>         Component: Licenses
>        AssignedTo: [email protected]
>        ReportedBy: [email protected]
>    Classification: Unclassified
> 
> 
> I've been working on a node.js module to match license files by applying the
> matching guidelines on the spdx website, but some licenses fail due to the 
> data
> content included in the license list.
> 
> The appendix to the Apache 2.0 license contains "how to apply the Apache
> License to your work"; this section is not included in many projects that
> include the Apache 2.0 license itself, nor is the content of its instructions
> listed in the SPDX license database as valid content for the Apache 2.0
> license.
> 
> It would be nice if any of the following happened:
> 
> - Remove appendix entirely, so that the text content of the license in the 
> SPDX
> database matches valid licenses in the wild
> - Surround the appendix with the optional meta tags
> - Add an entry for the "abbreviated" Apache 2.0 license as shown in the
> appendix
> 
> -- 
> Configure bugmail: https://bugs.linuxfoundation.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are the assignee for the bug.
> 
> 



SPDX Legal Team co-lead
[email protected]


_______________________________________________
Spdx-tech mailing list
[email protected]
https://lists.spdx.org/mailman/listinfo/spdx-tech

Reply via email to