Duplicate Include Library with distinct Aliases should not be allowed

[gregory-akins]

Using Cql-to-Elm translation, a Include with a distinct Alias is successfully translated, but should cause an error.

ie.,

include MATGlobalCommonFunctionsQDM version '8.0.000' called Global1
include MATGlobalCommonFunctionsQDM version '8.0.000' called Global2 

or

include MATGlobalCommonFunctionsQDM version '7.0.000' called Global1
include MATGlobalCommonFunctionsQDM version '8.0.000' called Global2 

According to CQL - https://cql.hl7.org/03-developersguide.html#libraries-1

The local [identifier](https://cql.hl7.org/03-developersguide.html#identifiers) for a referenced library must be [unqualified](https://cql.hl7.org/03-developersguide.html#qualified-identifiers) and unique within the artifact

Also, commented in CQL channel in Zuplip. https://chat.fhir.org/#narrow/channel/179220-cql/topic/Duplicate.20.27aliased.27.20libraries

Greg Akins: CQL-To-ELM allows the inclusion of different versions of a library if they're aliased, but not otherwise.

I can understand why non-aliased libraries aren't allowed, because they're not fully qualified.

cqframework/cql-to-elm appears to allow this, however.

Is that a defect in the translator, or is it compliant with the spec for CQL 1.5?

library MyLibrary version 1

include YourLibrary version 1 as YL1
include YourLibrary version 2 as YL2

JP: Currently forbidden by the spec (as I read it):
https://cql.hl7.org/03-developersguide.html#libraries-1

all references to the same library use the same version

So, bug in cql-to-elm. That said, there's some discussion here about it:
#758

Greg Akins: Thanks JP

Greg Akins: JP said:

Currently forbidden by the spec (as I read it):
https://cql.hl7.org/03-developersguide.html#libraries-1

    all references to the same library use the same version

So, bug in cql-to-elm. That said, there's some discussion here about it:
https://github.com/cqframework/clinical_quality_language/issues/758

Beside that issue, which isn't specifically related to the issue I described

Does anyone know if there is an existing issue for fixing cql-to-elm? If not, I can write one up

Bryn Rhodes: @greg Akins I'm not aware of any issues for this specifically, if you can submit an issue, that would be great, thank you!