11
Apr
2017
Groups audience:
... is of course before the next plenary ... ;-)
I just came across the OASIS OData specification which seems to be a
nice way of creating standardized, self-describing REST interfaces:
http://www.odata.org/
Some of this stuff should be easy adoptable to our collections API, some
would be harder, some makes no sense.
What do you think?
Best,
Tom
--
Dr. Thomas Zastrow
Max Planck Computing and Data Facility (MPCDF)
Gießenbachstr. 2, D-85748 Garching bei München, Germany
Tel +49-89-3299-1457
http://www.mpcdf.de
- Log in to post comments
- 5007 reads
Author: Bridget Almas
Date: 12 Apr, 2017
Hmm. I hadn't heard of OData before. Seems to be largely backed by
commercial providers (Microsoft, SAP). I did find a
odata->swagger/openapi converter...
I guess it would be worth looking at to see if it allows us to present
the API more clearly than OpenAPI/Swagger.
Author: Tom Demeranville
Date: 12 Apr, 2017
There is also JSON api, which I know is used by Datacite.
http://jsonapi.org/
Tom.
Author: Tobias Weigel
Date: 12 Apr, 2017
Well, I believe compatibility is generally a good thing to have, so it
might be worth looking into one of them and see whether we are erecting
some potential barriers. But I also see that there is a large overlap
and possibly unresolved competition, so the most reasonable path for now
that also takes us into the recommendation phase is to generally stick
with openAPI - I appreciate the general level of development there and
the transition from Swagger to openAPI is promising. Getting the final
details settled on the Swagger-based spec is one of the next top priorities.
Best, Tobias