Hi, I'm working on a small COMPOSITION generation service that will generate valid openEHR instances in XML, providing an OPT.
Playing around with some tests, I detected the Template Designer exports the attributes of the INSTRUCTION in a different order than the specified by the openEHR XSD. The OPT has "activities" before "protocol", and in the XSD those are in the inverse order. I'm not sure if this is a bug in the TD or if we shouldn't expect the OPT to have the same attribute ordering as the one defined in the XSD. If this is a bug, I will raise it in JIRA. Just wanted to confirm firm. -- Kind regards, Eng. Pablo Pazos Gutiérrez http://cabolabs.com
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
