Gerard, Ian, Thomas, thanks for all answers. On Fri, 2013-06-14 at 11:17 +0100, Thomas Beale wrote: > > Let me clarify a few things here. > > There are many possible TDSs that can be generated from a given > template. Some users want a 'flat schema' with minimal meta-data, > which makes working with integration data easier, but a TDD (TDS XML > document) -> canonical transformer harder to write (it has to look up > more from the archetypes.) > > Some users are happy with a fully featured schema that enables a > nearly trivial TDD -> canonical converter to be written. > > Some users want specific things like certain code annotations, or > hidden node markers or whatever, which in some cases can only be > obtained if they are in the annotations of the template or archetype > (i.e. most archetypes / templates won't have these specific > annotations). > > So, if we want to do a canonical -> TDD transform from a primary > openEHR repository, it means choosing which particular kind of TDS is > being targetted. If there were a default TDS for openEHR (we should > standardise on that), then canonical -> TDD could be implemented and > deployed, probably quite easily.
Such a standard TDS/TDD would have made the Swedish 2009-10 quality registry project significantly easier and a lot of the criticism towards openEHR could have been rejected. We more or less constantly had to reply to questions as to why use archtypes/templates using up several kilobytes when anyone can write an XSD for a specific use case using up a fraction of that space. The obvious conclusion is that we (as in Sweden) ourselves should have started that project. It's not always easy being an openEHR advocate ;). > It's just a question of what the community thinks is important. > > - thomas > > > On 14/06/2013 08:41, Daniel Karlsson wrote: > > > 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/roadmap and > > > 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 > > > > > > > > > > > > > > > _______________________________________________ > > > openEHR-technical mailing list > > > openEHR-technical at lists.openehr.org > > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > >
