IMO, we should take some widely used metamodel and apply the naming consistently.
Java reflection: Class, Field, Method EJB: Entity, Field, Method UML: Class (clazz), Feature, Attribute, Operation, Association (for relationships) MOF/XMI: same JavaBeans: BeanDescription, FeatureDescriptor, PropertyDescriptor I'll say, if it is not JavaBeans, it should be UML. Thus, my preferrence would be: Clazz, Attribute, Operation - Dmitri ----- Original Message ----- From: "Stephen Colebourne" <[EMAIL PROTECTED]> To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]> Sent: Monday, October 28, 2002 7:52 PM Subject: [clazz] Naming > Naming is always a tricky issue, especially when we get to a fundamental > level such as this. > > Meta class names > ------------------ > Java: > Class, Field, Method > > Names proposed for [clazz]: > MetaBean, MetaProperty, MetaOperation* > MetaClazz, MetaProperty, MetaOperation > Clazz, Attribute, Operation > AClass, AField, AMethod > Class, Field, Method > > Instance class names > --------------------- > Java: > Object, ., . > bean, property, method. > > Names proposed for [clazz]: > Bean, Property, Operation* > > MetaData name > ---------------- > Attribute* > MetaData > > > All of the[clazz] basic classes should be interfaces. > The meta class names should relate to the instance class names. > > I still favour the names marked with a * as being a consistent set > independent of reflection/Java, but still well known names. > > Stephen > > > -- > To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org> > > > -- To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
