-
Key: C2MS12-91
-
Status: open
-
Source: Kratos RT Logic, Inc. ( Mr. Mike Anderson)
-
Summary:
In the spec PDF, there is a lot of inconsistency about how XX Message Additional Information tables appear in the document.
Some have (mostly) heavy cell borders - ex: Table 8-36. Directive Response Message Additional Information
Some have normal cell borders - ex: Table 8-140. Command Request Message Additional Information
Some have both in the same table - ex: Table 8-31. Directive Request Message Additional Information
Having heavy cell borders leads to a propensity to add cells with inconsistent cell borders, unless care is taken by the editor. Because of this, I recommend using normal cell borders on all these tables. Normal borders are used in many of them and they look fine.
Similarly all the XX Message Header Field Values tables should be updated in the same way.
Additionally, there are other similar tables that follow this basic construct and should also be updated:
- Table 6-9. Ordinal Date and Time Field Type Definition
- Table 6-10. Response Status Substructure
- Table 8-3. Mapping of Message Header Fields to the C2MS Subject Name
- Table 8-9. Pass-Related Occurrence Types
- Table 8-10. Telemetry Limit Violation Occurrence Types
- Table 8-11. Command Verification Occurrence Types
- Table 8-12. Miscellaneous Occurrence Types
- Table 8-13. Log Message to Echo a Directive Request Message
- Table 8-14. Product Message to Echo a Directive Request Message
- Table 8-20. Examples of Start and Stop Times
- Table 8-26. Meaning of Response Status and Return Value with Recommended Actions
- Table 8-37. Group Hierarchical Associations
- Table 8-160. Meaning of RESPONSE-STATUS and RETURN-VALUE with Recommended Actions
- Table A-1. Software Class and Subclass Categories
Finally, - Table 8-161. Example Scenarios Using the Set of Product Messages should keep the format of the cells generally, but needs to be cleaned up.
As a note, there are some tables where the structure of the table is easier to distinguish with some heavy borders and these should remain. These are related to the XX Message Subject Naming Tables.
-
Reported: C2MS 1.1b1 — Fri, 22 Nov 2024 15:25 GMT
-
Updated: Fri, 22 Nov 2024 16:51 GMT
C2MS12 — Standardize Table Cell Borders
- Key: C2MS12-91
- OMG Task Force: Command and Control Message Specification (C2MS) 1.2 RTF