Hi Tim, It is great to here that you are taking AQL seriously and plan to write a python implementation, your feedback I am sure will be invaluable.
We have not done a lot of work on queries for some time but have recently been doing some work related to projects and have started to think about some changes to the current AQL proposal published on openEHR, to simplify and generalise the grammar and supporting more advanced queries features such as a matches operator. I have started a wiki page, http://www.openehr.org/wiki/display/spec/Proposed+AQL+changes, to briefly list what changes we are thinking about. When we get the time to update the BNF for these proposed changes, we will attach it. If you have a look at these proposed changes you will see that they are significant from a grammar (and parser perspective) but does not change the general intent. I would appreciate your (and anyone else) early feedback on these proposed changes even if you have not had a chance to implement AQL yet (even at a high level). My main concern is that you invest time into implementing the current proposal and make comments about issues when the proposed changes should make that task easier and shortcut some of the issues you would have commented on. I would like to think that we can work closely together during your implementation to ensure that we can address issues in real-time. Heath > -----Original Message----- > From: openehr-decisionsupport-bounces at openehr.org [mailto:openehr- > decisionsupport-bounces at openehr.org] On Behalf Of Tim Cook > Sent: Friday, 25 July 2008 1:59 AM > To: Discussions relating to enabling decision support in openEHR > Subject: Re: AQL > > > On Thu, 2008-07-24 at 21:28 +0930, Sam Heard wrote: > > > I am trying to start a conversation here for those seeking to use AQL > > and openEHR. We could provide a some tooling to get this moving and > > would even be very pleased to have feedback on how the Query Interface > > might go best. > > > > Hope to hear some ideas about how to progress this the best. We have > > recently enabled interactive editing of the language which does make > > it easier to test the capability of the engine. We would be happy to > > support people working in the open source space with developing the > > language further. > > I just noticed that there is a new BNF. I have been waiting for it to appear > since the one I had was dated 2006. > > I have someone that will build a parser for this BNF and I will then map the > query to the query engine that we have in OSHIP. This will take 3-4 weeks and > by then we should be able to persist some sample data and start testing > queries. > > But at this point I do not have any feedback on the existing status of AQL. > Maybe in a couple of months. > > Cheers, > Tim > > > > -- > Timothy Cook, MSc > Health Informatics Research & Development Services LinkedIn > Profile:http://www.linkedin.com/in/timothywaynecook > Skype ID == timothy.cook > ************************************************************** > *You may get my Public GPG key from popular keyservers or * > *from this link http://timothywayne.cook.googlepages.com/home* > **************************************************************
