Yes and no. One of the problems of relying in reflection is that we'll need to be very careful with attribute renaming in the schema, and I'm not sure if  creating a constant (maybe in a class grouping all fields) for each of the fields in the schema is the best solution. We can think of something.

However, I think that the name of the action "EditScene" (and any other action) should have nothing to do with the field it manipulates. Here, you are using a constant that is the name of an action, to listen to a concrete field. Sounds confusing. And, e.g, I couldn't use OpenGame.NAME for the same purpose.

Again, maybe we need constants for some common fields, but I don't like mixing them with the names of actions.