[Css-csts] RID NASA-JVP-22

[Yves.Doat at esa.int]

Dear John,

With the latest mail exchange and updates on the document, I consider that 
your RID is answered as follows:
GET operation updated
QualifiedParameter type makes use of the type ParameterOrListName (which 
in turn makes use of the fucntional resource identifier and parameter 
identifier)
Notification procedure reviewed and updated
Notification procedure reviewed and updated
Notification procedure reviewed and updated
event-names renamed event-identifier

I propose to close your RID.

Best regards
Yves



From:
"John Pietras" <john.pietras at gst.com>
To:
<Yves.Doat at esa.int>
Cc:
css-csts at mailman.ccsds.org
Date:
03/11/2011 15:13
Subject:
[Css-csts] RID NASA-JVP-22
Sent by:
css-csts-bounces at mailman.ccsds.org



Yves,
I have started to go through the RIDs marked ?IMPLEMENTED? in the last RID 
status package (201110 Framework RIDs.docm) to review the proposed 
closures for the remaining RIDs that I generated. The first such RID is 
NASA-JVP-22, which deals with explaining in the Concept sections how 
publishedIdentifiers are used for the Cyclic Report, Information Query, 
and Notification procedures. As a result of our discussion yesterday about 
using pairs of identifiers for monitored parameters and notifiable events, 
the Concept sections for the Cyclic Report, Information Query, and 
Notification procedures will have to be adjusted. Of course, the changes 
will also affect lower-level parameter and type definitions.
 
1.       In the GET operation, the list-of-parameters (of type 
ListOfParameters in the ASN.1) will have to be redefined. 
2.       The QualifiedParameter type (used by both the GET operation and 
the qualified-parameters parameter of the TRANSFER-DATA operation of the 
Cyclic Report procedure) will have to be changed.
3.       The  list-of-events parameter of the START operation of the 
Notification procedure will have to be redefined. 
4.       The NotificationNotifyNotificationTypeExt type has a component 
parameter eventName, currently defined to be of type VisibleString. This 
needs to be changed to carry either a VisibleString (in the case of the 
IndividualEventNames events) or the publishedIdentifer pair eventNames 
associated with the listOfEvents type.
5.       The NotificationNotifyNotificationTypeExt type has a component 
parameter eventValue, currently defined to be of type VisibleString. This 
supports the generalized extension related to listOfEvents, but what 
values does it take when the eventName is one of the string-valued 
IndividualEventNames?
6.       Finally, there is a typo in table 4-50: ?event-names? should be 
?event-name?.
 
I will update the Concepts section of the affected procedures, but I?d 
like to wait to do it until after the changed to the operations, types, 
etc., have been made so that I can be sure to align the text with those 
changes.
 
I will work through the rest of the NASA-JVP ?IMPLEMENTED? RIDs tonight.
 
Best regards,
John  _______________________________________________
Css-csts mailing list
Css-csts at mailman.ccsds.org
http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20111128/576714e7/attachment.html