openEHR Querying specifications

Hi Gerard, I 'm afraid I agree with Tim on this one. The difference between 'breaking' Version changes and non-breaking Revisions is clearly documented in the specification. The reason for confusion and non-use within the NHS is simply that the current tools do not support Revisions. Now that the

Decision Support was: MIE-2008

Hi Gerard, I agree with most of your comments and in principle that most post-coordination (using modifiers in Snomed-space instead of Archetype/Template space) must end, this amounts to heresy in a UK context and I think we should be prepared to regard David Markwell's Grey Zone as a contested

openEHR Querying specifications

Heath Frankel wrote: [openEHR-EHR-COMPOSITION.encounter.v1*] (or perhaps more correctly [openEHR-EHR-COMPOSITION.encounter.v1.*], where the dot means any character not the version delimiter) and [openEHR-EHR-COMPOSITION.encounter.v\d+] are different. The first allows all revisions of .v1

openEHR Querying specifications

The v1draft convention is already deprecated. The BNF for AQL doesn't support it deliberately, to ensure only non-draft archetypes are used when committing/retrieving data. Heath -Original Message- From: openehr-technical-bounces at openehr.org [mailto:openehr-technical- bounces at

Decision Support was: MIE-2008

of Archetype/Template space) must end, -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080605/4d21b3e3/attachment.html

Decision Support was: MIE-2008

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080605/725c0b1f/attachment.html

openEHR Querying specifications

-technical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080605/61feb9cf/attachment.html

Parsing archetype xml with JAXB

-technical_lists.openehr.org/attachments/20080605/ee3d4a0f/attachment.html

Parsing archetype xml with JAXB

Greg - I think this question would be better on the implementers list - to avoid causing too many heart attacks among the readers of this list on seeing actual code ;-) - thomas beale Greg Caulton wrote: Hi, I used JAXB to generate java files from the XSD files but I am not getting very

Parsing archetype xml with JAXB

-technical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080605/ffa989a3/attachment.html

Parsing archetype xml with JAXB

Hi Greg, Have you tried XMLBeans? I have good experience in RM XML data binding using XMLBeans, http://www.openehr.org/svn/ref_impl_java/SANDBOX/xml-binding/ Haven't tried it with AOM XML binding, but it shouldn't be too different I suppose. Regards, Rong Hmm, well perhaps I should

Parsing archetype xml with JAXB

://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080605/5e197a7d/attachment.html

Parsing archetype xml with JAXB

If you are familiar with Maven, the best way is to check out the latest version from the trunk and build from source. You could also download jars from the continuous integration server from here http://openehr.cambiosys.org/continuum. Just click the component and follow the link working copy

Decision Support was: MIE-2008

-technical_lists.openehr.org/attachments/20080605/38e85b5f/attachment.html