-
Key: C2MS11-31
-
Status: closed
-
Source: NASA ( Mr. John Bugenhagen)
-
Summary:
This issue is related to
C2MS11-30, which is about the table immediately prior to every message UML diagram. The UML diagrams, for example figure 8-3, seem to indicate that "MESSAGE-TYPE" and "MESSAGE-SUBTYPE" are fields in the individual message when they are actually in the Message Header. -
Reported: C2MS 1.0 — Tue, 23 Jun 2020 17:43 GMT
-
Disposition: Resolved — C2MS 1.1b1
-
Disposition Summary:
Do this in 1.1
Remove the current block attributes, and instead show Constraints as in:
{Message Header.MESSAGE-TYPE == MSG, Message Header.MESSAGE-SUBTYPE == LOG}with the required values. Display the full Message Header classifier for clarity.
If this proposal is accepted, a complete set of before and after images will be provided as part of the RTF Report
Note that the final images may be a convergence with other voted in global changes. In other words, if this proposal is accepted and other figure-affecting proposals are also accepted, all sets of changes will be made in the final "after" images in the RTF Report.
-
Updated: Mon, 16 Sep 2024 14:18 GMT
-
Attachments:
- C2MS11-31_1_original.png 172 kB (image/png)
- C2MS11-31_1_revised.png 58 kB (image/png)
C2MS11 — Clarify the UML diagrams regarding the values for the fields inherited from Message Header
- Key: C2MS11-31
- OMG Task Force: Command and Control Message Specification (C2MS) 1.1 RTF