Command and Control Message Specification Avatar
  1. OMG Specification

Command and Control Message Specification — All Issues

  • Acronym: C2MS
  • Issues Count: 1
  • Description: All Issues
Open Closed All
All Issues

Issues Summary

Key Issue Reported Fixed Disposition Status
C2MS11-15 Log message scope too broad, need Alert/Status style message introduced C2MS 1.0b2 C2MS 1.1b1 Closed; No Change closed

Issues Descriptions

Log message scope too broad, need Alert/Status style message introduced

  • Key: C2MS11-15
  • Status: closed  
  • Source: The MITRE Corporation ( Ryan Conrad)
  • Summary:

    The LOG message is nice to cover a certain scope of messages needing to be utilize by developers using the specification, however the ProductMessage again and again finds itself utilized instead of the LOG message because of the structure the LOG message has versus the ProductMessage for making things like status or event messages.

    Because of this, I had looked at the ALMAS specification from Navy and the CAP (Common Alerting Protocol) from OMG to come up with an Alert Notification and Alert Ack message that would be greatly helpful in making a solid Header for alert and status messages that could be different in scope than typical LOG messages.

    I have these messages defined in GMSEC/COMPATC2, and would need to attach it for you to see the details. Thank you
  • Reported: C2MS 1.0b2 — Mon, 30 Sep 2019 18:57 GMT
  • Disposition: Closed; No Change — C2MS 1.1b1
  • Disposition Summary:

    The log message is fine, propose a new alert/event message instead

    Instead of modifying log beyond its original design goals, anyone may propose a new alert/event message for a future revision. Example: C2MS-1.2.
  • Updated: Mon, 16 Sep 2024 14:18 GMT