-
Key: C2MS12-44
-
Status: closed
-
Source: Kratos RT Logic, Inc. ( Mr. Mike Anderson)
-
Summary:
The various Navigation Data Messages are nearly identical. They should be consolidated into a hierarchy that defines a Navigation Data Message base class and then let the others derive from it for better model structure. The Tracking Data Message has a few extra fields. Otherwise, everything is identical across all messages except for some type values.
I thought about doing this when I was updating the model in 1.1, but would have also had to update the chapter text and didn't have time for all that in 1.1.
-
Reported: C2MS 1.0 — Mon, 15 Apr 2024 18:12 GMT
-
Disposition: Deferred — C2MS 1.2b1
-
Disposition Summary:
Defer to future 2.0 release
This would be really convenient to do, but should be in a major release.
-
Updated: Mon, 30 Mar 2026 14:00 GMT
C2MS12 — Consolidate Navigation Data Messages
- Key: C2MS12-44
- OMG Task Force: Command and Control Message Specification (C2MS) 1.2 RTF