Dear Gary, In message <002f01cec378$2f2a3470$8d7e9d50$@com> you wrote: > > If there is no conflict in license terms, however, I do not see an issue > in using this approach. I run across a large volume of MIT style and BSD > style licenses mixed in with GPL code, for example. Using "AND'd" > licenses is a compact way of stating all of the terms from license A and > all of the terms for license B apply.
But this example doesn't work either. If you mix a license that allows "modify and keep the modified code closed" with GPL, the only legally possible result is GPLed code. I see little value in constructing such more or less artificial examples. All code that I've seen so far in real life was either simple, i. e. covered by a single license, or it came under two (I'd have to think hard if I had to quote an example with more than two) licenses, which would implement a choice - either you use the code under GPL, or under a BSD license; either you use the commercial license, or GPL. It has always been <this> or <that>. Things become more difficult when importing such code into another project - then you usually have to decide which of the available choices you chose, and go with that. At this point, the other option becomes void. > I don't think it is critical to use the same syntax in the tagging as we > do in the SPDX documents. I do, however, think it is important that we > don't lose any embedded licensing information. For example, if there is > an MIT notice stuck in the middle of a GPL licensed file, we should > retain that information and not just call it a "GPL" licensed file. True. The clause "The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software." explicitly requires that. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [email protected] "Beware of programmers carrying screwdrivers." - Chip Salzenberg _______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
