Part 7-3 Table 16 defines substitution as potentially modifying any quality elements with the exception of q.source. Yet, Part 7-4 Annex A Table A.1 expects q.test=true when LN.Beh=test or test/blocked, and q.validity=invalid when LN.Beh=off.
One of these statements needs to take precedence over the other. If substitution takes precedence, then users need to understand that data objects with substituted quality could have a different q.test or q.validity value than expected based on LN.Beh. Users may need to disable substitutions during testing.
For reference, Part 7-3 Table 16 provides the following definitions of subQ and subEna:
subQ: "Any element other than the 'q.source' can be substituted."
subEna: "If 'subEna' = true, the data value and quality shall always be set to the same value as the attributes used to store the substitution data value and quality, ..."
Without clarification the contradiction between these parts seems likely to result in disparate vendor implementations and interoperability issues.
Proposal
Add clarification to Part 7-4 Annex A and/or Part 7-3.
Add conformance test case.
Discussion
Created
Status
changed state to discussion.
16 Sep 25
Discussion (red)
subQ has the ability to override the defined q bits, including test.
But Beh has an impact as well on q.
I think q is resulting of a combination of both input:
q = f ( subQ while subEna=true, Beh).
For instance, if
subQ.test = false, then q.test is false unless Beh = test, test/blocked.
subQ.validy = good, then q.validity is good unless Beh = off.
15 Sep 25
Accepted
Open for discussion.
15 Sep 25
Accepted
subQ has the ability to override the defined q bits, including test.
I believe this means that when used in a test environment/mode the user must take care.
I think this is clear, but support a clarifying note.