RE: Spec recommendation for paren encapsulation? (was: signifigance of nested parenthesis with only ORs?)

2017-10-12 Thread Wheeler, David A
Gary O'Neall [mailto:g...@sourceauditor.com]: > If we have more than one line for a compound set of licenses, it would be > ambiguous if the text following the first line of a compound license is part > of the license expression or just some other text. To solve this ambiguity, > we introduced

RE: Spec recommendation for paren encapsulation? (was: signifigance of nested parenthesis with only ORs?)

2017-10-12 Thread Gary O'Neall
> -Original Message- > From: spdx-legal-boun...@lists.spdx.org [mailto:spdx-legal- > boun...@lists.spdx.org] On Behalf Of Wheeler, David A > Sent: Thursday, October 12, 2017 12:07 PM > To: W. Trevor King > Cc: SPDX-legal > Subject: RE: Spec recommendation for paren encapsulation? (was: >

RE: Spec recommendation for paren encapsulation? (was: signifigance of nested parenthesis with only ORs?)

2017-10-12 Thread Wheeler, David A
W. Trevor King [mailto:wk...@tremily.us]: > The Appendix V wording for that is: > > Representing Multiple Licenses > > Multiple licenses can be represented using a SPDX license expression > as defined in Appendix IV. A set of licenses must be enclosed in > parentheses (this is a