Avoid validation warning for choices that are allowed to occur multiple times

[JohannaOtt]

Description done with an example case to make the schema construct easier to understand: Work with omso:ProfileObservation

The element result.ReferenceableGridCoverage.rangeSet.ValueArray.valueComponents can contain multiple occurrences of the choice used in it. That means, if multiple values (e.g. AbstractValue.Count and AbstractValue.QuantityList) are provided for one object, the transformed data should be valid. But there is a validation warning:

According to the relevant schema,

• ValueArray (expanding CompositeValue) is referencing valueComponent
• valueComponents is using the ValueArrayPropertyType
• the ValueArrayPropertyType is using a sequence with group:Value that can occur n times (unbounded)
  --> this means that it can be replaced by multiple group:Value elements (which are using various abstract elements respectively their children) and there should be no validation warning in hale studio

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in two weeks if no further activity occurs. Thank you for your contributions.

[florianesser]

@JohannaOtt I think this can only be investigated meaningfully with a reproduction case. Do you still happen to have the project that caused this problem?

I've tried to create a simple reproduction case (attached here) but couldn't get the same validation message when adding two Count elements to valueComponents. Would be great if you could check if the repro case does in fact recreate the situation that you reported, given that it uses the type ElevationGridCoverage instead of ReferenceableGridCoverage.
issue955.zip

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in two weeks if no further activity occurs. Thank you for your contributions.

[JohannaOtt]

I created this repo case
955.zip

It has many validation warnings as I did not aim to fill al mandatory elements but it also has the validation warning described in this issue