The document discusses open data and RESTful publishing. It recommends structuring data in non-proprietary formats like CSV instead of images or Excel. An upcoming data adapter will allow for improved access, documentation, and semantics. The first stable release is scheduled for December 5th and interested parties can contribute on GitHub or contact the authors.

1. Follow the stars RESTful publishing of high level Open Data Miel Vander Sande (Ghent University – IBBT - MultimediaLab) Pieter Colpaert (iRail NPO)

2. Missionary work Spreading awareness make your stuff available on the web (whatever format)

3. Organising events Bringing data owners & consumers together make your stuff available on the web (whatever format)

4. Structure your data (e.g. excel instead of image scan of a table) Good example Open data in Vienna

5. Structure your data (e.g. excel instead of image scan of a table) But… we can always do better Business intelligence Direct access for Apps Community contact Automatic documentation More formats Semantics Feedback Versioning

6. Structure your data (e.g. excel instead of image scan of a table) But… with minimal effort for the data owner

7. A data adapter Improving the web’s serendipity PHP 5.3 RESTful Distributed

8. Non-proprietary format (e.g. csv instead of excel) One PUT request Feedback Versioning

9. Non-proprietary format (e.g. csv instead of excel) Business intelligence Automatic documentation

10. Web of things ready Identifying real world objects Use URI to identify, output RDF Name, Firstname Vander Sande, Miel Colpaert, Pieter URI URI URI Metadata Metadata Metadata

11. Elaborating your data Adding semantics Use URI to identify, output RDF RDF Serialising

12. Elaborating your data Adding semantics Use URI to identify, output RDF With optional basic ontology… Automatic enrichment Ontology mapping RDF Serialising Ontology sharing

13. First stable release The 5 th of December

14. Feeling adventurous? Fork us on Github! https://github.com/iRail/The-DataTank

15. Questions? [email_address] @pietercolpaert [email_address] @miel_vds Feel free to contact us: