Hi Bert, My understanding only - but I'll give it a go to answer your questions as good as I can.
On 22.10.2014 11:52, Bert Verhees wrote: > I have, in context of my previous question some more questions. > > Is it the case that there are no formal definitions for OET and for OPT? > Is it maybe because both are not yet definitely defined? That is a > good reason. OPT just uses the reference model xsds I believe: https://github.com/openEHR/reference-models/tree/master/models/openEHR/Release-1.0.2/XSD OET: There is a OET parser in the Java Implementation, see here: https://github.com/openEHR/java-libs/tree/master/oet-parser It also includes the xsds: https://github.com/openEHR/java-libs/tree/master/oet-parser/src/main/xsd - CompositionTemplate.xsd is the main one. The parser is then just generated That said, OETs (or their equivalent) will be expressed pretty similar to how specialised archetypes are expressed in ADL 2.0 source format I believe - see here for a starting point: http://www.openehr.org/wiki/display/ADL/ADL+1.5+templates+as+single+artefacts > > I would like to see the formal XSD-definition the Template-designer > works with and which results are published on CKM and used in several > community-projects. > Is that possible? I will take in account that they are not the > definite version. > You can generate the TDS which I think you are referring to from CKM directly for any COMPOSITION template. Go to the Export Template tab for a Composition template, e.g. http://openehr.org/ckm/#showTemplate_1013.26.2_EXPORT and download it from there. It is generated for you on the fly. > Another question: > > I wonder why there are two artefacts, OET and OPT. Both contain > different information, but also have a part of overlap/redundancy. > Isn't it possible to combine the two to one formal definition for an > archetype? OPT would be generated from OET+the archetypes. So essentially it is combining archetypes and restricting them further. Not much different to a specialisation of an archetype. So, compare OET as just listing the differences and OPT as the full specification. OPT is just generated from the oet + the underlying archetypes as required. During deployment you are likely only interested in the OPT, but during the development of archetypes & templates, you are much happier dealing with a file format that just restricts the archetypes for your use case, but which doesn't carry the whole information from the archetypes - that would get you into a maintenance nightmare. Hope this helps and clarifies Cheers Sebastian
