AQL Release-1.1.0 goals & requirements

Objective

To identify, analyse, prioritize and get a planning for AQL specifications Release 1.1.0. The goal is to release this mid Dec 2020.

Assumptions

Requirements

The following is an overview of all candidate issues (some not yet recorded in JIRA) for Release 1.1.0.

We try to separate those issues that have a broader acceptance, or are trivial or forward, from those that we’ll need presumably more in depth discussions.
The “provisional acceptance” should be given (individually), once you consider that the issue is clear, potentially trivial to accept in the end, and you don’t see major problems working on it, progressing on Jira CR itself. If this is not the case, then please state shortly (in few words) what would be problematic from your perspective, or what keeps you away or against it.
Remember, this page is just an overview - longer discussions debates on these topics should take place on discourse, or on the Jira CR under the comments.

If you have other AQL features in your implementation that are not yet in the specs or on this page, please add them here, so that we can consider it for next release(s).

Requirement

Priority / Importance

Category

Provisional acceptance

Notes

Requirement

Priority / Importance

Category

Provisional acceptance

Notes

 

syntax / concept

SI

 

 

concept

SI

 

 

concept

SI

 

 

syntax

SI

 

 

doc

SI

SI: this is an umbrella
TB: I think this must be close to done in 1.0.1?

HIGH

concept

 

SI: need more discussions, examples; need good standard behaviour

HIGH

concept

SI

TB: should be based on @Luis Marco-Ruiz / @Diego Bosca et al work on the wiki pages:

 

concept

SI

SI: need support for system & party types
TB: this is just a question of giving AQL visibility of any RM, e.g. via a BMM or JSON-schema.

07-Dec: moved to v1.2.0

 

syntax

SI, TB

 

 

syntax

SI, TB

 

 

doc

SI

TB: should become AT_TIME, as suggested by Seref, and be documented to mean clinical (i.e. ‘world’) time, not commit time. Requires formal changes.

 

doc

SI

TB: this should be defined in terms of a generic set of rules that tell a query process what things to ignore; this CR is just one specific rule.

 

syntax

SI, TB

 

Support for UNION

 

syntax

SI

 

Support for FOLDERs

 

syntax

SI

TB: supported generically by use of RM model (i.e. BMM, JSON-schema or similar).

Support for TAGs

 

syntax

SI

SI: TAGs should use functions

functions / UDF

 

concept

SI

 

 

syntax

SI

 

 

concept / syntax

SI

TB: this also requires access to an RM description that shows what ‘links’ are logically containment etc

terminology and value sets

 

 

 

should be covered by SPECQUERY-12 ?

Support for SET (declarations)

 

syntax

 

 

 

concept / syntax

SI

07-Dec splitted original ticket in two tickets, GROUP BY and HAVING moved to v1.2.0

 

concept / syntax

 

 

 

concept / syntax

SI

 

 

 

 

 

Open Questions

Question

Answer

Date Answered

Question

Answer

Date Answered

 

Out of Scope

  • REST Api specification for AQL