# OpenAPI schemas generated from BMM files

**URL:** <https://discourse.openehr.org/t/openapi-schemas-generated-from-bmm-files/2116>\
**Category:** Platform\
**Tags:** rest-apis\
**Created:** [26 November 2021 12:54 UTC](https://discourse.openehr.org/t/openapi-schemas-generated-from-bmm-files/2116 "2021-11-26T12:54:08Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![erik.sundvall](https://discourse.openehr.org/user_avatar/discourse.openehr.org/erik.sundvall/32/1961_2.png) [@erik.sundvall](https://discourse.openehr.org/u/erik.sundvall)\
**Post date:** [29 November 2021 08:59 UTC](https://discourse.openehr.org/t/openapi-schemas-generated-from-bmm-files/2116/9 "2021-11-29T08:59:00Z")

</div>

> [@borut.jures](#):
>
> Maybe what they are asking for isn’t the best approach (see the paragraph about using AM model instead of intermediary formats above). Sometimes cleaner architecture makes applications easier to develop, maintain and upgrade.

Yes that is certainly true for some use cases. I am not sure what you are suggesting, but if it is to use paths in a way similar to what is described on a wikipage from 2012 by @thomas.beale [https://openehr.atlassian.net/wiki/spaces/spec/pages/4915205/Ocean+EhrGate+-+Composition+Builder+programming+example](https://openehr.atlassian.net/wiki/spaces/spec/pages/4915205/Ocean+EhrGate+-+Composition+Builder+programming+example), then note @heath.frankel’s comment at the bottom of that page regarding what developers not familiar with openEHR thought:

 ![image](https://discourse.openehr.org/uploads/default/original/2X/d/d7a54cea7246dcf52656059a4a13a9105ef56097.png)

---

_[View the full topic](https://discourse.openehr.org/t/openapi-schemas-generated-from-bmm-files/2116)._