View Issue Details

IDProjectCategoryView StatusLast Update
000474610000-003: Address SpaceSpecpublic2023-03-28 14:09
ReporterWolfgang Mahnke Assigned ToJim Luth  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionno change required 
Summary0004746: Clarification on subtyping of structure data types
Description

I have not found a clear definition on rules for subtyping Structure DataTypes.
The StructureDefinition (Table 34) defines for the "fields":
"For Structures derived from another Structure DataType this list shall begin with the fields of the baseDataType followed by the fields of this StructureDefinition."
Is it allowed to modify the fields of the baseDataType and use a subtype as data type (as I would expect)? What are the rules?
The specification is very vague on this topic. I guess that was intentionally because we thought about different types of dictionaries used etc. Since we are more concrete now how to describe structures, do we have to be more concrete here as well?

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0004421 closedJeff Harding Handling of StructureFields with abstract DataType 

Activities

Jim Luth

2019-05-14 17:14

administrator   ~0010239

This was discussed in the UA call today. We believe the spec statement "For Structures derived from another Structure DataType this list shall begin with the fields of the baseDataType followed by the fields of this StructureDefinition." is unambiguous and it is clear the the fields of the base type can not be altered in any way. If you want a new construct to be added to UA that allows a more a flexible inheritance model, please add it as a new feature request.

Issue History

Date Modified Username Field Change
2019-04-30 10:55 Wolfgang Mahnke New Issue
2019-04-30 10:56 Wolfgang Mahnke Relationship added related to 0004421
2019-05-14 17:14 Jim Luth Note Added: 0010239
2019-05-14 17:14 Jim Luth Assigned To => Jim Luth
2019-05-14 17:14 Jim Luth Status new => closed
2019-05-14 17:14 Jim Luth Resolution open => no change required