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

add swagger for the api description? #15

Open
seralf opened this issue Nov 25, 2014 · 3 comments
Open

add swagger for the api description? #15

seralf opened this issue Nov 25, 2014 · 3 comments

Comments

@seralf
Copy link
Contributor

seralf commented Nov 25, 2014

i wonder if the current format for the api.json is a standard format, compatibile with CKAN.
If not, what about using the javascript, "static" version of the swagger api, instead?
http://swagger.io/

it could give access to a simple HTML documentation without much effort

@rlafuente
Copy link
Contributor

That's a good question. I think @metaodi might have some helpful insights here, since he took care of the API implementation.

@metaodi
Copy link
Contributor

metaodi commented Nov 25, 2014

I like the idea a lot, I'll look into this.

The current API is nothing else but the concatenated datapackages of all the datasets on the portal. Because we only have static files there are not very many possibilities. I try to find a description so that swagger can be used. Ideally we'll have a separate route for each dataset.

@seralf
Copy link
Contributor Author

seralf commented Nov 25, 2014

yes and they recently put up an online editor to help produce the json
description which can be consumed by the html front (the other options is
for the server side annotations, if/when you have one, but it's not the
case here :-)

2014-11-25 20:13 GMT+01:00 Stefan Oderbolz [email protected]:

I like the idea a lot, I'll look into this.

The current API is nothing else but the concatenated datapackages
http://dataprotocols.org/data-packages/ of all the datasets on the
portal. Because we only have static files there are not very many
possibilities. I try to find a description so that swagger can be used.
Ideally we'll have a separate route for each dataset.


Reply to this email directly or view it on GitHub
#15 (comment)
.

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

3 participants