If I read the error message correctly, those elements are missing on the NamespaceMetaDataType not on an instance. Types in general are required to have all elements available even optional ones. Optional fields can only be missed on instances of the types.

Could you please check if those elements are available on the type?

Yes, we only have the type here and no instances,
but we might have a misunderstanding about what optional means.
Do you have a pointer to the spec where this is explained?

Just think about the information modeling of OPC UA as being classes in programming. The declarations of classes are always required to be complete including all optional elements. Otherwise the class would not be considered the same. Exactly the same happens with OPC UA, e.g. to allow an aggregating server to determine if this specific type is already being exposed by itself, the server can have logic based on the type definitions. But if not all optional elements are available the type definitions would not be the same across the different servers and therefore no optimization would be possible.

Therefore a type definition always is required to be complete including all optional elements. In the instances though it is expected to omit any unsupported optional elements.

The mentioned (optional) properties were missing in the TypeDefinition i=11616 [NamespaceMetadataType].
If a Type is exposed in the TypeSystem of the server it must contain all elements defined in the specifications regardless of their ModellingRule.
Therefore no change to the test script is required.

Agreed to nochange - closed issue