06/23/2022
I got a tips from I’m assuming Randy Armstrong here: https://github.com/OPCF-Member…../issues/12 that enums with names that includes a dash ‘-‘ is not valid, and it needs to be proper SymbolicNames.
I’m assuming this would be invalid:
<UADataType NodeId=”ns=1;i=71″ BrowseName=”1:CtlModelKind”>
<DisplayName>CtlModelKind</DisplayName>
<References>
<Reference ReferenceType=”HasProperty”>ns=1;i=72</Reference>
<Reference ReferenceType=”HasSubtype” IsForward=”false”>i=29</Reference>
</References>
<Definition Name=”1:CtlModelKind”>
<Field Name=”status-only” Value=”0″ />
<Field Name=”direct-with-normal-security” Value=”1″ />
<Field Name=”sbo-with-normal-security” Value=”2″ />
<Field Name=”direct-with-enhanced-security” Value=”3″ />
<Field Name=”sbo-with-enhanced-security” Value=”4″ />
</Definition>
</UADataType>
I see some related changes done to the NodeSet files here: IEC61850/Opc.Ua.IEC61850-6.NodeSet2.xml
I cannot find this requirement in the NodeSet XML schema file: https://files.opcfoundation.or…..odeSet.xsd
To me it looks like the Name attribute can be a type=”xs:string”, and the changes done to the Name attribute in the IEC61850 NodeSet file is not needed.
Is there something I’m missing here?
05/30/2017
https://reference.opcfoundatio…../docs/F.13
A symbolic name for the field that can be used in autogenerated code. It should only be specified if the Name cannot be used for this purpose. Only letters, digits or the underscore (‘_’) are permitted. |
IOW, the implied requirement is the Name can only have letters, digits or the underscore (‘_’) unless a SymbolicName is specified.
Such requirements cannot be captured by the XML schema definition.
1 Guest(s)