You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @ttjaden,
great work to free the hp data and make it available for all kinds of modelling.
As an expert on open data licenses I would like to help to improve on the data publication.
At the moment, the resulting data is part of the repository and thus licensed under the MIT license.
While this is an excellent choice for the open-source software, it is not suitable for the resulting (open) data.
If you want to go deep into the open data licenses I can recommend this tutorial:
CC-BY-4.0 a well known and standard open data license. Users only need to attribute correctly.
ODbL-1.0 an OSM-like copyleft license. When people use and extend the data, they need to share the improvements. Downside: it can prevent people from using it.
My personal view would be option 1 for this data set, because the list has been generated by a script, not a manual collection and extraction of the pdf data (correct me if I am wrong).
In addition I suggest to create a standardised metadata string that contains all necessary information in machine and human readable formats. The OEMetadata was developed for this purpose:
Hi @ttjaden,
great work to free the hp data and make it available for all kinds of modelling.
As an expert on open data licenses I would like to help to improve on the data publication.
At the moment, the resulting data is part of the repository and thus licensed under the MIT license.
While this is an excellent choice for the open-source software, it is not suitable for the resulting (open) data.
If you want to go deep into the open data licenses I can recommend this tutorial:
As a tldr, I would recommend two license options:
My personal view would be option 1 for this data set, because the list has been generated by a script, not a manual collection and extraction of the pdf data (correct me if I am wrong).
In addition I suggest to create a standardised metadata string that contains all necessary information in machine and human readable formats. The OEMetadata was developed for this purpose:
I would be happy to assist you in creating the string, review and publish it.
The text was updated successfully, but these errors were encountered: