Hi all,
I've been working in the last 2 months on a new release for XML Schemas (XSDs). We had several discussions inside the SEC group and we also had several issues recorded in our JIRA environment, all about what needs to be changed and how. We reached a point where most of the intentions and planned actions are performed, but now we would like to have (some) more feedback from you, the community. It will help us proceed to final steps towards releasing these new schemas. If you did not follow or notice changes lately in the openEHR-ITS, here is a little explanation: The openEHR had for many years the RM 1.0.2 as the stable release, and a set of XML Schema files associated with it. These files were not always easy to find by newcomers, or sometimes not properly versioned controlled or not stored on right place (an ITS repository). With the release of RM 1.0.3 back in 2015 and lately the release of REST Api and the preparation and the release of RM 1.0.4 it became an urgency to address and tackle XSDs, and bring them up-to-date. In the last months of 2018 we split the ITS repository on github into smaller dedicated repos (ITS-XML, ITS-REST, ITS-BMM, ITS-JSON) so that we can have independent release of each of these technologies. Each of this repo is internally 'addressing' (implementing) one or more openEHR specification releases (i.e. RM 1.0.2, RM 1.0.3, etc., or 'latest'), but on the same time it has his own release schema, independent of openEHR spec releases. For instance ITS-XML is planned to be released as 2.0.0, whereas ITS-REST was recently released as 1.0.0, but both are related to RM 1.0.4 (beside others). If a repo is addressing more spec releases then you'll find their implementation as subfolders under their right component (RM, AM, BASE, etc.). If you will look in the XML repo, you will find the originals as a Release 1.0.2 tag (containing schemas as you were used to), and in the master-branch you'll find several folders like components/RM/Release-1.0.2, components/RM/Release-1.0.3, etc. Also, you will notice that the new schemas file names and their location are following more closely the specification components and chapters (IMs). Files are now just a collections of types, not intending to validate XML-documents or XML-elements directly. The idea was to allow reuse of these types or XSD files as a whole, and to have them overall in sync with the openEHR specs. This will perhaps open the door in the future to generate these schemas from UML/BMM models, but also ease maintenance. Some useful links: github repo: https://github.com/openEHR/specifications-ITS-XML original release 1.0.2: https://github.com/openEHR/specifications-ITS-XML/releases/tag/Release-1.0.2 Specs index: https://specifications.openehr.org/releases/ITS/latest/index CRs: https://openehr.atlassian.net/projects/SPECITS/versions/12520/tab/release-report-all-issues slack: https://openehrspecs.slack.com/messages/CCNA5F3M3 (#xml_schemas) If you actively use the openEHR XML schemas in your implementation or tools, please take a look at the new variants and provide us some feedback so that we can release them shortly and safely. Best regards, Sebastian Iancu SEC member
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
