ALMAS16 — Interface/method signature inconsistencies

From William (Bill) Beavin's AB comments on ALMAS 1.5 RTF
• RemoveAlertsWithDynamicMessageData heading shows (String, String) but parameters list three inputs: CancellerID, DataType, DataValue.
• RaiseAlertWithDynamicData parameter typing appears corrupted:
o operation title includes DynamicMessageDataTypeSet, AlertDataExtraAttributesTypeSet
o parameter list ends with DynamicMessages: AlertDataExtraAttributesTypeSet
• UpdateDynamicMessageData(int, String, DynamicMessageData) uses parameter name ObjectValue, but summary says OldData identifies what changes.
• GetAllTemplateIDs mentions Filter non-null behavior, but type/null semantics are not specified consistently.
• GetTemplate(int) is described differently in DDS mapping table than in PIM table.
• RaiseAlertFromData says a temporary AlertTemaplate is created — typo, but also conceptually should clarify whether full template validation applies.