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 repla

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 Thoma

On Information and Interoperability

/mailman/private/openehr-technical_lists.openehr.org/attachments/20080418/52856012/attachment.html>

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 > a

On Information and Interoperability

Correction "MIF/MIF Mapping" should read "MIF/MOF Mapping" Sorry. Spotted just as I clicked send. Adam > > BTW sidenote: I have looked at both a "MIF/MIF Mapping " (I like the > name if not the result ) & an AOM MOF. > > > **

Archetype documentation using XML + XSLT

Peter Gummer wrote: > 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 >> engineer

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 Open

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 reason

Archetype documentation using XML + XSLT

An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080418/fed221ab/attachment.html>

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. XF

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 in

On Information and Interoperability

p-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>