OOo uses a periodic save recovery mechanism.  This has two deficiencies:

1) For significant sized documents the periodic save interrupts the user's work.
2) If it is ever invoked any work performed by the user since the last save is
lost and must be reentered by the user.

Both of these concerns impact on the productivity of users.

Although periodic save is characteristic of competing products, I believe that
OOo should exceed the marketplace.

As a counter-example all current popular file systems, with the exception of
FAT, use journaling to minimize lost data during a system failure.

I am surprised that this requirement does not appear to have been considered,
even if there are valid reasons that I am unaware of to defer implementation.