Hi Daniel, I should have been more precise. I still don't see how it would be possible to create a single generic Canonical XML -> TDD transform. It should be possible, however, to generate a per-TDD schema (TDS) transform ,by applying the same sort of generic rules that are used to create a TDS from an operational template, but in this case generating an XSL rather than a TDD. Might be an interesting research project.
So TDD -> canonical requires only a single generic xslt but the reverse process requires a custom xsl, which it may well be possible to automatically generate from the operational template. Ian On 14 June 2013 09:42, Sam Heard <sam.heard at oceaninformatics.com> wrote: > Hi > We designed the process to allow ant XML schema generated to be > transformed to openEHR with a single transform. > > I expect it may well be possible to do the reverse. At least it would be > possible to get to a consistent flattened form. > > The reason for the TDS is to validate data using XML tools. > > Cheers Sam > > Dr Sam Heard > FRACGP, MRCGP, DRCOG, FACHI > Chairman, Ocean Informatics > Chairman, openEHR Foundation > Chairman, NTGPE > +61417838808 > ------------------------------ > From: Daniel Karlsson <daniel.karlsson at liu.se> > Sent: 14/06/2013 5:12 PM > To: openehr-technical at lists.openehr.org > Subject: Re: TDS (and TDD) implementations? > > Hi Ian, > > On Thu, 2013-05-30 at 10:34 +0100, Ian McNicoll wrote: > > Hi Erik, > > > > > > The Ocean TDD->canonical transform is available at > > > > > > http://openehr.codeplex.com/SourceControl/latest#176376 > > > > > > > > look for TDD_to_openEHR.xsl > > > > > > As far as I know a generic reverse transform is not possible. > > How could that be? Is there something in the TDD format that is not in > the RM format? The intuition tells me that it should be easier going > from the rich RM format to the TDD format than in the opposite > direction. What are the specific issues that make a reverse > transformation problematic? Could anything be changed to make the > transformation possible? > > /Daniel > > > > > > There are at least 3 or 4 companies using TDD as part of their CDR > > offering. > > > > > > It would be good to make this part of the managed standard and public > > spec . > > > > > > Ian > > > > > > > > On 30 May 2013 10:21, Erik Sundvall <erik.sundvall at liu.se> wrote: > > Hi! > > > > > > Which projects and products out there support TDS (Template > > Data Schema)? And do they support conversion of TDDs (Template > > Data Documents) to standard "canonical" openEHR RM instances > > (in e.g. XML)? Is there any available XSLT, webservice or > > other thing that can convert bidirectionally between TDD and > > openEHR RM-based instances? > > > > > > What about a TDS specification? Is there any published or > > work-in-progress document? If not is there any entity, group > > or person that could/should be sponsored or bribed to produce > > such a thing? :-) It seems to be on the > > roadmap http://www.openehr.org/programs/specification/roadmapand > > described there anyway... > > > > > > I think TDS is an essential component in the toolbox in > > practical openEHR integration projects but without a public > > spec, it will be harder to take seriously and hard to make > > compatible implementations. > > > > > > (ExampleTDS-info for people not familiar with the > > approach: > http://www.mz.gov.si/fileadmin/mz.gov.si/pageuploads/eZdravje/Novice/gradiva_predstavitve_dogodkov/Open_EHR/7_integration.pdf > ) > > > > > > Best regards, > > Erik Sundvall > > Tel: +46-72-524 54 55 > > LiO: erik.sundvall at lio.se > http://www.lio.se/Verksamheter/IT-centrum/ > > LiU: erik.sundvall at liu.se http://www.imt.liu.se/~erisu/ > > > > _______________________________________________ > > 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 > > > > _______________________________________________ > > openEHR-technical mailing list > > openEHR-technical at lists.openehr.org > > > http://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 > > _______________________________________________ > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/c4c77563/attachment.html>
