After the plenary ....

11 Apr 2017

... 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

  • Bridget Almas's picture

    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.

    On 04/11/2017 06:37 AM, ThomasZastrow wrote:
    > ... 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
    >

  • Tom Demeranville's picture

    Author: Tom Demeranville

    Date: 12 Apr, 2017

    There is also JSON api, which I know is used by Datacite.
    http://jsonapi.org/

    Tom.

    On Wed, Apr 12, 2017 at 2:34 PM, balmas wrote:

    > 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.
    >
    > On 04/11/2017 06:37 AM, ThomasZastrow wrote:
    >
    >> ... 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
    >>
    >>
    >
    > --
    > Full post: https://www.rd-alliance.org/group/research-data-collections-
    > wg/post/after-plenary
    > Manage my subscriptions: https://www.rd-alliance.org/mailinglist
    > Stop emails for this post: https://www.rd-alliance.org/ma
    > ilinglist/unsubscribe/55992
    >
    >

  • Tobias Weigel's picture

    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

    On 12.04.2017 16:03, tom demeranville wrote:
    > There is also JSON api, which I know is used by Datacite.
    > http://jsonapi.org/
    >
    > Tom.
    >
    > On Wed, Apr 12, 2017 at 2:34 PM, balmas > wrote:
    >
    > 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.
    >
    > On 04/11/2017 06:37 AM, ThomasZastrow wrote:
    >
    > ... 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
    >
    >
    >
    > --
    > Full post:
    > https://www.rd-alliance.org/group/research-data-collections-wg/post/afte...
    >
    > Manage my subscriptions: https://www.rd-alliance.org/mailinglist
    >
    > Stop emails for this post:
    > https://www.rd-alliance.org/mailinglist/unsubscribe/55992
    >
    >
    >
    >
    >
    > --
    > Full post:
    > https://www.rd-alliance.org/group/research-data-collections-wg/post/afte...
    > Manage my subscriptions: https://www.rd-alliance.org/mailinglist
    > Stop emails for this post:
    > https://www.rd-alliance.org/mailinglist/unsubscribe/55992

    --
    Dr. Tobias Weigel
    Abteilung Datenmanagement

    Deutsches Klimarechenzentrum GmbH (DKRZ)
    Bundesstraße 45 a • 20146 Hamburg • Germany

    Phone: +49 40 460094-104
    Email: weigel@dkrz.de
    URL: http://www.dkrz.de
    ORCID: orcid.org/0000-0002-4040-0215

    Geschäftsführer: Prof. Dr. Thomas Ludwig
    Sitz der Gesellschaft: Hamburg
    Amtsgericht Hamburg HRB 39784

submit a comment