How should the ingestion process handle out of order arrivals?

[smessie]

Currently, the specification provides no guidance on the creation of an LDES, leaving publishers uncertain about how to handle various scenarios.

With this issue, I want to propose adding a section to the specification on LDES creation. Specifically, this section should address how the ingestion process SHOULD handle out-of-order arrivals.

However, this issue depends on the outcome of #62, which determines whether members MUST be added to the LDES in order.

[sandervd]

What is an out-of-order arrival in an append-only log?

[smessie]

This issue depends on the outcome of #62 and would only make sense if the outcome is that a timestampPath value is required on every member and that they should arrive in ascending order. Given that, an out-of-order arrival means that the timestampPath value of a to-be-added member is before the timestampPath value of the latest member that has been added to the LDES.

[pietercolpaert]

The merged #92 closes this issue during the workshop 4 closes this issue. The spec should not be clear about this. If still unclarities are discovered, please open up a new issue!