Seref, to add to my questions: > AQL is the most neglected, yet, probably one of the most important components of an openEHR implementation.
Does this imply that each implementation of openEHR is sufficiently different from others as not to allow for easy sharing of such things as search or storage technologies? Randy On Thu, Apr 18, 2013 at 6:09 AM, Thomas Beale < thomas.beale at oceaninformatics.com> wrote: > On 17/04/2013 22:04, Randolph Neall wrote: > > Thomas, somehow I'm not finding the AQL specification. It's probably right > under my nose on your specification/release page. Also, do you have any > references describing the AQL processor? Did you write *that* from > scratch?? It would seem that the AQL processor would indeed function as > a formidable DBMS in its own right, at least with regard to reads, capable > of managing AND/OR logic trees and serving up flat "tables" of joined data > structures like any RDBMS. > > Randy > > > http://www.openehr.org/wiki/display/spec/AQL-+Archetype+Query+Language > > - thomas > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130419/558d436f/attachment.html>
