Well, the system is roughly analogous to an RDBMS: A class takes the place of a table, class attributes are columns of that table, an object is a certain row in that table, and for every class attribute, there's an object attribute. So their naming convention does kind of make sense, but is awkward when scripting.
Even using the database analogy, I wouldn't want a tableTableGateway, and a rowTableGateway, obviously those classes can be very misleading. I was thining maybe structure, or template, for the class, but I can't figure out a sensible renaming of object that would fit with those.
Thanks for the suggestions though, I'll have to look into Java a bit and see what kind of naming conventions they have.