In clause 17.2.1, "buffered-report-control-block (BRCB) – internal events (caused by trigger options
data-change, quality-change, and data-update) issue immediate sending of reports or buffer the events (to some practical limit) for transmission, such that values of data object are not lost due to transport flow control constraints or loss of connection."
In clause 17.2.2.5, "The BRCB shall monitor the values of the DataAttributes referenced by the DataSet. Internal events as result of the trigger conditions data-change (dchg), quality-change (qchg), and data-update (dupd) shall be buffered (up to a practical limit)."
These clauses do not say anything about "Integrity will be buffered"
But in clause 17.2.3.2.3.6, "The BRCB shall buffer entries based on the trigger options data-change, quality-change,
data-update and integrity during all states: disabled, resync, and enabled."
Proposal
Change the statement in 17.2.1 with "buffered-report-control-block (BRCB) – internal events (caused by trigger options
data-change, quality-change, data-update and integrity) issue immediate sending of reports or buffer the events (to some practical limit) for transmission, such that values of data object are not lost due to transport flow control constraints or loss of connection." and in 17.2.2.5 with "The BRCB shall monitor the values of the DataAttributes referenced by the DataSet. Internal events as result of the trigger conditions data-change (dchg), quality-change (qchg), data-update (dupd) and integrity shall be buffered (up to a practical limit)."
Discussion
Created
Status
6 month over
30 Nov 22
In Force (green)
batching of tissue has been circulated 57/2445/INF
Move to mustImplement:
as specified in the attachmenet.
01 Feb 22
Must Implement
ballot period expired - moved to accepted.
11 May 21
Solution Accepted
7-2 Editors:
Agree with the conclusion of the Testing actors. Move to Ballot period.
13 Apr 21
Ballot Period
UCA TPWG has determined that sBr22 already tests this item
02 Mar 21
Conformance Test Verification
No compatibility issues as this is an editorial clarification.
No change to test procedures are expected.
16 Feb 21
Conformance Test Preparation
No comments, proposal accepted
16 Feb 21
Analysis Of Compatibility
Draft implementation attached, no issues found.
25 Nov 20
Verify Draft Implementation
Draft implementation attached.
16 Nov 20
Drafting Implementation
and we can move to draft the interpretation
13 Nov 20
Drafting Implementation
While the test procedure have interpreted the standard in the way that integrity reports have to be buffered.
To avoid interoperability risks, the standard shall be enhanced to integrate the interpretation of the test sBr22.
13 Nov 20
Discussion (red)
I do not think we agree that this is editorial
11 Nov 20
Approval (Editoral)
move to Editorial - Will be modified in the next revision.
No technical change.
11 Nov 20
Approval (Editoral)
I would challenge that this is editorial. Currently we have two conflicting statements; according to the first two statements, apparently integrity reports as GI are not buffered; only the second statements adds that integrity are buffered as well.
So we have inconsistent statements that can lead to two different implementations that may not be interoperable?
03 Nov 20
Discussion (red)
move to Editorial - Will be modified in the next revision.
28 Oct 20
Approval (Editoral)
I agree with the editorial change indicated in the proposal.