ISC: Add <alt> tags #423
Merged
ISC: Add <alt> tags #423
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Following the example set by BSD-2-Clause, because users who are not the ISC are going to want to put their own name (or something generic like the BSD's "the copyright holders and contributors") in those slots.
|
Also odd about the ISC license is that the title ends in a colon. We only have three licenses like that in the current master (unless some slipped through my grep): The OSI does not include the trailing colon and the ISC has (added?) “Text of the” to their title. I haven't touched any of that in this PR yet either, but we may want: <title>
<p><optional>Text of the </optional>ISC License<optional>:</optional></p>
</title> |
|
And we may also want: <p>Permission to use, copy, modify, and<optional>/or</optional> distribute… |
|
re: colon in the title - it doesn't matter, as matching guidelines don't count the title for matching purposes, so I don't think there's any need for putting an tag inside the <title> tag. re: adding the tag to the /or text - yes, that would be accurate - good catch! |
OpenBSD uses an earlier form of this license with a bare "and". There has been some discussion in the past about whether, as the University of Washington at some point claimed, the "and" form forbids distributing modified copies (vs. having local copies and distributing unmodified copies, but not distributing the modified copies). For more on the discussion, see [1,2]. However, the SPDX legal team decided on 2015-04-30 that *it* didn't see significant difference between the "and" and "and/or" forms [3]. This commit encodes that decision for use in matching software. [1]: https://www.gnu.org/licenses/license-list.html#ISC [2]: https://lists.debian.org/debian-legal/2000/08/msg00147.html [3]: https://lists.spdx.org/pipermail/spdx-legal/2015-April/001398.html Subject: New License/Exception Request Date: Thu Apr 30 17:56:52 UTC 2015
|
On Thu, Aug 03, 2017 at 08:36:46PM -0700, Jilayne Lovejoy wrote:
re: colon in the title - it doesn't matter, as matching guidelines
don't count the title for matching purposes, so I don't think
there's any need for putting an <optional> tag inside the <title>
tag.
That makes sense for human readers and matching, although see [1]
about “how do machines decide if something is allowed alternative
copyright (or title) text, and not forbidden leading substantive
text?”. And even if we don't want to help machines by tightening up
title/copyright matching, it seems strange to not match the current
upstream's “Text of the ISC License:” [2].
re: adding the <optional> tag to the /or text - yes, that would be
accurate…
Pushed with 233ae57.
[1]: #404 (comment)
[2]: https://www.isc.org/downloads/software-support-policy/isc-license/
|
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following the example set by BSD-2-Clause, because users who are not the ISC are going to want to put their own name (or something generic like the BSD's “the copyright holders and contributors”) in those slots. The OSI has replaced the original “ISC” occurrences with “THE AUTHOR” and not marked them for replacement.
I'm not sure about the naming. I expect the values to be the same or similar for the two
copyrightHolder*entries. But the BSD's seem to use different names while other licenses like the MPL-1.1 seem to reuse the same name.Addresses part of spdx/license-list#7 (see also #404).
Also interesting, but probably unrelated, is that the ISC has bumped their terminal copyright year from 2010 to 2013. Presumably they're showing how the replacable text would change and are not claiming an extended copyright on the license content, because I see no changes in the license text. I've left the terminal year alone for this commit.