<span style=" font-size:10pt;font-family:sans-serif">Hi Wes,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">   
            yes that would make sense, if
srvPkgReqVersion is removed from the SMURF request there is no sensible
way in which it could be used in the SPDF.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Cheers for now,</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Colin</span>
<br><span style=" font-size:10pt;font-family:sans-serif"><br>
<br>
---------------------------------------------------------------------------------------------------------<br>
Dr. Colin R. Haddow,<br>
HSO-GI, European Space Agency,<br>
European Space Operations Centre,<br>
Robert-Bosch-Str 5,<br>
64293 Darmstadt,<br>
Germany.<br>
<br>
Phone; +49 6151 90 2896<br>
Fax;      +49 6151 90 3010<br>
E-Mail;  colin.haddow@esa.int<br>
---------------------------------------------------------------------------------------------------------<br>
</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">"Eddy,
Wesley M. (GSFC-580.0)[MTI SYSTEMS, INC.]" <wesley.m.eddy@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">"Colin.Haddow@esa.int"
<Colin.Haddow@esa.int>, "CCSDS Service Mgmt WG" <smwg@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
       </span><span style=" font-size:9pt;font-family:sans-serif">"Wolfgang.Frase@dlr.de"
<Wolfgang.Frase@dlr.de></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
       </span><span style=" font-size:9pt;font-family:sans-serif">22/07/2021
14:56</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] [cssm] Updates:- Service Management Common data Entities Book,
SMURF Book, UML Model, XML Schema.</span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">On
the point below about srvPkgReqVersion, I think we would additionally remove
the corresponding serviceReqVersion attribute from the ServicePkgBody in
the SPDF.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:</b>
SMWG <smwg-bounces@mailman.ccsds.org> <b>On Behalf Of </b>Colin.Haddow@esa.int<b><br>
Sent:</b> Thursday, July 22, 2021 5:55 AM<b><br>
To:</b> CCSDS Service Mgmt WG <smwg@mailman.ccsds.org><b><br>
Cc:</b> Wolfgang.Frase@dlr.de<b><br>
Subject:</b> [EXTERNAL] [cssm] Updates:- Service Management Common data
Entities Book, SMURF Book, UML Model, XML Schema.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#004080;font-family:Arial">…</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
One point for discussion at the next telecon. At the last telecon (13/07/2021)
we agreed to make the srvPkgReqVersion parameter of the ServicePkgReq class
in the SMURF optional. On going through Marcins notes from the SMURF prototyping
test report I found that Marcin, Anthony and I had discussed deleting this
parameter completely. I think that this is actually a better solution and
recommend, unless someone has got a really good reason for keeping it,
that we delete the srvPkgReqVersion parameter.</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
<br>
</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>