Search

Scope: Core (OPC-10000-*) All specs

13 result(s) for locale

OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.11.4.1 Description

with the DataType LocalizedText , the Client can add or overwrite the text for a locale by writing the text with the associated LocaleId . Writing a null String for the text ... locale shall delete the String for that locale. Writing a null String for the locale and a non-null String for the text is setting the text for an invariant
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.7.3 FilterOperator

sequence of hexadecimal digits. LocalizedText values are converted to Strings by dropping the Locale . Strings are converted to LocalizedText values by setting the Locale to "". QualifiedName values
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.12 DiagnosticInfo

localizedText contains a translation for the description of a StatusCode , the symbolicId is -1. locale Int32 The locale part of the vendor-specific localized text describing the symbolic id. This ... Client in the stringTable parameter of the ResponseHeader parameter defined in 7.33 . The locale parameter contains the index into the stringTable for this string. -1 indicates that no string
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.2.12 DiagnosticInfo

encoded form. As described in OPC 10000-4 , the SymbolicId , NamespaceUri , LocalizedText and Locale fields are indexes in a string table which is returned in the response header. Only ... mask has the following bits: 0x01 Symbolic Id 0x02 Namespace 0x04 LocalizedText 0x08 Locale 0x10 Additional Info 0x20 InnerStatusCode 0x40 InnerDiagnosticInfo SymbolicId Int32 A symbolic name for the status code
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.13 DiagnosticInfo

default value is -1. It is not encoded if the value is -1. Locale Int32 The locale used for the localized text. The default value ... null. It is not encoded if the value is null. The SymbolicId , NamespaceUri , Locale and LocalizedText fields are encoded as JSON numbers which reference the StringTable contained in the ResponseHeader
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.15 LocalizedText

shown in Table 39 . Table 39 - JSON Object Definition for a LocalizedText Name Description Locale The Locale portion of LocalizedText values shall be encoded as a JSON string. The field
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

H.6 LocalizedText

shown in Table H.5 . Table H.5 - JSON Object Definition for a LocalizedText Name Description Locale The Locale portion of LocalizedText values shall be encoded as a JSON string Text
OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture

14.3 Mapping of ISDU Errors in DiagnosticInfo

symbolicId Error Code and Additional Code as 4-digit hex number "0x8012" locale Locale of localizedText "en" localizedText String that describes the symbolicId "Subindex ... Link Specification ) as 4-digit hex number converted to a String. The field locale contains the country and region description of the language that is used in localizedText. The field
OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture

14.4.1 No IODD information available

Table C.1 or Table C.2 in column "Incident" as localizedText . Default locale is "en". Servers may provide vendor-specific translations to other languages. (In this case ... they have to adjust the value of locale as well.) If the combination of IO-Link Error Code and Additional Code is vendor-specific (0x8101 to 0x81FF) no string shall
OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture

14.4.2 IODD information available

StandardDefinitions (see IODD Specification ), the server shall use text specified there with the appropriate locale as localizedText . Servers may provide vendor-specific translations to other languages. (In this case they ... have to adjust the value of locale as well.) If the combination of IO-Link Error Code and Additional Code is vendor-specific (0x8101 to 0x81FF) the IODD should contain
OPC-30130 – OPC UA for Control & Communication System Profile(for Machine)

6.4.8.2.1 TwoStateDiscreteType VariableType

DATA item value of the Language element in the FILE_INFO part to the Locale element. When the LABEL2 item of the CSPP element is not specified, set the LABEL ... text element of the Value Attribute . Set "en-US" to the Locale element
OPC-30130 – OPC UA for Control & Communication System Profile(for Machine)

6.4.8.2.2 MultiStateDiscreteType VariableType

DATA item value of the Language element in the FILE_INFO part to the Locale element. When the LABEL2 item of the CSPP element is not specified, set the LABEL ... item value to the text element. Set "en-US" to the Locale element
OPC-30130 – OPC UA for Control & Communication System Profile(for Machine)

6.4.8.2.3 MultiStateValueDiscreteType VariableType

DATA item value of the Language element in the FILE_INFO part to the locale element for the Display element. When the LABEL2 item of the CSPP element ... LABEL item value to the text element. Set "en-US" to the Locale element