Concepts
Metamodel definition commands concern:
• MetaClasses (or object types)
• links possible between these MetaClasses (called MetaAssociations)
• the two MetaAssociationEnds of each of these MetaAssociations
• MetaAttributes (characteristics).
Object comments or texts are assimilated in MetaAttributes.
 
Concept
Syntax
MetaClass (or object type)
metaclass
MetaAssociation (or link)
MetaAssociation
MetaAssociationEnd
MetaAssociationEnd
MetaAssociationType (or link type)
MetaAssociationType
MetaAttribute (or characteristic)
MetaAttribute
MetaAttributeGroup (or group of MetaAttributes)
MetaAttributeGroup
MetaAttributeValue (or value of MetaAttribute)
MetaAttributeValue
Concept names
The name of a concept is unique, ie. the name for a MetaClass, a MetaAssociation, a MetaAttribute or a text must be used only once, including all languages.
Names of MetaClasses with standard naming rule contain 255 characters maximum.
*For information on namespaces, see Managing Namespaces.
Name of a concept must begin with a letter (A to Z). The following characters are authorized for use in concept names:
 
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
a b c d e f g h i j k l m n o p q r s t u v w x y z
à á â ã ä å ç é è ë ê ì í î ï ñ ò ó ô ö ù ú û ü ÿ ý
0 1 2 3 4 5 6 7 8 9
* ( ) / = + % ? $ _ & €
, ; - :
*Hiragana, Katakana and Kanji characters are accepted for object names in the Japanese language.
You cannot use “& , ; - : ” as the first character. There can be spaces in the name, except as first and last character.
*Unlike the other characters, the ampersand (&) is not controlled as the first character:
• it can be used in an object name.
• it should not be used in the name of a MetaClass, MetaAssociation, MetaAssociationEnd or MetaAttribute.
Technical concepts other than repository core concepts, (MetaClass, MetaAssociation and MetaAttribute) have names beginning with an underscore (_).
*It is impossible to define extensions with names beginning with characters "_" or "$".
*It is not recommended to restrict the list of characters as this may generate issues when executing queries or descriptors (see Restricting the names of object types).
As you cannot use a name already in use, you must attach a prefix to your extension names. This avoids conflicts that might occur later when the standard metamodel is upgraded.
For example, if you create a metamodel extension called "Table" for Hopex Business Process Analysis and later install Hopex Database, a conflict will occur.
Metamodel diagram
 
All of these MetaClasses have the following attributes:
• Name
• Absolute Identifier
• Authorization
• Creation Date
• Modification Date
• Creator, Modifier
• Creator Name
• Modifier Name
• Authorization Level
• Creation Version
• Modification Version
• Comment and History