-
Key: C2MS12-33
-
Status: open
-
Source: Kratos RT Logic, Inc. ( Mr. Mike Anderson)
-
Summary:
Some message fields of type Boolean are listed as optional. This has a pretty ambiguous meaning for a boolean, which if present, is always True or False.
For one non-exhaustive example, some messages include a FINAL-MESSAGE boolean field that is optional. What does it mean when not present? It could be inferred that it is equivalent to False, but it could also be inferred that this is ignored when there is only one message, which would be the same as True.
We need to go through all these usages individually and decide if these should be required, rather than optional.
-
Reported: C2MS 1.0 — Thu, 18 Jan 2024 21:04 GMT
-
Updated: Thu, 26 Sep 2024 22:24 GMT
C2MS12 — Re-evaluate Optional Boolean Fields
- Key: C2MS12-33
- OMG Task Force: Command and Control Message Specification (C2MS) 1.2 RTF