1) MessageType MUST be divided in subtypes separated by dash: <ST1>-<ST2>-<ST3>-...
2) The first subtype MUST be unique to the particular business application(s) involved and unique within NEM: "NBM" or "ESETT" or "NBS"
3) MessageType subtypes MUST be uppercase alphanumeric characters
4) MessageType MUST have at minimum two subtypes and COULD have more subtypes
5) MessageType MUST be static
6) MessageType subtype COULD identify the ProcessType or EntityType(Market,Nationality,Bidzone,etc)
7) MessageType subtype COULD identify the DocumentType/Format
8) MessageType subtype for DocumentType/Format SHOULD be placed after the subtype for ProcessType/EntityType if the latter exists
9) MessageType SHOULD NOT be more than 25 character, but can be as long as necessary (ECP/EDX-GUI will not show more than 25 char)
10) If Document is CIM, then MessageType COULD be on this form:
                <NEM-unique-prefix>-CIM-PT<CIMProcessType>-MT<CIMMessageType>-<Zero-of-more-optionals>

Examples

1) Simple example, adhering to 1-5 MUST requirements
                MYSYSTEM-ABC123
2) Slighty more explanatory type, adhering to 1-8 - showing which processtype/documenttype this is about
                MYSYSTEM-A39-Z35
3) An example showing to preferred way for a CIM-document
                MYSYSTEM-CIM-PTA39-MTZ35