<html 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:Courier;
panose-1:2 0 5 0 0 0 0 0 0 0;}
@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:"Times New Roman \(Body CS\)";
panose-1:2 2 6 3 5 4 5 2 3 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Times;
panose-1:2 0 5 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.p1, li.p1, div.p1
{mso-style-name:p1;
margin:0in;
font-size:10.5pt;
font-family:Times;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:Courier;
color:windowtext;}
.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>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">To All (especially Lead Editors):<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">This is a bit of an esoteric topic, but I think it's worth a quick read. Start with my message at the bottom.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">David<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Thomas Gannett <thomas.gannett@tgannett.net><br>
<b>Date: </b>Tuesday, April 20, 2021 at 7:56 AM<br>
<b>To: </b>David Berry <david.s.berry@jpl.nasa.gov><br>
<b>Subject: </b>[EXTERNAL] RE: "Shall", "Must", "Should", "May" Quandary With Respect to Informative Annexes<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D">David:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">The disclaimer note in section 1 (“these conventions do not imply constraints. . . .”) indeed makes it not really necessary to worry about diction in something clearly identified as being informative. Generally
try to update such terminology anyway if the opportunity presents itself, but I don’t worry too much about it.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Tom</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1F497D"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1F497D">Logothete, L.L.C.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1F497D">thomas.gannett@tgannett.net</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1F497D">+1 443 472 0805</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<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"> Berry, David S (US 3920) [mailto:david.s.berry@jpl.nasa.gov]
<br>
<b>Sent:</b> Monday, April 19, 2021 5:56 PM<br>
<b>To:</b> CCSDS Secretariat<br>
<b>Subject:</b> "Shall", "Must", "Should", "May" Quandary With Respect to Informative Annexes</span><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:Courier">Tom:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">I'm working on an internal WG proofreading review of the Orbit Data Messages which is in revision and nearly ready to be sent to you for preparation for Agency Review.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">I came across something that has clearly escaped my attention, and I need your expert opinion.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">The ODM annex titled "SECURITY, SANA, AND PATENT CONSIDERATIONS" (primarily the SECURITY section) has a large number of instances of "should", a "shall", and a few instances of "may", but
it is an informative annex. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">I started to contort the English language to offer the ODM Lead Editor non-normative substitutes for these violations, but then thought I should check the TDM V.2, recently published, to
see what it had. To my chagrin, it has nearly the same text in the SECURITY section as does the new ODM. I recalled that in the days when the TDM V.1 was being developed, the SECURITY section was a fairly new requirement, and it appeared in the TDM as a normative
section (Section 5, not an Annex). Later the SECURITY sections were supposed to be placed in an informative annex and combined with SANA Considerations and Patent information. When the TDM V.1 section 5 was moved to an informative annex as I prepared TDM V.2,
all the "should"/"shall"/"may" language went with it. And I managed to overlook it (even though I read through the entire document several times)!</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"> </span><o:p></o:p></p>
<p class="p1"><span style="font-size:12.0pt;font-family:Courier">I recalled that the CCSDS Publications Guide has a NOTE in section 1.6.2.1 stating that "NOTE – These conventions do not imply constraints on diction in text that is clearly informative in nature."
Can this be construed to mean that Annexes clearly labelled "Informative" can use the words "shall", "must", "should", "may" as applicable? The language will be less contorted and thus easier to understand if that's the case.</span><o:p></o:p></p>
<p class="p1"><span style="font-size:12.0pt;font-family:Courier"> </span><o:p></o:p></p>
<p class="p1"><span style="font-size:12.0pt;font-family:Courier">Thanks for your guidance!</span><o:p></o:p></p>
<p class="p1"><span style="font-size:12.0pt;font-family:Courier">David</span><o:p></o:p></p>
<p class="p1"><span style="font-size:12.0pt;font-family:Courier"> </span><o:p></o:p></p>
<p class="p1"><span style="font-size:12.0pt;font-family:Courier"> </span><o:p></o:p></p>
</div>
</body>
</html>