DDSXTY_ — Conflicting data types applied to several Attributes, Operations and Parameters in UML notation

The following figures exhibit inconsistent application of data types to attributes, operations and parameters:
Figure 4
Figure 9
Figure 10
Figure 13
Figure 14
Figure 16
Figure 26
Figure 30
Figure 33
Figure 36
Figure 37
Figure 38
Figure 39

Certain attributes/parameters have 'int' or 'string' applied which conflict the data types defined within the aforementioned model, and the PrimitiveTypes defined in UML. What is the intent with these? Which set of primitive data types are intended for application here (IDL? Java, C++, UML, XTypes?)

For example, the 'Enumeration' class in Figure 10 defines a 'bit-bound' property of type int.

Use DDS-XTypes types consistently. Note that Figures 9 and 16 are already correct—they use the DDS-XTypes-derived basic types, not the UML-built-in ones.
Note that if the resolution to issue #16561 is accepted, the modification to figure 38 will be irrelevant, because the corresponding section of the document will be removed.