There are roughly three issues that have been discussed for years that could potentially be addressed. Ideally, addressing one or more of these could increase clarity of relevant CC licenses, and increase range of and differentiation within CC license suite.
Effectively, this has been treated as identical to potentially tweaking the definition of adaptations vs collections.
- Version 2.0 added "For the avoidance of doubt, where the Work is a musical composition or sound recording, the synchronization of the Work in timed-relation with a moving image ("synching") will be considered a Derivative Work for the purpose of this License." (Please discuss this particular clarifying language on the License subject matter page.)
- Many have wanted something similar added clarifying when use of an image creates an adaptation/derivative. This was visited especially during discussions with the Wikimedia community, leading to no immediate change, but an assurance that the scope of BY-SA's copyleft would only be increased, if changed at all in the 3rd point of CC Attribution-ShareAlike Intent
Relatedly, it has also been pointed out that CC license definitions of work/adaptation/collection are somewhat hard to read.
Proposals relating to SA scope in 4.0
For ease of reference on discussion lists, please do not alter proposal numbers.
SA Proposal No. 1: Make no changes.
- Cons: Does not allow the creation to evolve. It is not made clear how to incorporate SA materials into otherwise licensed works.
- Other comments: There is already a 'no derivatives' option. The concept of derivation could be made more clear with examples such as "remix, translate, integrate, aggregate, etc."
SA Proposal No. 2: Make work/adaptation/collection definitions easier to read, but strive to not make any effective change.
- Pros: Will clarify terminology.
- Cons: New observations based on experience with current CC licenses may bot be taken into account.
- Other comments: Explain that the Share Alike clause discourages exploitave commercial uses while still allowing commerce in the commons and OER landscape.
SA Proposal No. 3: Expand scope of adaptation (thus SA) specifically for some class of use of images, analogous to synching added in 2.0.
- Other comments: Also allow certain exceptions such as mixing CC-by-SA with GPL or similarly spirited licenses.
SA Proposal No. 4: A more aggressive expansion of SA, including some collections, except those that are mere aggregations (see GPL).
- Other comments:
Please add other SA proposals here, and number them sequentially.
(Note that scope and whether source required are independent of each other.)
Some would like a copyleft for creative works that requires not just sharing adaptations under the same license, but making preferred form for modification available, as the GPL does for software. FDL includes a weaker requirement of providing copies in "transparent" formats. Especially the former may be too far for BY-SA to go (but costs/benefits could be listed to see). Could possibly be addressed via compatibility, see next.
Compatibility with other copyleft licenses
Directly related to the interoperability goal of 4.0. The following licenses have been discussed at various points, regarding compatibility with BY-SA:
- Free Art License
- Free Documentation License
- GPL (unique among these, could only be one-way with BY-SA as donor; would address desire for source-requiring license, long-term trend toward more mixing of "code" and "content" in ways beyond former accessing latter)
- Open Database LIcense (ODbL)
Some things to consider in 4.0 process:
- What could be done to bring BY-SA into better alignment technically with these other licenses where they are in the same spirit?
- Should explicit compatibility with any of these be aimed for? In theory this could be a post-4.0 discussion assuming compatible licenses hook remains, but in practice, if compatibility is to be possible, 4.0 changes should be considered in that light
- Discuss with stewards of each of above licenses, with regard to BY-SA 4.0, future versions of their licenses, alignment, and explicit compatibility statements
- Similar to above, discuss with other stewards possibility of agreeing on/promoting common license text
Considerations regarding compatibility of other licenses
Please add other important considerations to this discussion here.
We encourage you to sign up for the license discussion mailing list, where we will be debating this and other 4.0 proposals. HQ will provide links to related email threads from the license discussion mailing list here.
Please add citations that ought inform this 4.0 issue below.