<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">SMWG colleagues ---<o:p></o:p></p>
<p class="MsoNormal">In Gaithersburg one of the things that we discussed with respect to the Configuration Profiles work was the addition of a “user friendly” “nickname” for Functional Resource (FR) instances. Formally, FR Instances are named in terms of the
combination of the FR Type (an Object Identifier (OID)) and the FR Instance Number (FRIN). It was pointed out that using OIDs and numerical indices to identify FR instances is not very “user friendly”. In response to this observation, I am adding the
<span style="font-family:"Courier New"">frNickname</span> parameter to the <i><span style="font-family:"Courier New"">FunctionalResource</span></i> abstract class. The frNickname parameters will be populated by the Mission, using names that are most meaningful
to that Mission. E.g., Forward401SpaceLinkCarrierTransmission FR instance #2 could be assigned the frNickname “X—band transmitter”.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Similarly, the parameters are formally identified by OIDs which are equally “unfriendly” to human eyes. Fortunately, in the case of the parameters, each parameter is also formally assigned a string-valued
<i>classifier</i> (it is the classifiers that appear as the “names” of the parameters in the Space Link Service Profiles and Configuration Profiles).
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I bring this up now because it will impact the SMURF book.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In order for these nicknames and classifiers to be most useful for SM purposes, they should also be usable in Service Package Requests, Service Package Results, and (presumably) in Event Sequences. Putting them into Event Sequences should
be relatively easy, since the details of those data structures have yet to be worked out. They will also be available by default in Service Package Results since the nicknames will just be an additional parameter of each FR instance that is reported back in
verbose mode, and the classifier is an attribute of each parameter.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This leaves the SMURF Service Package Request. In this case, the nicknames would come into play when respecifying the values of configuration parameters. This is done using the objects (instantiations) of the OIDParameter class. Per the
current SMURF, the FR instances are identified using the frType and frInstanceNumber parameters of the OIDParameter class. The frNickname should be able to be used instead of the frType:frInstanceNumber combination to identify the FR instance. One possible
way to do this would be to replace the current individual frType and frInstanceNumber parameters with a single frName parameter of complex type FrName:<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:blue"><o:p> </o:p></span></p>
<p class="MsoNormal"><img width="472" height="173" id="Picture_x0020_2" src="cid:image002.png@01D3E394.863EBD80"><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Similarly, instead of the OIDParameter class offering the OID-valued parameterId parameter as the only way of “naming” the parameter to be respecified, the classifier should be able to be reused instead. Again, since this would be an either/or
situation, a choice-valued parameter of type FrParameterNameType could be used instead of the current parameterId:<o:p></o:p></p>
<p class="MsoNormal"><img width="378" height="123" id="Picture_x0020_3" src="cid:image001.png@01D3E394.EEB6D1E0"><o:p></o:p></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>
</div>
</body>
</html>