[Css-csts] Re: prototypes updates
Fabienne.Delhaise at esa.int
Fabienne.Delhaise at esa.int
Wed Jul 31 10:28:19 EDT 2013
dear John et al.
>we have all agreed to add the option to ask for the Functional Resource Type
in the GET invocation list-of-parameters, Cyclic Report START invocation
list-of-parameters, and Notification START invocation list-of-events.
[Fabienne] this seems to me a good idea (by analogy with the decision taken
for parameter name and label)
>For the MD-CSTS, the derived Behavior specification will require that the
Provider send all parameters or events of *all* instance of that Functional
Resource Type _in the Service Package_.
[Fabienne] OK with me but can we mandate (i.e. force) the provider to
"clearly" specify the FR instance number which is associated to each returned
parameter. I would see a problem if all parameters or events values are
returned by the provider and the user could not differentiate which parameter
belongs to which FR instance number. Also the user should be be able to map
each FR instance number to the service production (e.g. "1" is RAF in X-band
and "2" is RAF in Ka band)
Best regards
Fabienne
From: John Pietras <john.pietras at gst.com>
To: "Margherita.di.Giulio at esa.int" <Margherita.di.Giulio at esa.int>, "Lassere Francois"
<Francois.Lassere at cnes.fr>
Cc: "css-csts at mailman.ccsds.org" <css-csts at mailman.ccsds.org>
Date: 31/07/2013 15:13
Subject: RE: [Css-csts] Re: prototypes updates
Sent by: css-csts-bounces at mailman.ccsds.org
Margherita,
Regarding the MD-CSTS, I will try to get the update on the CWE sometime next
week. I assume that we have all agreed to add the option to ask for the
Functional Resource Type in the GET invocation list-of-parameters, Cyclic
Report START invocation list-of-parameters, and Notification START invocation
list-of-events. When Functional Resource Type is used as the argument in
list-of-parameters or list-of-events (respectively), the standard behavior
will be that the Provider will send the values for all parameters or events
(respectively) of the single instance of that Functional Resource Type that
is associated with the CSTS that executes the procedure. This is the nominal
definition, and the gist of the last set of CSTS SFW modifications that I
sent to Yves.
For the MD-CSTS, the derived Behavior specification will require that the
Provider send all parameters or events of *all* instance of that Functional
Resource Type _in the Service Package_.
Best regards,
John
From: css-csts-bounces at mailman.ccsds.org [
mailto:css-csts-bounces at mailman.ccsds.org] On Behalf Of
Margherita.di.Giulio at esa.int
Sent: Wednesday, July 31, 2013 4:00 AM
To: Lassere Francois
Cc: css-csts at mailman.ccsds.org
Subject: [Css-csts] Re: prototypes updates
Dear Francois,
these are very good news!
Concerning the CSTS SFW version to use, you may have seen some exchanges of
e-mail between us (esoc) and John. The outcome of that brainstorming were few
more changes to the list of parameters and list of events, etc.
John has already entered the changes in the June version. In the next couple
of days Yves will finalise the book, and will upload it to the CWE. Yves will
notify the Working Group about it ( the version number - or name - will be
updated)
That version shall be seen as "the final version" for the Return Services.
(By the way, that version will be used for entering the material of the
Forward DPPs).
Please do use that version of CSTS SFW as baseline for the prototypes update
activity.
Concerning the MD Service, I would like to ask John by when he plans to
produce the new version that aligns to the new CSTS SFW.
Now, I would conclude that, if everything works fine, we will have the
finalised books (CSTS SFW RED-2 and MD CSTS RED-1 respectively) as well as
the prototypes by the end of the year !!!!
Kind regards,
Margherita
-------------------------------------------------------------
Margherita di Giulio
Ground Station Back-end Section (HSO-GIB)
European Space Agency ESA/ESOC
Robert-Bosch-Str. 5
D-64293 Darmstadt - Germany
Tel: +49-6151-902779
e-mail: Margherita.di.Giulio at esa.int
From: Lassere Francois <Francois.Lassere at cnes.fr>
To: "Margherita.di.Giulio at esa.int" <Margherita.di.Giulio at esa.int>
Cc: "css-csts at mailman.ccsds.org" <css-csts at mailman.ccsds.org>
Date: 30/07/2013 10:49
Subject: prototypes updates
Dear Margherita,
At the Bordeaux meetings I had presented the status of prototypes for the
framework and the provider part of the MD service :
(MoM of Bordeaux meeting : The development has to split into two parts
(budget). First phase will update the framework and the provider part of the
MD service(s). A second phase could provide (budget unclear) the MMI, which
is necessary to perform the actual validation and if necessary, final
updates.
In the worst case this will delay the implementation by a couple of month
until budget is available at the beginning of 2014.)
Today I can tell you that we have got budget to do all the work this year, so
the work final updates will begin by september/october and will be completed
by end of 2013. So far I think that the last version provided by Yves is the
June version, if no more modifications have been done we will work with this
version.
Best regards.
François
This message and any attachments are intended for the use of the addressee or
addressees only. The unauthorised disclosure, use, dissemination or copying
(either in whole or in part) of its content is not permitted. If you received
this message in error, please notify the sender and delete it from your
system. Emails can be altered and their integrity cannot be guaranteed by the
sender.
Please consider the environment before printing this email.
NOTE: This message was trained as non-spam. If this is wrong, please correct
the training as soon as possible.
Spam
Not spam
Forget previous vote_______________________________________________
Css-csts mailing list
Css-csts at mailman.ccsds.org
http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts
This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
More information about the Css-csts
mailing list