HX 19.1.002 - SAME
Streamlined Advanced Messaging Environment, Take 2
Originally, SAME was to be a distinct environment for integration. There were three parts to the system... the frontend client, the SAME server side, and then the integration componenents. The display ended up looking something like the thing on the right. The server side and some integrations were also in the works, but not very useful. Originally, the Net Intex project was supposed to integrate into SAME, but a new teleprinter pushed me back towards the telegraphic messaging network idea as the main project.
Ultimately, the content of SAME messages were either simple lines of text that were the whole message, simple blobs of html that were the whole message, or data in JSON format. Now that I have a teleprinter and want to use it, I needed to use a data format that was friendlier for humans. I had toyed around with EDIFACT-style messages, but the format is ugly. While researching the various ACP specifications I stumbled across USMTF, the United States Message Text Format. It's essentially a slash-delimited text format that the military has been using for decades. Its primary use is to transmit formal data... literally forms data... from one location to another in a method that is machine processable and human-readable. They already solved the problem!
So, with that in mind, the Service/Facility/Level concept in SAME becomes a hierarchy of subscription points for PubSub messages. Generally speaking, an endpoint would be subscribed to one or more services, though it is possible for someone to want it filtered down to the Level level. The message format will be practically the same as USMTF, but renamed the Undeniabily Similar Message Text Format, abbreviated as SAME/USMTF to disambugiate any potential confusion. SAME is now an addressing mode for the Net Intex Messaging System. SAME/USMTF is used for SAME messages, as well as for service messages in general NIMS service.