0010286: Part 6, Section 5.1.13 XML Name Encoding Rules

ID	Project	Category	View Status	Date Submitted	Last Update

0010286	10000-006: Mappings	Spec	public	2025-04-15 03:45	2025-04-15 15:07

Reporter	Kevin Herron (Inductive Automation)	Assigned To	Randy Armstrong
Priority	normal	Severity	minor	Reproducibility	always
Status	assigned	Resolution	open
Product Version	1.05.04

Summary	0010286: Part 6, Section 5.1.13 XML Name Encoding Rules
Description	https://reference.opcfoundation.org/Core/Part6/v105/docs/5.1.13 This section says: The following rules are used to convert a DataType Name or a Structure Field Name to a string supported by the Encoding: Any character that is not permitted by the DataEncoding is replaced by an underscore (U+005F); A name with text sequence that is not valid in the first position has an underscore (U+005F) added as a prefix. But the examples it lists in Table 8 do not consistently apply these rules. `_Hello` should become `__Hello`
Tags	No tags attached.

Commit Version
Fix Due Date

Date Modified	Username	Field	Change
2025-04-15 03:45	Kevin Herron (Inductive Automation)	New Issue
2025-04-15 03:50	Kevin Herron (Inductive Automation)	Note Added: 0022639
2025-04-15 15:06	Jim Luth	Assigned To	=> Randy Armstrong
2025-04-15 15:06	Jim Luth	Status	new => assigned
2025-04-15 15:07	Jim Luth	Project	10000-004: Services => 10000-006: Mappings

Kevin Herron (Inductive Automation) 2025-04-15 03:50 reporter ~0022639	I think the example for `3 (冷水。)-Hello` is wrong too. Spec says it should be `_3__冷水___-Hello`, but I think it should be `_3__冷水__-Hello` (one less underscore before -Hello)