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

Mon Jul 15 17:33:40 UTC 2019

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

From: CSS-CSTS <css-csts-bounces at mailman.ccsds.org> On Behalf Of Holger.Dreihahn at esa.int
Sent: Wednesday, July 10, 2019 9:39 AM
To: CCSDS_CSTSWG(css-csts at mailman.ccsds.org) <css-csts at mailman.ccsds.org>
Subject: [Css-csts] Fw: Draft Technical Corrigendum of the Guidelines

Dear CSTS WG Colleague,
Pleas have a look at Wolfgang's message below.

Regards,
Holger

Holger Dreihahn
European Spacecraft Operations Centre | European Space Agency | S-431
+49 6151 90 2233 | http://www.esa.int/esoc
----- Forwarded by Holger Dreihahn/esoc/ESA on 10/07/2019 15:37 -----

From:        "Wolfgang Hell" <whell at gmx.de<mailto:whell at gmx.de>>
To:        "Holger.Dreihahn at esa.int<mailto:Holger.Dreihahn at esa.int>" <Holger.Dreihahn at esa.int<mailto:Holger.Dreihahn at esa.int>>
Date:        10/07/2019 11:58
Subject:        Fwd: Fwd: Draft Technical Corrigendum of the Guidelines
________________________________

Once again my original email has bounced ...

-------- Weitergeleitete Nachricht --------
Betreff:
Fwd: Draft Technical Corrigendum of the Guidelines
Datum:
Wed, 10 Jul 2019 11:42:43 +0200
Von:
Wolfgang Hell <wo_._he at t-online.de><mailto:wo_._he at t-online.de>
Antwort an:
wo_._he at t-online.de<mailto:wo_._he at t-online.de>
An:
Wolfgang Hell <whell at gmx.de><mailto:whell at gmx.de>

-------- Weitergeleitete Nachricht --------
Betreff:
Draft Technical Corrigendum of the Guidelines
Datum:
Wed, 10 Jul 2019 11:17:38 +0200
Von:
Wolfgang Hell <wo_._he at t-online.de><mailto:wo_._he at t-online.de>
Antwort an:
wo_._he at t-online.de<mailto:wo_._he at t-online.de>
An:
Holger Dreihahn <Holger.Dreihahn at esa.int><mailto:Holger.Dreihahn at esa.int>

Hi Holger,

Please forward the message below to the CSTS WG. Thanks.

Dear All,

in response to the action items I took during the Spring Meet related to the Guidelines document I have now drafted a Technical Corrigendum (attached). I would appreciate a sanity check by the WG members before we make this an official request. The Technical Corrigendum may be somewhat difficult to review, among others because of the changes in section / paragraph numbers which have occurred due to some of the necessary corrections. To make the review easier, I'm attaching also the Guidelines document modified in accordance with the proposed Technical Corrigendum. Thank you in advance for your feedback.

Best regards,

Wolfgang

This message is intended only for the recipient(s) named above. It may contain proprietary information and/or

protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received

this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect

personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo at esa.int<mailto:dpo at esa.int>).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/css-csts/attachments/20190715/010ef016/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Guidelines Technical Corrigendum 1-locked.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 25310 bytes
Desc: Guidelines Technical Corrigendum 1-locked.docx
URL: <http://mailman.ccsds.org/pipermail/css-csts/attachments/20190715/010ef016/attachment-0001.docx>