<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 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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* 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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",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:11.0pt;
font-family:"Calibri",sans-serif;}
span.EstiloDeEmail19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EstiloDeEmail20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EstiloDeEmail21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EstiloDeEmail22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EstiloDeEmail24
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;}
.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="PT-BR" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Years ago I was in charge of compiling a Glossary as part of the SpaceOps Committee publication activities. In that context, soon, it became very clear that multiplicity of definitions
for a same Glossary Term or <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Item should be taken into account, for the sake of precision. In the context of CCSDS (and of ISO TC20/SC13, of course) this kind of multiplicity is even a more easy, clear and imperative
evidence. A must to be <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">taken into account. Unfortunately, there is no “short-cut” way, in this case.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Thank you for your comment, Osvaldo.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Merry Christmas and New Year for you and for all of our CCSDS colleagues,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Eduardo <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">___________________________________________________________________________________________________________________________________________________________________________<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>De:</b> osvaldo.peinado@dlr.de <osvaldo.peinado@dlr.de> <br>
<b>Enviada em:</b> sexta-feira, 21 de dezembro de 2018 05:58<br>
<b>Para:</b> eduardo.w.bergamini@outlook.com; Michael.Blackwood@asrcfederal.com<br>
<b>Cc:</b> cmc@mailman.ccsds.org<br>
<b>Assunto:</b> AW: INPE Informal Review of the Draft Minutes of the October 2018 CMC Meeting (Berlin).<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">I agree with you Eduardo<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">I had several times the same discussion, it makes absolutely no sense to have a unify definition, that is not realistic.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">For example the term Bandwidth has 4 different definitions and are all correct and with quite different meaning, depend on the context and also the book.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Thanks for bringing up this point<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Merry Christmas to everyone<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Osvaldo</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><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 lang="DE" style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Von:</span></b><span lang="DE" style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> CMC [<a href="mailto:cmc-bounces@mailman.ccsds.org">mailto:cmc-bounces@mailman.ccsds.org</a>]
<b>Im Auftrag von </b>Eduardo W. Bergamini<br>
<b>Gesendet:</b> Freitag, 21. Dezember 2018 02:44<br>
<b>An:</b> 'Michael D. Blackwood, Mr. - ASRCFederal / CCSDS & ISO TC20/SC13 Secretariats'<br>
<b>Cc:</b> CMC - CCSDS Management Council (<a href="mailto:cmc@mailman.ccsds.org">cmc@mailman.ccsds.org</a>)<br>
<b>Betreff:</b> [CMC] INPE Informal Review of the Draft Minutes of the October 2018 CMC Meeting (Berlin).<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Dear Michael,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">I would have a comment that I wish to propose for consideration in the context of the enclosed <CMC Fall 2018 MoM Draft_v1.2> minutes.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Therefore, I leave to your consideration on what could be a best way to rephrase and synthesize my comment in a way that it may permit an adequately, brief inclusion in the context of
the CMC draft minutes.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">The comment. At our CMC meeting, when discussion came up on the Glossary to be maintained by SANA. At that point I made a point to the plenary of the meeting that can be equivalently
expressed under <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">the following comment. It can be observed that a Term or Item of the Glossary may have conceptually more than one definition (2, or more), depending on the context it is being defined
and used, for <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">instance, across the work context of more than one of the CCSDS WGs. To say the least, because the same term may also be in use with also conceptually different definitions by other
groups or organizations, <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">outside of CCSDS. As a result, it is honestly unconceivable to try to “unify” under an “unique” conceptual definition a set of two or more definitions, associated to a same Glossary
Term or Item which have been <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">that are being adopted under different contexts, for instance, of Standards and or Best Practices documents, or else. In conclusion, the point I expressed in the pertinent discussions
we held in the CMC plenary <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">is that, for each Term or Item of the Glossary it may also include a pointing to the at least one document (a CCSDS Recommendation, Best Practice, or else) where it is originated from,
or, simply cited, in the way it <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">is being defined, in the context of the pointed document. That is, each Term or Item of the Glossary can eventually hold more than one conceptually different definition, each of them,
depending on the origin <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">where it has been defined. If such a proposed care is not taken in the context of a Glossary, it will fatally open the possibility of polemic interpretations or, even, misinterpretations
to a specific Term or Item of <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">the Glossary, that may actually bear more than one conceptually different definitions that depend on the specific conceptual context they were defined from.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Thank you for your attention and consideration, as possible.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Sincere regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">EDUARDO W. BERGAMINI<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">- INPE/CMC-CCSDS<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="mso-fareast-language:EN-US">ENCLOSURE:</span></b><span lang="EN-US" style="mso-fareast-language:EN-US"> <CMC Fall 2018 MoM draft_v1.2> Draft Minutes. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">__________________________________________________________________________________________________________________________________________________________________________
<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>De:</b> CMC <<a href="mailto:cmc-bounces@mailman.ccsds.org">cmc-bounces@mailman.ccsds.org</a>>
<b>Em nome de </b>Blackwood, Michael D. via CMC<br>
<b>Enviada em:</b> quinta-feira, 13 de dezembro de 2018 14:46<br>
<b>Para:</b> 'cmc@mailman.ccsds.org' <<a href="mailto:cmc@mailman.ccsds.org">cmc@mailman.ccsds.org</a>><br>
<b>Assunto:</b> [CMC] Draft Minutes of the October 2018 CMC Meeting for Informal Review<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">Dear CMC Members,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Please find attached to this message the draft minutes of the CMC’s October 2018 meeting. If you would, please take a moment to review these minutes and reply to me with any changes or updates by Friday, 21 December 2018.
After this informal review, the minutes will proceed to CMC poll for final approval.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Michael Blackwood<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">CCSDS Secretariat<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">W: 301-837-3901 | </span><a href="mailto:michael.blackwood@asrcfederal.com"><span lang="EN-US">michael.blackwood@asrcfederal.com</span></a><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">7515 Mission Drive, Seabrook, MD 20706<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">ASRC Federal | <i>Customer-Focused. Operationally Excellent.<o:p></o:p></i></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span lang="EN-US">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray"><br>
The preceding message (including attachments) is covered by the Electronic Communication Privacy Act, 18 U.S.C. sections 2510-2512, is intended only for the person or entity to which it is addressed, and may contain information that is confidential, protected
by attorney-client or other privilege, or otherwise protected from disclosure by law. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please
reply to the sender that you have received the message in error and destroy the original message and all copies.</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</body>
</html>