Question: Redundant normative statements

[datafoo]

What do you want to know?

How is it relevant to have both of this sets of normative statements?

• Set A1
  • [tck-id-topics-nbirth-mqtt] NBIRTH messages MUST be published with MQTT QoS equal to 0 and retain equal to false.
• Set A2
  • [tck-id-message-flow-edge-node-birth-publish-nbirth-qos] The Edge Node’s NBIRTH MQTT QoS MUST be 0.
  • [tck-id-message-flow-edge-node-birth-publish-nbirth-retained] The Edge Node’s NBIRTH retained flag MUST be set to false.

To me, they both seem equivalent and this duplication makes the specification longer to read than necessary.

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

• [X] I agree to the terms of EFTL

[datafoo]

Same with these other 2 sets:

• Set B1
  • [tck-id-topic-structure-namespace-a] For the Sparkplug B version of the payload definition, the UTF-8 string constant for the namespace element MUST be: spBv1.0
  • [tck-id-topics-nbirth-topic] The Birth Certificate topic for a Sparkplug Edge Node MUST be of the form namespace/group_id/NBIRTH/edge_node_id where the namespace is replaced with the specific namespace for this version of Sparkplug and the group_id and edge_node_id are replaced with the Group and Edge Node ID for this specific Edge Node.
• Set B2
  • [tck-id-message-flow-edge-node-birth-publish-nbirth-topic] The Edge Node’s NBIRTH MQTT topic MUST be of the form spBv1.0/group_id/NBIRTH/edge_node_id where group_id is the Sparkplug Group ID and the edge_node_id is the Sparkplug Edge Node ID for this Edge Node

[datafoo]

Another example:

• Set C1
  • [tck-id-host-topic-phid-death-payload] The STATE Death Certificate Payload MUST be JSON UTF-8 data. It MUST include two key/value pairs where one key MUST be online and it’s value is a boolean false. The other key MUST be timestamp and the value MUST be a numeric value representing the current UTC time in milliseconds since Epoch.
• Set C2
  • [tck-id-operational-behavior-host-application-connect-will-payload] The Death Certificate Payload MUST be JSON UTF-8 data. It MUST include two key/value pairs where one key MUST be online and it’s value is a boolean false. The other key MUST be timestamp and the value MUST be the same value that was used for the timestamp in its own prior MQTT CONNECT packet Will Message payload.

Except in that case, there seems to be a copy-paste mistake (see #510).

[datafoo]

I would like to add that for me, reading such a specification requires extreme focus. Having to read redundant statements thinking there is a slight difference from previously read statements leads to unnecessary high mental efforts.

I believe the specification would be clearer and much easier to read without these redundant statements.