<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1209144319;
mso-list-type:hybrid;
mso-list-template-ids:-748640858 -830674704 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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"><span style="color:#1F497D">Dear Wes and SMWG,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I assume when you write about <i>
servicePackageType</i> you actually mean <i>servicePackageSatus</i> (otherwise I can’t find any mention of
<i>servicePackageType</i> in the current white book).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">We also said, that eventually the
<i>servicePackageStatus</i> should be rather called <i>servicePackageState</i>, which however would imply actually state machine behind. As we said, this won’t however be formalized for time being, therefore
<i>servicePackageStatus</i> could stay as it is.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Now to the main issue: I agree, in case the only states would be SCHEDULED and ALTERNATIVE there is no much sense in having something else than activeScenario flag. Here is to note, however, in case the scenarios
are not being used at all for specific case, than there is no other way of conveying the status (which is than apparently the only “SCHEDULED”). Here we come actually to my main question: are we than imply, that as soon the Service Package exists, it is immediately
SCHEDULED? This may be appealing for the simplicity, but it does not correspond to the real life right now. I think everybody has in their scheduling systems some notion of the state or status of the request or pass or service or whatever. And they are being
somehow “requested”, later on are “planned” and/or firmly “booked”, than are being “executed” to get finally “done”. Whatever we do in CCSDS (if it will be state machine or some other mechanism) we need (in my opinion) to reflect such states/statuses.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Getting back to the state machine a bit, the question (again) is, when the Service Package actually comes into life? I remember some discussion where we’ve said, the Service Package actually pops up already when
the request is being initially processed. This was the time, when we decided to work on the state machine (-ish) to exactly check how the Service Package actually behaves. Therefore (despite of future continuing work on that), I’d say we have currently 8 states/statuses:
CREATED, SCHEDULED, REJECTED, CANCELLED, ABORTED, ARCHIVED, EXECUTING and ALTERNATIVE. What eventually comes to my mind is to actually scratch the ALTERNATIVE status, because it is truly covered by
<i>ScenarioDetails</i> class and <i>activeScenario</i> parameter.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">And finally, because we need to support the user’s notion of
<b>pass/contact/service/schedule/request*</b> status, the same time however are not yet so far to provide consistent state machine model or automation services which would such model support,
<u>I’d vote for keeping the <i>servicePackageStatus</i> as optional parameter with data type set to string,</u> allowing in early implementation phases to bilaterally agree between user and provider how this field is being used.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph"><i><span style="font-size:9.0pt;color:#1F497D">*I intentionally use all these terms as synonyms, because the currently in the world used definitions are not clear, and being used randomly – users asking “what is the status of my
request” often expect to hear “it is scheduled” or “is being executed” – ergo unconsciously they actually ask for status of the service or, in our terms, Service Package.
<o:p></o:p></span></i></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Except that, I saw you changed the
<i>servicePkgStatus</i> into <i>servicePkgUsage</i>, which I think nicely now differentiates to the status itself. I like it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Marcin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<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""> SMWG [mailto:smwg-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Eddy, Wesley M. (GRC-LCN0)[MTI SYSTEMS, INC.] via SMWG<br>
<b>Sent:</b> Dienstag, 20. November 2018 19:04<br>
<b>To:</b> smwg@mailman.ccsds.org<br>
<b>Subject:</b> [Smwg] SPDF: second WG review<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello, as discussed in today’s meeting, there is an updated SPDF book ready for the 2<sup>nd</sup> working group review:<o:p></o:p></p>
<p class="MsoNormal"><a href="https://cwe.ccsds.org/css/_layouts/15/WopiFrame.aspx?sourcedoc=/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Service%20Package%20Data%20Formats/White%20Book/Drafts/ServicePackageSpecification%20902.4-w0.02.docx&action=default">https://cwe.ccsds.org/css/_layouts/15/WopiFrame.aspx?sourcedoc=/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Service%20Package%20Data%20Formats/White%20Book/Drafts/ServicePackageSpecification%20902.4-w0.02.docx&action=default</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">The question we discussed in the meeting is:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:#1F497D">-</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">Right now, we have both:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt"><span style="font-family:"Courier New";color:#1F497D">o</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">a servicePackageType that is OPTIONAL indicating the state machine status (which right now is just whether the package is primary/active/scheduled or an alternate)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt"><span style="font-family:"Courier New";color:#1F497D">o</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">within the OPTIONAL ScenarioDetails, there is an activeScenario boolean that indicates the same thing<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:#1F497D">-</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">If we don’t have any additional state machine states that are conveyed, then the activeScenario is better placed because the distinction between scheduled vs alternative is only relevant when using scenarios, in which case
ScenarioDetails (and activeScenario) is present.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:#1F497D">-</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">I think the servicePackageType is only useful to retain if there are additional sub-states that it would indicate, but from what I could tell in the examples Marcin worked with the group, I wasn’t sure that we had any. Marcin
had some other states like ‘CREATED’, etc., that I think were internal, and wouldn’t be relevant to the message exchanges, if I understood correct.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">So, I think the options are:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:#1F497D">1.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">Get rid of servicePackageStatus. </span><span style="color:#ED7D31">(this did not seem to be preferred in the meeting, and there might be uses for conveying states in the future)</span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:#1F497D">2.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">Define other states in the enumeration for servicePackageStatus, or leave it open to take some additional TBD states (e.g. by making it an xsd:string rather than an enumeration). </span><span style="color:#ED7D31">(this seems
slightly preferable at the moment?)</span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:#1F497D">3.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">Leave it alone under the assumption that there will be more states we think of later that we want the servicePackageStatus to be able to convey and that we’ll add them to the enumeration at some point in the future?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Other than this, I will also update the XML schema file and post that as well.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
</div>
</body>
</html>