Problem description

API Design Guideline states subscription-ends notification shouldn't be counted in the subscriptionMaxEvents. However, such a statement is not available for notifications resulting from initialEvent=true.

In addition, there may be cases where a single notification may not be sufficient to initialize/synchronize the data on the client side and clients need to know when the initialization end and when the events start occurring.

Possible evolution

One possible solution might be to introduce a feature initialEventSync with enums like 'synchronizing', synchronizationComplete. This feature can be added similar to terminationReason attribute.

Alternative solution

Additional context