Hi!

On Thu, Apr 17, 2008 at 2:04 PM, Thomas Beale
<thomas.beale at oceaninformatics.com> wrote:
>  ADL and XML
[...removed a load of XML-bashing from the man with a brain-integrated
ADL-parser :-) ...]

> ADL can be guaranteed as 100% correct all the time, and are the mathematical
> reference form of archetypes

Actually I would prefer more emphasis on the view that the AM is the
main reference and that ADL is a serialization of it. But a "reference
form" of individual _archetypes_ needs a serialization not just an
object model of course...

No matter how nice and pure ADL might be, I have seen people getting
suspicious of "this OpenEHR-thing" when ADL has been focused too
strongly. (Or people getting upset by having to learn yet another
language, alternatively having been put of by the idea of having to
write an ADL parser in a new environment.)  It's wonderful that there
are now two "official" ways (ADL and XML) to serialize AM constructs,
having even more would probably not hurt.

Thomas Beale wrote:
>  Interesting links:
> http://www.json.org/xml.html

For some months I have been wanting to experiment with making a simple
JSON implementation of the AM (and eventually also the RM) as a
compact javascript- and Flash/Flex-friendly alternative to ADL/dADL
and then submit it as an ITS for openEHR. I realize I won't have the
time for it though so I drop the idea here hoping that someone else
gets inspired.

Links
http://www.json.org/
http://groups.google.com/group/json-schema (You'd probably want a
schema in the ITS)
http://www.jspon.org/ (Not sure if you need the power of JSPON. The
built in name/path mechanisms of the AM/RM might be enough.)

Anybody interested? :-)

Best regards,
Erik Sundvall
erisu at imt.liu.se http://www.imt.liu.se/~erisu/ Tel: +46-13-227579

Reply via email to