<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: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;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
/* 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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Georgia","serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Georgia","serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle24
{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;}
--></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">Hi,<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">Short drop from my side:<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 think as long we can distinguish these parameters and we explain in the Blue Book what for they are good, than we are fine. So if we call them “Modified” I’m fine…<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">Btw. the consideration between respecified and dynamically assigned (both came I believe from John) came from the point of view, where the parameter is respecified only once during service lifetime, and implying
them being already specified, whereas some parameters may be dynamically assigned multiple times during the service lifetime and also meaning previously not necessarily set. Anyhow, as Erik correctly mentioned, these is nerd’s talk ;-).<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">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>Barkley, Erik J (3970)<br>
<b>Sent:</b> Freitag, 21. September 2018 22:02<br>
<b>To:</b> Eddy, Wesley M. (GRC-LCN0)[MTI SYSTEMS, INC.]; CCSDS Service Mgmt WG<br>
<b>Subject:</b> Re: [Smwg] terminology "respecified" versus "dynamically assigned"<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";color:#1F497D">Hi Wes, that works for me.
<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"><span style="font-size:12.0pt;font-family:"Georgia","serif";color:#1F497D">-Erik
<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>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> SMWG <<a href="mailto:smwg-bounces@mailman.ccsds.org">smwg-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b>Eddy, Wesley M. (GRC-LCN0)[MTI SYSTEMS, INC.]<br>
<b>Sent:</b> Friday, September 21, 2018 12:52<br>
<b>To:</b> Barkley, Erik J (3970) <<a href="mailto:Erik.J.Barkley@jpl.nasa.gov">Erik.J.Barkley@jpl.nasa.gov</a>>; CCSDS Service Mgmt WG <<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>><br>
<b>Subject:</b> Re: [Smwg] terminology "respecified" versus "dynamically assigned"<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks Erik, that makes sense to me. Would “ModifiedParameter” be an agreeable thing to call these in the UML and schema?<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 #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> Barkley, Erik J (3970) <<a href="mailto:Erik.J.Barkley@jpl.nasa.gov">Erik.J.Barkley@jpl.nasa.gov</a>>
<br>
<b>Sent:</b> Friday, September 21, 2018 3:05 PM<br>
<b>To:</b> Eddy, Wesley M. (GRC-LCN0)[MTI SYSTEMS, INC.] <<a href="mailto:wesley.m.eddy@nasa.gov">wesley.m.eddy@nasa.gov</a>>; CCSDS Service Mgmt WG <<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>><br>
<b>Subject:</b> RE: terminology "respecified" versus "dynamically assigned"<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia","serif";color:#1F497D">Hi Wes,<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"><span style="font-size:12.0pt;font-family:"Georgia","serif";color:#1F497D">Related to terminology – I just want to note that the OIDs are still in the picture – rather that we are looking at using the “common” name (I believe John has labeled
this the “nickname” in the FRM). I agree that it’s not the 1.2.3.4.5.7.etc numbering being used, but technically, the object is being identified.
<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"><span style="font-size:12.0pt;font-family:"Georgia","serif";color:#1F497D">Okay, onto the main event :-) I think both dynamically assigned and re-specification etc. smack a little too much of computer science. From a software engineering
perspective of course these are just fine terms. But I think the use case here is that these are configuration parameters for this specific service package instance. So my thinking would be to go along the lines of something like "modified configuration parameters"
-- I think that gets a little closer to the day-to-day usage envisioned.<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"><span style="font-size:12.0pt;font-family:"Georgia","serif";color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia","serif";color:#1F497D">-Erik<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>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> SMWG <<a href="mailto:smwg-bounces@mailman.ccsds.org">smwg-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b>Eddy, Wesley M. (GRC-LCN0)[MTI SYSTEMS, INC.]<br>
<b>Sent:</b> Thursday, September 20, 2018 12:17<br>
<b>To:</b> CCSDS Service Mgmt WG <<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>><br>
<b>Subject:</b> [Smwg] terminology "respecified" versus "dynamically assigned"<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello, in the course of moving away from using OIDs to indicate the respecified parameter values in the Service Package, there are a couple different alternative terms that people suggested that would replace the “OIDParameter” in the service
package class description and schema.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Initially, John suggested “RespecificationParameter”. This sounds good to me. It’s what I’ve currently used in the latest draft of the book and XML schema description.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">However, I found some meeting notes I’d jotted down that indicate someone had also suggested “dynamically assigned” as the terminology we could use. I didn’t capture the rationale, but I believe it might have been because the terminology
of respecifiable parameters is rooted in the legacy SN messaging, so we wanted to distinguish the new standard from that, while having equivalent functionality.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Are there other books (e.g. on the service profile or agreement) where we’re already using one or the other of these terms, so that we can make sure this is consistent?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Should I change to:<o:p></o:p></p>
<p class="MsoNormal">“DynamicallyAssignedParameter”<o:p></o:p></p>
<p class="MsoNormal">versus<o:p></o:p></p>
<p class="MsoNormal">“RespecificationParameter”<o:p></o:p></p>
<p class="MsoNormal">?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>