Nov 09 11:16 2018, mark lewis wrote to Andrew Leary:
AL>> FTS-1 really could be split into several documents. The stored AL>> message definition section is useful information, but not absolutely AL>> required for a FTS-1 compatible implementation.
ml> this is why other proposals like the Hudson Message Base format and ml> others were discussed to be placed as reference documents in the ml> library and specifically not set as FTSC standards... putting them in ml> the library was to aid others as to the workings of them but not to ml> exhibit them as a FTSC standard... i remember discussion about it but ml> do not recall if the documents were actually written and archived...
AFAIK, there aren't any of the messagebase formats in the FTSC library, besides classic *.MSG.
