Test Case:
Randomly inject one of the following code. Repeat this test several times each tmie varying the result

1. ServiceResult = Good, but the publishTime parameter uses a time in the future, i.e. Now + 1 day.
   2.ServiceResult = Good, but the publishTime parameter uses a time in the
   future, i.e. Now + 1 year.

Expected Result:
Client logs and/or displays a warning message stating that it is receiving events from the future.
Client by default should discard the data, unless the end-user selects an option to consume the data.

To log the unexpected timestamp makes sense.

But to discard the data makes no sense. We had the same discussion with the time stamps in the request/response headers. This test case expects that clocks are always synchronized. If not, the client would discard all data received from a server where the clock is in the future (or the client clock is not in sync).

If the client want to decide what to do with the values, it should check if the timestamps of the values make sense compared to the other received before. But the publishTime is not relevant for this decision.