Difference between revisions of "4.0/Disclaimer of warranties and related issues"

From Creative Commons
Jump to: navigation, search
Line 1: Line 1:
 
{{4.0 Issue}}
 
{{4.0 Issue}}
 
{{Infobox |'''Draft 1 Treatment:'''  The language has been simplified but is intended to operate and have the same scope as its counterpart in 3.0.  We are mindful that a complete disclaimer and limitation of liability may not be allowed depending on local law, and accordingly have prefaced the provision with the qualifier found suitable by several jurisdictions for 3.0 ports, “To the greatest extent permissible,...”  We expect that for some, this provision may be inadequate.  We want to hear ideas on both improving this provision, and the proposal for allowing additional terms to the license to allow for more specialized language to be included by licensors.}}
 
  
 
<div style="padding: 1em; margin-bottom: 1em; border: 1px dotted red; background-color: #eee; width: 97%;">
 
<div style="padding: 1em; margin-bottom: 1em; border: 1px dotted red; background-color: #eee; width: 97%;">
 
'''Page summary:''' The CC 1.0 license suite included an explicit warrant by the licensor.  The 2.0, 2.1, 2.5 and 3.0 versions of the suit all expressly disclaimed any warranties.  This decision was made after a long and detailed debate. The reason for this shift is explained nicely in this [http://creativecommons.org/weblog/entry/4216 blog post.]  We are exploring options related to the disclaimer of warranties, including leaving things as they were in 3.0, going back to the 1.0 licensor warranties and other middle-group options between the two.  
 
'''Page summary:''' The CC 1.0 license suite included an explicit warrant by the licensor.  The 2.0, 2.1, 2.5 and 3.0 versions of the suit all expressly disclaimed any warranties.  This decision was made after a long and detailed debate. The reason for this shift is explained nicely in this [http://creativecommons.org/weblog/entry/4216 blog post.]  We are exploring options related to the disclaimer of warranties, including leaving things as they were in 3.0, going back to the 1.0 licensor warranties and other middle-group options between the two.  
 
</div>
 
</div>
 +
 +
{{Infobox |'''Draft 1 Treatment:'''  The language has been simplified but is intended to operate and have the same scope as its counterpart in 3.0.  We are mindful that a complete disclaimer and limitation of liability may not be allowed depending on local law, and accordingly have prefaced the provision with the qualifier found suitable by several jurisdictions for 3.0 ports, “To the greatest extent permissible,...”  We expect that for some, this provision may be inadequate.  We want to hear ideas on both improving this provision, and the proposal for allowing additional terms to the license to allow for more specialized language to be included by licensors.}}
 +
  
 
{| class="wikitable" cellspacing="0" cellpadding="5" width=100%
 
{| class="wikitable" cellspacing="0" cellpadding="5" width=100%

Revision as of 21:32, 9 October 2012

This page presented an issue for consideration in the CC license suite 4.0 versioning process. The discussions have now concluded with the publication of the 4.0 licenses, and the information on this page is now kept as an archive of previous discussions. The primary forum for issues relating to the 4.0 versioning process was the CC license discuss email list. You may subscribe to contribute to any continuing post-launch discussions, such as those surrounding compatibility and license translation. The wiki has been populated with links to relevant email threads from the mailing list where applicable, and other topics for discussion were raised in the 4.0/Sandbox. See the 4.0 page for more about the process.

Page summary: The CC 1.0 license suite included an explicit warrant by the licensor. The 2.0, 2.1, 2.5 and 3.0 versions of the suit all expressly disclaimed any warranties. This decision was made after a long and detailed debate. The reason for this shift is explained nicely in this blog post. We are exploring options related to the disclaimer of warranties, including leaving things as they were in 3.0, going back to the 1.0 licensor warranties and other middle-group options between the two.

Draft 1 Treatment: The language has been simplified but is intended to operate and have the same scope as its counterpart in 3.0. We are mindful that a complete disclaimer and limitation of liability may not be allowed depending on local law, and accordingly have prefaced the provision with the qualifier found suitable by several jurisdictions for 3.0 ports, “To the greatest extent permissible,...” We expect that for some, this provision may be inadequate. We want to hear ideas on both improving this provision, and the proposal for allowing additional terms to the license to allow for more specialized language to be included by licensors.


Draft 2 Treatment:' No change in Section 4 language itself. However, we have added a new Section 6(b) that permits licensors to disclaim or offer warranties or to limit liabilities differently from Section 4. This is intended to ensure licensors can tailor those provisions in the manner most suitable based on differing consumer protection laws that may apply to them and have those changes be deemed part of the license itself.

Post 4.0d2 update: During the post-d2 discussion period, several affiliates and community members proposed changing the language to require documentation of third-party rights. Discussion around the issue was then opened up on the list, including discussion of the very different treatment in 1.0.

Disclaimer of warranties and related issues

Considerations

There are several important factors to be considered in connection with any proposal to change the current treatment. Generally, proposals fall into two categories: those that would require licensors to provide a warranty as in version 1.0, and those that would require licensor documentation of other rights in some manner. Without reference to any specific proposal, here are some general considerations to inform the issue.

Factors weighing against warranties, marking requirements or similar licensor undertakings

  • These requirements would not relieve the underlying problem in some if not many cases given the complex web of copyright and other laws that may apply to any given work. Many licensors -- even sophisticated licensors -- are not aware of all possible rights that may exist in a work. By way of illustration, a licensor could apply a CC license to a work she authored but the applicable law considers it a "joint work" requiring agreement of all authors before licensing; or, a licensor might share a photograph with blurry (but upon close examination, identifiable) persons in the background under a CC license that permits commercial reuse and the photograph is reused in a manner than violates those persons' privacy or publicity rights.
  • Warranty and marking requirements are simply not an option for some licensors wanting to share and comply in good faith. Transaction costs associated with clearing and documenting all possible rights are high for well funded organizations let alone an individual licensor wanting to share. The problem is particularly acute when the work is restricted by complex layers of rights, such as a musical work or performance, or a film production.
  • Other licensors may be unable to make any affirmative statements about having cleared third-party rights, sometimes as a matter of institutional policy. These licensors are often acting in good faith, using best efforts to clear rights appropriately notwithstanding the current disclaimers. Upgrading to the 4.0 licenses will not be an option for those licensors.
  • The existing treatment seems to work well in practice. The current (and 4.0) attribution and marking requirements make contact with licensors easy for those seeking formal assurances or warranties.
  • Partial solutions already exist and could be leveraged where affirmative statements are important to licensees. Many third-party platforms that enable CC licensing already require uploaders to affirmatively agree that they have cleared all necessary rights in their licensed content. (While there are many licensors who are ignorant of this requirement or mistakenly believe they have all rights, it is also likely that including an affirmative warranty or undertaking in the licenses would be similarly missed.)
  • Warranties provide only partial benefit and protection to licensees, as they do not address the underlying problem. If a licensor applies a license without having cleared all other rights, a licensee may still be required to cease distribution or pay damages when rightsholders enforce. While warranties may shift liability to the licensor, they cannot give the licensees guaranteed recourse from a licensor who has limited assets or is difficult to find.
  • In some jurisdictions, warranties cannot be disclaimed as fully as the license attempts, and implied warranties are read into licenses, all by operation of local law. This raises the question of the need for warranties, at least in those jurisdictions.
  • Disclaiming liabilities is the standard for open content licenses (although a few open software licenses include warranties). Reversing course to include warranties breaks with that.
  • CC prefers the licenses operate as licenses to the greatest extent possible, wherever possible. Having licensors undertake affirmative obligations could work against this interpretation in jurisdictions where the license is construed as a license and not a contract.

Factors weighing in favor of warranties, marking requirements or similar licensor undertakings

  • CC licenses are designed to enable reuse of works. When the work being shared is restricted by rights that are not licensed and are not identified (so that they can be cleared), the reusability of the work is diminished and may be effectively non existent for some or all reuses depending on the unlicensed rights in play.
  • As betweens licensors and licensees, licensors are generally better informed about what other rights may exist in the work that should be cleared before reuse, and arguably better positioned to clear those rights. Additionally, tracking and documenting the origin and status of works is a standard procedure for many licensors.
  • The current language puts the entire burden of clearing rights on the licensee without any corresponding obligation on the licensor. Arguably, this does not give licensors incentive to be as careful as they might otherwise be when applying a license, or properly marking third party content in a work.

Opportunities outside the licenses

There are several things that Creative Commons could undertake outside of the licenses to further encourage licensors to clear rights and document known third party rights or other limits on the licenses that could actually improve the underlying situation in a way that no shift of responsibility in the licenses can.

  • Facilitate offers of warranties by licensors who can and want to provide them, and possibly highlight those who do so on the Deed. The current draft of 4.0 anticipates such offers.
  • Include options in the Chooser for identification of known or potential third-party rights. This could take several different forms, including optional additional fields.
  • Make information about the possible existence of other rights more prominent on the Deed. The Deed currently is silent in this regard. There is also an open proposal to combine the Deed or replicate the Deed on the same page as the Legal Code, facilitating still more easy access to the Legal Code where details of limitations are made clear.
  • Create additional tools (such as options for additional metadata and/or symbols on the deed) to facilitate marking. It may be desirable for CC to design some visual indication a licensor may use when a work may be subject to additional rights and create additional tools for licensors and platforms who wish to use this marking.
  • Additional FAQs and best practice guidelines from CC. Licensors are already admonished to be careful before applying CC licenses, in the FAQs, at the top of the new Chooser and (on a dedicated page linked to from the FAQs Before Licensing#Make_sure_you_have_the_rights). CC and its affiliates could create still more detailed guides, highlight those more prominently on the Chooser and elsewhere, and engage in outreach to licensors promoting best practices and how-to documents on how to identify and clear rights, and mark their works in a more informative manner for licensees.

Proposals for disclaimer of warranties in 4.0

For ease of reference on discussion lists, please do not alter proposal numbers.

[Note: these proposals are not necessarily mutually exclusive]

Disclaimer Proposal No. 1:

  • Pros:
  • Cons:

Please add other Disclaimer proposals here, and number them sequentially.