Hi Thomas, thanks for your input.
I understand perfectly the what and why. Personally I'm looking for the easiest
path possible to start _testing_ (not implementing) how to integrate AQL with
the EHRServer, because I don't have much developmwnt time and don't have money
to hire developers. Actually I'm looking for partners that want to fund this
open source project.
In the other hand, the published grammars are a little old and don't know who's
maintaining them, or if those are being maintained at all. And I don't have
much experience working with grammars, so for me the learning curve will be
huge. So for me a XML or JSON form of AQL queries is a nice starting point.
Also I would like AQL to become normative (part of the openEHR specs, as well
as opts :). Right now the docs we have available is one paper (I think from
2007), and a couple of wiki pages. Not sure if the doc and the grammars match
or not.
Sent from my LG Mobile
------ Original message------From: Thomas BealeDate: Mon, Jan 19, 2015 7:57
AMTo: openehr-technical at lists.openehr.org;Subject:Re: Does anyone
implemented a transformation between AQL and XML?
Hi Pablo,
I see Seref has provided some technical input. Just a note on what
AQL is for, and why it is a language with a parser etc. The goal is to
have queries that rely only on archetypes, and that can be shared across
systems and vendors, enabling CDS and other second level processing
solutions to be economic. The point of having a language is that the
language is standard for this purpose, and that in each type of
installation, an interpreter, or pre-compiler or similar, converts the AQL
statements to what they need to be in that installation. The result will
usually be different for each different vendor / type of solution - due to
different DB, schema etc.
The AQL grammars currently online are what is in use - AQL is in
fact very stable. However it will certainly get upgraded this year, due to
useful changes made by the guys at Marand, to do with server side
processing, functions etc. We also need to upgrade its terminology
handling and specify some of the semantics better, which Seref knows a lot
about.
- thomas
On 17/12/2014 20:31, pablo pazos wrote:
Hi Seref, what I asked here was if anyone did
implemented that, so I don't have to :)
As I said, my experience tells me it requires more
hours-man to work with a syntax, a model and a parser than having XML
and parse parts of it when required (so I can have 1. many ad-hoc
parsers, 2. no model just ad-hoc data structures, 3. no API, 4. no
parser e.g. it requires a lot of time to find a problem update the jj,
generate the parser and test).
Hope that clarifies my vision.
Of course, I didn't started yet to do anything about AQL
support, just trying to make the community aware that I'll do so and
maybe generate some collaboration momentum. Maybe the syntax
definition is very stable and there are a lot of good parsers for
Java, but the syntax definition I found seems to be old
(https://openehr.atlassian.net/wiki/display/spec/Archetype+Query+Language+Grammar?&?https://openehr.atlassian.net/wiki/display/spec/AQL-+Archetype+Query+Language)
and I don't know about AQL parsers for Java (just found this old
discussion, no response about the
parser:?http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/2009-March/004400.html).
I'm sure I need to do more research, but I doubt I can find
the basic building blocks, even to start working with AQL
directly.
Please if you know where I can find stuff to help me, any
pointers will be very welcome!
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150119/3cb4117a/attachment.html>
