- From: Jim J. Yang via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Jun 2021 09:55:23 +0000
- To: public-dxwg-wg@w3.org
Thanks for the suggestion, @smrgeoinfo. Yes, we do recommend using OpenAPI. However, we need to support DataServices which are described using other description languages as well, among others [WSDL20](https://www.w3.org/TR/wsdl20/) and [wadl](https://www.w3.org/Submission/wadl/) from W3C. As stated above, you need to know formats/mediaTypes of a DataService, already when you _decide if_ a DataService is (re)usable. My main point which might not be clear enough in my proposal above, is, _inside_ the catalog, our user may need to: - Know formats/mediaTypes of a DataService (instead of being forced to read an external endpointDescription, as @oystein-asnes also pointed out in [Issue #1005](https://github.com/w3c/dxwg/issues/1055)). - Sort/query DataServices according to formats/mediaTypes. We need these values stored _in_ the catalog instead of extracting them from external endpointDescriptions (which are based on different description languages) on the fly, each and every time a user needs to display or sort/query on formats/mediaTypes. -- GitHub Notification of comment by jimjyang Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1381#issuecomment-860557062 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 14 June 2021 09:55:42 UTC