Difference between revisions of "Metaclass"
(→Basics) |
|||
| Line 2: | Line 2: | ||
== Basics == | == Basics == | ||
| − | In UBIK, a MetaClass is used to define the appearance and behavior of a certain set of future [[Contentclass|content objects]]. | + | In {{UBIK}}, a MetaClass is used to define the appearance and behavior of a certain set of future [[Contentclass|content objects]] or [[Instance|Instances]]. |
| − | A MetaClass can, and actually has to, inherit from another MetaClass. | + | A MetaClass can, and actually has to, inherit from another MetaClass, so it is usually also a [[Derivate|derivate]]. The inherit source can be a built in [[:Category:UBIK System Object|UBIK System-MetaClass]], which is typically the case when customizing starts in an "empty" data model. Of course, and more likely, it will be another MetaClass that was already created during customizing. |
==See also== | ==See also== | ||
Revision as of 09:32, 29 January 2013
Basics
In UBIK®, a MetaClass is used to define the appearance and behavior of a certain set of future content objects or Instances.
A MetaClass can, and actually has to, inherit from another MetaClass, so it is usually also a Derivate. The inherit source can be a built in UBIK System-MetaClass, which is typically the case when customizing starts in an "empty" data model. Of course, and more likely, it will be another MetaClass that was already created during customizing.
