-
Notifications
You must be signed in to change notification settings - Fork 114
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
W3C CSV on the web recommendations #984
Comments
Thanks for the suggestion @timrobertson100. We are actually drafting an overview on the differences between CSVW and Data Package and we will add it to the documentation very soon! We'll include the points you suggested on governance, future roadmap, maintenance and the state of tool development. I'll ping you here (and close this issue) once we have the overview up on the website. Great to know about your future plans for table schemas. |
Hi @timrobertson100, @peterdesmet pushed a PR outlining the difference between DP and CSVW, you can preview the page here: https://csvw.datapackage-6gp.pages.dev/guides/data-package-csvw/ Here are some additional information on the roadmap and adoption: Technical roadmap The main focus of the project for next few years will be in the realm of implementations, integrations, and extensions. As the standard already has a mature foundation in its core specifications and decent software implementations, it will focus on working with key data repositories like Zenodo or CKAN to adopt the standard natively, as well as on improving software implementations and adding new ones, especially visual such as Open Data Editor developed by Open Knowledge Foundation, fully-featured Data Package based editor. Facilitating Data Package extensions is another important direction to the project, as there are already a few very prominent ones like Camera Trap Data Package, and Gapminder DDF. The project is going to simplify the process of creating extensions and end-user usage. The project will also work with different working groups to support the implementation of domain-specific extensions. Perceived adoption Among the projects that adopted the Frictionless Data Package standard, here are some notable ones:
Hope this helps. Let us know if you have other questions and what your plans end up being regarding Table Schema. |
Wow, that was fast. Thank you very much We'll start digesting this. Under the adoption section, you are very welcome to list our repository software; perhaps linking to our news item. |
Thanks to @peterdesmet huge effort the CSVW comparison has been just published - https://datapackage.org/guides/csvw-data-package/ 🎉 |
Thank you all very much for putting this together. It's impressive indeed. |
A good addition to datapackage.org might be a summary of the differences between its approach and W3C CSVW recommendations, along with any other relevant information to help guide decisions on which is best to adopt.
We are looking to evolve our CSV guidelines within the Darwin Core standard and are keen to align with an established framework for table schemas. We’re exploring the differences between the guidelines but would appreciate any thoughts on things like governance, future roadmap, maintenance and the state of tool development that might be also relevant to a decision. We presume others may be in a similar position so thought it worth suggesting to document this on the site.
People from Darwin Core have been involved in both activities; we provided a use case for csvw and @peterdesmet is an active maintainer of both Darwin Core and datapackage.
Thank you very much.
The text was updated successfully, but these errors were encountered: