11 thoughts on “UKOER 2: Licences and encoding

  1. I must admit I’m very surprised that so few projects chose to use cc:by after it was strongly recommended by the programme. It would be interesting to do some follow up research to find why this has been the case.

  2. Pingback: UKOER 2: Technical synthesis introduction

  3. @Viv arguably, yes but as you note the trick is that is anyone using your content has to use By SA as well – in theory this makes things more open but because it forces anyone using your content to cascade the licence. However, users of your content can’t use either CC: BY SA NC to (in theory) prevent commercial use or use CC: BY to permit any form of use. It also means you can’t, for example, use most of the content from UKOER 1 and 2… [only CC: By and CC: By SA). It’s one of the reasons the programme tried to push CC: BY.

  4. Pingback: The OER Turn : Information Environment Team

  5. ok, this may be a slight tangent but it serves as good illustration of the tension in choosing a licence: Scott Leslie’s written a piece about possible licence choice impact on SEO http://www.edtechpost.ca/wordpress/2011/09/19/seo-as-enclosure/ – do you want your content to be as widely shared as possible (including by people who sell want to sell access to it) or do you want your site (as a source of open content) to be as prominent as possible?

  6. Pingback: UKOER 2: Licences and encoding | iTunes U as a Channel of Open Educational Resources | Scoop.it

  7. Pingback: UKOER 2: Licences and encoding | Open Educational Arts Practice | Scoop.it

  8. Pingback: UKOER 2: Licences and encoding | ORIOLE project | Scoop.it

  9. Pingback: UKOER 2: Licences and encoding | Creating Podcasts & Vodcasts for education | Scoop.it

  10. Pingback: UKOER 2: Licences and encoding | Open Education Resources | Scoop.it