Difference between revisions of "Versioning to 3.0"

From Creative Commons
Jump to: navigation, search
(created Versioning to 3.0 page for Legal Lead reference)
 
(Technical requirements)
Line 13: Line 13:
  
 
# Transform the final version 3.0 license into the possible 6 different licenses.
 
# Transform the final version 3.0 license into the possible 6 different licenses.
# Start with the by-nc-sa version 3.0 un-ported legalcode XHTML (save the un-ported by-nc-sa 3.0 legal code as html). Do not attempt to generate license html from Microsoft Word. It produces junk html, which will be returned to you and you will have to redo.
 
# Produce the 6 license files named in the form:
 
  
{license-code}_{version}_{country-code}.html
+
# Start with the by-nc-sa version 3.0 un-ported legalcode XHTML.  
  
e.g.
+
# Follow the steps listed [[Project_leads_finalize_licenses_and_arrange_technical_requirements#Creating_the_XHTML_files | here]] to generate and validate the XHTML files.
 
 
by-nc-sa_3.0_at.html
 
by-nc_3.0_at.html
 
 
 
If your jurisdiction will have legalcode in multiple languages, name the 6 times files in the form:
 
 
 
{license-code}_{version}_{country-code}_{language_code}.html
 
 
 
e.g.
 
 
 
by-nc_3.0_ca_en.html
 
by-nc_3.0_ca_fr.html
 
# Please validate the XHTML using the W3C validator at http://validator.w3.org. The XHTML must be modeled after the XHTML used in other CC licenses, incl. using the same stylesheet. The XHTML provided must be valid according to the W3C Markup Validator (http://validator.w3.org)
 
  
 
# Send the 6 licenses as UTF8-encoded XHTML to CCi.  
 
# Send the 6 licenses as UTF8-encoded XHTML to CCi.  

Revision as of 11:28, 23 May 2008

This page provides important information for the CC Legal Leads when versioning up to 3.0

After long and fruitful discussions, and a heavy, but delicious cake in the shape of a 3, courtesy of CCi affiliates, the new CC license version 3.0 was launched on February 23rd, 2007. Many, many thanks to Mia Garlick and all of you who have particpated in the process! It was announced on our blog and outlined in more detail on our wiki.

Content requirements

  1. Work through the check-list, the “Working document” and CS document
  2. Produce first draft with help of the three documents available on this wiki, re-translate to English (if needed), and prepare English explanation of substantial legal changes.
  3. Send re-translated license and English explanation of substantial legal changes to the Director of CCi for discussion.
  4. Optional: Conduct a public discussion. After public discussion produce final draft and send to CCi.

Technical requirements

  1. Transform the final version 3.0 license into the possible 6 different licenses.
  1. Start with the by-nc-sa version 3.0 un-ported legalcode XHTML.
  1. Follow the steps listed here to generate and validate the XHTML files.
  1. Send the 6 licenses as UTF8-encoded XHTML to CCi.
  1. CC Tech will check the XHTML files and send them back to you for final proof reading. Please check the documents very carefully as no further changes will be possible once they have been published.

Versioning documents

  1. The checklist for easier versioning: Version 3.0 Checklist (updated)]]
  1. Version 3.0 Working Document Version 3.0 working document (updated)]]
  1. A document referenced in the checklist, about the collecting society language is here: Collecting society language (updated)]]
  1. A document explaining the reasoning behind the proposed harmonization with regards to "sui generis database rights" in the European Licenses: Database Rights Note]]

Additional information

A longer article explaining the changes is here: [Version 3.0]


Please be aware that there are specific steps involved, depending on if you have already ported a previous license version or if you are in the process of porting CC licenses to your jurisdiction and plan to use version 3.0. Please contact Catharina Maracke directly if you plan on versioning to 3.0