> About Operation, it is more that this is tuple based and the user thinks entity.

My reasoning is that the tuple-like represention is closer the persistent data in the store, e.g. with respect to data types, column names etc. When e.g. getting a log file with changes that have been applied and need to be revised, this form may be more suitable than the more abstract entity-based representation; E.g. if I need to manually create a statement for compensating a certain change.