While doing the write up for the change we identified some wording enhancements which would make the text easier to understand as well as some other types which do not follow the same rules for the BrowseNames.

Regarding the text updates this is the original text in the spec:
=============START===============
This complex VariableType is used for diagnostic information. For each entry of the array, instances of this type will provide a Variable of the SubscriptionDiagnosticsType VariableType having the SubscriptionId as BrowseName. The VariableType is formally defined in Table 71 .
==============END================
I would consider that text easier to understand:
=============START===============
This complex VariableType is used for diagnostic information. For each entry of the array, instances of this type will provide a Variable of the SubscriptionDiagnosticsType VariableType (defined in Table 72) having the SubscriptionId as BrowseName. The SubscriptionDiagnosticsArrayType VariableType is formally defined in Table 71.
==============END================

The other three arrays not following the same concepts are the SamplingIntervalDiagnostics, SessionDiagnostics and SessionSecurityDiagnostics.

SamplingIntervalDiagnosticsArrayType:
In this array type the only required change is to changed the BrowseName for components of the array to "<SamplingIntervalDiagnostics>" in Table 69 as the BrowseName in the text is the sampling rate of each element of the array and therefore is different for every component.

SessionDiagnosticsArrayType:
In this array type two changes are required to align them with the others. First the actual BrowseName needs to be changed to actually use something to identify the element. Right now the BrowseName is set to "SessionDiagnostics" for every element. Instead it should be using something being unique like the SessionId or helps identifying the element like the SessionName. To do that the text needs to be changed to this:
=============START===============
This complex VariableType is used for diagnostic information. For each entry of the array instances of this type will provide a Variable of the SessionDiagnosticsVariableType VariableType, having the SessionId as BrowseName.
==============END================
Next also the BrowseName in Table 73 needs to be updated to "<SessionDiagnostics>".

SessionSecurityDiagnosticsArrayType:
In this array type two changes are required to align them with the others. First the actual BrowseName needs to be changed to actually use something to identify the element. Right now the BrowseName is set to "SessionSecurityDiagnostics" for every element. Instead it should be using something being unique like the SessionId or helps identifying the element like the SessionName. To do that the text needs to be changed to this:
=============START===============
This complex VariableType is used for diagnostic information. For each entry of the array instances of this type will provide a Variable of the SessionSecurityDiagnosticsType VariableType, having the SessionId as BrowseName. Those Variables will also be referenced by the SessionDiagnostics Objects defined by their type in 6.3.5. The VariableType is formally defined in Table 75. Since this information is security related, it should not be made accessible to all users, but only to authorised users.
==============END================
Next also the BrowseName in Table 75 needs to be updated to "<SessionSecurityDiagnostics>".

After review with Wolfgang Mahnke we agreed that no change should be made.

The ExposesItsArray is a rather old ModellingRule, before we introduced the “Placeholder” ModellingRules.
Part 3 clearly states for ExposesItsArray:
“The BrowseNames of those instances are not defined by the ModellingRule.”
That means, that the BrowseName of the InstanceDeclaration could be anything.
If we would create the type now we probably would have put <SubscriptionDiagnostics> into it, but the spec is not requiring this at all. I would not change it since this is changing a long-time-defined name, I cannot imagine that it would break anything (or help with anything).

The current description is not incorrect and since it has been this way for many years we will not change it. See detailed explanation in note.

Agreed to no-change required in Virtual F2F.