[License-discuss] Canons of construction
van.lindberg at gmail.com
Wed Jul 3 14:13:12 UTC 2019
Raising this comment to a new thread.
Many of the things we are discussing could be resolved, or at least helped,
by elevating certain interpretive principles as "canons of construction"
that would guide analysis. This approach does not require amending the OSD
directly, but instead creating a body of literature that helps all parties
reason about it. For example, the comment below:
On Tue, Jul 2, 2019 at 12:55 PM Pamela Chestek <pamela at chesteklegal.com>
> As to "where in the OSD," I disagree with your framing that every
> license must be approved unless we can point to a specific rule broken.
> "Out of scope" is a valid reason; that is one reason why the human
> rights licenses are rejected. Some things are just not appropriate
> subject matter for trying to fix in an open source license.
I don't intrinsically disagree with this, but in my head I have various
"canons of construction" related to the OSD, and the specific one here is
that I had always accepted that an OSD-compliant license must act only
through the grant of permissions or conditions on the software itself (as
well as being consistent with other elements of the OSD). Thus, "Do no
evil" or "do not work more than 40 hours in a week" were appropriately out
of scope for an open source license. But in the specific case of the CAL, I
had drawn the data portability aspects carefully to only include
permissions or conditions on the software itself, thus keeping it in scope
for the OSD.
I think it would be useful, both in this case, and generally, to elaborate
on some of these implicit canons of construction. I think it is valid to
say that something is "out of scope," but I would suggest that this is a
good case to use to develop an articulable rule for what that means.
Similarly, there may be something to the international applicability of a
license that could be fertile ground for a canon of construction.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the License-discuss