Optional but empty arrays are considered an error

[otto-ifak]

Currently, arrays which are optional (i.e. not required) are considered as an error when present but empty.
Eg:

{
  "conceptDescriptions": []
}

is currently rejected.

We need to clarify if this is compliant to the spec.

[otto-ifak]

See also #13 (comment)

[otto-ifak]

I would argue for removing minItems: 1 from https://github.com/admin-shell-io/aas-test-engines/blob/main/aas_test_engines/data/file/3.0.yml then (currently 28 instances)

[sebbader-sap]

The desired behaviour, as agreed in the AAS Specification working group, is that no empty conceptDescriptions array is present. Therefore, the minItems: 1 clauses are correct.

[sebbader-sap]

We need to clarify if this is compliant to the spec.

It is :-)

[otto-ifak]

Great, thanks @sebbader-sap for clarifying this!

[juileetikekar]

Related issue in the specifications, admin-shell-io/aas-specs#418