You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure how you'd get Actions from an OPENAPI file. It defines a set of paths for the different resources offered by a 'RESTful' API, but the operations are the standard HTTP get, put, post, delete, options, head, patch and trace. Open API descriptions are designed for resource oriented REST service endpoints, and don't map well onto various legacy service implementations like the older OGC services.
For OGC, then perhaps we need a set standard templates.
Can't we map REST API calls documented in openApi to this spec? if not how is this done, so we can implemented it... many environments have an endpoint specification.
As a starting point, create a list of potential actions from an OPENAPI/swagger file
A different starting point would be to use the OPENAPI as the starting point for a tool description
The text was updated successfully, but these errors were encountered: