Alert Management Service Avatar
  1. OMG Specification

Alert Management Service — Closed Issues

  • Acronym: ALMAS
  • Issues Count: 19
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
ALMAS12-46 Error in ALMAS_RaiseAlertWithDynamicData topic struct declaration ALMAS 1.1 ALMAS 1.2 Resolved closed
ALMAS12-26 RaiseAlertFromOverrides Summary formatting ALMAS 1.1 ALMAS 1.2 Resolved closed
ALMAS12-3 Greater Granularity and Clarity in Conformance Levels ALMAS 1.1b1 ALMAS 1.2 Resolved closed
ALMAS12-45 Inconsistency in DynamicMessageData param between PIM and PSM ALMAS 1.1 ALMAS 1.2 Resolved closed
ALMAS12-63 DDS PSM Mapping rationale for the ALMAS_CreatedAlert topic is missing ALMAS 1.1 ALMAS 1.2 Resolved closed
ALMAS12-21 Typo in RemoveAlertsWithDynamicMessageData Summary ALMAS 1.1 ALMAS 1.2 Resolved closed
ALMAS12-44 Repeat of RaiseAlertFromOverrides in CORBA PSM ALMAS 1.1 ALMAS 1.2 Resolved closed
ALMAS12-15 Use less colloquial language in ValidAlertResponse ALMAS 1.1 ALMAS 1.2 Resolved closed
ALMAS12-37 Typo in AlternativeAction xml schema element ALMAS 1.1 ALMAS 1.2 Resolved closed
ALMAS12-14 Rogue hyphen in DataValue attribute description ALMAS 1.1b1 ALMAS 1.2 Resolved closed
ALMAS12-43 Typo in CORBA PSM Section Heading ALMAS 1.1 ALMAS 1.2 Resolved closed
ALMAS12-13 Ambiguity in dynamic message data substitution ALMAS 1.1b1 ALMAS 1.2 Resolved closed
ALMAS12-8 Formatting and duplication of Status description ALMAS 1.1b1 ALMAS 1.2 Resolved closed
ALMAS12-2 Remove Original Submission Information ALMAS 1.1 ALMAS 1.2 Resolved closed
ALMAS12-27 UpdateAlertPriority summary grammar ALMAS 1.1 ALMAS 1.2 Resolved closed
ALMAS12-25 ALMAS Producer component terminology ALMAS 1.1 ALMAS 1.2 Resolved closed
ALMAS12-4 Incomplete Normative References ALMAS 1.1b1 ALMAS 1.2 Resolved closed
ALMAS12-28 UnregisterReceiver hyphen typo ALMAS 1.1 ALMAS 1.2 Resolved closed
ALMAS12-1 Add GraphQL PSM for ALMAS ALMAS 1.1 ALMAS 1.2 Resolved closed

Issues Descriptions

Error in ALMAS_RaiseAlertWithDynamicData topic struct declaration

  • Key: ALMAS12-46
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    The declaration of the DynamicMessages field is incomplete and incorrect.
    It is missing the DynamicMessages field name
    It has an extra space in the type's package qualification
    The type should be ALMAS_DynamicMessageDataTypeSet

  • Reported: ALMAS 1.1 — Tue, 8 Feb 2022 12:08 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Fix Issues with DynamicMessages field

    Apply suggested changes from the issue

  • Updated: Wed, 13 Jul 2022 14:17 GMT
  • Attachments:

RaiseAlertFromOverrides Summary formatting

  • Key: ALMAS12-26
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    No space between sentences. Would be improved by inserting new-lines.

    Also RaiseAlertWithDynamicData has an extra new-line.

    Also RaiseAlertFromData needs a new-line instead of a space.

  • Reported: ALMAS 1.1 — Mon, 7 Feb 2022 11:42 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Improve Raise Alert Summary Formatting

    Add improvements as suggested by the issue.

  • Updated: Wed, 13 Jul 2022 14:17 GMT

Greater Granularity and Clarity in Conformance Levels

  • Key: ALMAS12-3
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    The Conformance section talks about general conformance level 1 functionality, but then adds extensions which are also numbered 1 to 4. There could be confusion as to what conformance to level 1 actually means.
    Also a useful system could be composed of components that implement a subset of the core (level 1) interface. Therefore, there should be one or more additional levels of conformance defined that reflects this.

  • Reported: ALMAS 1.1b1 — Mon, 31 Jan 2022 09:54 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Basic, Advanced and Extended Conformance on an Interface Role Basis

    There are three distinct roles in the ALMAS abstracted by the interface classes defined in the ALMAS Management package: Producer, Manager and Receiver. Conformance should recognise that a conforming application will be performing only one of these roles and therefore only a subset of the interface will be applicable.
    Additionally, conformance should recognise a minimal basic level of conformance as a pathway to adoption and use of the specification. This is the set of methods to support raising and receiving alerts without templates, customisation or modification.

  • Updated: Wed, 13 Jul 2022 14:17 GMT
  • Attachments:

Inconsistency in DynamicMessageData param between PIM and PSM

  • Key: ALMAS12-45
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    In the PIM the parameter for DynamicMessageDataSet in operations RaiseAlertFromOverrides and RaiseAlertWithDynamicData is StringSet, but in the CORBA and DDS PSM the type is DynamicMessageDataTypeSet (which is a sequence of the DynamicMessageDataType struct)

  • Reported: ALMAS 1.1 — Tue, 8 Feb 2022 12:01 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Re-align PIM for DynamicMessageDataSet

    Change the PIM type to match the PSMs as the additional information in the PSM types is required to enable the required behaviour. Also align the parameter names (i.e. change to DynamicMessages).

  • Updated: Wed, 13 Jul 2022 14:17 GMT
  • Attachments:

DDS PSM Mapping rationale for the ALMAS_CreatedAlert topic is missing

  • Key: ALMAS12-63
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    There is no rationale for the DDS DCPS/IDL PSM topic type ALMAS_CreatedAlert.
    By closer inspection, this is introduced to map to the AlertID out parameter of the various alert creation methods in the Producer interface.
    It is needed so that producer know the alert id and are therefore able to cancel alerts that they have previously raised.

  • Reported: ALMAS 1.1 — Sat, 12 Feb 2022 11:49 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Add explanation of ALMAS_CreatedAlert

    Add explanatory text to the ALMAS Management DDS DCPS/IDL PSM section

  • Updated: Wed, 13 Jul 2022 14:17 GMT

Typo in RemoveAlertsWithDynamicMessageData Summary

  • Key: ALMAS12-21
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    There is an erroneous space in the summary cell of RemoveAlertsWithDynamicMessageData
    "specific rea l world object" should be "specific real world object"

  • Reported: ALMAS 1.1 — Mon, 7 Feb 2022 11:19 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Remove space in real

    Remove space (this is only in the published spec not in the 1.1 RTF convenience doc)

  • Updated: Wed, 13 Jul 2022 14:17 GMT

Repeat of RaiseAlertFromOverrides in CORBA PSM

  • Key: ALMAS12-44
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    In the CORBA PSM there are two operations with the name RaiseAlertFromOverrides but RaiseAlertWithDynamicData is missing.

  • Reported: ALMAS 1.1 — Tue, 8 Feb 2022 11:55 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Change second RaiseAlertFromOverrides to RaiseAlertWithDynamicData

    In the CORBA PSM change the second occurrence of RaiseAlertFromOverrides to RaiseAlertWithDynamicData so as to match the PIM

  • Updated: Wed, 13 Jul 2022 14:17 GMT

Use less colloquial language in ValidAlertResponse

  • Key: ALMAS12-15
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    The use of "pecking order" rather than prioritisation is unhelpful, particular if readers don't have English as first language.

  • Reported: ALMAS 1.1 — Sat, 5 Feb 2022 15:44 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Rework Pecking Order

    Change pecking order to actionee prioritisation

  • Updated: Wed, 13 Jul 2022 14:17 GMT

Typo in AlternativeAction xml schema element

  • Key: ALMAS12-37
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    "none standard" should be "non-standard"

  • Reported: ALMAS 1.1 — Mon, 7 Feb 2022 18:09 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Fix typo in AlternativeAction documentation element

    none should be non

  • Updated: Wed, 13 Jul 2022 14:17 GMT

Rogue hyphen in DataValue attribute description

  • Key: ALMAS12-14
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    Attribute DataValue for DynamicAlertData has instantia-tion. This does not need to be split.

  • Reported: ALMAS 1.1b1 — Sat, 5 Feb 2022 15:32 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Remove hyphen

    remove hyphen in description

  • Updated: Wed, 13 Jul 2022 14:17 GMT

Typo in CORBA PSM Section Heading

  • Key: ALMAS12-43
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    Section heading is
    OMG ORBA/IDL Platform Specific Model
    should be
    OMG CORBA/IDL Platform Specific Model

  • Reported: ALMAS 1.1 — Tue, 8 Feb 2022 11:48 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Add C for CORBA back

    Correct Typo

  • Updated: Wed, 13 Jul 2022 14:17 GMT

Ambiguity in dynamic message data substitution

  • Key: ALMAS12-13
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    The description of class DynamicMessageData and its DataTag attribute is ambiguous as to whether one or two percent (%) markers are required. Also the protocol is ambiguous when there are 10 or more markers. Also, particularly with a single % marker there isn't a defined way to escape the markers.

  • Reported: ALMAS 1.1b1 — Sat, 5 Feb 2022 15:30 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Clarify Dynamic Message Substitution

    Placeholder tags to be designated by a single exclosing percent characters.
    Multiple - in principle unbounded - replacements supported with each tag enclosed by space (or other non-alphanumeric character). The examples given in the current specification (t1, tn) are examples and more meaningful tags can be used and are encouraged (e.g. %number%, %score% or %name%).
    It is not necessary to provide a means of specifying a way to express %name% as a literal substring in a static message as this would have no meaning to a system user.
    Additionally, it should be possible to specify a replacement at the start or end of the static message. Equally it should be possible to have dynamic data at the start or end of the message and it should be possible to use punctuation around it (e.g. a comma). Therefore substitution points should be defined by:
    (start | non-alphanumeric)%t(numeric){end | non-alphanumeric)
    It is an error to specify static and dynamic data message instances with different substitution tags for the same alert template. In particular all static message instances (for different language locales) must have the same substitution set.

  • Updated: Wed, 13 Jul 2022 14:17 GMT

Formatting and duplication of Status description

  • Key: ALMAS12-8
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    The description of the status attribute for class AlertData repeats the information for the Status enumeration. This is also poorly formatted and so difficult to read.

  • Reported: ALMAS 1.1b1 — Sat, 5 Feb 2022 13:22 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Remove duplicate information

    Remove duplication of enumeration values for status attribute

  • Updated: Wed, 13 Jul 2022 14:17 GMT

Remove Original Submission Information

  • Key: ALMAS12-2
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    Section 11 Changes or extensions required to adopted OMG
    specifications applies to the submission and should not have been retained in the published specification

  • Reported: ALMAS 1.1 — Mon, 31 Jan 2022 09:38 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Remove section 11

    Remove Section 11: Change or extensions required to adopted OMG specifications

  • Updated: Wed, 13 Jul 2022 14:17 GMT

UpdateAlertPriority summary grammar

  • Key: ALMAS12-27
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    This is missing an apostrophe and is in any case could be stated more clearly

  • Reported: ALMAS 1.1 — Mon, 7 Feb 2022 11:48 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Improve UpdateAlertPriority Summary description

    Improve description to be "Updated the priority of existing alert instances that have previously been raised."

  • Updated: Wed, 13 Jul 2022 14:17 GMT

ALMAS Producer component terminology

  • Key: ALMAS12-25
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    Refer to system components rather than system objects in first sentence

  • Reported: ALMAS 1.1 — Mon, 7 Feb 2022 11:36 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Change objects to components

    Change objects to components in ALMAS Producer description

  • Updated: Wed, 13 Jul 2022 14:17 GMT

Incomplete Normative References

  • Key: ALMAS12-4
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    The Normative References is missing entries for the PIM and PSM technologies

  • Reported: ALMAS 1.1b1 — Mon, 31 Jan 2022 09:56 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Add new Normative Reference Section

    Base style on TDAI normative reference section
    Add references for DDS, IDL, GraphQL, COM, CORBA, XML

  • Updated: Wed, 13 Jul 2022 14:17 GMT
  • Attachments:

UnregisterReceiver hyphen typo

  • Key: ALMAS12-28
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    Extra hyphen in summary for UnregisterReceiver (avail-able)

  • Reported: ALMAS 1.1 — Mon, 7 Feb 2022 11:52 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Remove hyphen in UnregisterReceiver

    remove hyphen in available

  • Updated: Wed, 13 Jul 2022 14:17 GMT

Add GraphQL PSM for ALMAS

  • Key: ALMAS12-1
  • Status: closed  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    Add a GraphQL PSM option using the mapping defined in the TDAI specification for implementations using web technologies

  • Reported: ALMAS 1.1 — Sat, 29 Jan 2022 18:58 GMT
  • Disposition: Resolved — ALMAS 1.2
  • Disposition Summary:

    Add GraphQL Platform Specific Model

    Add a GraphQL platform specific model as an alternative technology particular aimed at contexts using this technology and other similar web technologies.
    Base the PSM mappings on those defined for the TDAI specification, noting the principles of categorizing the PIM noted in the DDS / IDL / DCPS PSM.
    The schema is to be added to the normative machine readable files.

  • Updated: Wed, 13 Jul 2022 14:17 GMT
  • Attachments: