The DDS-Xtypes specification now provides a standard way of specifying keys. This specification should use that mechanism

The specification does not standardise the logging mechanism. This could be achieved by PSM specific means.

The semantics of the reason attribute of the CallStatus call should be encapsulated as an enumeration. Also the formatting of the description of the attribute doesn't help clarity.

The formatting of tables for operations for interface classes doesn't aid readability

Topic types ALMAS_RegisterReceiver and ALMAS_UnregisterReceiver are not required as this functionality is covered by the statndard (DCPS) DDS Subscription Model.

The summaries for operations AttachCategorisationRule and DetachCategorisationRule refer to Categorization Rules. Whilst there is some description in section 6.4 there is no overview of purpose prior to this point or forward sign-posting to section 6.4, so the purpose of these methods is left somewhat opaque.

The spec does not appear to offer an interface for an alert client to be informed of the alternative or non-standard choice that has been made in response to an alert.

The description of ALMAS Manager does not give a clear picture of where it fits into the ALMAS system.