Currently naive timestamp-based scheme is implemented.
It is not enough. At least because two of events happened one after another quickly could get the same timestamp and their ordering becomes fuzzy.
It is not a big deal if events are absolutely independent (two different subjects created) - order is indistinguishable indeed in such case.
However it is a problem if these events are assumed to be in proper order to make history timelime re-constitution to work correctly (for example creation of property is tracked as property creation event on object properties timeline followed by update of parent object on objects timeline and to handle adding of link to child property to object it is critical to have property creation tracked in timeline).
Currently naive timestamp-based scheme is implemented. It is not enough. At least because two of events happened one after another quickly could get the same timestamp and their ordering becomes fuzzy. It is not a big deal if events are absolutely independent (two different subjects created) - order is indistinguishable indeed in such case. However it is a problem if these events are assumed to be in proper order to make history timelime re-constitution to work correctly (for example creation of property is tracked as property creation event on object properties timeline followed by update of parent object on objects timeline and to handle adding of link to child property to object it is critical to have property creation tracked in timeline).