<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=utf-8">
<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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
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.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Hi, Holger. Okay, now I remember. The bit about it not being in SANA confused me.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Adding the “intended for provider-internal use” text to the description has the advantage that it would not require a change to the structure of the SANA FR registry.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">However, in the case of configured parameters that are only configurable internally by the provider, we might want to add another attribute to the FRM XML database
and editor so that those parameters can be excluded from the generation of configuration profile XSDs.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Regarding non-configurable (i.e., read-only) parameters, it’s okay be me to somehow flag (in the description and/or by an additional attribute) that they are
intended for provider-internal use, but in any case since it is up to the provider to decide which parameters are available to the users each provider can simply allow or disallow user monitoring of such parameters.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">John
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Holger.Dreihahn@esa.int [mailto:Holger.Dreihahn@esa.int]
<br>
<b>Sent:</b> Monday, November 2, 2020 9:34 AM<br>
<b>To:</b> John Pietras <john.pietras@gst.com><br>
<b>Cc:</b> css-csts@mailman.ccsds.org; wo_._he@t-online.de<br>
<b>Subject:</b> RE: [Css-csts] Minutes of Fall Meeting<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Hello John,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The statement you quote is a statement we carried forward from last meeting. Last week we just decided briefly to keep it. It is addressing the fact that in some cases provider internal parameters
are modelled in the FRM for the sake of completeness. I have put an addendum which reflects my recollection:</span>
<br>
<br>
Suggestion: Put in the description (possible another attribute) saying that this is primarily foreseen for provider internal use.
<b>Addendum: Then it would actually be published in SANA.</b> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I have changed the title of section 7 as suggested.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Best regards,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Holger</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Holger Dreihahn<br>
European Spacecraft Operations Centre | European Space Agency | H-293<br>
+49 6151 90 2233 | </span><a href="http://www.esa.int/esoc"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">http://www.esa.int/esoc</span></a>
<br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"John Pietras" <<a href="mailto:john.pietras@gst.com">john.pietras@gst.com</a>></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"<a href="mailto:Holger.Dreihahn@esa.int">Holger.Dreihahn@esa.int</a>" <<a href="mailto:Holger.Dreihahn@esa.int">Holger.Dreihahn@esa.int</a>>,
"<a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a>" <<a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a>>, "<a href="mailto:wo_._he@t-online.de">wo_._he@t-online.de</a>" <<a href="mailto:wo_._he@t-online.de">wo_._he@t-online.de</a>></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">02/11/2020 14:58</span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">RE: [Css-csts] Minutes of Fall Meeting</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<span style="font-family:"Calibri",sans-serif;color:#004080">Holger and all,</span>
<br>
<span style="font-family:"Calibri",sans-serif;color:#004080">I am not remembering the context and meaning of the Statement made in section 7 of the MOM:</span>
<br>
<span style="font-family:"Calibri",sans-serif;color:#004080"> </span> <br>
A mechanism to allow local parameters in the FRM for use by the provider, but not for the publication at SANA.
<br>
Suggestion: Put in the description (possible another attribute) saying that this is primarily foreseen for provider internal use.
<br>
<span style="font-family:"Calibri",sans-serif;color:#004080"> </span> <br>
<span style="font-family:"Calibri",sans-serif;color:#104160">If it’s not going to be in the SANA registry, then how will anyone know that it exists? Can we add that as a topic for clarification in our Wednesday (or Thursday) telecon?</span>
<br>
<span style="font-family:"Calibri",sans-serif;color:#104160"> </span> <br>
<span style="font-family:"Calibri",sans-serif;color:#104160">Also, the heading for that section 7, “Functional Resources Technical Note and FR Model” should be changed to something like “Functional Resource Model Magenta Book and FR Model Database” to reflect
both the change of document type and the fact that we are now using “Functional Resource Model” to designate both the document and the more-detailed XML-based data structure that is the basis for the SANA Registry and configuration profiles (and maybe more
in the future).</span> <br>
<span style="font-family:"Calibri",sans-serif;color:#104160"> </span> <br>
<span style="font-family:"Calibri",sans-serif;color:#104160">Thanks.</span> <br>
<span style="font-family:"Calibri",sans-serif;color:#104160"> </span> <br>
<span style="font-family:"Calibri",sans-serif;color:#104160">Best regards,</span>
<br>
<span style="font-family:"Calibri",sans-serif;color:#104160">John</span> <br>
<span style="font-family:"Calibri",sans-serif;color:#104160"> </span> <br>
<b><span style="font-family:"Calibri",sans-serif">From:</span></b><span style="font-family:"Calibri",sans-serif"> CSS-CSTS [</span><a href="mailto:css-csts-bounces@mailman.ccsds.org"><span style="font-family:"Calibri",sans-serif">mailto:css-csts-bounces@mailman.ccsds.org</span></a><span style="font-family:"Calibri",sans-serif">]
<b>On Behalf Of </b><a href="mailto:Holger.Dreihahn@esa.int">Holger.Dreihahn@esa.int</a><b><br>
Sent:</b> Monday, November 2, 2020 2:42 AM<b><br>
To:</b> <a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a>;
<a href="mailto:wo_._he@t-online.de">wo_._he@t-online.de</a><b><br>
Subject:</b> [Css-csts] Minutes of Fall Meeting</span> <br>
<br>
<span style="font-family:"Arial",sans-serif">Dear CSTS WG Colleagues,</span> <span style="font-family:"Arial",sans-serif">
<br>
Please find the minutes of the fall meeting and the other meeting materials on the CWE for your review:</span>
<u><span style="color:blue"><br>
</span></u><a href="https://cwe.ccsds.org/css/docs/CSS-CSTS/Meeting%20Materials/2020/Fall"><span style="font-family:"Arial",sans-serif">https://cwe.ccsds.org/css/docs/CSS-CSTS/Meeting%20Materials/2020/Fall</span></a>
<br>
<span style="font-family:"Arial",sans-serif"><br>
Thank you all for the productive meeting.</span> <br>
<span style="font-family:"Arial",sans-serif"><br>
Best regards,</span> <span style="font-family:"Arial",sans-serif"><br>
Holger</span> <br>
<span style="font-family:"Arial",sans-serif"><br>
Holger Dreihahn<br>
European Spacecraft Operations Centre | European Space Agency | H-293<br>
+49 6151 90 2233 | </span><a href="http://www.esa.int/esoc"><span style="font-family:"Arial",sans-serif">http://www.esa.int/esoc</span></a>
<br>
<span style="font-family:"Courier New"">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or</span>
<br>
<span style="font-family:"Courier New"">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received</span>
<br>
<span style="font-family:"Courier New"">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect</span>
<br>
<span style="font-family:"Courier New"">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (</span><a href="mailto:dpo@esa.int"><span style="font-family:"Courier New"">dpo@esa.int</span></a><span style="font-family:"Courier New"">).</span>
<o:p></o:p></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></pre>
</div>
</body>
</html>