This page was designed as a gathering place for suggestions from the community. 4.0 has now been published and no new suggestions will be incorporated; this page is maintained as an archive of past discussion.
- Review the existing issue pages to see if your new idea would fit on an existing page. If so, feel free to add it yourself.
- Please refer to the Legal Code Errata<ref> This page contains a list of errors and typos in the licenses. CC will be making changes in 4.0 to correct these problems (assuming the problematic text remains in 4.0).</ref> page to see if your concern is addressed here.
- If the issue is not already addressed, please refer to the License Versions page to review issues debated in prior versions and the CC license discuss archives.<ref>TK</ref> If you want to re-open a conversation on an issue or proposal debated in a prior versioning effort, please summarize and link to that prior discussion, indicating why the issue ought be revisited.
- If your issue is not adequately covered, you can't find a proper home on these pages, or you would prefer that HQ decide where it best fits on the wiki, please add the issue in the relevant section below.
Moved to 4.0/Disclaimer of warranties and related issues.
Treatment in 4.0d3: Unchanged in d3. Following consultation with our affiliates, as well as with the collecting societies themselves, we have decided not to change the treatment of this issue between d2 and d3. In particular, we sought guidance that the simplified language would be treated by the collecting societies as having the same substantive meaning as the language in 3.0. We also examined the issue of Extended Collective Licensing jurisdictions, and whether there were improvements to make that would increase the likelihood of this provision being interpreted as intended by the ECLs; there was no strong case to make any particular alteration, and so the language here was left unchanged.
Treatment in 4.0d2: Unchanged in d2. Please note that based on input from our affiliates in Europe, CC is looking harder at situations involving extended collective licensing arrangements. This review is still underway, and we expect to submit a proposal for consideration to the license discussion list shortly following publication of d2.
Please include a description of the issue(s) with links to relevant references where applicable.
- Allow collecting societies to collect royalties even where arrangements are otherwise waivable. Specific language proposed with supporting arguments on license-discuss.
- Treatment in 4.0d1: Not addressed because it seems to undermine the permissions being granted by the license if licensor can both encourage free permission via a CC license and voluntarily collect royalties from those same uses simultaneously. But if collecting society can and will still collect even if licensor is not a member, this may need to be addressed in the licenses.
ND has not been nearly as discussed as NC, but it has the same problems of non-freeness and probable over-use. Some of the NC proposals (eg rebranding, dropping, or only keeping one instance of) have ND analogues that ought be separately and thoroughly evaluated.
Other ND issues:
- Should there be a clarification of what qualifies as "modifications as are technically necessary to exercise the rights in other media and formats"? For example, "algorithmic reductions of the color depth of still or moving images" in case printing in greyscale or b&w is not unambigously an "other media" or "format" unto itself? Proposed at http://lists.ibiblio.org/pipermail/cc-licenses/2012-January/006530.html
- Treatment in 4.0d4: See the Treatment of adaptations page; ND was modified so that the conditions only applies when works are Shared, not to private uses.
(Font) Embedding Issues
This issue comes from the field of font licensing: if you release a font under a CC-SA license, do all users who embed the font in their PDF documents have to put their PDFs under CC-SA as well?
The CC general counsel seems to believe that they do not. The German legal counsel seems to believe that the font creator can use a "font exception" (known from GNU), number 8. of the license notwithstanding.
I tend to see it differently, as do the vast majority of type designers and font publishers; their postition wrt font embedding is very clear and many of them have updated their license agreements to allow font embedding under restrictive terms (subsetting required etc.).
I'm coming from the font side of this, but I can imagine that there are many more fields, where this "if you modify the work itself, you need to reciprocate, if you just use it as it's supposed to be used without modifications, mere embedding/aggregating do not legally force you to use CC-SA" would be beneficial.
Fair use baseline
"CC 4.0 could promote fair use by guaranteeing fair use internationally. Just as the main terms of the CC license are applicable internationally, instead of simply specifying that the CC license doesn’t interfere with or supersede one’s common law or statutory fair use or fair dealing rights (because, you know, how could it?), the CC licenses could guarantee some uncontentious and shared subset of fair use/fair dealing rights as part of the license."
Above from http://blog.tommorris.org/post/14114334627/creative-commons-4-0-proposal-fair-use-baseline and discussion at https://plus.google.com/110114902730268262477/posts/PTnqvZHKEBT
Time-based switch to more freedom
Discussed in cc-licenses thread http://lists.ibiblio.org/pipermail/cc-licenses/2011-December/thread.html#6453
Which freedoms gained?
- A particular condition (NC) is dropped after time (eg BY-NC-SA work becomes available under BY-SA in a specified year)
- This being intended as a replacement to current NC-licensing, i.e. CC 4.0 only offer NC licencing with a time-limited NC-condition, thus continuing to support desire for NC, but limit its attractiveness, changing BY-NC to BY or BY-NC-SA to BY-SA after 5, 10 etc. years
- All conditions dropped after time (eg work under any CC license also becomes available under CC0 in a specified year)
- Time out of conditions built into all CC licenses, or those specifically to which relevant condition (eg NC) applies; eg part of using BY-NC-ND 4.0 is that work is available under CC0 after 28 years.
- Specific time-out duration is up to licensor; support built into license deed, license name and equivalent URLs, eg BY-NC(14)-SA for condition expires 14 years after publication or BY-NC(until-2017)-SA for year condition expires. This supports automatic discovery of originally closed-content licenced works that have become open content in the meantime.
- No specific support for time-out of conditions built into license, but documented, perhaps encouraged in license chooser, means of stipulating a work's availability with more freedoms after some time duration
In the wild examples:
Related, abandoned mechanisms:
- Grants more freedoms to licensees sooner than waiting for expiration of copyright term.
- Gives more public visibility to the creator community's perception on copyright terms duration
- Increases license complexity.
- CC+ mechanism already exists for licensors who want to grant more permissions beyond standard license terms.
- Other comments:
Additional terms framework
- Treatment in 4.0d3: Similar to d2, but with headings and revisions for clarity. We have also removed the provision about license terms controlling where there is a conflict and added more detail about the mechanism under which licensors may customize the disclaimer and limitation of liability, or alternatively, undertake affirmative warranties. We feel that being clear about the limited ways in which CC licenses may be customized provides important clarity for licensors and licensees. While licensors may always make separate agreements relating to the licensed material, CC wanted to make it clear those contractual agreements are independent from the license and thus would not follow the work in the same way as the license conditions.
Occasionally, there is a need to attach additional terms to a licensed work. A proposal for dealing the issue was raised on license-discuss.
The GPL dealt with this in v.3 with the following provision:
Additional permissions are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
Essentially, this does three things:
- Gives licensors/copyright holders (not licensees!) formal permission to create additional permissions.
- Explains when and to what extent the additional permissions apply (either to part of the program, or the whole).
- Creates a mechanism for *removing* additional permissions, in case such removal is necessary (primarily for compatibility purposes).
- Treatment in 4.0d1: CC has not made a proposal in the first draft, but believes that such a provision merits discussion and a proposal for the next license draft. GPL’s provision may provide a starting point for a proposal.
Moved to 4.0/Termination.
Please aggregate small changes to language used in the first draft here. If you are proposing a change to defined terms or other substantial language, please include the proposal in the relevant topic page on the wiki and do not include it here.
Please remember that language may change through different drafts. The discussion focus for the first draft is high level policy decisions. You may want to save small language suggestions until a later draft.
Other issues for 4.0
Please include a description of the issue with links to relevant references where applicable.
- Explicitly support an open data commons addressing the different requirements of:
- public data providers (protect against abuse & misuse of data products - organisations & individuals credibility & reputations need an assurance) see UK Govt Open Government Licence: "ensure that you do not mislead others or misrepresent the Information or its source;" at http://www.nationalarchives.gov.uk/doc/open-government-licence/
- NOTE: CC licenses already contain a non-endorsement provision (Section 4b of CC BY v.3), which serves a similar function. CC licenses also preserve moral rights, which would often prevent someone from misrepresenting the licensed content. Together, these two aspects of CC licenses are designed to achieve the same effect of the provision in the OGL. Because they track other existing laws (trademark and moral rights), they do this without introducing extra ambiguity.
- This is not a solution but actually is the cause of the problem, due to two main issues: 1. Because moral rights are very different in different countries, a CC licence may give strong protection in one country, but much weaker in another. So the CC licences are in effect quite different. This is critical in the areas of data licencing, where data providers (as in the UK example) require some protection against misuse. If CC provided some such protection as part of the CC framework, then a genuine common international licence is feasible. 2. Because moral rights are tied up in copyright, trademark,and various areas of legislation, it can take an expert lawyer to work out just what "moral rights" protections are provided under CC. This all becomes too hard, so CC licences are discarded as a viable option. To resolve both these issues, a simple and clear moral rights provision needs to be available under CC, even with a proviso/caveat that it may be subject to limitations under local national legislation.
- Explicitly support open source, with CC licences consistent with GPL & BSD licences.
- This is critical in the computer gaming industry, where sound tracks, imagery & code need to have a single consistent licence which is applicable to the entire mix of components. See the discussion about compatibility for more on this topic.
- CC-licensed works are not share-able on common platforms. One way to address this issue is to change CC license terms.
- Although the problem is widespread, it may be difficult to come up with a good language to grant platform owners additional license permissions and waive some of the obligations.
- NOTE: Relatedly, because CC licenses do not allow sublicensing, anyone other than the rightsholder cannot upload a CC-licensed work to platforms like Facebook. The TOU on Facebook and many other platforms require that the uploader grant a license to the platform for all uploaded content. Other than removing the prohibition against sublicensing in CC licenses (something that would have larger implications), there is probably no way to address this problem in Version 4.0.
- (Consider allowing sub-licensing, for at least adaptations created under BY-SA, but possibly for a lot wider range of uses.) : moved to Treatment of adaptation page (by this edit)
- Consider explicitly introducing an interoperability clause for CC licenses such CC-BY.
- Right now, it is not clear without close examination of a pair of licenses, for example CC-BY-US 2.0 and CC-BY-JP 2.0 licenses, if they have the exact same set of permissions and obligations. Scope of use permitted by one of those licenses may be narrower than the other, in which case the works under those two different licenses are not compatible to a maximum degree.
- NOTE: As a general rule, the basic permissions are aligned across all ported licenses. This is arguably the single most important factor for interoperability. Nonetheless, the ported licenses do introduce complexity into the license suite, which can make it difficult for licensees to understand their obligations under different licenses.
- Consider providing clearer and more explicit guidance/ provisions as to licenses a licensee using a licensed work can choose to release the work or its adaptation. (In other words, make it easier for people to answer this frequent question: "I want to use this CC-licensed work in a particular way. But under which license can I release the work?"
- The CC-BY-SA licenses are clear and explicit which licenses a licensee can choose to release an adaptation, IF the licensee is distributing or publicly performing the adaptation. The licenses are not clearly stated, however, the range of choice when the licensee is handing a copy just to a few people, for example. Absent explicit grant of permissions, we should perhaps assume that it is prohibited to choose a later version of the license or CC Compatible license. Absent explicit requirement, perhaps it is okay to even fully copyright the adaptation.
- "You may not sublicense the Work" is a phrase found in multiple licenses. But such prohibition seem to exist only for a limited type of use - namely, when a licensee "distribute or publicly perform" "the Work". When a licensee shares the work within a small group (which is probably not "distribution" according to CC licenses definition section) or deals with adaptation, there is no such restriction. Does that mean a licensee can sublicense, then? I suppose not, because there is no explicit grant of such permission. But is it arguable in some cases that some implicit grant exist? I don't know the answer to that, but this is at least confusing for non-experts who want to read and understand license.
- But some would say that this issue may be better handled by a FAQ entry than a provision legal code.
- Treatment in 4.0d3: Incorporated provision specifying how adaptations of BY and BY-NC works may be licensed. Details provided on the Treatment of Adaptations page.
- Require releasing the source when releasing a finished product under a CC license, similar to requirements in GPL.
- Determining what counts as "source" in creative works can be very difficult.
- Discussion at this thread on license discuss and elsewhere on the 4.0 wiki.
- Consider an even clearer labeling of license conditions, esp. regarding place of anti-TPM clause.
- The public draft version 1 does a great job in organizing license conditions. But it could be improved, it seems. The clause dealing with technological protection measure is currently placed at Section 3 (a)(3) and (b)(3). However, prohibition of TPM that contradicts with license grant is not something people would understand as an attribution requirement. It is better if the anti-TPM clause be separated into something like, say, (c) Technological Protection Measures.
- Another justification for treating anti-TPM clause as a separate subsection is that, judging from email inquiries CC Japan receives, many people mistakenly think that the license deed exhausts the license conditions, and misses additional conditions such as anti-TPM clause. Having a subsection and subsection title would visually clarify that CC-BY-NC-SA is not just about attribution, non-commercial, and share-alike.
- Similarly, if there is going to be a clause like "You may not offer or impose any terms on the Work that restrict the terms of this License or the ability of the recipient of the Work to exercise the rights granted to that recipient under the terms of the License." (taken from CC BY-NC-SA 3.0 Unported 4.a.), that could be bundled with the anti-TPM clause in the same subsection (its title could be "restriction of recipients' ability to use Licensed Work," for example).
- On a related note, the 4.0/Draft 1 currently place this imposition of restriction of recipients' ability to use Licensed Work in Section 6 (c). The title for the section is Miscellaneous. Given the language that "If You fail to comply with any conditions of this Public License, this Public License will terminate automatically " (Section 5 (a) emphasis added by me), and that the title for Section 3 is License Conditions, it would perhaps be better to place that part of 6 (c) to Section 3.