Re: call tomorrow, agenda
J Lovejoy wrote:On Fri, May 15, 2015 at 12:57 AM, Alan Tse <Alan.Tse@...> wrote:The issue identified on the call today (and Mark will correct me if I've
And just to confirm, does "OR" have the same 3 interpretation problem at theIMHO yes. This is really left to the SPDX authors to provide the level
of details they want to provide.
More is better but not mandated.
Here's another thought I had for real world practice. When a package takesI have seen it done both ways. And quite often this is a combination of both.
Taking Apache as an open source example, you see quite often an
aggregated composite notice and license texts listing every licenses
of non-Apache and Apache components embedded in a given package
(Tomcat is a good example). You also see each individual original
notice and licenses left as-is further down the tree. When translated
to SPDX it would be likely redundant to repeat things ... But it is
convenient to have things in one place summarized. In practice having
a summary report produced from lower level could be a tool-provided