Cardinality > 1, distinguish between Map / Array

[alexgordtop]

The model should distinguish for attributes with cardinality > 1, it it is a kind of array/list or a kind of object/map.

This is relevant for Value-Only serialization only. For Normal it is always an array.

[BirgitBoss]

In Part 2 for interfaces

Mandatory and Cardinality are distinguished. So there might be an optional element but the cardinality is 1. No Null object allowed in this case.

Similar we can add an additional column to the class definitions. For all cases with 0..1, 0..* etc. we need to define whether empty lists or NULL objects are allowed. To be backward compatible to the schema implementations we would have in the moment:

• mandatory: false
• Cardinality: 1 or 1..*
  etc.

[s-heppner]

If I get this correctly, you want to specify in the model how a given attribute with cardinality > 1 should be implemented? (As a list or an array?)

That is nothing a technology-neutral model should specify in my opinion. What if there was an AAS implementation in a programming language that handles multivalued attributes differently and does not offer one or the other?
If you want to specify this, it should be in the return value of the API call, imo.

Please correct me, if I didn't get the problem right.