Search

11 result(s) for Body

• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.3.1 Description
  RequestHeader and ResponseHeader like other Services . Those parameters are already part of the body which contains the Message for the Service to invoke. Any Endpoint used for normal communication could ... does not support Session -less invocation for the request specified in the body . If it supports invocation but not with the combination of Endpoint and security settings used it returns
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.2.15 ExtensionObject
  able to seek backwards in the stream and update the length after encoding the body. When a decoder encounters an ExtensionObject it shall check if it recognizes the DataTypeEncoding identifier ... does, then it can call the appropriate function to decode the object body. If the decoder does not recognize the type, it shall use the Encoding to determine
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.4.2.17 Variant
  Variant Name Description UaType The built-in type for the value contained in the Body (see Table 1 ) encoded as JSON number. Value If the value is a scalar
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.4.3 Decimal
  encoded as an ExtensionObject with the JSON object in Table 43 as the Body . The TypeId shall be the NodeId of the Decimal DataType and the Encoding shall
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  G.3 OpenAPI Mapping
  Table G.1 - OpenAPI Message Envelope Name Type Description ServiceId NodeId The DataTypeId for the Body . LocaleIds [] LocaleId List of locale ids to use when creating a Response to a Request ... specified for Response messages. Body * The Request or Response associated with the Service . The ServiceId indicates the content of the Body. The authorization header needs to be handled
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  H.7 ExtensionObject
  DataType Node formatted using the rules in H.2 . Encoding The format of the Body field encoded as a JSON number. This value is 0 if the body is Structure encoded ... JSON object. This value is 1 if the body is a ByteString value encoded as a JSON string. This value is 2 if the body is a XmlElement value encoded
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  H.8 Variant
  Variant Name Description Type The built-in type for the value contained in the Body (see Table 1 ) encoded as JSON number. If type is 0 (NULL) the Variant contains ... replaced by the JSON literal 'null' (when an element of a JSON array). Body If the value is a scalar, it is encoded using the rules for type specified
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.7.1 PubSubConfigurationType
  encoded stream containing an instance of UABinaryFileDataType that contains a PubSubConfiguration2DataType or subtype as Body . The UABinaryFileDataType is defined in OPC 10000-5 . The PubSubConfiguration2DataType is defined
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.7.6 CloseAndUpdate Method
  changed. The file content shall be a UABinaryFileDataType with a PubSubConfiguration2DataType as Body . The ConfigurationReferences argument specifies the configuration elements to add, modify or remove. Configuration elements in PubSubConfiguration2DataType that ... Description Bad_TypeMismatch The file content is not a UABinaryFileDataType with a PubSubConfiguration2DataType as Body . Bad_InvalidArgument The file handle is not valid. Bad_InvalidState The file was not opened
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.2 ConnectionConfigurationSet file content
  file content. The structure of the UABinaryFileDataType file is illustrated in Table F.37 . Its Body contains an array of ConnectionConfigurationSetConfDataType or a subtype of it. Table F.37 - ConnectionConfigurationSet file content ... String[] Contains the namespaces used for the data that is contained in the Body of the File . As a minimum, the http://opcfoundation.org/UA/ and http://opcfoundation.org/UA/FX/CM/ namespace shall
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.3.3.1 CloseAndUpdate signature
  TypeMismatch The file content is not a UABinaryFileDataType with an array of ConnectionConfigurationSetConfDataType as Body . Bad_InvalidArgument The FileHandle is not valid. Bad_InvalidState The File was not opened ... allowed to modify the ConnectionManager configuration. Bad_NothingToDo The array in the Body of the File is null or empty. Table F.41 - CloseAndUpdate OperationResult Element Result Codes ResultCode Description