Archetype documentation using XML + XSLT

Thomas Beale wrote: Adam Flinton wrote: Other limitations on using XML - it's a no-show for enterprise scale databases or information processing. All that wasted space starts to count when you have to buy two ?20,000 high availability RAID disk arrays instead of oneand

On Information and Interoperability

Tim Cook wrote: [extracted from the thread Archetype documentation using XML + XSLT] Tim Cook wrote: ADL does semantically describe the AOM. No reason why XML could not. It can suffice for anything from a webform (e.g. XForms) to a vector graphic (e.g.

On Information and Interoperability

-- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080418/d79d2bcb/attachment.asc

Archetype documentation using XML + XSLT

Thomas Beale wrote: ... In our own EHR product we have had to resort to various kinds of compression, which impact on performance, and we have to have larger disc arrays than would be needed if the data were represented in a more efficient way. Our engineers are currently looking at replacing

On Information and Interoperability

-technical_lists.openehr.org/attachments/20080418/52856012/attachment.html

On Information and Interoperability

Tim Cook wrote: Hi Adam, On Fri, 2008-04-18 at 11:55 +0100, Adam Flinton wrote: Stepping outside of well supported standards increases maintenance requirements much much more. Well, I am not certain I would say much much more but in any case there are reasons why new

AOM MOF mapping

In a reply wrt On Information and Interoperability I have noted that there is a move underway to try produce an HL7 model (via EMF/MOF) for use in our /OHT eclipse tooling. Has anyone looked at an AOM/MOF mapping? If so any thoughts? E.g. were one to want to sit down do some Eclipse OpenEHR

Archetype documentation using XML + XSLT

Peter Gummer wrote: Adam Flinton wrote: I have already noted how using text children of an element to use a value vs a std value attribute in the archetype xml inflates the file sizes. So you aren't convinced by Thomas's objection that putting the values in XML attributes

Archetype documentation using XML + XSLT

Adam Flinton wrote: Peter Gummer wrote: Adam Flinton wrote: I have already noted how using text children of an element to use a value vs a std value attribute in the archetype xml inflates the file sizes. So you aren't convinced by Thomas's objection that