C2MS11 — Consolidate all "Additional Information" Table and Model Figure changes into one Issue

Because many separate changes have been made in the [MESSAGE-TYPE] Message Additional Information Tables and in the [MESSAGE-TYPE] Message Contents (model) Figures, this issue seeks to consolidate all such changes together for final review. Changes here should be considered, therefore, to supersede all other C2MS 1.1 changes to the specific tables and figures enclosed in this issue.

All such tables/figures are in Chapter 8 PIM - Message Definitions.

Consolidate already-approved C2MS 1.1 Changes

Make all tables and figures in the document match what is in this issue. Note that if a table/figure is not shown here, it still may be modified in other already-approved issue(s). In other words, this proposal only governs the tables and figures listed here.

The changes here include and are limited to:

• [MESSAGE-TYPE] Message Additional Information Tables
• [MESSAGE-TYPE] Message Contents (model) Figures
• Occasional text associated with the above as indicated in this resolution

As part of this issue, we are also revising the types for CCSDS Telemetry message fields, SCID, VCID and APID. After lengthy discussion in the SDTF and C2MS 1.1 RTF, it was decided that these should be U32 for SCID and U16 for VCID and APID. This does not affect Replay Telemetry Data Request Message which uses String types for these fields, because it supports specifying a comma-delimited list or a range as a String. This change is also not made to the now-deprecated Telemetry CCSDS Frame Message.

Note, too, that as part of this resolution, we discovered and discussed in the SDTF and C2MS 1.1 RTF the need to rename one field type that is in conflict. Many messages have a PROD-SUBTYPE, a NUM-OF-PROD-SUBTYPES and a series of items called PROD-SUBTYPE.n. The series and its corresponding NUM-OF relate to a subcategory of PROD-SUBTYPES, so the name is in conflict and not possible to describe in UML. For this reason, the field names in question will now be NUM-OF-PROD-SUBTYPE-SUBCATEGORIES and PROD-SUBTYPE-SUBCATEGORY.n. This is manifest in Table 8-20 Archive Message Retrieval Request, 8-26 Archive Message Retrieval Response, 8-114 Archive Mnemonic Value Request Message, 8-119 Archive Mnemonic Value Response Message, 8-146 Product Request Message, 8-150 Product Response Message, and 8-156 Product Message.

As part of this resolution, use HEADER-VERSION "2024" and CONTENT-VERSION "2024" for any messages whose content has changed and preserve CONTENT-VERSION "2019" for all others. In the model figures add ".0" to keep with convention from C2MS 1.0. Eg: "2024.0" and "2019.0".

NOTES FOR REVIEWERS AND DOC EDITOR:

Throughout the table changes in this document, generally deleted text is lined-out, inserted text is underlined, tables within cells of a table are handled inline, but have a different look in the jira wiki markup than will exist in the final table, for example:

In the above table section, columns that have no header name should not be represented as columns in the final table. Tables-within-tables create rows with no row name, and sometimes columns with no values. So the above should appear in the final document as shown in attachment "C2MS-187 Tables-in-Tables"

In some cases, if there is no change to a cell, especially for a table within a table, we may use the designator [NO CHANGE]. Any other special cases will be made as a note to the reviewer and document editor, as [NOTE: ***]. Tables should use the same basic format as present in the 1.0 Spec.

Just the way the wiki markup works in JIRA, it's not easy to control column widths, so often text will be wrapped within a cell. The review/editor should take note to use the format of the existing document tables and make logical word breaks. For example, sometimes in the changes text the word SPECIFICATION might be split after SPECIFICAT with ION on the next line... clearly the document editor should make this look right in the final document.

For the modified figures, in the "C2MS-187xxx original" attachments, I have included the figure caption in the original document in the image for the purpose of locating it when reviewing/editing the document. However, the caption is, of course, not part of the figure, so it's not being included in the "C2MS-187 xxx" revised attachment should not be interpreted as removal when editing the figure in the document. Some figures may be new, so there will be a "C2MS-187 xxx new" attachment, and I'll make note of where that belongs below.

And just as a cautionary note for the review and document editor, other approved issues may reference one of these tables or figures, which are superseded here, but may also have other document changes, and there are other approved issues still that have their own changes not related to these figures and tables, so take care not to assume that other issues are superseded in their entirety by this issue.

The original, revised, and new diagrams related to this issue are attached as zip files rather than individual attachments due to their large number.

Finally, please see the attached Review Guide to help with contextual information related the consolidating effort of this issue resolution.