TS-0004: Non-Normative "should" when handling "expirationTime" in <request> resource creation
In TS-0004, Table 7.3.2.21: Common attributes settings for <request> resource, the last sentence for expirationTime says:
The expirationTime of the <request> resource should last longer than the specified Result Persistence if provided in the request.
The "should" is non-normative, and also contradicting the text before in the same table cell IF it DOESN'T last longer:
The value of the expirationTime shall be chosen dependent on the Request Expiration Timestamp, Result Expiration Timestamp, Operation Execution Time and Result Persistence parameters associated with the original request. If the value consistent with the Request Expiration Timestamp, Result Expiration Timestamp, Operation Execution Time and Result Persistence parameters is too long, the Hosting CSE shall reject the request.
Also, the second sentence is a bit hard to understand (is there a "is" missing?).
TS-0001
A similar text exits in TS-0001, 8.1.2 Request:
Result Expiration Timestamp: optional result message expiration timestamp. The Receiver CSE should return the result of the request before the time expires.