DataType of i=17292 in Opc.Ua.NodeSet2.xml

[basyskom-jvoe]

The node with the id i=17292 has the "String" DataType and a HasTypeDefinition reference to i=16309.

<UAVariable NodeId="i=17292" BrowseName="TransportProfileUri" ParentNodeId="i=14417" DataType="String">
    <DisplayName>TransportProfileUri</DisplayName>
    <References>
      <Reference ReferenceType="HasProperty">i=17706</Reference>
      <Reference ReferenceType="HasTypeDefinition">i=16309</Reference>
      <Reference ReferenceType="HasModellingRule">i=78</Reference>
      <Reference ReferenceType="HasComponent" IsForward="false">i=14417</Reference>
    </References>
  </UAVariable>

The DataType of i=16309 is i=862

  <UAVariableType NodeId="i=16309" BrowseName="SelectionListType" DataType="i=862" ValueRank="-2">
    <DisplayName>SelectionListType</DisplayName>
    <References>
      <Reference ReferenceType="HasProperty">i=17632</Reference>
      <Reference ReferenceType="HasProperty">i=17633</Reference>
      <Reference ReferenceType="HasProperty">i=16312</Reference>
      <Reference ReferenceType="HasSubtype" IsForward="false">i=63</Reference>
    </References>
  </UAVariableType>

Which is a structured type.

  <UADataType NodeId="i=862" BrowseName="ServerStatusDataType">
    <DisplayName>ServerStatusDataType</DisplayName>
    <References>
      <Reference ReferenceType="HasSubtype" IsForward="false">i=22</Reference>
    </References>
    <Definition Name="ServerStatusDataType">
      <Field Name="StartTime" DataType="i=294" />
      <Field Name="CurrentTime" DataType="i=294" />
      <Field Name="State" DataType="i=852" />
      <Field Name="BuildInfo" DataType="i=338" />
      <Field Name="SecondsTillShutdown" DataType="i=7" />
      <Field Name="ShutdownReason" DataType="i=21" />
    </Definition>
  </UADataType>

Is this an error in the schema file or is an instance permitted to override the DataType attribute of its type definition node?

[opcfoundation-org]

Instances can override with a subtype of the datatype in the type definition.
What you report here seems to be an error which has already been fixed.