<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:x="urn:schemas-microsoft-com:office:excel" 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:"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;}
/* 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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">CSTSWG and CSSMWG colleagues ---<o:p></o:p></p>
<p class="MsoNormal">The CSTS SFW defines (in section 3.4.2.2.7.2) the service-instance-identifier as comprising 4 components, one of which is “<span style="letter-spacing:-.3pt">the facility identifier as defined by the service package
</span><span style="letter-spacing:-.3pt;mso-fareast-language:FR">specified</span><span style="letter-spacing:-.3pt"> in references
</span><span style="mso-fareast-language:JA">[</span>2]<span style="letter-spacing:-.3pt"> and
</span>[1]<span style="letter-spacing:-.3pt">”, where reference 1 is the SC<i>CS SM Service Request and Service Package Data Formats</i> Recommended Standard that the CSSMWG is currently developing.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="letter-spacing:-.3pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="letter-spacing:-.3pt">As far as I know, we in the CSSMWG have not progressed the content of the book to specifically identify a “facility identifier”. However, the
<i>Simple Schedule Format</i> book that is working its way through CESG and CMC approval for Red-1 release
<i>does</i> define a s<b>tationRef</b> parameter (defined as “</span>The ground station or relay satellite to which the scheduled activity applies”)
<span style="letter-spacing:-.3pt"> that appears to contain the same type of identification intended by the CSTS SFW’s facility identifier. So in SM we have adopted the concept of associating the delivery of services with a specific facility or station. We
in the CSSMWG need to make sure that this identification is also present in the Service Package format (schema) defined in the SC<i>CS SM Service Request and Service Package Data Formats</i> Blue Book.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="letter-spacing:-.3pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="letter-spacing:-.3pt">Assuming that will happen, I recommend that we adopt a common term across all three books (CSTS SFW, Simple Schedule, and Service Request/Service Package). As noted above, CSTS SFW uses ‘facility identifier”
and the Simple Schedule book uses “stationRef”. I personally don’t have any preference for one or the other, just a belief that a single name should be used for simplicity and clarity.
<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">John<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>