This page outlines the changes to AQL being explored by Ocean Informatics. In general the changes presented here intend to generalise and extend the capability of AQL.
This will simplify the grammar and improve parser performance. The is currently no identifed need to have the path broken down into the path parts except to validate the path syntax. This can be achieved using a terminal definition rather than a rule.
This generalises the utility of the language to other reference models including demographics
This ensure that only archetype ID predicate expressions can be specified on classes in the FROM clause. All other RM attribute constrains must be expressed as WHERE criteria. This change is intended to make the rules about what attributes can be used in the FROM CLASS expressions interoperable. It also provides a better correlation to a relational model query where an archetyped class can be thought of as a relational table.
Allow a NOT CONTAINS statement to be made
Allow ADL like expressions to provide value set, value range and regular expression criteria. For example:
items[...]/value/defining_code/code_string MATCHES { '13452.2', '14062.3' }
Also allow TYPE based criteria. For example:
items[..]/value MATCHES { DV_TEXT }
Allow a NOT MATCHES statement and other bollean and comparable expressions