Greg, The XML representation of Archetypes are just as normaitive as ADL, the XML (just like ADL using a different syntax) is a serialisation of the Archetype Object Model representation of an Archetype.
The OET files are a proprietary template definition used by the Ocean Template Designer product. This Template Designer also has a Form Designer that can take a template definition and automatically build a form. This form can be output as a Form Definition with control constraints expressed using the Archetype Object Model constraint object. This form definition can be used within the Ocean EhrView web components to render this form using ASP.NET. As mentioned in a separate email, we can also generate an XML representation of a template represented using Archetype Object Model constraint objects, called an operational template. This is based on the draft template specification but has need some augmentation to provide enough information for producing other artefacts. One of these artefacts is what we call a Template Data Schema. It is an XSD based on the Template and Archetype definitions. The schema doesn't convey all the constraints expressed in the template and archetypes but does give someone that is not an expert in openEHR to use the template for the purposes you indicated. We have a single XSLT transform to take an XML Document valid against the Template Data Schema and produce an XML document valid against the openEHR RM XML Schema. Regards ? Heath ? Heath Frankel Product Development Manager Ocean Informatics Ground Floor, 64 Hindmarsh Square Adelaide, SA, 5000 Australia ? ph:?+61 (0)8 8223 3075 mb: +61 (0)412 030 741 email:?heath.frankel at oceaninformatics.com Regards Heath > -----Original Message----- > From: openehr-technical-bounces at openehr.org [mailto:openehr-technical- > bounces at openehr.org] On Behalf Of Greg Caulton > Sent: Monday, 22 October 2007 11:56 PM > To: openEHR-technical at openehr.org > Subject: parsing templates > > Hi, > > More basic questions... > > The Archetype-Editor is great for defining archetypes for technical > users. I am looking to leverage templates and archetype content but > provide a simple to use front end. > > The user would go through iterations of searching and selecting > content, adding it to what would be their own template - or at least > something I can persist without losing the archetype hierarchy. > > Looking at the oet template files e.g. > > http://my.openehr.org/wsvn/knowledge/templates/dev-uk- > nhs/xml/openehr/ehr/composition/Emergency-Headache-v2draft.oet?op=file&sc=1 > > The xsd is a general one, not related to templates. The archetypes do > not have an xsd either - so I cannot use JAXB to generate java classes > from the definition. > > Does this mean that technically only the ADL is the true > specification, the XML is just for viewing purposes? Would I have to > dig into the Java implementation to figure out how to parse the ADL > into a set of objects that I can then display on screen or print? > > Is there a simple Java API I can use to get at the OET templates? > > thanks! > > Greg > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
