View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000844110000-006: MappingsSpecpublic2022-11-18 15:282023-01-24 17:56
ReporterWolfgang Mahnke Assigned ToRandy Armstrong  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionreopened 
Fixed in Version1.05.03 RC1 
Summary0008441: Clarification on AllowSubtypes field usage in UaNodeSet
Description

In Table F.13 it is defined for AllowSubtypes:
This field is ignored if the DataType is BaseDataType, Structure or if the DataType is a subtype of simple built-in types such as a String or Int32.
...
This field shall be TRUE for all abstract DataTypes where the possible subtypes have different encodings.

This could be interpreted as for the BaseDataType or Structure DataType (which are abstract), you always have to set the field, but it is ignored when interpreting. It should be clarified that in case of BaseDataType and Structure the AllowSubtypes shall be not present in the nodeset.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Jim Luth

2022-11-22 17:22

administrator   ~0018180

One rule is for writing the flag, the other rule is for reading and interpreting the flag. There is no ambiguity or conflict as written. No change required.

Wolfgang Mahnke

2022-11-22 19:16

developer   ~0018186

That would mean that all NodeSet-Files using BaseDataType or Structure DataTypes as fields published today are invalid because it is now required to have the "AllowSubtype" flag set which was not even defined before! Is this really what you want to do? Why would we have such a requirement? What purpose would this be?

Jim Luth

2022-11-29 16:43

administrator   ~0018206

Agreed that Part 6 needs to be updated to clarify the flag is never set for BaseDataType and structure.

Randy Armstrong

2022-12-28 07:00

administrator   ~0018358

Updated F.13 to require that AllowSubtypes not be set for BaseDataType and Structure.

Jim Luth

2023-01-24 17:56

administrator   ~0018576

Agreed to changes edited in web meeting.

Issue History

Date Modified Username Field Change
2022-11-18 15:28 Wolfgang Mahnke New Issue
2022-11-22 17:22 Jim Luth Note Added: 0018180
2022-11-22 17:22 Jim Luth Assigned To => Jim Luth
2022-11-22 17:22 Jim Luth Status new => closed
2022-11-22 17:22 Jim Luth Resolution open => no change required
2022-11-22 19:16 Wolfgang Mahnke Status closed => feedback
2022-11-22 19:16 Wolfgang Mahnke Resolution no change required => reopened
2022-11-22 19:16 Wolfgang Mahnke Note Added: 0018186
2022-11-29 16:42 Jim Luth Assigned To Jim Luth => Randy Armstrong
2022-11-29 16:43 Jim Luth Status feedback => assigned
2022-11-29 16:43 Jim Luth Note Added: 0018206
2022-11-29 16:46 Jim Luth Description Updated
2022-12-28 07:00 Randy Armstrong Status assigned => resolved
2022-12-28 07:00 Randy Armstrong Fixed in Version => 1.05.03 RC1
2022-12-28 07:00 Randy Armstrong Note Added: 0018358
2023-01-24 17:56 Jim Luth Status resolved => closed
2023-01-24 17:56 Jim Luth Note Added: 0018576