Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Component: Potential Actions from OpenAPI Spec #12

Open
valentinedwv opened this issue Mar 7, 2022 · 2 comments
Open

Component: Potential Actions from OpenAPI Spec #12

valentinedwv opened this issue Mar 7, 2022 · 2 comments

Comments

@valentinedwv
Copy link
Contributor

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

@smrgeoinfo
Copy link
Contributor

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.

@valentinedwv
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants