-
Key: C2MS-12
-
Status: closed
-
Source: NASA ( Mr. John Bugenhagen)
-
Summary:
(Product Messages) Section 7.11 (Though these comments are related to guidance for custom messages
- Consider providing guidance regarding what the minimal set of attributes should be for a custom message type.
- Indicate that custom messages can be considered to become sponsored message types in future versions of the specification.
- Extending the lexicon should be encouraged by the implementation, not discouraged, as the strictest of the GMSEC 4.x MIST modes does.
-
Reported: C2MS 1.0a1 — Mon, 10 Sep 2018 19:26 GMT
-
Disposition: Resolved — C2MS 1.0
-
Disposition Summary:
Change section 8.1 to mention extensions
Change: "The Message Header is a super-class for all C2MS messages in the sense that all fields in the Message Header appear in all of the C2MS messages." to "The Message Header is a super-class for all C2MS messages and any extensions in the sense that all fields in the Message Header appear in all of the C2MS messages.
-
Updated: Tue, 8 Oct 2019 17:51 GMT
C2MS — Product Messages comments
- Key: C2MS-12
- OMG Task Force: Command and Control Message Specification (C2MS) 1.0 FTF