View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000774210000-006: MappingsSpecpublic2022-02-16 17:072023-01-03 16:41
ReporterLiam Power Reduktive Assigned ToRandy Armstrong  
PrioritynormalSeverityminorReproducibilityN/A
Status closedResolutionduplicate 
Product Version1.05.00 
Fixed in Version1.05.03 RC1 
Summary0007742: Requirement for escaping characters in NodeId string identifier
Description

Section 5.3.1.11 ExpandedNodeId states: "Any reserved characters in the URI shall be replaced with a ‘%’ followed by its 8
bit ANSI value encoded as two hexadecimal digits (case insensitive). For example, the character ‘;’ would be replaced by ‘%3B’"

Is this also the case for for a string identifier in a NodeId?

Section 5.3.1.10 states: "Note that the Identifier may contain any non-null UTF-8 character including whitespace."

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

duplicate of 0006720 closedRandy Armstrong Simplified JSON encoding as a text string for BuiltIn types ExpandedNodeId and QualifiedName 

Activities

Randy Armstrong

2022-12-27 11:44

administrator   ~0018352

Issue is fixed by the new normative NodeId string representation.

Jim Luth

2023-01-03 16:41

administrator   ~0018389

agreed to overlap with related issue (duplicate).

Issue History

Date Modified Username Field Change
2022-02-16 17:07 Liam Power Reduktive New Issue
2022-03-11 17:01 Jim Luth Assigned To => Randy Armstrong
2022-03-11 17:01 Jim Luth Status new => assigned
2022-12-27 11:44 Randy Armstrong Status assigned => resolved
2022-12-27 11:44 Randy Armstrong Resolution open => duplicate
2022-12-27 11:44 Randy Armstrong Fixed in Version => 1.05.03
2022-12-27 11:44 Randy Armstrong Note Added: 0018352
2022-12-27 11:44 Randy Armstrong Relationship added duplicate of 0006720
2022-12-28 06:43 Randy Armstrong Fixed in Version 1.05.03 => 1.05.03 RC1
2023-01-03 16:41 Jim Luth Status resolved => closed
2023-01-03 16:41 Jim Luth Note Added: 0018389