[odc-discuss] ODbL Release Candidate out

Wed Apr 29 22:36:46 UTC 2009

Hi everyone,

Apologies for brevity, but the Release Candidate of the ODbL is now up.
<http://www.opendatacommons.org/wp-content/uploads/2009/02/odbl_10_rc.zip 
 >

Co-ment text at:
<http://www.co-ment.net/text/1123/>

Announcement at
<http://www.opendatacommons.org/2009/04/29/open-database-license-odbl-v10-release-candidate-available/ 
 >

(and inline below)
=====
The Open Database License (ODbL) v1.0 "Release Candidate" is now  
available at:

<http://www.opendatacommons.org/licenses/odbl/>

This updated version of the license incorporates a whole set of  
changes arising out of the [earlier comments period](/2009/02/27/open- 
database-license-draft-available-for-comments/) and the main changes  
are summarized below.

As the naming suggests, we believe this text is now very close to a  
"production-ready" 1.0 license. To allow interested individuals and  
communities time to review the latest set of changes, as well as to  
provide an opportunity to catch any last minute "bugs", there will be  
a **1 week comment period** starting today and ending at midnight next  
Wednesday (6th May). **Full details on how to comment can be found on  
the [ODbL home page][odbl-home].**

In preparation for the 1.0 release we have also prepared detailed  
instructions on how to apply the license which can also be found on  
the [ODbL home page][odbl-home]. Any feedback on these is also very  
welcome.

Finally, we'd like to take this opportunity to say a big thank-you to  
everyone who contributed to that process as well as special thank-you  
to [Jordan Hatcher](http://www.jordanhatcher.com/), advisory board  
member and the person primarily responsible, not only for creating the  
original version of this license, but preparing this latest revision.

http://www.opendatacommons.org/licenses/odbl/

### Summary of Changes

For the license, specific changes include:

   1. A variety of typos, grammar fixes and minor renaming
   2. Change "Publicly Convey" to "Use" as Trigger for SA
   3. Clarify "Publicly Convey"
   4. Change from "Data" to "Contents" for contents of DB.
   5. Introduction of proxy for specification of compatible licenses
   6. Clarification of what is required when making available of  
derivatives
   8. Reinstatement of terminated rights if breach ceases
   9. Move "How To Apply" section to website (not strictly part of  
license)

We have also prepared several new FAQs to address issues that were  
raised during the comment process, including:

   * Choice of Law
   * Enforceability
   * Confusion
   * Substantial
   * Upgrading (updated)

http://www.opendatacommons.org/faq/licenses/
=====

Thanks

~Jordan
____
Mr. Jordan S Hatcher, JD, LLM

jordan [at] opencontentlawyer dot com

More details at:
<http://www.jordanhatcher.com>

Open Data at:
<http://www.opendatacommons.org>