Describe the problem
I recently came across an OSI trace file of a SensorDataSeries message. It was marked as sd in the file name, so I assumed it was a SensorData trace file which lead to a failure during deserialization.
Describe your research
Next to SensorData, there is also SensorDataSeries and SensorDataSeriesList. Both are not listed in the top-level interfaces in the standard documentation and they are also not listed as types in the OSI trace file naming convention.
Ask your question
Should SensorDataSeries and SensorDataSeriesList be added to the top-level messages and also as separate types to the trace file naming convention?
And as an additional question: What is the intention of the SensorDataSeries? Why not just use SensorData directly?
Describe the problem
I recently came across an OSI trace file of a SensorDataSeries message. It was marked as sd in the file name, so I assumed it was a SensorData trace file which lead to a failure during deserialization.
Describe your research
Next to SensorData, there is also SensorDataSeries and SensorDataSeriesList. Both are not listed in the top-level interfaces in the standard documentation and they are also not listed as types in the OSI trace file naming convention.
Ask your question
Should SensorDataSeries and SensorDataSeriesList be added to the top-level messages and also as separate types to the trace file naming convention?
And as an additional question: What is the intention of the SensorDataSeries? Why not just use SensorData directly?