WASHWeb/WASHWeb-2019
0
0
Fork 0
Code Issues 17 Pull Requests Packages Projects 1 Releases Wiki Activity

Updated Minutes for October 23rd 2019 (markdown)

Nicolas Dickinson 2019-10-23 11:35:05 +02:00
parent 1237a43b03
commit eef3630ec1
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Minutes-for-October-23rd-2019.md

@ -21,4 +21,10 @@ Actions:
* What is the open packaging format we can use to store the registry data as a source
* How to get that data onto wikidata, what kind of layout, what kind of structure etc.
Again, this is about proving this is useful and worth pursuing.
Again, this is about proving this is useful and worth pursuing.
Post meeting notes on sharing the registry on the web for humans and machines:
* For WASHNote.com we can add a custom table to feed into pages and provide a quick and easy way to display registry data on WASHNote.com. However, ideally we can have https://washweb.org/registry/ID as the actual place where the data can be seen in a browser and read by a machine.
* Flask is a simple Python microserver environment we could use and implement quickly.
* In the past I worked on this with OpenAPI to define a simple REST API and implemented a demo in Flask and Connexion to serve the API from simple data tables (also included authentication): https://github.com/Stroomversnelling/monitoring_udb_resource_server
* Another option is existing syndication platforms and software packages: data.world / CKAN / etc.