> Good. I can happily help with this. > >> C) Same as (B) but for the CSV files. > >> > > These are from templates so they require the kernel. > Ah good so I can transform with XSLT from the .oets [Heath Frankel] The transforms cannot be done from .oets as they do not have the details of the archetypes, only references and further constraints of archetypes. In addition, the .oet files are currently a proprietary format used by the Ocean Template Designer since there is no finalised specification for templates in openEHR.
Having said that, Ocean has developed an Operational Template generator that effectively compiles the .oet and archetypes into a single constraint definition which can be serialised to XML and be used for these kind of transformations. This Operational Template utilises the existing Archetype Object Model and R1.0.1 XML schema with minor extensions based on the draft openEHR Template specification (with minor modifications that will be provided as implementation feedback to the specification author for consideration). This approach has already been used by Ocean to generate XML Schema's for a specific template using XSLT from a compiled and serialised Operation Template. This resolves both problems identified above. Heath
