<span style=" font-size:11pt;font-family:Arial">Dear Peter,</span>
<br>
<br><span style=" font-size:11pt;font-family:Arial">these recommendations
have been made and they are sensible recommendations relevant to the document
under poll. I am just asking to the SOIS what they are going to do about
them in this context. It is not clear to me why do you have to answer on
their behalf.</span>
<br>
<br><span style=" font-size:11pt;font-family:Arial">Regards,</span>
<br>
<br><span style=" font-size:11pt;font-family:Arial">__Mario</span>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">"Shames,
Peter M (312B)" <peter.m.shames@jpl.nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">"Mario.Merri@esa.int"
<Mario.Merri@esa.int>, "Wilmot, Jonathan J. (GSFC-5820)"
<jonathan.j.wilmot@nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">"cesg@mailman.ccsds.org"
<cesg@mailman.ccsds.org>, "thomas.gannett@tgannett.net"
<thomas.gannett@tgannett.net></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">28/03/2019
23:39</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">Re:
[EXTERNAL] Re: SOIS-APP responses to CCSDS 876x0-B-0 CESG Poll Conditions
Feb-16-2019b</span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Dear
Mario,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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>
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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. </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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?</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Thanks,
Peter</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"><b>From:
</b>Mario Merri <Mario.Merri@esa.int><b><br>
Date: </b>Thursday, March 28, 2019 at 11:18 AM<b><br>
To: </b>"Wilmot, Jonathan J. (GSFC-5820)" <jonathan.j.wilmot@nasa.gov><b><br>
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><b><br>
Subject: </b>[EXTERNAL] Re: SOIS-APP responses to CCSDS 876x0-B-0 CESG
Poll Conditions Feb-16-2019b</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Arial">Dear
Wilmot,</span><span style=" font-size:11pt;font-family:Calibri"> <br>
</span><span style=" font-size:11pt;font-family:Arial"><br>
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><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:11pt;font-family:Arial"><i><br>
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:</i></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:11pt;font-family:Arial"><i><br>
– replacing the term ‘namespace’ with ‘area’, as that
avoids confusion with XML namespaces;</i></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:11pt;font-family:Arial"><i><br>
– 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’;</i></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:11pt;font-family:Arial"><i><br>
– 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.</i></span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:11pt;font-family:Arial"><br>
Have these been taken into account?</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:11pt;font-family:Arial"><br>
Thanks,</span><span style=" font-size:11pt;font-family:Calibri"> <br>
</span><span style=" font-size:11pt;font-family:Arial"><br>
__Mario</span><span style=" font-size:11pt;font-family:Calibri"> <br>
<br>
<br>
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
From: </span><span style=" font-size:9pt;font-family:Arial">"Wilmot,
Jonathan J. (GSFC-5820)" <jonathan.j.wilmot@nasa.gov></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
To: </span><span style=" font-size:9pt;font-family:Arial">"Mario.Merri@esa.int"
<Mario.Merri@esa.int>, "Shames, Peter M (JPL-312B)[Jet Propulsion
Laboratory]" <peter.m.shames@jpl.nasa.gov></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Cc: </span><span style=" font-size:9pt;font-family:Arial">"thomas.gannett@tgannett.net"
<thomas.gannett@tgannett.net>, "cesg@mailman.ccsds.org"
<cesg@mailman.ccsds.org></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Date: </span><span style=" font-size:9pt;font-family:Arial">25/03/2019
21:06</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Subject: </span><span style=" font-size:9pt;font-family:Arial">SOIS-APP
responses to CCSDS 876x0-B-0 CESG Poll Conditions Feb-16-2019b</span><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<div align=center>
<hr noshade></div>
<p style="margin-top:0px;margin-Bottom:240px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">Dear
Mario, Peter</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">
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. </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt">
Kind regards,</span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt">
Jonathan</span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt">Jonathan Wilmot</span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt">NASA/GSFC</span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt">CCSDS SOIS
Area Director[attachment "CCSDS 876x0-B-0 CESG Conditions Feb-16-2019b.xlsx"
deleted by Mario Merri/esoc/ESA] </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">This
message is intended only for the recipient(s) named above. It may contain
proprietary information and/or</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">protected
content. Any unauthorised disclosure, use, retention or dissemination is
prohibited. If you have received</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">this
e-mail in error, please notify the sender immediately. ESA applies appropriate
organisational measures to protect</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">personal
data, in case of data privacy queries, please contact the ESA Data Protection
Officer (dpo@esa.int).</span></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p><PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE>