Hello everyone

A brief email to let you know that a first version of ADL and cADL
expressed in EBNF and ANTLR's meta-language is now avaialble at:
https://github.com/aanastasiou/adl_ebnf

Next up is ODIN.

The ANTLR definitions specifically are available at:
https://github.com/aanastasiou/adl_ebnf/tree/master/src/antlrDefs/adl


In general, transcribing from:
http://www.openehr.org/wiki/display/spec/ADL+1.5+parser+resources was a
straightforward task for the majority of the rules.

However, there are a few points where i would appreciate some help /
guidance in order to end-up with a useful set of definitions for the 
specification. A list of these items is attached at the end of this message.

If you require any additional information, please let me know.

All the best
Athanasios Anastasiou



POINTS OF NOTICE REGARDING ADL 1.5:

1) Are there any ADL 1.5-specific files available out there for testing
purposes?

2) How significant is whitespace such as "[ \t\n\r]*" for ADL?
If no assumptions are made (like, "New line marks the start of a new
statement"), i would like to include a universal rule that skips such
whitespace.

3) Is ID_CODE_LEADER always going to be 'id'? Is it then considered a
SYMbol?

4) There is something odd about the definition of
V_ISO8601_DURATION_CONSTRAINT_PATTERN. The definition seems to include a
trailing '}' but then the parser puts it back in the stream. In the
ANTLR definition i have omitted the '}', would this be a problem? Can we
clarify this rule a bit?

5) Some rules contain comments such as: "rule to be removed once
archetypes containing "T" are gone"...Are these archetypes gone by now?
Can i clean up those rules?

6) Throughout the yacc definitions there are some conditionals whose
purpose i do not entirely understand. For example, during the definition
of V_REGEXP, there are conditional definitions for each constituent part
of a regular expression. Why is this? Same goes for V_STRING,
V_CADL_TEXT, V_RULES_TEXT, V_ODIN_TEXT. At the moment, i am matching these
with a non-greedy operator. Would this be a problem?

Reply via email to