Hi Bert, Have a look at what Ripple is doing in terms of 'meaningful APIs'.
See http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/2018-February/014799.html Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: [email protected] twitter: @ianmcnicoll Co-Chair, openEHR Foundation [email protected] Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On Mon, 16 Jul 2018 at 15:06, Bert Verhees <[email protected]> wrote: > On 16-07-18 15:56, Bert Verhees wrote: > > But again, the starting point must be the API's defined, maybe in a > > transformerable language like swagger, which seems to connect well to > > the OpenAPI initiative.(I never liked swagger much, but my last > > experience with it was from years ago, maybe it is better now) > > > > And then you mentioned BMM, I don't know about that. I should look at > > it, I saw your other email. Do you have somewhere a document why BMM > > is so good? > > The latest version of Open API (swagger became the Open API) > > https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md > > > _______________________________________________ > openEHR-technical mailing list > [email protected] > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
