Wayne Beaton wrote on Monday, 2 October: > (EPL-2.0 OR (LicenseRef-GPL-2.0-with-Assembly-exception OR GPL-2.0 > with Classpath-exception-2.0)) OR Apache-2.0 > > I threw in the extra grouping because it felt like they needed to be > together.
Could you explain a bit further why the extra parenthesis grouping is needed when only ORs are involved? Looking at the SPDX spec at https://spdx.org/spdx-specification-21-web-version, I see: >> For example, when given a choice between the LGPL-2.1 or MIT licenses, a >> valid expression would be: >> (LGPL-2.1 OR MIT) >> An example representing a choice between three different licenses would be: >> (LGPL-2.1 OR MIT OR BSD-3-Clause) It seems that the spec suggests that when you put a bunch of OR's together, it should be: (EPL-2.0 OR LicenseRef-GPL-2.0-with-Assembly-exception OR GPL-2.0 with Classpath-exception-2.0 OR Apache-2.0) The nested parens are covered in a later section, but only for combining ANDs and ORs. What's the significance of the extra parenthesis in the case of only ORs? It seems not to be covered in the spec at all. (If I just missed that part, someone please do point me to where it is covered.) Thanks! -- Bradley M. Kuhn _______________________________________________ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
