Complain over the last years is that RM XML Schema files are not usable other than validating COMPOSITION, VERSION, etc. This is due to (local) type declaration in the some of the schema: ... <xs:include schemaLocation="Content.xsd"/> <xs:element name="composition" type="COMPOSITION"/> <xs:complexType name="COMPOSITION"> ....
The wish is to have RM types defined into reusable schema files, while maintaining current functionality of current schema (validating XML messages). This will allow openEHR implementers to use schema also generate code, and at the same time will open the possibility to add other missing RM classes to ITS-XML repo.
Changes this big on the schema can be potentially troublesome for us, although everything should be fine as I think we have dealt with these kinds of changes in the past (specially schemaLocation pointing to arbitrary paths). I'll check the schemas and comment on this
Complain over the last years is that RM XML Schema files are not usable other than validating COMPOSITION, VERSION, etc. This is due to (local) type declaration in the some of the schema:
...
<xs:include schemaLocation="Content.xsd"/>
<xs:element name="composition" type="COMPOSITION"/>
<xs:complexType name="COMPOSITION">
....
The wish is to have RM types defined into reusable schema files, while maintaining current functionality of current schema (validating XML messages). This will allow openEHR implementers to use schema also generate code, and at the same time will open the possibility to add other missing RM classes to ITS-XML repo.