[Css-csts] Updated MD-CSTS and RID status document on CWE

Tue Mar 31 20:25:21 UTC 2015

Tim,
I've had the chance to look at your comments and proposal. I'll note that the pre-Red-1 version of book in the spring of 2014 had lists similar to what you have recommended, but all but the first one (for Cyclic Report) were collapsed in response to a comment from the WG saying that the MD-CSTS book was too repetitious of the material in the Framework. In response to that comment, I compressed the material in section 2.2.3.

However, I may have compressed it too much, and there is certainly merit in helping the reader to compare the three procedures through parallel descriptions. So I have put corresponding lists back into the Notification and Information Query procedure sections (2.2.3.3 and 2.2.3.4). However, these lists are not as descriptive as the one in the Cyclic Report section, under the theory that the more-elaborate description of each of the data types in the Cyclic Report section provides adequate information for the reader to understand their purposes in the other two procedures.

One final comment on this - the lists are not completely parallel across all three procedures. Specifically, the Notification procedure does not mention procedure configuration parameter change events, procedure types, or procedure instance identifiers because none of the MD-CSTS procedures have dynamically-changeable configuration parameters that would result in an event notification.

I'm in the process of making other changes resulting from Wolfgang's comments and a few other things that need to be cleaned up, but I hope to have an updated MD-CSTS book out to the WG sometime next week.

Thanks for your review and the good suggestion.

Best regards,
John

From: Ray, Timothy J. (GSFC-5830) [mailto:timothy.j.ray at nasa.gov]
Sent: Sunday, March 22, 2015 11:37 PM
To: John Pietras; CCSDS_CSTSWG (css-csts at mailman.ccsds.org)
Subject: Re: [Css-csts] Updated MD-CSTS and RID status document on CWE

Dear CSTS-WG colleagues,

Please forgive me for putting in input so late in the cycle...

Sections 2.2.3.2 and 2.2.3.3 of the MD-CSTS Red Book include a list of the possibilities for requesting cyclic reporting of parameters and event notifications, respectively.  Both sections list five possibilities.  In section 2.2.3.2, these are labeled 'a)' through 'e)'.  In section 2.2.3.3, they are contained within a single sentence near the top of page 2-8.

It appears that, for each possibility listed in section 2.2.3.2, there is an analogous possibility in section 2.2.3.3:

  1.  the names of individual monitored parameters (2.2.3.2a), or the names of event names (2.2.3.3).
  2.  The labels of monitored parameter types (2.2.3.2b), or event labels (2.2.3.3).
  3.  The name of a list of parameter labels (2.2.3.2c), or an event label list (2.2.3.3).
  4.  The name of a Functional Resource type (2.2.3.2e), or a Functional Resource type (2.2.3.3).
  5.  The name of a specific Functional Resource instance (2.2.3.2d), or a Functional Resource Name (2.2.3.3).  (Page 1-8 of the CSTS SFW defines "Functional Resource Name" as "The unique identifier of an instance of a functional resource.  A Functional Resource Name is made of a Functional Resource Type and a Functional Resource Instance Number."
My comment:  (assuming that what I have said so far is correct) can we be consistent in the order that the possibilities are presented?  For example, this could be done by changing the following sentence in section 2.2.3.3 from:

"The START invocation may subscribe to notifiable events by using the names of events names, event labels, an event label list (named or default), a Functional Resource type, or a Functional Resource Name."

TO:

"The START invocation may subscribe to notifiable events by using the names of events names, event labels, an event label list (named or default), a Functional Resource Name, or a Functional Resource type."

Note:  Section 2.2.3.4 (Query of Parameters) matches section 2.2.3.3.  So if we change 2.2.3.3, we should make a corresponding change to 2.2.3.4.  (Or we could swap 2.2.3.2d and 2.2.3.2e, and avoid any need to change 2.2.3.3 and 2.2.3.4).

Best regards,
Tim

From: John Pietras <john.pietras at gst.com<mailto:john.pietras at gst.com>>
Date: Thursday, March 12, 2015 at 3:45 PM
To: SLE-CSTS <css-csts at mailman.ccsds.org<mailto:css-csts at mailman.ccsds.org>>
Subject: [Css-csts] Updated MD-CSTS and RID status document on CWE

CSTSWG colleagues ---
I have uploaded what I believe to be the final draft update of the MD-CSTS Red Book (MD-CSTS-922x1r1_2-150312) to the CWE in the Cross Support Services Area (CSS)<http://cwe.ccsds.org/css> > Documents<http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D> > CSS-CSTS<http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%2DCSTS&View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D> > CWE Private<http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%2DCSTS%2FCWE%20Private&View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D> > 2 - MD CSTS RED-1 Review material folder, at URL:
http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/2%20-%20MD%20CSTS%20RED-1%20Review%20material/MD-CSTS-922x1r1_2-150312.doc

This update includes all Red-1 Review RID resolutions, and is also in compliance with Wolfgang's current working draft of the CSTS SFW.

I have also uploaded to the same folder the complete set of MD-CSTS RID resolutions (MD-CSTS-Red1-Proposed_RID_Resolutions-150216), which have now been closed. The RID resolutions can be found at URL:
http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/2%20-%20MD%20CSTS%20RED-1%20Review%20material/MD-CSTS-Red1-Proposed_RID_Resolutions-150216.docx

I'm looking forward to seeing you in Pasadena.

Best regards,
John

________________________________

Spam<https://filter.gst.com/canit/b.php?i=01O6PEKGN&m=28a88c27811a&c=s>
Not spam<https://filter.gst.com/canit/b.php?i=01O6PEKGN&m=28a88c27811a&c=n>
Forget previous vote<https://filter.gst.com/canit/b.php?i=01O6PEKGN&m=28a88c27811a&c=f>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/css-csts/attachments/20150331/ab03e380/attachment.html>