DDS11 — Clarification of order preservation on reliable data reception

Does reliability include order preservation up to API level?
In other words should data be made available to applications if older data exists but has not yet arrived (e.g. due to network irregularities), note that if a late arriving sample is accepted even after newer samples are made available then state inconsistencies may occur. In addition, not accepting a late coming sample should generate a sample lost notification.
Resolution:
Specify that data from a single writer (reliable and/or best-effort) will NOT be made available out-of-order.
Revised Text:
TBD

No Data Available