<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 15 (filtered medium)">
<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:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@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: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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Georgia",serif;
color:windowtext;}
span.begin-antispam-voting-links
{mso-style-name:begin-antispam-voting-links;}
span.end-antispam-voting-links
{mso-style-name:end-antispam-voting-links;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Georgia",serif;
color:#1F497D;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:1329016740;
mso-list-type:hybrid;
mso-list-template-ids:-1562087656 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D">John,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D">It strikes me that the abstract header type (SchemaCssmSmInfoEntityHeader-v1_0_0.xsd) should have no target namespace and that when it is
included into a "payload" schema that we should in fact have a target namespace at that level. So that means that rather than declaring (in SchemaCssmSimpleSchedule-V1_0_0.xsd) "targetNamespace="urn:ccsds:schema:cssm:1.0.0” we should in fact do something like
"targetNamespace="urn:ccsds:schema:cssm:SSF:1.0.0” (assuming we still want to version the namespaces). It strikes me then that the status definition that is put in here is a restriction that is in the SSF sub namespace and that presumably the status coming
from, say the PIF, would be in the PIF namespace. <o:p></o:p></span></a></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D">I think this addresses Marcin’s concern and strikes me as being a fairly clean approach.
<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D">Best regards,<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D">-Erik
<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></span></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> John Pietras [mailto:john.pietras@gst.com] <br>
<b>Sent:</b> Thursday, July 20, 2017 4:05 AM<br>
<b>To:</b> Barkley, Erik J (3970) <erik.j.barkley@jpl.nasa.gov>; CCSDS Service Mgmt WG <smwg@mailman.ccsds.org><br>
<b>Subject:</b> RID SSF-R2-2, regarding the 'status' parameter<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">CSSMWG colleagues –<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">For what it’s worth, when I wrote the last draft (June 2016) of the Service Agreement and Configuration Profile book
<o:p></o:p></span></p>
<p class="MsoNormal">(<a href="http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Service%20Agreement%20and%20Configuration%20Profile%20Book/ServiceAgreementAndConfigProfile-902.5-W-0.5-160626.zip">http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Service%20Agreement%20and%20Configuration%20Profile%20Book/ServiceAgreementAndConfigProfile-902.5-W-0.5-160626.zip</a><span style="color:#1F497D">
)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">It was based on the common Service Management Header (SrvMgtHeader) class *<b>including</b>* the ‘status’ parameter, which was at the time cast simply as String32, not an Enumeration type as it is in the current
Simple Schedule book . The Service Agreement/Config Profile book constrained the string values to certain contents, but it did not redefine the base type (which is the issue in RID SSF-R2-2<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">The formulation of the ‘status’ parameter in this way - as a simple string type in the SrvMgtHeader base class in which the individual specifications would constrain the string contents to specific sets of strings
- was the result of discussions that we had on the exact topic that is the source of RID SSF-R2-2: how to avoid multiple definitions of the same element type (parameter) in the same namespace. Those discussions and the resulting decision to treat the ‘status’
parameter that way seem to have been forgotten in the intervening year or so.<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">NOTE 1 – We also discussed an approach in which we would keep the status parameter as an enumerated value, but pre-determine all of the possible values that all of the future services *<b>might</b>* use so as
to keep one definition of the type, but we concluded that that would counter the concept of “extensible”.<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">NOTE 2 – We recognized that casting the ‘status’ parameter as a simple String type would require application-level validation (i.e., above XML validation), but that an enumerated-value ‘status’ that contained
all possible values across all format books would still require application-level validation to ensure that the value is correct for correct for the given format.<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 if you want to keep things in the same namespace, I think that there are two possible solutions to the RID:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Return to the previous approach, in which the (simple) String-typed ‘status’ parameter belongs to the base SrvMgtHeader class, and each data format specified the allowed string value(s) for that format.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Adopt Marcin’s solution of creating a format-specific enumerated-value status type that has a unique name.<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 of course, creating separate namespaces (also as proposed by Marcin) would also solve this problem.<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">John<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"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<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 [<a href="mailto:smwg-bounces@mailman.ccsds.org">mailto:smwg-bounces@mailman.ccsds.org</a>]
<b>On Behalf Of </b>Barkley, Erik J (3970)<br>
<b>Sent:</b> Tuesday, July 18, 2017 7:03 PM<br>
<b>To:</b> CCSDS Service Mgmt WG<br>
<b>Subject:</b> [Smwg] Preliminary RID dispositions uploaded<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif">CSSM Colleagues,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif">Thank you to those of you who participated in the RID disposition session at today's teleconference. The dispositions that were recorded in the spreadsheet during our WebEx session
have been uploaded to the CWE and may be retrieved via the link below.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif">For those not at the teleconference, the goal is to have the final dispositions by August 1<sup>st</sup>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif"><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Schedule%20of%20Services/Red%20Book/Agency%20Review/Red-2/902.1-R-2-ConsolidatedRIDs-PrelimDispositions-18-July-2017.xlsx">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Schedule%20of%20Services/Red%20Book/Agency%20Review/Red-2/902.1-R-2-ConsolidatedRIDs-PrelimDispositions-18-July-2017.xlsx</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
</div>
</div>
</div>
</body>
</html>