<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)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@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;}
p
{mso-style-priority:99;
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;}
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.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{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: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"><span style="color:#1F497D">Dear Wolfgang,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Okay, we can start simple (no intermediate hierarchy) and change that if it becomes unmanageable.<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">We don’t have to make the edits on-line. Instead, we can upload files revised files with the same filename, and SharePoint provides the option to treat the new upload as a new version. We only have to make sure
to delete previous versions if the file names change, e.g., to remove Fwd and Rtn prefixes.
<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">While the CWE (SharePoint) will keep the version modification dates straight, I am a bit concerned that once one downloads a file that information is lost and the operating system stamps the file with the date/time
of the download. I can see myself getting confused and accidentally working with/updating an older version on my computer and not the latest one on the CWE. I’d like to suggest that in the Status line for every Errata sheet we include a sentence along the
line of “This version was generated on <date> by <name of person who updated the file>.” Then if someone has two errata documents with the same name they need only to look at the Status line to know which is the most recent. (Note that the generation date
may not necessarily be the same as the date that the file is uploaded to the CWE. )<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 have created the Functional Resource Errata Sheets folder within the CWE Functional Resources Definition folder:
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="https://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Functional%20Resources%20Definition/Functional%20Resource%20Errata%20Sheets/">https://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Functional%20Resources%20Definition/Functional%20Resource%20Errata%20Sheets/</a>
<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">and uploaded the 11 errata sheets that I have updated, with the data stamps and author initials removed from the file names. I also included the generation data in the version information field for each file
to provide further traceability. The Version History for any file can be read by clicking on the ellipses (…) next to the file name, and then clicking on the ellipses (…) at the bottom of the box that pops up.<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 hope that you find this workable and useful.<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">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">John<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 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Wolfgang Hell <wo_._he@t-online.de> <br>
<b>Sent:</b> Tuesday, November 05, 2019 9:25 AM<br>
<b>To:</b> John Pietras <john.pietras@gst.com><br>
<b>Cc:</b> Holger.Dreihahn@esa.int; harald.ernst@esa.int; Pham, Timothy T (3300) <Timothy.T.Pham@jpl.nasa.gov><br>
<b>Subject:</b> Re: updated Errata sheets and posting them on the CWE<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Dear John,<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The fact that meanwhile we have so many Errata Sheet files is attributable to the fact that for our convenience each time we changed something we changed the file name so that from that file name the date and editor is obvious. There is
however no good reason to keep all the files for the same FR type with an earlier issue date than the latest one because we both kept all items in the file even though they had been closed. I'm advocating to continue doing that because more than once it proved
useful to be able to go back and figure out why certain decisions had been taken. That means that there is no reason for an ever growing number of documents, but we only need the most recent errata sheet for each FR type. Given that within the folder I can
sort by FR name (classifier) or release date and so far that was all I needed. I'm not opposed to intermediate folders, but I do not see a real need for them.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">SharePoint on the CWE may be a good way to go, but I have no experience with working on online copies of files. I would not like to depend on being always online when working on Errata Sheets. But other than that I agree that we should
"publish" the Errata Sheets on the CWE.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Wolfgang<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Am 04.11.2019 um 17:31 schrieb John Pietras:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">CSTSWG colleagues ---<o:p></o:p></p>
<p class="MsoNormal">At the Fall 2019 Workshop, we resolved a number of questions/issues regarding various FRs, and Wolfgang and I agreed to update their respective errata sheets. For my part, I initially had 3 errata sheets to update – TCMcMux, TcVcMux, and
FCltuTsProvider. There was one issue common to all transfer service provider FRs (related to network and ISP-1 parameter settings), so I updated the errata sheets for those FRs also. Al errata sheets that contain updates that are solely the result of decisions
made at the fall meeting carry the date stamp “191024”. However, in updating the errata sheets, I came across a few new issues. Errata sheets that contain these new issues have date stamps of today – 191104. The updated errata sheets are attached.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I think that we briefly discussed putting the errata sheets on the CWE, but I don’t think that we made any specific plans. I propose that they should be uploaded to a new FR Errata Sheets folder in the CWE > Functional Resources Definition
folder. Beyond that, I think that we have 2 decisions to make.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The first decision is whether to just put all of the FR errata sheets directly into the FR Errata Sheets folder, or to introduce in intermediate set of folders. Personally I would like to see an intermediate set of folders, because otherwise
we will have a long (and over time, increasingly long) list of documents that will be organized by FR name (classifier). A relatively simple set of intermediate folders could be named for the FR strata: Aperture, Physical Channel, etc. If we choose to go this
way (or to use a different set of intermediate folders) I will put those folders into the CWE.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The second decision is on the naming of the errata sheets. So far Wolfgang and I have been including a data stamp and our initials in the names of the files to keep them sorted out. However, by using the SharePoint-based CWE, we have the
opportunity to keep just the one copy of the file and perform our updates to the online copy. Wolfgang and I have already established a pattern for labeling our updates with our initial and a data stamp, so traceability of changes shouldn’t be an issue.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I am interested in hearing your comments.<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>
</blockquote>
<p><o:p> </o:p></p>
</div>
</body>
</html>