After a couple of months of work, we can proudly publish the first production version (1.0) of Open Data Product Specification! The path to this point has been longer though.
The full longer story of the benefits and history in separate specification home page
Path to version 1.0
Jarkko Moilanen was invited to join the ranks of a data platform development company in Dec 2018. In May 2019 Jarkko had worked with multiple data operating companies and discovered the need to build new tools - business tools for data owners. This resulted in the creation of the Data Product Toolkit.
The toolkit however was somewhat crippled without underlying machine-readable data product standard; something that binds together business, technology, legal and ethical aspects of the data product. The idea of Open Data Product Specification was born around Sept 2019. However, the idea was buried under other development tasks and the dream almost died. Sept 2021 Jarkko resurrected the standardization idea and quickly drafted the first version of the specification in cooperation with Jussi Niilahti.
And here we are now! Version 1.0 has been published and is available openly for all to use. The specification is shared under Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.
Open Data Product Specification is a technical machine-readable data product metadata model. It defines the objects and attributes as well as the structure of digital data products. It has four build-in aspects:
Technical (infrastructure & access)
Business (pricing & plans)
Legal (licensing & IPR)
Ethical (privacy & mydata)
About the future - work continues
The development of the specification continues. The specification has gained a significant amount of interest from individuals and companies alike. We are having online meetings with several contributors during the coming weeks about expanding the cooperation. You can always toss us feedback and we happily apply any improvements to the model. You can find the feedback links from the Open Data Product Specification page.
The next steps to take at the practical level are:
Define a comprehensive ready-made schema for the model and publish is in selected Schema catalogs and as part of the specification
Create 1-2 use case + code examples to exemplify the benefits and usage of the specification.
Join us, contribute via Github, feedback, and just be posting the link to this page to your colleagues and friends.