<font size=2 face="sans-serif">Michele,</font>
<br>
<br><font size=2 face="sans-serif">I suggest we wait for the presentation
in Darmstadt and use the slot to discuss rather than exchanging emails.
I think most of what you are asking for (including format specification
and retrieval from the catalogue for each product) has already been taken
into account by the attached draft spec but I rather go through the points
during the meeting than explaining in email.</font>
<br><font size=2 face="sans-serif">It will help in the discussions, if
you find the time to read the spec before the meeting.</font>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br><font size=2 face="sans-serif">Mehran</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Michele Zundo"
<michele.zundo@esa.int></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">mehran.sarkarati@esa.int,
</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">moims-sc@mailman.ccsds.org</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">28/10/2015 09:58</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [Moims-sc]
MO Mission Data Product Distribution Services</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=3>Hi Mehran,</font>
<br>
<br><font size=3>thanks for the clarification. My interpretation was coming
primarily from the examples in the</font>
<br><font size=3>powerpoint from GMV, and not from the draft standard.</font>
<br><font size=3>For this we could then add some example of use based on
files like you explain below so that all type</font>
<br><font size=3>of users are catered for.</font>
<br>
<br><font size=3>Regarding the data format and my previous comments with
Dan, one important aspect when dealing </font>
<br><font size=3>with product is also to facilitate/allow the distribution/access
to product related metadata; when they </font>
<br><font size=3>are physically embedded into the data then it is not a
problem but when the metadata is separated and</font>
<br><font size=3>logically associated it is.</font>
<br>
<br><font size=3>The most important case of required metadata (but not
the only one) is the format specification/data-dictionary. </font>
<br><font size=3>So I would foresee the ability for service to support
request and distribution for any data of the</font>
<br><font size=3>relevant (user defined) formatspec files (regardless
of what they are).</font>
<br>
<br><font size=3>Michele</font>
<br>
<br>
<br>
<br>
<br><font size=3>On 27 Oct 2015, at 20:47 , </font><a href=mailto:mehran.sarkarati@esa.int><font size=3 color=blue><u>mehran.sarkarati@esa.int</u></font></a><font size=3>
wrote:</font>
<br>
<br><font size=3>Hi Michele,</font>
<br>
<br><font size=3>Mission data product is very generic and not limited at
all to M&C data products. It can be a TM timeline or an image or a
science data product, etc.</font>
<br>
<br><font size=3>The given products definitions are "examples"
from typical M&C area. Look at the service specifications, the concepts
and data types for product in the attached draft book and product definition
details and catalogue entry and you will see that the service is deliberately
kept generic to support any kind of data product distribution.</font>
<br><font size=3>The consumer can query to find which products are supported
in what format and from which source. It can then retrieve the product
definition and then send a req to get the product.</font>
<br>
<br><font size=3>Regards</font>
<br><font size=3>Mehran <br>
Sent from my iPhone</font>
<br><font size=3><br>
On 27.10.2015, at 16:28, Michele Zundo <</font><a href=mailto:michele.zundo@esa.int><font size=3 color=blue><u>michele.zundo@esa.int</u></font></a><font size=3>>
wrote:<br>
</font>
<br><font size=3>Dear Mehran,</font>
<br>
<br><font size=3>thanks for this.</font>
<br>
<br><font size=3>One high level comment regards the scope for such service,
which covers in </font>
<br><font size=3>your draft type of data coming from M&C type of systems
but leave out the</font>
<br><font size=3>“real” mission data, “<i>mission</i>" being the
end-product of the mission i.e. science products and related data</font>
<br><font size=3>either downloaded on payload link or produced by payload
data processing canters</font>
<br>
<br><font size=3>I believe that we should include in the scope of this
service not only TT&C TM (packets, parameters, etc)</font>
<br><font size=3>but also science and related data e.g. as formatted file
products (level 0, Level 1 etc). </font>
<br><font size=3>We have already working practice and formats description
standards and we</font>
<br><font size=3>should make sure that we define service in a generic way
so that we can support that</font>
<br><font size=3> as well.</font>
<br>
<br><font size=3>I can elaborate more during the meeting in November.</font>
<br>
<br><font size=3>Michele</font>
<br>
<br>
<br>
<br><font size=3>On 27 Oct 2015, at 12:36 , </font><a href=mailto:Mehran.Sarkarati@esa.int><font size=3 color=blue><u>Mehran.Sarkarati@esa.int</u></font></a><font size=3>
wrote:</font>
<br>
<br><font size=3><MDPDS.pptx></font>
<br>
<br><font size=1 face="Helvetica">-----------------------------------------</font>
<br><font size=1 face="Helvetica">Michele Zundo</font>
<br>
<br><font size=1 face="Helvetica">Head of Ground System Definition and
Verification Office</font>
<br><font size=1 face="Helvetica">EOP-PEP</font>
<br><font size=1 face="Helvetica">European Space Agency, ESTEC</font>
<br><font size=1 face="Helvetica">e-mail: </font><a href=mailto:michele.zundo@esa.int><font size=1 color=blue face="Helvetica"><u>michele.zundo@esa.int</u></font></a>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br><font size=1 face="Helvetica">-----------------------------------------</font>
<br><font size=1 face="Helvetica">Michele Zundo</font>
<br>
<br><font size=1 face="Helvetica">Head of Ground System Definition and
Verification Office</font>
<br><font size=1 face="Helvetica">EOP-PEP</font>
<br><font size=1 face="Helvetica">European Space Agency, ESTEC</font>
<br><font size=1 face="Helvetica">e-mail: </font><a href=mailto:michele.zundo@esa.int><font size=1 color=blue face="Helvetica"><u>michele.zundo@esa.int</u></font></a>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<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>