The standard allows user to specify five diffenet languages that define in what language certain properties are presented. The standard does not put any constraints on these choices. Clearly there are implicit constraints. They should be made explicit.
Resolution:
A section will be added to the report that provides constraints and an appropriate example for each language type that is in the MDMI specification. This section will be added to the description of the MessageGroup class as this is where default languages are specified for all messages in the group.

The first time a property is specified whose value is an expression language reference; a description of any constraints that language must meet will be inserted. Five language references are first mentioned as properties of MessageGroup. The OrderingLanguage property is first mentioned in the description of the SemanticElement class.

The FTF report does not contain a description of each class's associations. These should be added.

Resolution:
For every class in the MDMI metamodel, as described in the Beta 2 document, definitions of the associations for each class have been added as a subsection after the subsection describing the class's properties.

There are a number of references in the specification that need to be changed. For example, the specification still refers to the standard as CM4PM instead of MDMI. In addition, there will be some general editing that will be required, once the specific text associated with the suggested changes in the metamodel is made.Resolution:
A general editing pass will be made on the text of the specification once all the text changes associated with accepted resolved issues is made.

A general editing pass will be made on the text of the specification once all the text changes associated with accepted resolved issues is made.