Must support Tag 279=1 (Change) for incremental refresh

Currently, in my marketdata response stream, I can only differentiate between new orders and orders that were deleted from the orderbook. This is due to the fact that the current FIX specification only supports 279=0 (New) and 279=2 (Delete).

Thsi is insanity, as these are not the only events that take place during trading! Orders are also updated, and for the data to make sense, you must also be able to determine what orders were changed as well.

If you can only see new and deleted orders, how is the user supposed to accomodate for a price level whose volume was updated?

Cumone spoteware. Up your game and allow your users to have full transparancy of the market data. Currently, without this ability to see market updates, a vital piece of info is missing, rendering the market data stream practically useless!!

I vote that in the next iteration, the following Incremental Update response should support:

279=0 (New)

279=1 (Update)

279=2 (Delete)