> Jim Alateras wrote: > > Rong, > > I was looking thorough the Java ADL parser and it looks good. I > have a couple of questions > > 1. Do you have a URL for the ADL Specifications for v0.9? > > > No, I don't. It seems to be quite old, at least from 2003. What do you > need it for? Our parser is mostly based on ADL 1.2 Draft, which is > very close to the latest one - v1.2.1.
In general, if you realy want the old version of things, you can get them by looking in the TAGS directory - you can do a checkout on that and you will see 0.9 and 0.95 releases. You can use URLs like http://uluru.chime.ucl.ac.uk/svn/specification/TAGS/Release-0.9 and http://uluru.chime.ucl.ac.uk/svn/specification/TAGS/Release-0.95. But as Rong says, these are of course out of date specifications. > > > 2. Do you have any plans for moving it towards v1.2? > > > Certainly, we will bring it up to the latest ADL specification. > Actually, the current ADL syntax supported by the parser is almost the > same as that in the v1.2.1. Since the assertion package of archetype > object model has gone through some major rewriting during the time the > parser was constructed, the support of that in ADL is not supported by > the parser( as well as the aom implementation in the kernel). > > What's also need to be improved is the post-parsing validation for > stuff like missing term definition and wrong information model > reference, which are beyond the BNF rules and need to verified after > the object tree is constructed. We will publish these rules in the next release of the specs - I have a lot of them in the Eiffel/.Net parser, and Rong has undoubtedly found more, so we should have a pretty good set to put into the specs. > > However these won't stop you from creating serious archetypes to power > your EHR application. With the current ADL parser and kernel, we have > successfully created archetypes for Composition, Entry level objects > and demographic objects like Person and use them for date entry and > validation. Note that 0.96 (released today) specifies one invariant clause per archetype, a simplification of what was there. See for example, http://svn.openehr.org/knowledge/archetypes/dev/adl/openehr/ehr/section/openEHR-EHR-SECTION.soap_headings.v1.html (don't take this as good archetype design - it's just to show the principle). > > Again, any help in terms of bug report, patches and improvements will > be highly appreciated. > > Cheers, > > Rong - thomas -- ___________________________________________________________________________________ CTO Ocean Informatics (http://www.OceanInformatics.biz) Research Fellow, University College London (http://www.chime.ucl.ac.uk) Chair Architectural Review Board, openEHR (http://www.openEHR.org) - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
