View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000169510000-004: Servicespublic2011-08-04 07:232012-02-09 22:51
ReporterKarl Deiretsbacher Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.01 
Fixed in Version1.02 
Summary0001695: Need to define behaviour when writing LocalizedText with Null Locale.
Description

Part 4 currently specifies the following behaviour:

"If a Server allows writing of Attributes 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 a locale shall delete the String for that locale. Writing a null String for the text and a null String for the LocaleId shall delete the entries for all locales."

One additional case has to be clarified: "Writing a null String for the LocaleId with a valid String for the text."
Adding such a variant to other language variants makes no sense since it would never be delivered to clients on a read.

Proposal:
Specify that Servers are allowed to reject such a Write operation.
Specify the StatusCode to be used.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Randy Armstrong

2011-08-23 17:36

administrator   ~0002848

The Invariant Locale is represented by a empty string "". This is a special local that represents the default. i.e. what you get if none of the preferred locales is available so Servers can choose to accept such values.

However, there is no requirement to support all possible locales so we need a Bad_LocaleNotSupported if a client attempts to write a locale that is either syntatically invalid or not supported.

Matthias Damm

2011-09-13 00:01

developer   ~0002942

Added two clarifications to 5.10.4 Write description:
(1) Writing a null String for the locale and a text is setting the text for an invariant locale.
(2) If a Client attempts to write a locale that is either syntatically invalid or not supported, the Server returns Bad_OutOfRange.

Changed in document version OPC UA Part 4 - Services 1.02.07 Draft.doc

Randy Armstrong

2011-09-14 19:43

administrator   ~0002970

Discussed at F2F

Issue History

Date Modified Username Field Change
2011-08-04 07:23 Karl Deiretsbacher New Issue
2011-08-23 17:36 Randy Armstrong Note Added: 0002848
2011-08-23 17:36 Randy Armstrong Status new => assigned
2011-08-23 17:36 Randy Armstrong Assigned To => Matthias Damm
2011-09-13 00:01 Matthias Damm Status assigned => resolved
2011-09-13 00:01 Matthias Damm Resolution open => fixed
2011-09-13 00:01 Matthias Damm Note Added: 0002942
2011-09-14 19:39 Randy Armstrong Issue cloned: 0001738
2011-09-14 19:43 Randy Armstrong Status resolved => closed
2011-09-14 19:43 Randy Armstrong Note Added: 0002970
2012-02-09 22:51 Jim Luth Fixed in Version => 1.02
2012-02-09 22:51 Jim Luth Description Updated