<span style=" font-size:10pt;font-family:sans-serif">Hello<br>
</span>
<br><span style=" font-size:10pt;font-family:sans-serif">I have implemented
SMURF w0.19 generation on our system (EMSP) limited to booking <b>request</b>,
<b>replace </b>and <b>delete</b>, and validated them against the xsd.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Here are my findings<br>
</span>
<br><span style=" font-size:10pt;font-family:sans-serif"><b><u>Syntax:</u></b></span>
<br>
<br><span style=" font-size:9pt;font-family:Default MultiLingual"><b>1)
srvPkgRef </b>is </span><span style=" font-size:9pt;color:#800000;font-family:Default MultiLingual">attribute
</span><span style=" font-size:9pt;font-family:Default MultiLingual">for
<b>replaceSrvPkg</b>, and </span><span style=" font-size:9pt;color:#800000;font-family:Default MultiLingual">element
</span><span style=" font-size:9pt;font-family:Default MultiLingual">for
<b>deleteSrvPkg</b>. Any reason why ?</span>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">It has
also different upper/lower case for the first S : <b>srvPkgRef </b>is
attribute for replace, and (S upercase </span><span style=" font-size:9pt;color:red;font-family:Default MultiLingual"><b>S</b></span><span style=" font-size:9pt;font-family:Default MultiLingual"><b>rvPkgRef</b>),
element for delete. </span>
<br>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">2) I
can see</span>
<ul>
<li><span style=" font-size:9pt;font-family:Default MultiLingual">newOnlineSrvPkgReq</span>
<li><span style=" font-size:9pt;font-family:Default MultiLingual">replaceOnlineSrvPkgReq</span></ul>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">But no
</span><span style=" font-size:9pt;color:red;font-family:Default MultiLingual"><b>deleteOnlineSrvPkgReq</b></span><span style=" font-size:9pt;font-family:Default MultiLingual">.
Shall we use </span><span style=" font-size:9pt;color:blue;font-family:Default MultiLingual"><b>deleteSrvPkg
</b></span><span style=" font-size:9pt;font-family:Default MultiLingual">instead
?</span>
<br>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">3) What
about <b>replaceOnlineSrvPkgReq </b>vs <b>replaceSrvPkg</b> ?</span>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">May be
an answer to point 2). I was not able to implement <b>replaceOnlineSrvPkgReq</b>.
I din't find how to incorporate new times parameters in a way which validates
against the xsd.</span>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">I have
use <b>replaceSrvPkg</b> instead.</span>
<br>
<br><span style=" font-size:9pt;font-family:Default MultiLingual"><b><u>XSD</u></b></span>
<br>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">SANA
xsd import via hmtl link doesn't work for me. I had to download the file
onto my system and edit the xsd to remove the html link.</span>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">e.g.
</span>
<br><span style=" font-size:9pt;font-family:Default MultiLingual"><xsd:include
schemaLocation="</span><a href="https://sanaregistry.org/r/ndmxml_qualified/ndmxml-2.0.0-master-2.0.xsd"><span style=" font-size:9pt;color:blue;font-family:Default MultiLingual">https://sanaregistry.org/r/ndmxml_qualified/ndmxml-2.0.0-master-2.0.xsd</span></a><span style=" font-size:9pt;font-family:Default MultiLingual">"/>
can not be found</span>
<br>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif"><b><u>Looking
at the example provided</u></b></span>
<br>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">Contains
absolute times. It needs to be updated for each support, and in case the
support track times are modified, it becomes invalid.</span>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">Time
should be offset relative to the of start/end of the service package.</span>
<br>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">Anyway,
Absolute Time format shall be Time format B instead of </span>
<br><span style=" font-size:11pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;color:#000080;font-family:Verdana"><startTime></span>
<br><span style=" font-size:11pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;color:#000080;font-family:Verdana"><year</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">
</span><span style=" font-size:10pt;color:#008080;font-family:Verdana">value</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">="2020"</span><span style=" font-size:10pt;color:#000080;font-family:Verdana">/></span>
<br><span style=" font-size:11pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;color:#000080;font-family:Verdana"><dayOfYear</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">
</span><span style=" font-size:10pt;color:#008080;font-family:Verdana">value</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">="184"</span><span style=" font-size:10pt;color:#000080;font-family:Verdana">/></span>
<br><span style=" font-size:11pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;color:#000080;font-family:Verdana"><hourOfDay</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">
</span><span style=" font-size:10pt;color:#008080;font-family:Verdana">value</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">="11"</span><span style=" font-size:10pt;color:#000080;font-family:Verdana">/></span>
<br><span style=" font-size:11pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;color:#000080;font-family:Verdana"><minuteOfHour</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">
</span><span style=" font-size:10pt;color:#008080;font-family:Verdana">value</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">="20"</span><span style=" font-size:10pt;color:#000080;font-family:Verdana">/></span>
<br><span style=" font-size:11pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;color:#000080;font-family:Verdana"><secondOfMinute</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">
</span><span style=" font-size:10pt;color:#008080;font-family:Verdana">value</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">="30"</span><span style=" font-size:10pt;color:#000080;font-family:Verdana">/></span>
<br><span style=" font-size:11pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;color:#000080;font-family:Verdana"></startTime></span>
<br>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif"><b><u>Philosophical:</u></b></span>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">Unnecessary
verbose and complex.But I suppose this is CCSDS trademark.</span>
<br>
<br>
<br>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">So many
options will never be implemented by any single network.</span>
<br>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">The approach
of keeping items to accomodate very specific needs will result in a non-standard
usage of the standard. </span>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">Each
network will implement its own concept in the background. </span>
<br>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">I have
a strong preference to standardise only concept currently supported by
ALL network (or at least a majority). Everything else shall be covered
by "extended parameters".</span>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">But as
time is running short, I will not object to go for agency review with the
current version.</span>
<br>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">I now
it has been agreed that <b>preferredDuration </b>is now an <b>unsignedInt
</b>instead of a <b>ISO duration</b>, but I still have a bad feeling of
going away from existing standard.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif"><br>
Regards<br>
________________________________________<br>
Martin UNAL<br>
Ground Operation Manager<br>
Ground Facilities Ops HSO - ONO<br>
H-376<br>
ESOC<br>
Robert-Bosch Strasse 5<br>
64 293 Darmstadt<br>
Germany<br>
Tel +49 6151 90 2959 <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">"Barkley,
Erik J\(US 3970\) via SMWG" <smwg@mailman.ccsds.org></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></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">"CCSDS
Service Mgmt WG" <smwg@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">10/02/2022
23:40</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">[cssm]
Review comments on the SMURF</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by: </span><span style=" font-size:9pt;font-family:sans-serif">"SMWG"
<smwg-bounces@mailman.ccsds.org></span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia">Dear
Colin,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia">Attached
please find my comments on the SMURF draft recommended standard. Overall
this is quite an impressive document and I think it is very close to being
ready for agency review. Here is a summary of the more significant comments:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia"> </span></p>
<br><span style=" font-size:10pt;font-family:sans-serif">1.
</span><span style=" font-size:11pt;font-family:Georgia">I
think there is still some cleanup needed with regard to removal of the
request for accounting report. Here and there it is still referenced but
the main UML diagram and the report request UML specific diagrams have
the accounting report removed which I think is just fine given that we
are quite unlikely to produce any kind of definition for a standardized
accountability report anytime soon.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">2.
</span><span style=" font-size:11pt;font-family:Georgia">There
is still some leftover stuff with regard to the scenario sets which I think
we all agreed we are not putting in the book so a bit of cleanup is needed
there.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">3.
</span><span style=" font-size:11pt;font-family:Georgia">For
a few of the parameter descriptions there are essentially usage consideration
notes rather than a direct description of the parameter itself. It strikes
me that we could either collect these notes in a usage considerations Annex
or move the note like material in the description into specific notes about
usage consideration where this occurs (i.e. essentially in line with the
parameter table entry). In either case, I think this then would make the
description entries more in line with CCSDS "terse style" pedantic
as it may be.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">4.
</span><span style=" font-size:11pt;font-family:Georgia">Optional
use of start and end times for requests seems odd to me – for example,
a request for communication geometry (Communications Planning Information
Format) seems like it would have to be bounded in time. This might
need further explanation if these values are optional and/or perhaps they
should be mandatory?</span>
<br><span style=" font-size:10pt;font-family:sans-serif">5.
</span><span style=" font-size:11pt;font-family:Georgia">Location
of the XML Instance examples: the CPIF calls out the github repository
directly; I am okay with the a SANA GitHub repository registry as indicated
by the SMURF, but if we are to do that I think we need to add a description
of the registry (simple though it may be) and start working with the SANA
guys to get it into place. </span>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia">Well,
that’s it. What do you think? </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia">Best
regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia">-Erik[attachment
"902x9w0_19 - ServiceManagementUtilizationRequestFormats-eb.doc"
deleted by Martin Unal/esoc/ESA] </span><tt><span style=" font-size:10pt">_______________________________________________<br>
SMWG mailing list<br>
SMWG@mailman.ccsds.org<br>
</span></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/smwg"><tt><span style=" font-size:10pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/smwg</span></tt></a><tt><span style=" font-size:10pt"><br>
</span></tt></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>