CWM11 — We only need one COBOL Data Division model

CWM vol. 2 3.1 says
"The concepts and ideas implicit in the definition of the COBOL language's
DATA DIVISION were one of the earliest (if not the first) formalizations of
the ubiquitous record model. A COBOL program contains much more than just
record descriptions. However, because neither CWM nor UML attempt to
describe programming languages directly, only the DATA DIVISION is described
here. The model presented here is compliant to the COBOL 85 language
standard [COBOL].

The primary purpose of the COBOL DATA DIVISION metamodel extension package
in CWM is to allow the structure of DATA DIVISIONs to be captured so that
their usage of other model elements (such as RecordDefs and Fields) can be
modeled. This allows definition of files and databases created by COBOL
programs as well as direct support for tools that attempt to track the
lineage and determine the impact of proposed changes to COBOL application
programs. The metamodel does not, however, provide sufficient structure to
support tools that want to capture the structure of a DATA DIVISION source
into a CWM repository and then be able to faithfully reproduce the source on
demand.

The COBOL DATA DIVISION metamodel extension also serves as an example of
the use of the CWM Record metamodel. The CWM Record package is intended as a
foundation upon which many record-oriented programming languages can be
described. The COBOL Data Division extension package is provided as example
demonstrating appropriate usage of CWM and UML classes in modeling the data
structure representation parts of this and similar programming language
environments."

UML Profile for EAI 14.1 says
"The goal of this COBOL model is to capture the information that would be
found in the Data Division." .

Both define partial COBOL language meta models with different levels of
detail. We only need one COBOL Data Division model.

see above