Dear Thomas,
Not sure if this is discussed here before, but I wonder why you don't use
XML for ADL. So that, it will be possible to use tens of ready made
parsers and validators against a DTD for a number of programming language;
visualize using a xslt etc. Here a quick example:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE archetype
PUBLIC "-//openEHR Foundation//DTD Archetype 1.2//EN"
"http://www.openehr.org/dtds/achetype-12.dtd";>
<archetype id="achetype_id" specialize="parent_archetype_id">
<concept>at0010 <!-- haematology result -->
</concept>
<description>
<!--dADL meta-data section -->
<author>Sam Heard <s.heard at littlerock.con></author>
<submission>
<organisation>openEHR Foundation</organisation>
<date>2003-06-10</date>
</submission>
<revision identifier="1.2">
<author>Thomas Beale <t.beale at home.net></author>
<date>2003-12-11</date>
</revision>
<status>draft</status>
<purpose>
<items lang="en">general model of haematology lab results</items>
<items lang="de">Allgemeines Modell fuer Haematologie
Laborwerte</items>
</purpose>
<use>
<items lang="en">can be used directly or specialised for particular
result types</items>
<items lang="de">kann entweder direkt benutzt werden, oder speziell
fuer besondere Ergebnissarten</items>
</use>
<misuse/>
</description>
<definition>
<!-- cADL structural section -->
</definition>
<ontology>
<!-- dADL definitions section -->
</ontology>
</archetype>
Ergin Soysal, MD
>
> Dear colleagues,
>
> there is a proposed revision of the Archetype Definition Language (ADL)
> v 1.2 available at http://www.openehr.org/tmp/adl-1_2_draft_d.pdf. Only
> small changes to ADL itself are proposed, but the explanations have been
> improved, and complete grammars have been included in the document. The
> main change is a complete redesign of the object models corresponding to
> ADL, informed by previous work in GEHR, ongoing archetype development,
> and the DSTC team engaged on the HealthConnect project in Brisbane,
> Australia.
>
> This proposal will be reviewed in the proper fashion by the openEHR ARB,
> but of course we welcome community review and input on this discussion
> list. The software (sorry, only on Windows so far) which implements this
> specification is at
> http://www.openehr.org/repositories/implem/latest/publishing/tools/windows/index.html.
> Please read the READMEs first if you intend using it.
>
> We are still working on the packaging and use instructions, so please be
> patient, and of course post any complaints about difficulties you
> encounter. As I'm sure many of you appreciate, perfect packaging takes
> time and effort, and requires user feedback.
>
> regards,
>
> - thomas beale
>
>
>
> -
> If you have any questions about using this list,
> please send a message to d.lloyd at openehr.org
>
Pleksus Bili?im Teknolojileri
http://www.pleksus.com.tr
Tel: +90 (312) 435 5343
Fax: +90 (312) 435 4006
-
If you have any questions about using this list,
please send a message to d.lloyd at openehr.org
