<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Mario,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I am putting together a position paper on how XTCE and GOVSat should be handled by CCSDS. Both are OMG standards that will be formally approved very soon.
I would like to see them either be recognized as formal CCSDS standards (best approach) or, at a minimum, be posted on the CCSDS site and clearly referenced from the MOIMS web page area.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We have found the letter from the OMG lawyers from several years ago about working with CCSDS on this and we found the Peter Shames memo agreeing that taking
the OMG document and putting CCSDS intro material on it is acceptable.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I will attach these documents in my paper in January.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Dan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D">=========================<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Dan Smith<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D">NASA/GSFC<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Code 580<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Bldg 23, Room E443<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D">8800 Greenbelt Road<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Greenbelt, MD 20771<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D">301-286-2230<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Dan.Smith@nasa.gov<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> moims-sc-bounces@mailman.ccsds.org [mailto:moims-sc-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Mario.Merri@esa.int<br>
<b>Sent:</b> Wednesday, December 17, 2014 10:27 AM<br>
<b>To:</b> moims-sc@mailman.ccsds.org<br>
<b>Cc:</b> Mauro.Pecchioli@esa.int<br>
<b>Subject:</b> [Moims-sc] SM&C WG Action 141111-09: ESA XTCE Strategy<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Dear all,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">during the last CCSDS meeting, NASA stated that they would like to make GovSat (the NASA tailoring of XTCE) a CCSDS standard (not yet clear what book colour). They asked if we (ESA, Europe or both)
would like to do the same with XTCE-CC and I took an action on this. This email aims at answering to this action.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:blue">Action 141111-09 MM to check if the EGC-CC ICD based on XTCE could be published as it may be done for NASA/GovSat (i.e. directly in SANA). Due 31Dec14.</span>
<br>
<br>
<b><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Background</span></b>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">The ESA strategy on XTCE is to develop a tailoring of XTCE as the exchange format for the TM/TC information of the EGS-CC, the next generation European monitoring and control infrastructure. The
scope of the EGS-CC XTCE exchange format, XTCE-CC, has been restricted to the XTCE native scope (TM/TC general concepts without EGS-CC specific aspects) with a minimum set of extensions to ensure consistency of the mapping and data exchange, without changing
the semantics of the XTCE standard. In addition, the compatibility of XTCE-CC with the ISIS XTCE (XTCE tailoring by CNES) is being considered already for the production of the XTCE-CC. An ICD is being produced to define the XTCE-CC tailoring, with an annex
listing the deviations with respect to ISIS ICD, and how to handle them for compatibility.</span>
<br>
<br>
<b><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Response to Action</span></b>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">At the end of this exercise there will hopefully be a tailoring of XTCE, XTCE-CC, that is also compatible with the CNES ISIS. This tailoring could be a candidate for standardisation similarly as
the one done by NASA with GovSat. This will be known approximately mid 2015. It may also make sense to wait for the publication of XTCE1.2.</span>
<br>
<br>
<b><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Use Cases</span></b>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">A. European S/C and US MCS: Option 1: US MCS use XTCE-CC native; Option 2: European S/C generates GovSat; Option 3: A converter exists GovSat<->XTCE-CC</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">B. US S/C and European MCS: Option 1: European MCS use GovSat native; Option 2: US S/C generates XTCE-CC; Option 3: A converter exists GovSat<->XTCE-CC</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">C. Interoperability between ESA and CNES</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">D. Use either GovSat/XTCE-CC to exchange TM/TC info with other applications within the ground segment (e.g. MPS, SIM, FDS)</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Regards,</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">__Mario</span> <o:p>
</o:p></p>
<pre>This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre>content is not permitted.<o:p></o:p></pre>
<pre>If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Please consider the environment before printing this email.<o:p></o:p></pre>
</div>
</body>
</html>