You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ossie.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2026/10/09 04:42:27 UTC
[INFO][SPEC] Adding HOLISTICS_AQL dialect to core specification (PR #538)
Hi everyone,
As part of the work on PR #538, which introduces a bidirectional converter
between Apache Ossie and Holistics AML (Analytics Modeling Language), we
are registering HOLISTICS_AQL as a supported dialect in the Ossie
core specification.
### Summary of Changes
1. Core Specification & Schema:
• Added HOLISTICS_AQL to the dialects enumeration in:
• core-spec/spec.yaml
• core-spec/spec.md
• core-spec/ossie-schema.json
• python/src/ossie/models.py (OssieDialect.HOLISTICS_AQL)
2. Dialect Semantics & Validation:
• Analytical Query Language (AQL) is Holistics' relationship-aware
formula language used in AML metric and dimension definitions.
• Like other non-SQL domain languages already supported by Ossie
(e.g., MDX, MAQL, THOUGHTSPOT, DAX), HOLISTICS_AQL expressions are
preserved verbatim and excluded from standard sqlglot SQL parsing in
validation/validate.py.
• The addition is strictly additive and non-breaking for existing
models.
### Pull Request & Discussion
The full implementation, documentation, and tests can be reviewed in:
• PR #538: https://github.com/apache/ossie/pull/538
Please let us know if there are any questions, comments, or feedback on
this addition.
This is a good practice I'm proposing to inform the community when specs
are updated without vote (for non breaking change addition or documentation
clarification).
Thanks,
JB
Re: [INFO][SPEC] Adding HOLISTICS_AQL dialect to core specification (PR #538)
Posted by Justin Talbot via dev <de...@ossie.apache.org>.
Thanks JB. A heads up on things like this is very much appreciated!
If we don't have it yet, we should document what being a "supported Ossie
dialect" entails.
If Ossie is to be an interchange format, diverse dialects make interchange
substantially harder. (At least it would have, pre-LLM.) Are there any
expectations around public-facing documentation of the dialect? A converter
between the dialect and the official Ossie SQL dialect?
Conversely, does making a dialect officially supported imply any
expectations on Ossie? For example, maybe we won't adopt features unless
they can be expressed in all of our supported dialects?
Alternatively, if being a supported dialect only means it gets a reserved
enum value with no other expectations, we should document that, along with
best practices for interchange. E.g. users interested in interchange should
restrict themselves to the official Ossie SQL dialect.
Justin
On Thu, Oct 8, 2026 at 9:42 PM Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> Hi everyone,
>
> As part of the work on PR #538, which introduces a bidirectional converter
> between Apache Ossie and Holistics AML (Analytics Modeling Language), we
> are registering HOLISTICS_AQL as a supported dialect in the Ossie
> core specification.
>
> ### Summary of Changes
> 1. Core Specification & Schema:
> • Added HOLISTICS_AQL to the dialects enumeration in:
> • core-spec/spec.yaml
> • core-spec/spec.md
> • core-spec/ossie-schema.json
> • python/src/ossie/models.py (OssieDialect.HOLISTICS_AQL)
> 2. Dialect Semantics & Validation:
> • Analytical Query Language (AQL) is Holistics' relationship-aware
> formula language used in AML metric and dimension definitions.
> • Like other non-SQL domain languages already supported by Ossie
> (e.g., MDX, MAQL, THOUGHTSPOT, DAX), HOLISTICS_AQL expressions are
> preserved verbatim and excluded from standard sqlglot SQL parsing in
> validation/validate.py.
> • The addition is strictly additive and non-breaking for existing
> models.
>
> ### Pull Request & Discussion
> The full implementation, documentation, and tests can be reviewed in:
>
> • PR #538: https://github.com/apache/ossie/pull/538
>
> Please let us know if there are any questions, comments, or feedback on
> this addition.
>
> This is a good practice I'm proposing to inform the community when specs
> are updated without vote (for non breaking change addition or documentation
> clarification).
>
> Thanks,
> JB
>