Talk:Open Content Licensing/Home

From WikiEducator
Jump to: navigation, search


Thread titleRepliesLast modified
Cc-by-sa vs cc-by vs cc0 vs pd002:29, 4 November 2010
Why stop at CC-BY on the road to freedom?023:58, 13 October 2010

Cc-by-sa vs cc-by vs cc0 vs pd

This is a question for those involved in this initiative and/or a possible learning activity to adapt and include among the resources.

  • Which license is more supportive of freedom to learn for all: cc-by vs cc-by-sa ?
    • Does fewer restrictions always imply more freedom in the long run?
      • What "freedom" does the "sa" restriction restrict?
      • To protect and encourage growth of the commons, which of these two licenses would you recommend?
        • What assumptions are you making?
      • Would public domain or cc0 be even better (or worse) in terms of freedom to learn for all in the long term? (explain your answer).


  • Imagine a proprietary company developing intelligent agents to automatically find, package, attribute, summarise, translate and sell resultant content under an all rights reserved license and restricting access only to whom the company chooses.
    • Would it be permissible (legally) to incorporate cc-by content? cc-by-sa content? Public domain content? Cc0 content?
      • Which clauses in the licences/deeds permit/disallow this?
KTucker (talk)02:15, 4 November 2010

Why stop at CC-BY on the road to freedom?

Recall that the rationale for using cc-by-sa includes growing the commons and encouraging a culture of collaboration and sharing (share and share alike). It is tactical.

With cc-by the resources may be adapted (or not) and incorporated into 'all rights reserved' mixes and sold - an incentive to those who just want to make money out of other people's work and impose restrictions.

Having one license cc-by-sa across all resources makes it easy for people to mix without having to think too much. For example, it is easy to copy/paste/adapt (mix) text from multiple WikiEducator/Wikipedia pages - but easy to miss a potentially incompatible difference in licensing (e.g. if WikiEducator also includes cc-by text).

It is possible that

(1) The share-alike tactic is unnecessary. Successful examples include PLOS, Connexions, ..., and as far as I know, no-one has demonstrated that the tactic works (except possibly Wikpedia) or can explain why the tactic nolonger applies for WikiEducator (it does still apply for libre software[1]).

(2) the (WikiEducator/...) user base is sophisticated enough to handle such license issues (and not mix cc-by-sa content from WikiEducator/Wikipedia etc. into cc-by resources on WE/cnx/...).

If both (1) and (2) apply (i.e. share-alike is nolonger a necessary tactic for growing the WikiEducator commons and our users, including new future users, are savvy enough wrt licensing), then why stop at cc-by on the road to freedom?

By doing so, copyright law is still being used to 'control' an aspect of human behaviour which in my opinion should be cultural.

Why not focus on CC0? The existing culture in academia will ensure attribution. The the resources for open content licensing project's intended guidelines could cover such cultural norms.

Technically, it is difficult to check if users mix cc-by-sa text content into cc-by resources (or cc0 resources).

For some time there have been tools and services available to catch plagiarists (e.g. Turnitin), and I have long wondered why these are not used in a positive way (tools to help learners/writers etc. to be more original, recall and reference sources and improve their writing). Such tools do exist now (e.g. ) and even Turnitin is marketing itself as preventative: "Prevent plagiarism. Engage students.".

It would be great to find/develop libre software alternatives (on account of costs, privacy issues, etc. - see for example: ) - as tools to assist authors.

So, perhaps we are becoming more enlightened, and cc0 would be the way to go now?

On WikiEducator, permitting cc0 content could also mean relaxing the requirement to login to edit (as does Wikipedia).

  1. See
KTucker (talk)23:54, 13 October 2010