- From: ds-merck via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Jun 2020 08:38:57 +0000
- To: public-dxwg-wg@w3.org
Dear @andrea-perego, thanks a lot for the reply on this! I think one of the main points I have is that the data I want to catalog is not "on the web", as in "available via a REST API" (which I think is the focus of discussion also in [#1230](https://github.com/w3c/dxwg/issues/1230) Rather, data could be in an Oracle/Postgres/... database or a Hive big-data service reachable via a JDBC interface, which I think is the case in most enterprises for a substantial amount of datasets. For this data, it's not feasible to create a REST API/GraphQL/... wrapper around each JDBC interface, as the JDBC/ODBC interface itself already provides a ready-to-use interface for interoperability between a variety of systems. At the same time, I'd like to have the reference to the data machine-readable, e.g. only putting the connection information on a web page that is referenced in `dcat:accessURL` would not be sufficient from my perspective. So, it would be great to catalog these datasets sitting in a database using DCAT and it would be great to have a dedicated way of cataloging such JDBC/ODBC data sources (and maybe having an example of this at https://www.w3.org/TR/vocab-dcat-2/#collection-of-examples), as I think is is a very common need in corporate enterprises. What would be the best approach here? Do you think it's feasible with the current DCAT vocabulary or would some kind of extension be needed for this? I'm happy to jump on a call to discuss this topic further and share the background of the request. -- GitHub Notification of comment by ds-merck Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1240#issuecomment-647373305 using your GitHub account
Received on Monday, 22 June 2020 08:39:00 UTC