<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 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:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Dear Mario,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’m mostly, but not entirely, and observer here, but I have to admit to being rather puzzled by what you are asking for. The 876.0-B-0 document that is being reviewed is a stand-alone, normative, document that should be reviewed on it’s
own merits. And this is a SOIS document, it really has nothing to do with MOIMS unless you want to make use of its features.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">What really puzzles me greatly is why you would include this quoted text from the draft SOIS Yellow Book that is also being held up in review? In that report, which is separate from this Blue Book, and as a report is not normative on anything,
those quoted bits of text are introduced by this:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Therefore it can be deduced that attempting to create a common core specification, which the two usages would then differently extend, would be unlikely to be a worthwhile exercise.<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:33.0pt">Instead, lessons learned from this analysis should be fed back into the corresponding specification development processes, in order to improve areas where either is lacking in capability or excessively complicated.
For EDS, these could include<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So the report basically says that there may be little merit in trying to create a common specification between these two separate bodies of work. It then suggests things that could be done, separately, to improve the SOIS EDS, and later,
to improve the MOIMS MAL. These are just suggestions, in a non-normative report.
<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">I really fail to understand why they would even be brought into this discussion of this SOIS Blue Book, to which they bear no direct relationship.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If MOIMS does see benefit in using the set of terms that SOIS has carefully defined I think that is great. There may even be future benefit to MOIMS in using the SOIS EDS to describe deployment architectures, but that too is future work.
I do think it would be useful to have separate discussions of just how those could occur. But it does not seem appropriate to hold up the approval of this existing document for some speculative future activity that no one has discussed adequately, let alone
agreed to.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Can you agree to allow this poll to proceed and to separately take up the subject of some joint effort to explore this subject of re-use of EDS and DoT terms?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Mario Merri <Mario.Merri@esa.int><br>
<b>Date: </b>Thursday, March 28, 2019 at 11:18 AM<br>
<b>To: </b>"Wilmot, Jonathan J. (GSFC-5820)" <jonathan.j.wilmot@nasa.gov><br>
<b>Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org>, Peter Shames <peter.m.shames@jpl.nasa.gov>, Tom Gannett <thomas.gannett@tgannett.net><br>
<b>Subject: </b>[EXTERNAL] Re: SOIS-APP responses to CCSDS 876x0-B-0 CESG Poll Conditions Feb-16-2019b<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">Dear Wilmot,</span>
<br>
<br>
<span style="font-family:"Arial",sans-serif">The use of standard SOIS DoT entries for MOIMS standards is reasonable, the two WGs should therefore commit to making sure this happens. However, the current draft YB also has recommendations on EDS that have nothing
to do with MOIMS, specifically:</span> <br>
<br>
<i><span style="font-family:"Arial",sans-serif">Instead, lessons learned from this analysis should be fed back into the corresponding specification development processes, in order to improve areas where either is lacking in capability or excessively complicated.
For EDS, these could include:</span></i> <br>
<i><span style="font-family:"Arial",sans-serif">– replacing the term ‘namespace’ with ‘area’, as that avoids confusion with XML namespaces;</span></i>
<br>
<i><span style="font-family:"Arial",sans-serif">– replacing the term ‘interface instance’ with ‘port’, for better compatibility with Universal Modelling Language (UML) 2.0, and avoiding the potential confusion between ‘interface definition’ and ‘interface
instance’;</span></i> <br>
<i><span style="font-family:"Arial",sans-serif">– replacing the ‘mode’ SYNC/ASYNC flag on parameters and commands with a Boolean value ‘oneway’, by analogy with Common Object Request Broker Architecture (CORBA); this avoids overloading the term ‘mode’, also
used for arguments.</span></i> <br>
<br>
<span style="font-family:"Arial",sans-serif">Have these been taken into account?</span>
<br>
<br>
<span style="font-family:"Arial",sans-serif">Thanks,</span> <br>
<br>
<span style="font-family:"Arial",sans-serif">__Mario</span> <br>
<br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Wilmot, Jonathan J. (GSFC-5820)" <jonathan.j.wilmot@nasa.gov></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Mario.Merri@esa.int" <Mario.Merri@esa.int>, "Shames, Peter M (JPL-312B)[Jet Propulsion Laboratory]" <peter.m.shames@jpl.nasa.gov></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"thomas.gannett@tgannett.net" <thomas.gannett@tgannett.net>, "cesg@mailman.ccsds.org" <cesg@mailman.ccsds.org></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">25/03/2019 21:06</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">SOIS-APP responses to CCSDS 876x0-B-0 CESG Poll Conditions Feb-16-2019b</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<o:p> </o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Dear Mario, Peter<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Please find attached the SOIS-APP WG responses to the CESG Poll conditions placed on publication of CCSDS 876.0-B-1, Spacecraft Onboard Interface Services—XML Specification for Electronic Data Sheets (Blue Book, Issue 1). Please respond with your agreement
or comments. <o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Kind regards,<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Jonathan<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Jonathan Wilmot<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
NASA/GSFC<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
CCSDS SOIS Area Director[attachment "CCSDS 876x0-B-0 CESG Conditions Feb-16-2019b.xlsx" deleted by Mario Merri/esoc/ESA]
<o:p></o:p></p>
<pre style="margin-left:.5in">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre style="margin-left:.5in">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre style="margin-left:.5in">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre style="margin-left:.5in">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).<o:p></o:p></pre>
</div>
</body>
</html>