2 ms·
I am not a lawyer, and my knowledge over disclaimer clauses is mostly from a days lecture by a legal historian professor, and he summarized it as mostly forgott
by belorn 10y ago
I am not a lawyer, and my knowledge over disclaimer clauses is mostly from a days lecture by a legal historian professor, and he summarized it as mostly forgotten magic which is based on century old practices. For example, the practice of all caps just happens to be an example that a specific US agency gave in order to describe how to make a disclaimer "noticeable", but people just ran with it and now it just what everyone does.
I do have a guess on why Apache2 mention applicable law, which was something I read in Swedish contract law (if licenses is a contract or not is, of course, also debated between lawyers). The law mentioned specific situations in which either a clause in a contract or the contract as a whole could be declared invalid, which could happen when for example a clause is "too unfair" or when a party can be said as unaware of the clause or its consequences. My guess is thus that the Apache2 disclaimer mention applicable law as a way to dodge laws in countries which otherwise could make the whole disclaimer invalid.
As for the last question, a contributor might have sought advice from a lawyer which, as many lawyers do, gave an advice of caution. In some cases, foreknowledge about risks increases damages and risk of being sued, so my guess is that the disclaimer tries to avoid that situation.
In both cases, it seems as mostly efforts to try make the disclaimer more safe to use in a international context, where MIT and BSD is more focused on the law which govern Massachusetts and Berkeley. I personally doubt however that the differences matter much in practice, particular in the US and EU.