Search

5 result(s) for Names

• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.2 Encoding Rules for different kinds of DataTypes
  String that meets the requirements. This will result in text based DataEncodings with Names that are not friendly to human readers
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.51 StructureField
  String that meets the requirements. This will result in text based DataEncodings with Names that are not friendly to human readers
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.52 EnumField
  String that meets the requirements. This will result in text based DataEncodings with Names that are not friendly to human readers
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.13 Name Encoding Rules
  based DataEncodings such as UA XML ( 5.3 ) or UA JSON ( 5.4 ) make use of Names from the DataType and DataTypeDefinition to create the serialized data. XML and JSON formats impose ... serialized data so it is necessary to define a transformation that ensures any Names can be used in the DataEncoding . The following rules are used to convert a DataType Name
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.16.3.2 PubSubCommunicationModelConfigurationType definition
  AutomationComponents, see E.2 , and for the SKS, see E.5 . The ConfigurationValues Variable contains the names and identifiers that were assigned by EstablishConnections . They correspond to null names or 0 identifiers ... this does not apply since the entity generating PubSub configuration could uniquely determine all names and identifiers. For certain elements in PubSubConfiguration , the entity generating the ConnectionConfigurationSet may set their