<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><span style="background-color: rgba(255, 255, 255, 0);">The fact is, unlike any other FOSS license, under this license a user who does not modify any code is still not going to know if they are compliant or not. </span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">In every other license, if they provide source they know they are compliant. Here, if the original code licensed under CAL is not fully compliant with 4.2 then they are never going to be compliant unless they pay someone to make it compliant within 60 days.</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">That’s not “hypothetical”. That’s just the way the license is written.</span></div><div dir="ltr"><br>On Dec 6, 2019, at 5:48 PM, VanL <<a href="mailto:van.lindberg@gmail.com">van.lindberg@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div dir="ltr">Hi Nigel,<br></div><div><br></div><div>Let me start with the following:<br></div><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Answers that states with "as a general rule" or "your example is underspecified" means Alice has to spend lots of effort to make sure that the software complies with 4.2 even if she has made zero changes to that software. </div></div></blockquote><div>[snip]<br></div><div><br></div><div>I can talk about the license, but one of the things that seems to be a persistent desire here is for analysis of hypotheticals that aren't based in any concrete situation. As with any situation where we are talking about rights in software (or data), the analysis *usually* ends up being straightforward when the exact facts are known. </div></div></div></div></blockquote><div><br></div><div>The analysis requirement is excessively onerous for users of CAL licensed code to determine if they are compliant with 4.2 except in the most simple or benign case.</div><br><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div>But repeatedly in this process, I have attempted to make assumptions based upon preexisting knowledge, most likely implementations, etc, but have then been sharply criticized because my response does not allow for the whole range of possibilities.</div></div></div></div></blockquote><div><br></div><div>You refuse to address what happens if the original code is not 4.2 compliant.</div><br><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div class="gmail_quote">Thus, I try to answer as well as I can, but I am trying to resist the temptation to guess when the examples are underspecified. And this is why:<br></div><div class="gmail_quote"><div><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Bob has preexisting rights to US census data records because it is public information. Alice has spent time and money cataloging that information so it could be found in a name search. The service provides linkage from people in his tree to the historical US census data. </div></div></blockquote><div><br></div><div>This adds new facts. It possibly changes the analysis. And it is still underspecified.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div> What needs to be provided?</div></div></blockquote><div><br></div><div>The User Data:</div><br>“User Data” means any data that is an input to or an output from the Work, where the presence of the data is necessary for substantially identical use of the Work in an equivalent context chosen by the Recipient, and where the Recipient has an existing ownership interest, an existing right to possess, or where the data has been generated by, for, or has been assigned to the Recipient.<br></div></div></div></div></div></blockquote><div><br></div><div>All you did here was repeat your license text.</div><br><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div class="gmail_quote">Thanks,<br></div><div class="gmail_quote">Van<br></div><div class="gmail_quote"><br></div><div class="gmail_quote"><br><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div> </div></div></blockquote></div>
<br></div></div>
</div></blockquote><blockquote type="cite"><div dir="ltr"><span>_______________________________________________</span><br><span>License-review mailing list</span><br><span><a href="mailto:License-review@lists.opensource.org">License-review@lists.opensource.org</a></span><br><span><a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a></span><br></div></blockquote></body></html>