Hi! I believe TDS is a very nice approach for som especific integration purposes. Simple and wonderful invention (the best ones are often simple...) For those new to TDS there was a thread regarding this earlier: http://www.openehr.org/mailarchives/openehr-technical/msg03116.html
Are there any specific reasons for keeping the development internal to Ocean Informatics? As I understand it you sometimes internally use a wiki for these kinds of developments, I would suggest that you move the TDS (and if possible the AQL) development to the public openEHR wiki instead as they are of strategic importance to openEHR. Just post what you have right now including a comment that this is only experimental. This way you might get more input and wider testing.Certainly people/projects wanting to use TDS early will feel a lot more confident regarding progress and might trust it as a viable path to go for certain projects that would be riskier if there was only an expected release date from a company that may need to revise it's at priorities any time (as most companies do). Preliminary implementation experiments could be started right away and updated+launched when the real specification is finished. Best regards, Erik Sundvall erisu at imt.liu.se http://www.imt.liu.se/~erisu/ Tel: +46-13-227579 On Mon, Apr 28, 2008 at 3:46 AM, Heath Frankel <heath.frankel at oceaninformatics.com> wrote: > Ocean is also developing the idea of a Template Data Schema, which will be > published as a draft on openEHR in the coming months. This does provide a > specific XML schema for a template (or combined collect of archetypes) where > the XML element names come from the archetype element names, but there is > additional meta-data in the schema and the XML document based on that schema > which links each XML element back to the archetype element such as the > node_ids so that generic transformation logic can be written to generate an > openEHR instance for any set of archetypes. These Template Data Schemas can > be automatically generated from the archetype/template models based on a set > of rules. I can give you a sample of this if you would like but I suspect > that you don't need this template specific approach, which is intended more > for those that unfamiliar with openEHR or you want a intermediate data > representation that is closer to a specific use-case for integration > purposes.
