I'd like to see this concept combined with the open data movement.

Vast, powerful, but also intent on invisibility and slyness, careful to camouflage his actions behind routine data movements.

The open data movement has, to some degree, spread the assumption that government data is correct.

Reductions in duplicate data (especially as caused by data movement)

The ability to assess acquisition status to control data movement to enterprise systems (such as storage)

Would you feel comfortable doing the same tossing around if you doing a "sync" worth of data movement?

The data block is copied one byte at a time, and the data movement utilizes the zero-page indirect addressing modes.

The data block is copied one byte at a time, and the data movement and looping logic utilizes 16-bit operations.

It's the programmer's responsibility to ensure that data movement exceeds neither destination nor source boundary.

Software functional processes are further analysed into data movements.