...
It’ll almost certainly break some, or all of the AQL implementations at varying degrees.
This means we’ll have to commit to spending money as vendors.We may have to make some tough choices re scope.
We may have to consider limiting the scope of AQL if we cannot find a way of supporting everything under the openEHR umbrella. Different vendors and stakeholders may have different visions, and consequently different views of scope for AQL. We need to have a discussion and define a clear scope.<more points are welcome>
Next steps
We would probably like to have a discussion in SEC and attempt to identify the expectations, goals and scope based on input from SEC members. I think if the previous attempts and discussions to solve this problem delivered anything, it is the realisation that we do not seem to have a shared view or vision of AQL. That’s what we need to establish first.