Notes from 7/19 specification call:
- Collect auto-send will do its best to send submissions in order but server processing could happen out of order or someone could use manual submission (not recommended)
- These spec additions only matters for scenarios in which users are making several stacked offline updates to the same properties AND need the server Entity to be correct (sometimes they just need the info while offline to drive their workflow)
- Servers could choose to ignore
branchIdandtrunkVersioninitially or possibly forever - Central is planning to implement a queuing system to process Entity updates within a branch in order but will only minimally surface the concept in the UI