Should we gradually replace _make_tuples with simply make?

Here are my supporting arguments:

1. The term tuples comes from the relational model. We are coming to the understanding that DataJoint is much closer aligned with the Entity-Relationship model. In the ERM, the elements of sets are called "entities" rather than "tuples".
2. We follow different name conventions in different languages. For example, in MATLAB, we use camelCase and _make_tuples is called makeTuples. In the common documentation, we have to spell both versions.
3. The word tuple is overloaded since it has its own definition in Python. _make_tuples always inserts what amounts to Python dicts rather tuples.

Making the callback simply make would obviate these issues. Of course, we will keep things backward compatible to keep _make_tuples an acceptable name.

What do you think?