View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000817910000-006: MappingsSpecpublic2022-08-02 03:412023-10-10 15:28
ReporterRandy Armstrong Assigned ToRandy Armstrong  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.05.01 
Target Version1.05.03 RC1Fixed in Version1.05.03 
Summary0008179: StructureDefinition.DefaultEncodingId is not useful as described.
Description

In retrospect the field should have been an key-value array. Since that is not an option we need a compromise.

The proposal is this:

Part 6 is updated to explicitly data that JSON or XML encoded ExtensionObjects may use the DataType or the DataEncoding Id.
The DataType can only be used if the ExtensionObjects is being encoded as part of a larger JSON or XML document.
If JSON is being encoded into a binary stream then the DataEncodingId shall be used.

Part 3 is updated to say DefaultEncodingId shall always contain the BinaryEncodingId with a note that the DataType id is used for JSON and XML encoding.

TagsNo tags attached.
Commit Version1.05.03
Fix Due Date

Relationships

related to 0009073 closedJeff Harding 10000-003: Address Space Detail clarification needed for DefaultEncodingId in StructureDefinition 
related to 0009193 closedMatthias Damm 10000-014: PubSub StructureDefinition.DefaultEncodingId is not useful as described. 

Activities

Randy Armstrong

2022-12-29 07:00

administrator   ~0018367

Updated 5.4.2.16 to require the use of the DataType NodeId when ExtensionObjects are encoded within a JSON document.

Jim Luth

2023-01-17 16:45

administrator   ~0018523

Agreed to changes in web meeting,

Matthias Damm

2023-09-15 09:05

developer   ~0019993

From my colleague Frank:
It is not clear what the condition "If the ExtensionObject is being serialized as part of a JSON document [...]" means.

The binary encoding still uses the EncodingId for JSON bodys, it would be possible to also use the TypeId by adding a
value for JSON bodys to the Encoding byte.

Matthias:
Changing the TypeId to DataType also in binary ExtensionObject would solve also the discussion we had for related issue 0009073 and would eliminate the need for the JSON DataTypeEncoding nodes.

Randy Armstrong

2023-09-20 11:38

administrator   ~0020026

Changed text to:
When serializing a PubSub Message (see XXX), the NodeId of the DataType Node is used instead.

Jim Luth

2023-09-20 11:39

administrator   ~0020027

Agreed to changes in F2F.

Jim Luth

2023-10-10 15:28

administrator   ~0020111

We reverted Part 6 to allow either the DataType Encoding Node or a DataType Node. Part 14 needs to clarify "When serializing a PubSub Message (see XXX), only the NodeId of the DataType Node is used , never the DataType Encoding node.

Issue History

Date Modified Username Field Change
2022-08-02 03:41 Randy Armstrong New Issue
2022-08-02 15:58 Jim Luth Assigned To => Randy Armstrong
2022-08-02 15:58 Jim Luth Status new => assigned
2022-12-29 07:00 Randy Armstrong Status assigned => resolved
2022-12-29 07:00 Randy Armstrong Resolution open => fixed
2022-12-29 07:00 Randy Armstrong Note Added: 0018367
2022-12-29 07:01 Randy Armstrong Fixed in Version => 1.05.03 RC1
2023-01-17 16:45 Jim Luth Status resolved => closed
2023-01-17 16:45 Jim Luth Note Added: 0018523
2023-08-08 16:08 Jim Luth Relationship added related to 0009073
2023-09-15 09:05 Matthias Damm Status closed => feedback
2023-09-15 09:05 Matthias Damm Resolution fixed => reopened
2023-09-15 09:05 Matthias Damm Note Added: 0019993
2023-09-20 11:38 Randy Armstrong Status feedback => resolved
2023-09-20 11:38 Randy Armstrong Resolution reopened => fixed
2023-09-20 11:38 Randy Armstrong Fixed in Version 1.05.03 RC1 => 1.05.03
2023-09-20 11:38 Randy Armstrong Note Added: 0020026
2023-09-20 11:39 Jim Luth Status resolved => closed
2023-09-20 11:39 Jim Luth Commit Version => 1.05.03
2023-09-20 11:39 Jim Luth Note Added: 0020027
2023-10-10 15:28 Jim Luth Note Added: 0020111
2023-10-10 15:28 Jim Luth Issue cloned: 0009193
2023-10-10 15:28 Jim Luth Relationship added related to 0009193