UAF13 — The UML Profile for the UAF Does Not Specify UAF Architecture Views or View Content - No Mechanism Within the XML

It states:
'UAF provides a complete set of stakeholder viewpoints as the basis for defining the variety of necessary architecture views of an Enterprise and these views are specified in the UAFML.'

1) 'stakeholder viewpoints' should be 'architecture viewpoints' in accordance with ISO/IEC/IEEE 42010
2) a UML profile such as the UAFP does not specify architecture views nor view content. There is no standardised mechainsm within the UML to do so. The normative UML profile for the UAF - dtc/21-12-14 - contains no stereotypes to represent any UAF architecture view nor does it contain any definition of UAF architecture view content. [ The statement that 'these views are specified in the UAFML' is flat out untrue ]. Do the UAF authors not understand the architecture of the UML profile for the UAF?