<font size=2 face="sans-serif">Dear all,</font>
<br>
<br><font size=2 face="sans-serif">Please find below the IOAG responses
to the SC#1 comments raised by us.</font>
<br>
<br><font size=2 face="sans-serif">ciao</font>
<br><font size=2 face="sans-serif">nestor</font>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Nestor
Peccia/esoc/ESA on 05/10/2016 08:08 -----</font>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Gian Paolo Calzolari/esoc/ESA</font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Nestor Peccia/esoc/ESA@ESA</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"Adde, Barbara
(HQ-CG000)" <barbara.adde@nasa.gov>, "Jean-Marc Soula"
<Jean-Marc.Soula@cnes.fr>, Michael Schmidt/esoc/ESA@ESA</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">04/10/2016 23:20</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: Additional
comments on IOAG SC # 1</font>
<br>
<hr noshade>
<br>
<br><font size=2 face="sans-serif">Nestor,</font>
<br><font size=2 face="sans-serif"> here
the replies.</font>
<br><font size=2 face="sans-serif">Regards</font>
<br>
<br><font size=2 face="sans-serif">Gian Paolo & Jean Marc</font>
<br>
<br><font size=2 face="sans-serif">C: As reported at the Darmstadt meetings,
fall 2015, The CSSM Service Catalog will be a magenta book. </font>
<br><font size=2 face="sans-serif">R: It will be corrected in the next
version. It was blue in CWE when the catalog was prepared.</font>
<br>
<br><font size=2 face="sans-serif">C: Indeed. There is likely also
a need for ancillary management information. For example, some sort of
metadata to indicate radiation time and an ability to manage the file packets
itself should the mission decide that indeed these are not to be related
to the spacecraft etc.</font>
<br><font size=2 face="sans-serif">R: We do agree on the need for ancillary
management information. The text following the marked statement says in
fact "</font><font size=2 color=blue face="sans-serif">The ancillary
information and the reporting will be provided as part of Service Agreement,
and/or via Service Management services, and/or via a more ˇ§specializedˇ¨
file service (i.e. [FPFS]) and/or via metadata transferred with [CFXS].
As long as details on the [CFXS] and [FPFS] are not fully defined by CCSDS,
both standards are mentioned in this document</font><font size=2 face="sans-serif">."
</font>
<br><font size=2 face="sans-serif">Is this not sufficient to remark the
need for ancillary management information?</font>
<br>
<br><font size=2 face="sans-serif">C: Just curious as to why its listed
if it has been removed. Okay, but perhaps just the change log is
enough? </font>
<br><font size=2 face="sans-serif">R: The section was left there to avoid
heavy section renumbering with implied problems. Moreover the explicit
text would make easier the tracking for anybody looking for that service.</font>
<br>
<br><font size=2 face="sans-serif">C: There is probably additional metadata
needed here to indicate that the mapping for the creation of the file of
packets. For example, do packets of multiple APIDs map into one file or
are these separated into different files, etc. It strikes me that this
may be something to be considered at a higher level service catalog rather
than service catalog one. Although I did not make the remark for the forward
file of packets that may also hold as well in terms of proper service catalog
"home".</font>
<br><font size=2 face="sans-serif">R: Agreed. However the list is declared
to be incomplete as stated by the use of the formulation "e.g."
("This ancillary information is expected to include<b> e.g.</b> „Í
whether the file contains Space Packets or Encapsulation Packets....................".
Is there any need of remarking this more evidently? In general the details
are left to the CCSDS designers of the standard(s).</font>
<br>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Nestor Peccia/esoc/ESA</font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Michael Schmidt/esoc/ESA@ESA</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"Adde, Barbara
(HQ-CG000)" <barbara.adde@nasa.gov>, Gian Paolo Calzolari/esoc/ESA@ESA,
"Jean-Marc Soula" <Jean-Marc.Soula@cnes.fr></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">28/09/2016 11:46</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Additional comments
on IOAG SC # 1</font>
<br>
<hr noshade>
<br>
<br><font size=2 face="sans-serif">Michael</font>
<br>
<br><font size=2 face="sans-serif">Please find attached a marked-up SC
# 1 document including some additional comments from the CCSDS CSS Area
Chair</font>
<br>
<br><font size=2 face="sans-serif">[attachment "IOAG Service Catalog
One.v2.0-Approved-20160823-comments-eb-15-Sep-2016.pdf" deleted by
Gian Paolo Calzolari/esoc/ESA] </font>
<br>
<br><font size=2 face="sans-serif">ciao</font>
<br><font size=2 face="sans-serif">nestor</font>
<br>
<br>
<PRE>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.
</PRE>