It seems I can not edit my own issue. I meant to say that the ValueRank attribute of MultiStateValueDiscreteType is -2, not -1.

This issue was initially discussed here: https://github.com/open62541/open62541/issues/3826

The problem occures, when implementing the PADIM companion specification

MultiStateValueDiscreteType (ns=0;i=11238, ValueRank=-2[ANY]) --HasSubtype-->MultiStateDictionaryEntryDiscreteBaseType (ns=0;i=19077, ValueRank=-1[SCALAR]) --HasSubtype-->MultiStateDiscreteSignalVariableType(ns=PADIM;i1142, ValueRank=-2[ANY])

According to https://reference.opcfoundation.org/v104/Core/docs/Part3/6.2.7/ either MultiStateDictionaryEntryDiscreteBaseType should be ValueRank=-2, or MultiStateDiscreteSignalVariableType should have ValueRank=-1

Either PA-DIM needs to change to ValueRank = -1, or Part 19 needs to change to ValueRank=-2. Not sure which makes sense.

During the August 27, 2019 TWG review of the Part 19 draft the ValueRank of the MultiStateDictionaryEntryDiscreteBaseType was changed to a Scalar.
During this review it was noted that since it is a subtype of MultiStateValueDiscreteType (defined in Part 8) which has a ValueRank of Scalar then it also needs to be Scalar.
Reference to meeting recording is https://youtu.be/_pT2ka45LyE start listening at 1:52:00.

I suggest we advise FCG that the PA-DIM spec needs to be updated.

-

Agreed to change specs to match nodeset (that has always been "any" since 1.03). Affects Part 8 and Part 19. Need Errata for 1.03 and 1.04.
Nodeset also needs to be changed (1.04) for MultistateDictionaryEntryDiscreteBaseType and MultistateDictionaryEntryDiscreteType from Scalar to Any.

While making the changes to Part 19 I realized that while we can change MultiStateDictionaryEntryDiscreteBaseType to have a ValueRank of Any we can not do that with MultiStateDictionaryEntryDiscreteType. This is because of the ValueAsDictionaryEntries component which is mandatory in MultiStateDictionaryEntryDiscreteType. This component provides NodeIds (one per dictionary) for the current value. Since each value of an array may have a different value then the NodeIds would need to be a 2 dimensional array which it is not.

After discussions with PA-DIM they have decided to change their spec to Scalar so no change is required here.

Agreed to no-fix in Virtual F2F.