From eef3630ec1626cd5ea5b9a7237339f54712335cf Mon Sep 17 00:00:00 2001 From: Nicolas Dickinson Date: Wed, 23 Oct 2019 11:35:05 +0200 Subject: [PATCH] Updated Minutes for October 23rd 2019 (markdown) --- Minutes-for-October-23rd-2019.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/Minutes-for-October-23rd-2019.md b/Minutes-for-October-23rd-2019.md index e698c16..cf6d347 100644 --- a/Minutes-for-October-23rd-2019.md +++ b/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. \ No newline at end of file +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. \ No newline at end of file