Replace the RM Json Schemas with ones generated from BMM

[pieterbos]

Created using the code in https://github.com/openEHR/archie/pull/313

the RM version 1.0.3, 1.0.4 and 1.1.0 is included in this pull request. For each I added is a single-file version, the openehr_rm_1.1.0_all.json, plus one split up in multiple packages, just as the BMM files are organised.

There are some choices left to make, so leaving this as a Draft PR:

• I included the base file in the RM directories, instead of reusing a separate file.
• The json schemas itself contain possible types at the root of openehr json documents. COMPOSITION is an obvious choice, but currently this also contains ENTRY subclasses, as well as versions and several others. Are these the types we want to support?
• is this the way we want these files to be organised?
• these json schemas allow additional properties. I can easily generate them with additionalProperties: false at every place. that makes validation much more strict, and in fact that is what I use to validate the standards compliant output from Archie to see if it is properly compliant. Do we want that here as well?

Creating this, I encountered the following two small issues:

• four classes are missing in BMM, meaning they will also be missing in json schema. I created https://openehr.atlassian.net/browse/SPECPR-369 for that.
• ISO8601_TYPE , List, Array and Set are still left in the primitive types in the schema, even though they are not used

I will fix them soon, but I did not want to postpone creating this, to discuss whether this is the right approach, or whether things will need to be changed.

And of course descriptions are still missing. As soon as the BMM files contain the documentation, this can be regenerated with descriptions in place.

[sebastian-iancu]

As a suggestion, can you rename files/folder to follow the pattern: components/{component}/{release}/{package}/{file.json} or just components/{component}/{release}/{package.json}

e.g. components/RM/Release-1.1.0/Ehr/all.json or components/RM/Release-1.1.0/Ehr.json; components/RM/Release-1.1.0/Data_types/all.json or components/RM/Release-1.1.0/Data_types.json instead of components/RM/RM-1.1.0/openehr_rm_data_types_1.1.0.json

This will help future maintenance or additions of new files, plus is consistent with ITS-XML. On the other hand I see you made it compliant with ITS-BMM. components/RM/Release-1.1.0/openehr_rm_data_types_110.bmm

Which one you think is better (for present as well as future)?

[sebastian-iancu]

PR #10 was merged into master, this is not needed anymore