Search

9 result(s) for QualifiedNames

• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.3.2 Parameters
  arrays in the response. namespaceUris [] String A list of URIs referenced by NodeIds or QualifiedNames in the request. NamespaceIndex 0 shall not be in this list. The first entry ... serviceId . Response namespaceUris [] String A list of URIs referenced by NodeIds or QualifiedNames in the response. NamespaceIndex 0 shall not be in this list. The first entry in this list
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.31 DataTypeSchemaHeader
  array is referred to as NamespaceIndex . The NamespaceIndex is used in NodeIds and QualifiedNames , rather than the longer namespace URI. NamespaceIndex 0 is reserved for the OPC UA namespace ... used in the data that follows the DataTypeSchemaHeader . The index used in NodeId and QualifiedNames identify an element in this list. The first entry in this array maps to NamespaceIndex
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.12 QualifiedName, NodeId and ExpandedNodeId String Encoding
  QualifiedName, NodeId and ExpandedNodeId String Encoding QualifiedNames , NodeIds and ExpandedNodeIds optimize representation of NamespaceUris by using a NamespaceIndex to reference the location of the URI in a NamespaceTable . The NamespaceTable ... name> <name> = 1*(UNICODE) <short-index> = 1*DIGIT QualifiedNames in the OPC UA Namespace shall not use the form with a <namespace
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.2 UANodeSet
  URIs for namespaces used in the UANodeSet . The NamespaceIndexes used in NodeId, ExpandedNodeIds and QualifiedNames identify an element in this list. The first index is always 1 (0 is always
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.14 Variant
  used to serialize Variant in this file syntax. Variants can contain NodeIds , ExpandedNodeIds and QualifiedNames which must be modified so the NamespaceIndexes and ServerIndexes reference the NamespaceUri and ServerUri tables ... EncodingId and a Structure with fields which with any DataType including NodeIds , ExpandedNodeIds or QualifiedNames . The NamespaceIndexes and ServerIndexes in these fields shall also reference the tables in the UANodeSet
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.2.2 ExtensionFieldsType
  headers can be included in the body by adding extension fields with well-known QualifiedNames . These well-known QualifiedNames are shown in Table 249 . The qualifying namespace
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.6.6 Loading / Saving ConnectionConfigurationSets
  provides the following instructions related to NodeIds : " Variants can contain NodeIds , ExpandedNodeIds and QualifiedNames that must be modified, so the NamespaceIndexes and ServerIndexes reference the NamespaceUri and ServerUri tables
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.1.4 Additional Attribute values
  value field. Double quotes are not included. If the DataType includes a NamespaceIndex ( QualifiedNames , NodeIds or ExpandedNodeIds ) then the notation used for BrowseNames is used. If the value
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  4.2.3.2 Namespaces
  types of structured values in OPC UA that are qualified with NamespaceIndexes : NodeIds and QualifiedNames . NodeIds are locally unique (and sometimes globally unique) identifiers for Nodes . The same globally unique ... Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames