Hello Thomas Thank you for the quick response. I guess i am going to have to go through the yacc style files and get the definitions...it's been sometime since i last used that family of tools. I am primarily interested in ADL 1.5, for the new way of handling slots and for bringing in the "template" level of modelling.
All the best Athanasios Anastasiou On 17/03/2014 10:25, Thomas Beale wrote: > > I've put up a new page on this here > <http://www.openehr.org/wiki/display/spec/ADL+1.5+parser+resources>. > Please note that there are a few legacy rules that you don't need to > care about if you are doing pure 1.5. We'll make a pure version of these > parser grammars at some point. The ones at this link are straight from > the software, so they are always the 'latest' , and also implemented, so > you can trust they work in at least one place. > > Re: AQL, our current approach is to do writes/updates via APIs, > including things like SMART-flavoured APIs that are specific to the > content, e.g. allergies list, medications list and so on. I think this > approach is easier for app writers to deal with, and seems to be the way > the world is going these days (think SMART/FHIR). > > - thomas > > On 17/03/2014 09:45, ANASTASIOU A. wrote: >> Hello everyone >> >> Are there any resources that define the structure of ADL 1.5? As always, >> BNF would be great but other files that could help in deriving BNF would >> also be useful. >> >> Also, can i please ask if there are any plans to update the archetype >> query language with the rest of the operations that could be carried out >> over openEHR? At the moment, AQL supports data manipulation only and >> specifically querying. What about other operations such as update / >> insert / delete?) >> >> Looking forward to hearing from you >> Athanasios Anastasiou >> ________________________________ >> [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass> >> >> >> This email and any files with it are confidential and intended solely >> for the use of the recipient to whom it is addressed. If you are not >> the intended recipient then copying, distribution or other use of the >> information contained is strictly prohibited and you should not rely >> on it. If you have received this email in error please let the sender >> know immediately and delete it from your system(s). Internet emails >> are not necessarily secure. While we take every care, Plymouth >> University accepts no responsibility for viruses and it is your >> responsibility to scan emails and their attachments. Plymouth >> University does not accept responsibility for any changes made after >> it was sent. Nothing in this email or its attachments constitutes an >> order for goods or services unless accompanied by an official order form. > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > ________________________________ [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass> This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, Plymouth University accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. Plymouth University does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.
