Skip to content
This repository was archived by the owner on Mar 3, 2022. It is now read-only.

What about datasets, in addition to software #71

Closed
jameslaneconkling opened this issue Mar 22, 2016 · 8 comments
Closed

What about datasets, in addition to software #71

jameslaneconkling opened this issue Mar 22, 2016 · 8 comments

Comments

@jameslaneconkling
Copy link

This policy only addresses federally-funded software projects, but does not mention datasets generated by federally-funded projects. I know there is as much or more talk about opening up datasets--curious to know if there any complementary policies mandating the open licensing of datasets.

@mhogeweg
Copy link

hi, you'll be interested in Memorandum M-13-13 and the implementation guide over on the project open data site.

@jameslaneconkling
Copy link
Author

@mhogeweg thanks for the links.

Seems that M-13-13 is more of a best practices guide, given that there are not hard requirements for open licensing of datasets, if the agency in question chooses to categorize a dataset as enterprise data. No doubt a good foundation, though w/o requirements for obligating openness.

@jlberryhill
Copy link
Contributor

Thanks for the input, @jameslaneconkling and @mhogeweg. M-13-13 is formal policy and obliges agencies to assume a "by default" stance in opening data to the public. The goal of the Enterprise Data Inventory (EDI) is to catalog all data in the respective agency (i.e., enterprise), not only all data that @mhogeweg refers to as "enterprise data." You may also be interested in M-13-13's companion website Project Open Data, which provides best practices, tools, and resources for agencies. The draft Source Code Policy proposes a similar site called Project Open Source geared toward source code instead of data.

cc @justgrimes

@jameslaneconkling
Copy link
Author

@jlberryhill thanks for the link. By asking about obligations, I was wondering what the requirements were to justify keeping government-funded datasets behind a paywall, which are outlined in section D: Document if Data Cannot be Released. Thanks for sharing.

@jameslaneconkling
Copy link
Author

@jlberryhill is there anywhere in M-13-13 or elsewhere that documents the requirements dataset paywalls? Much of the discussion around the difference between public, restricted, and private data licensing has to do w/ issues of personal privacy and security, which would not apply to licensed datasets.

@jlberryhill
Copy link
Contributor

@jameslaneconkling -- Mind opening an issue on the Project Open Data issue tracker? There's an active open data community there that could also engage.

@jameslaneconkling
Copy link
Author

cross posted.... project-open-data/project-open-data.github.io#553

@jlberryhill
Copy link
Contributor

Thanks! I asked a member of the team to look into.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants