View Issue Details

IDProjectCategoryView StatusLast Update
000926010000-006: MappingsSpecpublic2024-03-21 22:39
ReporterMatthias Damm Assigned ToRandy Armstrong  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version1.05.02 
Fixed in Version1.05.04 RC1 
Summary0009260: XML value encoding in UANodeset for unknown XML encodingID
Description

We have a XML export feature in a client where the client can browse/read a server and export a namespaces as UANodeset XML.
Currently we export the values in binary encoded form if they are complex and not namespace 0
But this creates problems with modeling tools that do not support binary encoding.

Now we want to implement the XML encoding for all data but a lot of servers do not expose the XML encoding IDs for their structures if they do not support XML encoding.

Therefore we do not know the XML EncodingID for the structures. But the XML encoding of ExtensionObjects requires the knowledge of the EncodingId.

It Is currently not allowed to use the DataType NodeId instead.

The XML encodingId only works in client/server communication if the server provides the XML encoding IDs.

TagsNo tags attached.
Commit Version1.05.04 RC
Fix Due Date2024-01-30

Activities

Randy Armstrong

2024-02-03 05:20

administrator   ~0020758

Added a mapping from DataTypeEncoding NodeIds to DataType NodeIds. This mapping is only needed if default values for one or more Structures in the UANodeSet have a DataType that is not defined in the current UANodeSet or in the core UANodeSet.

Jim Luth

2024-03-21 22:39

administrator   ~0021000

Agreed to changes edited in Dallas F2F.

Issue History

Date Modified Username Field Change
2023-11-13 14:25 Matthias Damm New Issue
2023-12-05 21:04 Jim Luth Assigned To => Randy Armstrong
2023-12-05 21:04 Jim Luth Status new => assigned
2023-12-05 21:04 Jim Luth Commit Version => 1.05.04 RC
2023-12-05 21:04 Jim Luth Fix Due Date => 2024-01-30
2024-02-03 05:20 Randy Armstrong Status assigned => resolved
2024-02-03 05:20 Randy Armstrong Resolution open => fixed
2024-02-03 05:20 Randy Armstrong Note Added: 0020758
2024-03-21 22:39 Jim Luth Status resolved => closed
2024-03-21 22:39 Jim Luth Fixed in Version => 1.05.04 RC1
2024-03-21 22:39 Jim Luth Note Added: 0021000