Merge pull request #454 from project-open-data/rebeccawilliams-licenseupdate

first pass at consolidating license info + adding PD URL

Author: Jamie Berryhill

Diff for: index.md

@@ -28,9 +28,7 @@ This section is a list of definitions and principles used to guide the project.
 
 2-3 [Open Data Glossary](glossary/) - The glossary of open data terms.
 
-2-4 [Open Licenses](open-licenses/) - The definition for open licenses.
-
-2-5 [Project Open Data Metadata Schema](/v1.1/schema/) - The schema used to describe datasets, APIs, and published data at agency.gov/data.
+2-4 [Project Open Data Metadata Schema](/v1.1/schema/) - The schema used to describe datasets, APIs, and published data at agency.gov/data.
 
 ----------------
 
@@ -46,9 +44,11 @@ Implementation guidance for open data practices.
 
 3-4 [Documenting APIs](/v1.1/api/) - The specific guidance for documenting APIs in the data catalogs.   
 
-3-4 [Frequently Asked Questions](/faq/) - A growing list of common questions and answers to facilitate adoption of open data projects.
+3-5 [Open Licenses](open-licenses/) - Open license guidance and examples. 
+
+3-6 [Frequently Asked Questions](/faq/) - A growing list of common questions and answers to facilitate adoption of open data projects.
 
-3-5 [Open Data Cross Priority (CAP) Goal](http://goals.performance.gov/opendata) - Information on the development of the Open Data CAP goal as required in the [Open Data Executive Order](http://www.whitehouse.gov/the-press-office/2013/05/09/executive-order-making-open-and-machine-readable-new-default-government).
+3-7 [Open Data Cross Priority (CAP) Goal](http://goals.performance.gov/opendata) - Information on the development of the Open Data CAP goal as required in the [Open Data Executive Order](http://www.whitehouse.gov/the-press-office/2013/05/09/executive-order-making-open-and-machine-readable-new-default-government).
 
 ----------------
 
@@ -119,21 +119,17 @@ Resources to provide guidance and assistance for each aspect of creating and mai
 
 5-3 [General Workflows for Open Data Projects](future-case-study/) - A comprehensive overview of the steps involved in open data projects and their associated benefits.
 
-5-4 [Open License Examples](license-examples/) - Potential licenses for data and content.
-
-5-5 [API Basics](api-basics/) - Introductory resources for understanding application programming interfaces (APIs).
+5-4 [API Basics](api-basics/) - Introductory resources for understanding application programming interfaces (APIs).
 
-5-6 [Data Release Safeguard Checklist](http://www.data.gov/sites/default/files/attachments/Privacy%20and%20Security%20Checklist.pdf) - Checklist to enable the safe and secure release of data.
+5-5 [Data Release Safeguard Checklist](http://www.data.gov/sites/default/files/attachments/Privacy%20and%20Security%20Checklist.pdf) - Checklist to enable the safe and secure release of data.
 
-5-7 [Digital PII Checklist](digital-pii-checklist/) - Tool to assist agencies identify personally identifiable information in data.
+5-6 [Digital PII Checklist](digital-pii-checklist/) - Tool to assist agencies identify personally identifiable information in data.
 
-5-8 [Applying the Open Data Policy to Federal Awards: FAQ](federal-awards-faq/) - Frequently asked questions for contracting officers, grant professionals and the federal acquisitions community on applying the Open Data Policy to federal awards.
+5-7 [Applying the Open Data Policy to Federal Awards: FAQ](federal-awards-faq/) - Frequently asked questions for contracting officers, grant professionals and the federal acquisitions community on applying the Open Data Policy to federal awards.
 
-5-9 [Example Policy Documents](policy-docs/) - Collection of memos, guidance and policy documents about open data for reference.
+5-8 [Example Policy Documents](policy-docs/) - Collection of memos, guidance and policy documents about open data for reference.
 
-5-10 [Example Data Hubs](/data-hubs) - Collection of department, agency, and program data sites across the federal government.
-
-5-11 [Licensing policies, principles, and resources](/licensing-resources) - Some examples of how government has addressed open licensing questions.
+5-9 [Example Data Hubs](/data-hubs) - Collection of department, agency, and program data sites across the federal government.
 
 ----------------
 
@@ -157,7 +153,9 @@ Case studies of novel or best practices from agencies who are leading in open da
 
 6-8 [USAID Crowdsourcing to Open Data](http://transition.usaid.gov/our_work/economic_growth_and_trade/development_credit/pdfs/2012/USAIDCrowdsourcingCaseStudy.pdf) - A case study that shows how USAID invited the "crowd" to clean and geocode a USAID dataset in order to open and map the data.
 
-6-9 [Centers for Medicare & Medicaid Services (CMS) Data and Information Products](http://www.cms.gov/Research-Statistics-Data-and-Systems/Research/ResearchGenInfo/Downloads/CMS-Data-and-Information-Products.pdf) - a case study of how CMS is transitioning to a data-driven culture, including the creation of a new office for information products and data analytics, the release of open data summarizing provider utilization and payment information, and the responsible disclosure of restricted use data to qualified parties.  
+6-9 [Centers for Medicare & Medicaid Services (CMS) Data and Information Products](http://www.cms.gov/Research-Statistics-Data-and-Systems/Research/ResearchGenInfo/Downloads/CMS-Data-and-Information-Products.pdf) - a case study of how CMS is transitioning to a data-driven culture, including the creation of a new office for information products and data analytics, the release of open data summarizing provider utilization and payment information, and the responsible disclosure of restricted use data to qualified parties.
+
+6-10 [Licensing policies, principles, and resources](/licensing-resources) - Some examples of how government has addressed open licensing questions.
 
 **For Developers: [View all appendices](http://github.com/project-open-data/) (and source)**
 

Diff for: license-examples.md

@@ -2,9 +2,20 @@
 layout: default
 title: Open Licenses
 permalink: /open-licenses/
+redirect_from: /license-examples/
 filename: licenses.md
 ---
 
+The [Federal Open Data Policy](https://project-open-data.cio.gov/policy-memo/#c-ensure-information-stewardship-through-the-use-of-open-licenses) states: *"Agencies must apply open licenses, in consultation with the best practices found in Project Open Data, to information as it is collected or created so that if data are made public there are no restrictions on copying, publishing, distributing, transmitting, adapting, or otherwise using the information for non-commercial or for commercial purposes."* The [Project Open Data Metadata Schema](https://project-open-data.cio.gov/v1.1/schema/) provides a `license` field which is defined as *"the license or non-license (i.e. Public Domain) status with which the dataset or API has been published"* and [must be input as a URL](https://project-open-data.cio.gov/v1.1/schema/#license). Below is guidance and example URLs for properly documenting the license or non-license of your agency's data in accordance with the open data policy.
+
+## U.S. Public Domain 
+
+Data and content created by government employees within the scope of their employment are not subject to domestic copyright protection under [17 U.S.C. § 105](http://www.copyright.gov/title17/92chap1.html#105). Government works are by default in the U.S. Public Domain. If no other open license applies, the following URL should be used for the dataset's `license` field: 
+
+* [U.S. Public Domain](http://www.usa.gov/publicdomain/mark/1.0/), e.g. `"license":"http://www.usa.gov/publicdomain/mark/1.0/"`
+
+## Open Licenses  
+
 Open licenses grant permission to access, re-use, and redistribute a work with few or no restrictions. A license is open if it satisfies the following conditions:
 
 * *Reuse*. The license must allow for reproductions, modifications and derivative works and permit their distribution under the terms of the original work. The rights attached to the work must not depend on the work being part of a particular package. If the work is extracted from that package and used or distributed within the terms of the work’s license, all parties to whom the work is redistributed should have the same rights as those that are granted in conjunction with the original package.
@@ -13,4 +24,30 @@ Open licenses grant permission to access, re-use, and redistribute a work with f
 
 * *No Discrimination against Persons, Groups, or Fields of Endeavor*. The license must not discriminate against any person or group of persons. The license must not restrict anyone from making use of the work in a specific field of endeavor. For example, it may not restrict the work from being used in a business, or from being used for research.
 
-* [Examples of open licenses](http://project-open-data.github.io/license-examples/).  
+### Examples of Open Licenses
+
+When purchasing data or content from third-party vendors, however care must be taken to ensure the information is not hindered by a restrictive, non-open license. In general, such licenses should comply with [the open knowledge definition](http://opendefinition.org/okd/) of an open license. Several examples of open licenses for potential use by agencies are listed below:
+
+#### Data Licenses
+* [Open Data Commons Public Domain Dedication and Licence (PDDL)](http://opendatacommons.org/licenses/pddl/1.0/), e.g. `"license":"http://opendatacommons.org/licenses/pddl/1.0/"`
+* [Open Data Commons Attribution License](http://opendatacommons.org/licenses/by/1.0/), e.g. `"license":"http://opendatacommons.org/licenses/by/1.0/"`
+* [Open Data Commons Open Database License (ODbL)](http://opendatacommons.org/licenses/odbl/1.0/), e.g. `"license":"http://opendatacommons.org/licenses/odbl/1.0/"`
+
+#### Content Licenses
+* [Creative Commons BY, BY-SA, or CC0](http://creativecommons.org/choose/)
+    * e.g. `"license":"https://creativecommons.org/licenses/by/4.0/"`
+    * e.g. `"license":"http://creativecommons.org/publicdomain/zero/1.0/"`
+* [GNU Free Documentation License](http://www.gnu.org/licenses/fdl-1.3.en.html), e.g. `"license":"http://www.gnu.org/licenses/fdl-1.3.en.html"`
+
+## U.S. Public Domain
+* [U.S. Public Domain](http://www.usa.gov/publicdomain/mark/1.0/), e.g. `"license":"http://www.usa.gov/publicdomain/mark/1.0/"`
+
+## Worldwide Public Domain Dedication
+* [Creative Commons CC0 Public Domain Dedication](http://creativecommons.org/publicdomain/zero/1.0/), e.g. `"license":"http://creativecommons.org/publicdomain/zero/1.0/"`
+* [Open Data Commons Public Domain Dedication and License (PDDL)](http://opendatacommons.org/licenses/pddl/1.0/), e.g. `"license":"http://opendatacommons.org/licenses/pddl/1.0/"`
+
+## More Information
+* *[Copyright and Other Rights Pertaining to U.S. Government Works](http://www.usa.gov/copyright.shtml)*
+* *[Licensing Policies, Principles, and Resources: Examples of how government has addressed open licensing questions](https://project-open-data.cio.gov/licensing-resources/)*
+* *[Extended list of conformant licenses](http://opendefinition.org/licenses/)*
+

Diff for: licenses.md

@@ -5,7 +5,7 @@ permalink: /unknown-license/
 filename: unknown-license.md
 ---
 
-This page is meant to serve as a landing page and placeholder for licenses that were specified by name using the [Project Open Data schema v1](/schema/#license) and were automatically converted to a URL for [Project Open Data schema v1.1](/v1.1/schema/#license). Further guidance on specifying licenses (or non-licenses) will be continually updated on the [license examples](/license-examples/) page.
+This page is meant to serve as a landing page and placeholder for licenses that were specified by name using the [Project Open Data schema v1](/schema/#license) and were automatically converted to a URL for [Project Open Data schema v1.1](/v1.1/schema/#license). Further guidance on specifying licenses (or non-licenses) will be continually updated on the [license examples](/open-licenses/) page.
 
 <h3 id="legacy-license"></h3>
 <h3 id="legacy-license-url"></h3>
@@ -18,4 +18,4 @@ This page is meant to serve as a landing page and placeholder for licenses that
         document.getElementById("legacy-license").innerHTML='<span style="color:#666">License name: </span>' + legacy_license;
         document.getElementById("legacy-license-url").innerHTML='<span style="color:#666">License URL: </span>' + window.location;
     }
-</script>
+</script>

Diff for: unknown-license.md

@@ -586,7 +586,7 @@ Dataset Fields {#Dataset}
 **Cardinality** | (0,1)
 **Required** | Yes, if applicable
 **Accepted Values** | String (URL)
-**Usage Notes** | See [list of license-free declarations and licenses](/license-examples/).
+**Usage Notes** | See [list of license-free declarations and licenses](/open-licenses/).
 **Example** |  `{"license":"http://creativecommons.org/publicdomain/zero/1.0/"}`
 
 {: .table .table-striped #modified}
@@ -771,4 +771,4 @@ Additional Information
 ----------------------
 
 * [Template and Sample Files (CSV and JSON format)](/v1.1/metadata-resources/)
-* [DCAT](http://www.w3.org/TR/vocab-dcat/)
+* [DCAT](http://www.w3.org/TR/vocab-dcat/)