Thanks Sebastian, I had not appreciated that the various flavours or Template are published in the Java implementation. I suggest that we use this as the source of truth.
https://github.com/openEHR/java-libs/tree/master/oet-parser/src/main/xsd CompositionTemplate.xsd - .oet format https://github.com/openEHR/java-libs/blob/master/oet-parser/src/main/xsd/CompositionTemplate.xsd This is the native format that Template Designer uses internally . It is a diff i.e. it carries only the constraints on the underlying archetypes, not any of the archetype info itself. This isa only ever used as a design artefact. Template.xsd - .opt format https://github.com/openEHR/java-libs/blob/master/oet-parser/src/main/xsd/Template.xsd This is the technical artefact that most Template-supporting systems e.g OceanEHR, Marand Think!EHR, Cabolabs, Code 24 etc use. . It is is essentially a wrapper round the existing AOM schema, to support aggregation and further constrinty of the archetypes. It is essentially a 'compiled and flattened form which fuses the diff constraints of the .oet with the underlying archetypes. In that sense it is just a giant archetype, which internally is 90% compatible with the AOM (and imports the same AOM schema). In practice this means that if I create a .opt , I can upload this to one of these systems and it will be ready to use, with no need to upload or manage the individual archetypes. .opt is also used to generate other downstream artefacts such as GUI frameworks and code-stub libraries. The other schema that is generated is Template DataSchema In ADL 2.0 terms, the .oet will be replaced by differential ADL, but the .opt will remain as a final 'compiled' version of the template for technical use. As part of the tooling re-development we should set up a wiki page to document the various favours of template and template-related schema. Ian Ian On 22 October 2014 11:29, Ian McNicoll <ian.mcnicoll at oceaninformatics.com> wrote: > Hi Bert, > > You are correct - this is not the schema for .oet but an old very first > draft of a template schema which to my knowledge has never been used and > should probably be withdrawn. > > The schema for the operational template 1.4 .opt format is available and > I think that should be uploaded in its place. > > I am not sure that a schema for the .oet format exists. > > .opt is the key format > > Ian > > > > > On 22 October 2014 10:13, Bert Verhees <bert.verhees at rosa.nl> wrote: > >> On 22-10-14 10:34, Thomas Beale wrote: >> >> >> Hi Bert, >> >> this page >> <http://htmlpreview.github.io/?https://github.com/openEHR/specifications/Release-1.0.2/publishing/its/XML-schema/index.html>should >> help it's the 'XML schema' link from the specifications page >> <http://www.openehr.org/programs/specification/releases/1.0.2>, near the >> bottom. >> >> >> Hi Thomas, thank you very much. >> >> I found this link already: >> >> https://raw.githubusercontent.com/openEHR/specifications/Release-1.0.2/publishing/its/XML-schema/Template.xsd >> >> But I don't know how to understand this schema in context with OET-files >> I found on CKM. >> >> In those OET-files are elements like definition, integrity-checks, rules, >> item, items, and much more. >> It seems not to fit on the contents of this XSD which does not define >> those elements. >> >> Do I misunderstand something? >> >> Bert >> >> >> >> - thomas >> >> On 22/10/2014 09:02, Bert Verhees wrote: >> >> Hi, >> >> I must have been overlooking it all the time, but I cannot find the >> formal definition of the OET-XML >> Thanks for helping me out. >> >> Bert >> >> _______________________________________________ >> openEHR-technical mailing list >> openEHR-technical at lists.openehr.org >> >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> >> >> >> >> >> _______________________________________________ >> openEHR-technical mailing listopenEHR-technical at >> lists.openehr.orghttp://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> >> >> >> _______________________________________________ >> openEHR-technical mailing list >> openEHR-technical at lists.openehr.org >> >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> > > > > -- > Dr Ian McNicoll > office +44 (0)1536 414 994 > fax +44 (0)1536 516317 > mobile +44 (0)775 209 7859 > skype ianmcnicoll > ian.mcnicoll at oceaninformatics.com > > Clinical Modelling Consultant, Ocean Informatics, UK > Director openEHR Foundation www.openehr.org/knowledge > Honorary Senior Research Associate, CHIME, UCL > SCIMP Working Group, NHS Scotland > BCS Primary Health Care www.phcsg.org > -- Dr Ian McNicoll office +44 (0)1536 414 994 fax +44 (0)1536 516317 mobile +44 (0)775 209 7859 skype ianmcnicoll ian.mcnicoll at oceaninformatics.com Clinical Modelling Consultant, Ocean Informatics, UK Director openEHR Foundation www.openehr.org/knowledge Honorary Senior Research Associate, CHIME, UCL SCIMP Working Group, NHS Scotland BCS Primary Health Care www.phcsg.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20141022/30816e1a/attachment-0001.html>
