View Issue Details

IDProjectCategoryView StatusLast Update
000930410000-006: MappingsSpecpublic2024-03-21 22:43
ReporterThilo Bellinger Assigned ToRandy Armstrong  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.05.02 
Fixed in Version1.05.04 RC1 
Summary0009304: Unclear type for arrays in XML encoding
Description

In Part 6 Chapter 5.3.4 Arrays it is written "The name of the element in the array shall be the type name."
For cases where a data type is mapped to another built-in type it is not clear which type name to use.

Examples are

  • the simple Duration which is derived from Double
  • simple OptionSet types like AccessRestrictionType which is derived from UInt16

Inside of a Variant it is clear, since a Variant supports only the built in types.
But it is unclear if a structure contains an array of e.g. Duration or AccessRestrictionType.

It is unclear if the encoded type is
a ListOfDuration with single elements with the name Duration or
a ListOfDouble with single elements with the name Double.

I would assume to use the built-in type, but for structures or enumerations within a parent structure it is pretty clear to use the direct type name and not the built-in type ExtensionObject or Int32.

Please clarify and update the specification text.

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

Activities

Randy Armstrong

2024-02-03 12:31

administrator   ~0020759

This statement is not true:
"for structures or enumerations within a parent structure it is pretty clear to use the direct type name and not the built-in type ExtensionObject or Int32."

The element name in Structure is the field name not the type as explained in 5.3.5 Structures

"5.3.1.19 Subtypes of Built-in Types" also explicitly specifies that all subtypes of builtin types are encoded as the base built in type.

Cleaned up the text in 5.3.5 Structures.

Jim Luth

2024-03-21 22:43

administrator   ~0021001

Agreed to changes in Dallas F2F.

Issue History

Date Modified Username Field Change
2023-12-06 14:45 Thilo Bellinger New Issue
2023-12-06 20:29 Jim Luth Assigned To => Randy Armstrong
2023-12-06 20:29 Jim Luth Status new => assigned
2023-12-06 20:30 Jim Luth Commit Version => 1.05.04 RC
2023-12-06 20:30 Jim Luth Fix Due Date => 2024-01-15
2024-02-03 12:31 Randy Armstrong Status assigned => resolved
2024-02-03 12:31 Randy Armstrong Resolution open => fixed
2024-02-03 12:31 Randy Armstrong Note Added: 0020759
2024-03-21 22:43 Jim Luth Status resolved => closed
2024-03-21 22:43 Jim Luth Fixed in Version => 1.05.04 RC1
2024-03-21 22:43 Jim Luth Note Added: 0021001