For the task of storing object definitions and managing
classes in the coming GEASv2 there are two approaches which 
should be discussed.

Although they differ mainly by their names at the moment, it is
important to clarify it now, because the names implies an quite
different approach. 

The first approach is to have a place where object definitions, can 
be stored and which is used by the main part of the application 
server (=object server (neilt's drawing) or = GOAT (white paper)) to
build business objects (either virtual or as real python objects).
The place where the objects are stored is called GEOR (=GNUe 
Object Repository) and it would consist of objects of type GObjectDef.
(have a look in appserver/src/objrepos/geasClassDefs.py)

The second approach is to put the storage of object definitions and
the whole class management (like changing classes or building new instances) 
into one kind of object. This kind of object would be called a
geasMetaObject and would be "meta" in relation to geasInstance's.
( there is a description of Meta Objects in odmg.txt)
( geasMetaObject could also named geasClassObject (in opposition to
a geasInstance))


My opinion is to move the class handling code into a "geasMetaObject"
instead of splitting it into class<->instance handling code and 
class definition storage code. By moving it into one class it would
be easy to add new features just by inheritance. f.e. by a
"geasSupportInheritanceMetaObject" which is just a child of "geasMetaObject"
parts.


BTW. It would be good to change the Name "Object Repository", which I
think is a bit misleading.  I would suggest to name this part "Class
Repository" or "Object Definition Repository". 
something


Thanks,

Jan Ischebeck (siesel)
J.I. e-Services
address@hidden