Skip to content
This repository was archived by the owner on Jun 18, 2024. It is now read-only.

Latest commit

 

History

History
53 lines (36 loc) · 5.7 KB

licenses.md

File metadata and controls

53 lines (36 loc) · 5.7 KB
layout title permalink redirect_from filename
default
Open Licenses
/open-licenses/
/license-examples/
licenses.md

The Federal Open Data Policy 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 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. 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. 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:

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.

  • Redistribution. The license shall not restrict any party from selling or giving away the work either on its own or as part of a package made from works from many different sources. The license shall not require a royalty or other fee for such sale or distribution. The license may require as a condition for the work being distributed in modified form that the resulting work carry a different name or version number from the original work. The rights attached to the work must apply to all to whom it is redistributed without the need for execution of an additional license by those parties. The license must not place restrictions on other works that are distributed along with the licensed work. For example, the license must not insist that all other works distributed on the same medium are open. If adaptations of the work are made publicly available, these must be under the same license terms as the original work.

  • 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

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 of an open license. Several examples of open licenses for potential use by agencies are listed below:

Data Licenses

Content Licenses

U.S. Public Domain

Worldwide Public Domain Dedication

More Information