We have not yet finalized the naming of a few concepts. Below I provide a few possible alternative names for different concepts. Feel free to add more.
[ ] Field: I used the term field in the proposal because when I originally thought about it, the generated functions would only depend on position most of of the time. Now with anonymous attributes, the functions often depend on other things as well and the term "field" does not make too much sense in some cases.
* Falloff: This term mostly makes sense when controlling a float input in the range 0-1. A field can do that, but I see falloffs as a special case of fields and as such I find the name worse than fields.
* Field: People know that term already, but that might not be enough reason to stick to it. Generally, the concepts of scalar and vector fields are fairly ubiquitous in some areas but mostly refer to functions that only depend on position and sometimes on time. As such they are also only more of a special case.
* Function: That's a concept that at least technical artists will probably know from programming. It describes "fields" more correctly and is a name that could easily be used in other areas of Blender as well where "field" may make less sense. It should be noted that "fields" are not any kind of function in the proposal. They are functions with "semantic inputs" (which the caller of the function can understand) and a single output. The terms "vector function", "integer function" etc. could be used to describe the different types of functions. Not sure if the "semantic input" idea can be integrated into the name somehow.
* Callback: Very similar to "function".
* Operation: Also similarly to "function" but I don't like it as much, because to me "operation" sounds like it may have side effects.
* Procedure: Same as "operation".