View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003867 | 10000-006: Mappings | Spec | public | 2017-06-09 08:45 | 2020-04-21 15:06 |
Reporter | smyrman | Assigned To | randyarmstrong | ||
Priority | high | Severity | major | Reproducibility | N/A |
Status | closed | Resolution | duplicate | ||
Platform | N/A | OS | N/A | OS Version | N/A |
Product Version | 1.03 | ||||
Summary | 0003867: Confusion between CharArray and String in the spec part 5/6 and https://opcfoundation.org/UA/schemas/1.03/Opc.Ua.Types.bsd.xml | ||||
Description | Conflicting definitions of String/CharArray in the Spec Part 6 and Part 5 Appendix E, as well as inconsequent usage of CharArray v.s. String in Opc.Ua.Types.bsd.xml. Perhaps should the later file use type String in place of CharArray for all fields? In detail: From the Spec part 6 (1.04 RC and 1.03): 5.2.2.4 StringAll String values are encoded as a sequence of UTF8 characters without a null terminator and preceded by the length in bytes. No mention of CharArray. WideString or WideCharArray. However, from the spec part 5: E.3 Standard Type Descriptions
If String in Part 6 was meant to be CharArray notice the difference between "length in bytes" v.s. "number of characters", as that matters quite a bit for UTF-8... (edited) For more fun, the XML type specification (https://opcfoundation.org/UA/schemas/1.03/Opc.Ua.Types.bsd.xml) mentions both CharArray and String as field types for various "Structured Types". E.g. in DiagnosticInfo the "AdditionalInfo" field is a "String" according to te Spec part 6, but a "CharArray" according to "Opc.Ua.Types.bsd.xml". The Argument "Name" field in "Opc.Ua.Types.bsd.xml" has the type "String", both in this file, and in the Spec part 3 (under 8.6 Argument) (edited) smyrman Annex E However, since CharArray is not defined in Part 6 (neither is WideString or WideCharArrray for UTF-16), I am confused about the destinction between CharArray and String in the "Opc.Ua.Types.bsd.xml" file | ||||
Steps To Reproduce | N/A | ||||
Additional Information | This is the second issue I report for https://opcfoundation.org/UA/schemas/1.03/Opc.Ua.Types.bsd.xml, the previous one reported in 2015. We are writing out own OPC UA Stack in Searis (http://www.searis.no) for the Go programming language, so it would be nice to get the XML file updated to facilitate easier/safer code generation. | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
duplicate of | 0003750 | closed | jeffhardingabb | 10000-005: Information Model | Table E.9 - CharArray should be renamed to String |
|
Update: This appears to be a duplicate of https://opcfoundation-onlineapplications.org/mantis/view.php?id=3750 and could be closed as such. |
|
BTW, should Annex E Part 5 also be updated? Or is this an historic reference only? |
|
@jeffhardingabb, the Annex E with the conflicting definition is in Part 5: Information Model Release Candidate 1.04.09. |
|
Duplicate. Closed in Apr 21th WG Meeting. |
Date Modified | Username | Field | Change |
---|---|---|---|
2017-06-09 08:45 | smyrman | New Issue | |
2017-06-09 08:47 | smyrman | Note Added: 0008218 | |
2017-06-09 08:52 | smyrman | Note Added: 0008219 | |
2017-06-09 08:59 | smyrman | Note Added: 0008220 | |
2017-06-09 09:03 | smyrman | Note Edited: 0008220 | |
2018-08-28 16:12 | Jim Luth | Project | UA Specification => 10000-006: Mappings |
2018-08-28 16:12 | Jim Luth | Assigned To | => randyarmstrong |
2018-08-28 16:12 | Jim Luth | Status | new => assigned |
2019-03-01 18:16 | randyarmstrong | Status | assigned => resolved |
2019-03-01 18:16 | randyarmstrong | Resolution | open => duplicate |
2019-03-01 18:16 | randyarmstrong | Relationship added | duplicate of 0003750 |
2020-04-21 15:06 | randyarmstrong | Status | resolved => closed |
2020-04-21 15:06 | randyarmstrong | Note Added: 0011949 |