<font size=2 face="sans-serif">Hi John,</font>
<br><font size=2 face="sans-serif">I would love to resume the work on this
topic, hopefully we come to that soon. It is a very good idea to collect
the TODOs per FR. If we go for the SFW update for the simplified types,
there is an impact on all FRs so far specified, but in my mind it's worth
it.</font>
<br>
<br><font size=2 face="sans-serif">Let's discuss tomorrow, I have included
it in the agenda.</font>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br><font size=2 face="sans-serif">Holger</font>
<br>
<br><font size=2 face="sans-serif">Holger Dreihahn<br>
European Spacecraft Operations Centre | European Space Agency | S-431<br>
+49 6151 90 2233 | </font><a href=http://www.esa.int/esoc><font size=2 face="sans-serif">http://www.esa.int/esoc</font></a>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">John Pietras <john.pietras@gst.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"CCSDS_CSTSWG
(css-csts@mailman.ccsds.org)" <css-csts@mailman.ccsds.org>,
Wolfgang Hell <wo_._he@t-online.de></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">04/09/2018 16:09</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[Css-csts] SANA
FR Registry Item Workbook</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"CSS-CSTS"
<css-csts-bounces@mailman.ccsds.org></font>
<br>
<hr noshade>
<br>
<br>
<br><font size=3 face="Calibri">CSTSWG colleagues ---</font>
<br><font size=3 face="Calibri">Late last year, Holger put together a spreadsheet
that identified the responsible organization, editor, reviewer, and status
of each of the Functional Resources that are included in the candidate
SANA Registry. This was the first step to address cleaning up the FR Registry
“for real”.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">Owing to higher priorities, not much has
been done to progress the FR Registry, but we are now possibly reaching
a point where we can begin to pay some serious attention to it. </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">In support of this effort, I have taken
Holger’s spreadsheet and expanded it into an Excel workbook with a separate
sheet for each FR. I propose to use this workbook to record items that
need to be addressed for each of the FRs. Some of these items have already
been recognized, discussed, and agreed upon, whereas others are things
that I have stumbled upon in my work with the <i>Functional Resource Reference
Model</i> Tech Note, the <i>Requirements for Simple Configuration Profiles
and Service Agreements</i> Tech Note, and the several CSTS specifications.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">I have uploaded the worksheet to the CWE
> CSS-CSTS > CWE Private > Functional Resources Definition >
SANA folder at URL</font>
<br><a href="https://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Functional%20Resources%20Definition/SANA/FR_Registry_Items-2018-09-04.xlsx"><font size=3 color=#0082bf face="Calibri"><u>https://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Functional%20Resources%20Definition/SANA/FR_Registry_Items-2018-09-04.xlsx</u></font></a>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">Some of the “themes” that are found I
the workbook include:</font>
<br><font size=3 face="Calibri">- Conformance
with the naming and abbreviation conventions</font>
<br><font size=3 face="Calibri">- Adjustments
to the FR model itself (deletion of one FR, splitting of several FRs, possible
combination of some FRs)</font>
<br><font size=3 face="Calibri">- Proper
identification of configuration parameters</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">I have done my best to record the items
that need to be addressed of which I am aware, but it is very possible
that I have overlooked some things and/or did not apply the comments uniformly
across all FRs that might be affected. If we use this workbook as a tool
for issues tracking hopefully omissions will be filled and errors will
be corrected as we progress.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">It is my hope that we can use this workbook
to track our progress in building a complete and correct SANA FR Registry.
Once an item is resolved to the point that it has been validated and included
in the SANA Registry XML file, it can be closed in the spreadsheet for
that FR.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">We might want to break the single workbook
into separate workbooks, one for each editor (at this time, Wolfgang and
me) to serve as the “Captain” for that workbook. As the workbooks are
updated, they can be posted to the CWE. Perhaps we will have time to discuss
this a bit at this coming Thursday’s telecon.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">Best regards,</font>
<br><font size=3 face="Calibri">John</font><tt><font size=2>_______________________________________________<br>
CSS-CSTS mailing list<br>
CSS-CSTS@mailman.ccsds.org<br>
</font></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts"><tt><font size=2>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br>
<PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE>