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

[Ray, Timothy J. (GSFC-5830)]

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/css-csts/attachments/20150323/45131c09/attachment.html>