You do realize that DoD has nothing to do with data-driven, right?

Data oriented design is about structure the data in regard of how it is processed and the hardware. This is opposite of object oriented design which models the data around your mental model.

For example in DoD you could design a map with keys in one array together and one array of values. This would make it much faster to iterate over keys while searching because of cache memory.

While in object oriented you would store an array of pairs.

Both approaches can use data-driven.

Edit: would -> could