[Css-csts] Updated CSTS SFW on CWE - labels

[John Pietras]

Yves,
As we discussed in the CSTSWG telecon earlier today, I have identified an number of places where the additional capability to use parameter and event labels needs to be documented. I have marked-up a copy of the SFW draft and uploaded it to the CWE at URL
http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/CSTS%20Framework%20and%20Concept/921x1r2%5BDraft%20201306%5D%20-%20Return%20Services-JVP.docx

In addition to enabling Word markup for additions and deletions, I have also flagged each of my changes with a comment balloon to differentiate my proposed changes from the others that were already in the document.

Following is a summary of the changes that I made. I also found a few typos, which I corrected.


1.       3.11.2.2.2.1, GET list-of-parameters: In some places the list-of-parameters is specified as containing a list of individual parameter names or labels, but here it is specified as containing a list of individual parameter names or a list of individual parameter labels. The difference is significant: in the first case, the list-of-parameters can contain a mix of names and labels, whereas in the second case it is restricted to contain all names or all labels. I recommend that the more-general mix be supported, which would require that 3.11.2.2.2.1 be reworded. I marked the section with a comment but I did not make the change myself.

2.       3.11.2.3.1(b), GET diagnostic: extends 'unknown parameter identifier' to also cover parameter identifiers carried in Parameter Labels.

3.       4.4.2.2, Information Query Concepts: addresses querying using individual parameter labels.

4.       4.7.2.2, Cyclic Report Concepts: completes the uses of parameter labels.

5.       4.7.3.1.3, Cyclic Report Starting Behavior: adds support for parameter labels.

6.       4.7.4.1.2.4, Cyclic Report START list-of-parameters: In some places the list-of-parameters is specified as containing a list of individual parameter names or labels, but here it is specified as containing a list of individual parameter names or a list of individual parameter labels. The difference is significant: in the first case, the list-of-parameters can contain a mix of names and labels, whereas in the second case it is restricted to contain all names or all labels. I recommend that the more-general mix be supported, which would require that 4.7.4.1.2.4 be reworded. I marked the section with a comment but I did not make the change myself.

7.       4.7.4.1.3.1(b), Cyclic Report START diagnostic: extends 'unknown parameter identifier' to also cover parameter identifiers carried in Parameter Labels.

8.       4.8.2.2, Notification Concepts: adds individual event labels.

9.       4.8.3.1.3, Notification Starting Behavior: adds support for event labels.

10.   4.8.3.2, Notification Notifying Occurrence of Events Behavior: New requirements added: (a) if an event name is used in the list-of-events, then the corresponding notification-type parameter must use the event name; (b) services and derived procedures must specify whether and under what conditions event names or labels can be used in notification-type parameters when the list-of-events contains an event label.

11.   4.8.4.1.2.2.2.2, Notification START list-of-events: add support for event labels.

12.   4.8.4.1.3(b), Notification START diagnostic: extends 'unknown parameter identifier' to also cover event identifiers carried in Event Labels.

13.   Annex B: New requirements added: (a) if a parameter name is used in the list-of-parameters, then the corresponding qualified parameter must use the parameter name; (b) services and derived procedures must specify whether and under what conditions parameter names or labels can be used in qualified parameters when the list-of-parameters contains a parameter label.

14.   E3.3, Common Types: extends the ListofParamEventsDiagnostics type to allow for labels to be returned for the unknownParamEventIdentifier choice.

Best regards,
John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20130619/2f9ad2f0/attachment.htm