Hello Thomas Thanks for letting me know.
There's no problem in waiting for a couple of days for you to clean up the ADL 1.5 definitions. In any case, this is not going to be a 'walk-in-the-park' :) I did however try to take a different approach in the hope that it might produce results more quickly. You can read all about it here: https://github.com/aanastasiou/adl_ebnf In essence, i remembered that Tim Cook's Python reference implementation included the definition of a parser for ADL 1.4 through the (incredibly useful but slightly slow) pyparsing package. Pyparsing allows the definition of parsers using a very nice object oriented interface and its definition reads almost like natural language. So, going from that to an EBNF form is much easier than reverse engineering the yacc-like files (to my eyes at least :) ). So, in a nutshell, the plan would be to arrive at a valid definition of ADL 1.4 and then augment it with those key parts that are different in ADL 1.5. The current set of EBNF definitions is not that big, so if anyone wants to pitch in either by reviewing the current definitions or contributing additional ones, please do so. I hope that we can arrive at a good definition of ADL 1.5 in EBNF, it's a great resource to have and it can be used for a number of things. All the best Athanasios Anastasiou On 17/03/2014 19:07, Thomas Beale wrote: > On 17/03/2014 16:31, ANASTASIOU A. wrote: >> 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. > > Athanasios, > > if you want to wait a couple of days, I'll clean the ADL 1.5 parser up > to be pure, as I already had the idea to relegate the current mixed > parser to 'ADL 1.5 transitional'. > > - thomas > > _______________________________________________ > 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.
