In SBOns, a Select is made using a minimum amount of Service Parameters. The full set is provided with the Operate.
For cancelling a Select, a Cancel has to be issued with the full set of Service Parameters (7-2, clause 126.96.36.199).
On the client side, these Service Parameters have not not yet been specified at this time.
Question a: What is to be used in the Cancel?
Question b: On the server side, does the Server has to accept a Cancel with a full set of Service Parameters, which it cannot map - since it did not receive such data with the Select?
Moved to editorial - shall be integrated with the next revision of part 7-2
13 Jul 20
As opposed to "select" and "selectWithValue", "cancel" has only one primitive, and so for the case of normal security a cancel request has to carry service parameters that have no meaning.
10 Jul 20
a. any set of pertinent service parameters shall be used for the cancel. Actually, the ones that would have been used for the select request, if the control model had been SBO with enhanced security.
b. there is only one signature for cancel, therefore all the service parameters have to be used in the request.
The text in Table 108 could be adapted to give a better guidance in case of SBOns:
State: Ready, Service Request Cancel_req
For SBO control with enhanced security control model: discrepancy between SelVal_req and Cancel_req parameters are checked.
For SBO control with normal security, the discrepancy between the Sel_req and Cancel_req parameters cannot be checked.