View Issue Details

IDProjectCategoryView StatusLast Update
001041310000-003: Address SpaceSpecpublic2025-09-22 11:22
ReporterKároly Szabó Assigned ToJeff Harding  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version1.05.04 
Fixed in Version1.05.06 
Summary0010413: CONTROL Characters in Standard Data Type String
Description

The following update in the specification was introduced in 1.05.03

Opc UA Part 3 1.04 / 8.32 String
This Built-in DataType defines a Unicode character string that should exclude control characters
that are not whitespaces.
Opc UA Part 3 1.05.04 / 8.31 String
This Built-in DataType defines a Unicode character string that should exclude control characters. Unicode control characters are defined by Unicode C0 and Unicode C1

This a breaking change and would not allow white space charters or multi line strings, because '\t' (tab), '\n' (line feed), '\r' (carriage return) are part of Unicode C0.

This change was not mentioned in the Revision 1.05.03 Highlights. It seems like this was changed by mistake.
The only related mention is this:
"The CONTROL Characters not Allowed in NodeIds, QualifiedNames and ExpandedNodeIds." https://mantis.opcfoundation.org/view.php?id=9163

TagsNo tags attached.
Commit Version1.05.06
Fix Due Date2025-09-15

Activities

Jim Luth

2025-07-22 16:20

administrator   ~0023157

Clarify that Unicode Control Characters that are also Unicode whitespace characters are allowed.

Jeff Harding

2025-09-15 14:13

developer   ~0023281

Added statement about whitespace characters being acceptable and referencing the Unicode property list which defines what a whitespace character is.

Jim Luth

2025-09-22 11:22

administrator   ~0023315

Agreed to changes in F2F.

Issue History

Date Modified Username Field Change
2025-07-03 10:30 Károly Szabó New Issue
2025-07-22 16:20 Jim Luth Note Added: 0023157
2025-07-22 16:21 Jim Luth Assigned To => Jeff Harding
2025-07-22 16:21 Jim Luth Status new => assigned
2025-07-22 16:21 Jim Luth Commit Version => 1.05.06
2025-07-22 16:21 Jim Luth Fix Due Date => 2025-09-15
2025-09-15 14:13 Jeff Harding Status assigned => resolved
2025-09-15 14:13 Jeff Harding Resolution open => fixed
2025-09-15 14:13 Jeff Harding Fixed in Version => 1.05.06
2025-09-15 14:13 Jeff Harding Note Added: 0023281
2025-09-22 11:22 Jim Luth Status resolved => closed
2025-09-22 11:22 Jim Luth Note Added: 0023315