[Css-csts] FW: Fw: Draft Technical Corrigendum of the Guidelines

[John Pietras]

CSTSWG colleagues ---
Wolfgang has responded to my comments on the Draft Technical Corrigendum of the Guidelines, and I concur with his changes. He has asked me to forward the revised draft TC, as well as the version of the Guidelines Magenta Book as it would appear with the TC applied to them. The attached documents are therefore the ones that are now "on the table" for consideration.

Best regards,
John

From: Wolfgang Hell <wo_._he at t-online.de>
Sent: Wednesday, July 17, 2019 8:41 AM
To: John Pietras <john.pietras at gst.com>
Cc: Holger.Dreihahn at esa.int
Subject: Re: [Css-csts] Fw: Draft Technical Corrigendum of the Guidelines

Dear John,

Thank you very much for your feedback. The good news is that we are obviously in agreement regarding what needs to be changed.

For paragraph 4.3.11 I agree that what you suggest is clearer in terms what we expect a CSTS specification to state. However, I changed the initial words of item a) a bit because I was concerned that otherwise it is not obvious what is supposed to be replaced.

Regarding 4.3.11 item b) I agree with your suggested clarification and have added this to the TC, although as you I suspect that this will never become applicable in practice.

In order to avoid confusion because of the changes in subsection and paragraph numbers, the revised TC indicates the original and the post update number for each of the suggested changes.

For the other points, this was a mixture of my negligence and my ESA laptop not working and consequent use of a "German speaking" PC.

Please find attached the revised draft Guidelines TC and the updated Guidelines where the latter are now more accurate in the sense that I used the officially published Magenta Book as starting point.

Given that I do not know when you might have a chance to look at this and also bearing in mind that Holger is about to go on vacation, may I ask you to forward this material via the CCSDS mailman, provided that you are now happy with the suggested updates?

Best regards,
Wolfgang


Am 15.07.2019 um 19:33 schrieb John Pietras:
Dear Wolfgang,
I have reviewed your proposed Technical Corrigendum (TC). Here are my comments. But before getting into the specific comments one thing that immediately jumped out is that the TC is loaded with cross references that break (ERROR! Reference source not found) when the document is printed 9which is what I did). They will also likely break when transformed into the CCSDS TC. The attached copy has the cross references locked (accomplished by CTRL-A followed by CTRL-F11). Also, there was some formatting markup that I "accepted". However, the attached does not include the specific recommendations that I make below.


1.      The update for page 4-2, paragraph 4.3.11 - "Add the following new item to the list: a) in the introductory paragraph of the statement: ...". The "additional"  sentences are in fact a combination of new material and modifications of existing sentences in the "boilerplate", so it's not obvious how and where it is to be added. Also, the semi-colon between the "to-be-added" statement and the NOTE is confusing and I don't think belongs there. I suggest that the whole paragraph be replaced, i.e., the entry for this TC item would read

Page 4-2, paragraph 4.3.11

Add the following new item a) to the list:

a)      Replace the introductory paragraph with the following paragraph: "The following publications contain provisions which, through reference in this text, constitute provisions of this document.  At the time of publication, the editions indicated were valid.  It is important to note that the edition of the Cross Support Transfer Service-Specification Framework that is named in this subsection is the only edition that can be used as a source of requirements for this edition of this Cross Support Transfer Service Recommended Standard. All other publications in the list are subject to revision, and users of this document are encouraged to investigate the possibility of applying the most recent editions of the publications (other than the Specification Framework) indicated below. The CCSDS Secretariat maintains a register of currently valid CCSDS publications."



NOTE  -  In the CSTS Specification Framework (reference [1]), procedure version numbers are increased as soon as there are changes to those procedures, but only then. Consequently different CSTS Specification Framework editions may contain the same version of a given procedure type. One CSTS specification is bound to one specific edition of the CSTS Specification Framework and consequently only the procedure versions and ASN.1 module versions specified in that edition can be used for the specification of that CSTS.



2.      This is a perhaps just an academic question, but is it possible that a "new" CSTS specification could be written using a previous version of the SFW, e.g., to use a feature that was somehow eliminated by an update? Is so, then perhaps bullet b) under section 4.3.11 of the Guidelines should say "the version of the CSTS Specification Framework Recommended Standard that is applicable to the CSTS Specification Recommended Standard" instead of "the version of the CSTS Specification Framework Recommended Standard that is in effect when the CSTS Specification becomes a Recommended Standard".
Alternatively, if we assume that in such a case the SFW would be updated again to add back the needed functionality such that the "current' version of the SFW is indeed applicable, then the wording can remain as it is.



3.      With the insertion of the new 4.10.3, the section numbers will advance for the subsequent sections. I got confused when trying to cross check the TC against the version of the Guidelines with the changes integrated into them, because the renumbering took place. Perhaps some clarification can be added to the labels along the lines of:

-          the label "Page 4-30, paragraph 4.10.3.1" could be "Page 4-30, paragraph 4.10.3.1 (now renumbered to 4.10.4.1)";

-          the label "Page 4-30, paragraph 4.10.3.2" could be "Page 4-30, paragraph 4.10.3.1 (now renumbered to 4.10.4.2)";

-          the label "Page 4-31, paragraph 4.10.3.5" could be "Page 4-30, paragraph 4.10.3.1 (now renumbered to 4.10.4.5)";

-          "4.10.3.5" should be "4.10.4.5"; and

-          the label "Page 4-31, subsection 4.10.7" could be "Page 4-30, subsection 4.10.7 (now renumbered to 4.10.8)"



4.      Similarly, with the reorganization of subsections under 4.11.3:

-          the label "Page 4-36, paragraph 4.11.5.1.1" could be "Page 4-30, paragraph 4.11.5.1.1 (now renumbered to 4.11.3.3.1)";

-          the label "Page 4-37, paragraph 4.11.5.1.2" could be "Page 4-30, paragraph 4.11.5.1.2 (now renumbered to 4.11.3.3.2)": and

-          the label "Page 4-37, paragraph 4.11.5.1.5" could be "Page 4-30, paragraph 4.11.5.1.2 (now renumbered to 4.11.3.3.5)"



5.      Under the changes for Page 4-30, paragraph 4.10.3.1, the sentence "Add the word "and" to the end of of item c) of the list" has a repeated "of". [I also note the German(?) opening double quotation mark ("and") which I assume Tom G. will anglicize in the final TC.]

Best regards,
John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/css-csts/attachments/20190718/a347a379/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Guidelines Technical Corrigendum 190717.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 25693 bytes
Desc: Guidelines Technical Corrigendum 190717.docx
URL: <http://mailman.ccsds.org/pipermail/css-csts/attachments/20190718/a347a379/attachment-0001.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 921x2m1_final. plus TC.doc
Type: application/msword
Size: 1615872 bytes
Desc: 921x2m1_final. plus TC.doc
URL: <http://mailman.ccsds.org/pipermail/css-csts/attachments/20190718/a347a379/attachment-0001.doc>