[open-science] Open Database License (ODbL) v1.0 Release Candidate Available

Rufus Pollock rufus.pollock at okfn.org
Thu Apr 30 09:01:11 UTC 2009


Open Data Commons have released a v1.0 "Release Candidate" of  the
"Open Database License" (ODbL):

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

Full announce at:

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

(and inline below). Apologies in advance for any cross-posting.

Rufus


## v1.0 RC ("Release Candidate") Announce

The Open Data Commons "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 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:

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

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. 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 the comments process as well as a special
thank-you to Jordan Hatcher, advisory board member and the person
primarily responsible, not only for creating the original version of
this license, but preparing this latest revision.

### 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 com (+ partially
inlined below):patible 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/




More information about the open-science mailing list