I would like to know if the 'type' field of a property value should use a value from the Basic DataTypes enum in section 6.4.16 of the spec. So would this be a correctly formatted Property Value:
{ "type": 12, "value": "This is a String" }
I ask as test SendComplexDataTest.checkPropertiesValidType() in the TCK instead expects the 'type' to correspond with the numbers outlined below (Under message Property Value in section 6.4.1.)
Meaning that the below Property Value would be correct:
{ "type": 8, "value": "This is a String" }
This seems to contradict the spec requirement:
[tck-id-payloads-propertyset-quality-value-type] The type of the Property Value MUST be a value of 3 which represents a Signed 32-bit Integer.
This question also applies to 'datatype' in Metric, 'types' in DataSet and 'type' in Template.
What do you want to know?
I would like to know if the 'type' field of a property value should use a value from the Basic DataTypes enum in section 6.4.16 of the spec. So would this be a correctly formatted Property Value:
{ "type": 12, "value": "This is a String" }
I ask as test SendComplexDataTest.checkPropertiesValidType() in the TCK instead expects the 'type' to correspond with the numbers outlined below (Under message Property Value in section 6.4.1.)
Meaning that the below Property Value would be correct:
{ "type": 8, "value": "This is a String" }
This seems to contradict the spec requirement: [tck-id-payloads-propertyset-quality-value-type] The type of the Property Value MUST be a value of 3 which represents a Signed 32-bit Integer.
This question also applies to 'datatype' in Metric, 'types' in DataSet and 'type' in Template.
Thanks!
Is this related to a Sparkplug Listing request? If so, link the issue from https://github.com/eclipse-sparkplug/sparkplug.listings here.
No response
Version
3.0.0 (Default)
Accept EFTL Terms