Add the BMM 3.x specification to BASE. See http://www.openehr.org/releases/LANG/latest/bmm.html
Add specification for persistence form of BMM, http://www.openehr.org/releases/LANG/latest/bmm_persistence.html
One JSON example would be enough to show that the BMM is not ODIN-dependent, but if there is no tooling support for this, then do that in a later revision.
Somewhere in the intro we should probably mention something along the lines of: "Understanding of the BMM is not necessary in order to implement openEHR systems, if you are more comfortable using other available model formats, e.g. UML or openEHR libraries already implemented in a programming language. However if you want to auto-generate code stubs in a new language, understanding the BMM and using it as a machine readable source will save you time."
How about I add somewhere in section 7.1 (overview of Syntax -
http://www.openehr.org/releases/BASE/latest/docs/bmm/bmm.html#_overview_5 ) some statements about ODIN being one syntax, and an example showing JSON and YAML for one of the structures?
Agree on the second comment as well. Hopefully get to this today.
Add the BMM draft specification to BASE. See http://www.openehr.org/releases/BASE/latest/bmm.html
Add specification for persistence form of BMM, http://www.openehr.org/releases/BASE/latest/bmm_persistence.html