The Frictionless Data specification does not require a license property. Open data needs a license. I’m wondering why the license property isn’t required at either the package or resource levels? How would it be viewed if the app I’m making to create data packages required a license in datapackag…

@Stephen among other answers: Data Packages are designed for all types of data not just open data Someone may want to create a package they don’t yet know the license status of General point: the license field is indicative not binding (as stated in the spec) – though I guess in some cases the li…

A license is not mandatory in a data package but open data needs one

Frictionless Data

Stephen Split this topic December 25, 2017, 10:24pm 7

A post was split to a new topic: Open Data Business Models

Topic		Replies	Views
Applying licenses, waivers or public domain marks Frictionless Data	21	3506	September 3, 2020
Open License Requirements Global Open Data Index 2016	8	2674	January 10, 2017
What's an example of when more than one license is required in the licenses property? Frictionless Data	0	842	January 4, 2018
Help text and tool tips - 7. Openly licensed? Open Data Index	7	3751	August 11, 2015
A Public Domain Data Package Frictionless Data	2	963	October 24, 2017

A license is not mandatory in a data package but open data needs one

Related topics