-
Key: C2MS12-167
-
Status: open
-
Source: Kratos RT Logic, Inc. ( Mr. Mike Anderson)
-
Summary:
C2MS has constructs and language that make it seem like a pub/sub specification, though that is merely one possible architecture. C2MS message define a format for messages that could be used in a service-based architecture.
To aid with this, we should not use the term 'publish', and we should be careful with 'subscribe'.
This is in order to get away from the assumption of a pub/sub architecture. This will include renaming the MEPS that have "Publish".
Note that some already-approved issues in this release might have used "Publish". Need to find and correct these.
We should further state that the Subject is optional used to aid message delivery, most useful in a pub/sub setup, but the subject is derived from, rather than adding to the message itself.
In the document, use terms like 'send' instead of 'publish'. Make the patterns refer to Notify rather than publish.
-
Reported: C2MS 1.1b1 — Thu, 18 Sep 2025 14:16 GMT
-
Updated: Fri, 3 Oct 2025 00:25 GMT
-
Attachments:
- C2MS12-167_1_original.bmp 1.49 MB (image/bmp)
- C2MS12-167_1_revised.svg 14 kB (image/svg+xml)
- C2MS12-167_2_original.bmp 984 kB (image/bmp)
- C2MS12-167_2_revised.svg 6 kB (image/svg+xml)
- C2MS12-167_3_original.bmp 1.48 MB (image/bmp)
- C2MS12-167_3_revised.svg 12 kB (image/svg+xml)
- C2MS12-167_4_original.bmp 1.64 MB (image/bmp)
- C2MS12-167_4_revised.svg 15 kB (image/svg+xml)
C2MS12 — Documentation Changes to Move Away from Pub/Sub Expectation
- Key: C2MS12-167
- OMG Task Force: Command and Control Message Specification (C2MS) 1.2 RTF