-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Proposal] Retrofit the standards for Open Data, Open Standards #59
Comments
@christer-io has some inputs he has given another issue, I am linking that here its its relative. I am exploring the implications of accepting or rejecting the proposed change to standard.md. This should trigger a two week community input period that will end February 27. I suggest that we include some more specific language around data and file formats to ensure that indicator 8 is more specifically addressing the need for open and documented file and data formats. This change would be highly relevant for content and data being vetted against indicator 2. By being more specific we will ensure to avoid that a content repository/project that has content in an approved open license but at the same time use closed or undocumented file formats, making reuse difficult or impossible. An example of languages that could make indicator 8 more specific: "Open data and content must be made accessible in an open data or file format, including relevant metadata and documentation.". |
Adding relevant issues: #122 |
Adding relevant issues: #123 |
Adding relevant issues: #111 |
closing this issue, please follow #126 for all updates on this front. |
No description provided.
The text was updated successfully, but these errors were encountered: