<html><head></head><body><div id="content" contenteditable="true" spellcheck="true" autocorrect="true" autocapitalize="true" style="font-family: Helvetica;">It is normally a task of the chief technical editor<div>And not very difficult</div><div>It will take me 30' to do it<br><br>Sent from my iPhone using IBM Verse<br><br><hr>On 13 Sep 2016, 18:08:56, kscott@mitre.org wrote:<br><br>From: kscott@mitre.org<br>To: peter.m.shames@jpl.nasa.gov, Gian.Paolo.Calzolari@esa.int<br>Cc: cesg@mailman.ccsds.org<br>Date: 13 Sep 2016 18:08:56<br>Subject: Re: [CESG] Lack of a standardised approach for CCSDS Document Number<br><br><div id="MaaS360PIMSDKOriginalMessageId">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<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:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
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";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Courier;}
span.EmailStyle20
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:161048986;
mso-list-template-ids:862097714;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:467672450;
mso-list-template-ids:-1883760092;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I concur with Nestor / Gian-Paolo in principle, but with Peter in practice. We SHOULD normalize these, but I doubt it’s an issue affecting operations / daily work.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I have just confirmed that I can edit entries that aren’t SIS. How about somebody who cares just fix them (or ask the secretariat to do it)? Maybe its possible to implement a restriction
on data format in SharePoint to keep it from happening in the future.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> --keith<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><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-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">"cesg-bounces@mailman.ccsds.org" <cesg-bounces@mailman.ccsds.org> on behalf of Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Date: </b>Tuesday, September 13, 2016 at 12:00 PM<br>
<b>To: </b>Gian Calzolari <Gian.Paolo.Calzolari@esa.int><br>
<b>Cc: </b>CCSDS Exec <cesg@mailman.ccsds.org><br>
<b>Subject: </b>Re: [CESG] Lack of a standardised approach for CCSDS Document Number<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">And I ask, just how much real value does this add to our standards?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Peter</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> </span><o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><br>
<b>Date: </b>Tuesday, September 13, 2016 at 8:20 AM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org>, CESG <cesg-bounces@mailman.ccsds.org>, Nestor Peccia <Nestor.Peccia@esa.int>, CCSDS Secretariat <Secretariat@mailman.ccsds.org><br>
<b>Subject: </b>Re: [CESG] Lack of a standardised approach for CCSDS Document Number</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Helvetica">Peter,</span>
<br>
<span style="font-size:10.0pt;font-family:Helvetica"> the issue is much simpler and clearly visible if you access the link.</span>
<br>
<span style="font-size:10.0pt;font-family:Helvetica">Otherwise just look at the snapshot.</span>
<br>
<span style="font-size:10.0pt;font-family:Helvetica">BTW, Delta DOR WG is fully OK :o)</span>
<br>
<span style="font-size:10.0pt;font-family:Helvetica">Regards</span> <br>
<br>
<span style="font-size:10.0pt;font-family:Helvetica">Gian Paolo</span> <br>
<br>
<img width="609" height="694" id="_x0000_i1025" src="cid:409EBA5B-20FC-44E1-967C-1FFC5CD68B10"><br>
<br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:Helvetica;color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:Helvetica">"Shames, Peter M (312B)" <peter.m.shames@jpl.nasa.gov></span>
<br>
<span style="font-size:7.5pt;font-family:Helvetica;color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:Helvetica">"Nestor.Peccia@esa.int" <Nestor.Peccia@esa.int>, "Secretariat" <Secretariat@mailman.ccsds.org>, "CCSDS Engineering Steering
Group - CESG Exec(cesg@mailman.ccsds.org)" <cesg@mailman.ccsds.org></span> <br>
<span style="font-size:7.5pt;font-family:Helvetica;color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:Helvetica">13/09/2016 17:13</span>
<br>
<span style="font-size:7.5pt;font-family:Helvetica;color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:Helvetica">Re: [CESG] Lack of a standardised approach for CCSDS Document Number</span>
<br>
<span style="font-size:7.5pt;font-family:Helvetica;color:#5F5F5F">Sent by: </span><span style="font-size:7.5pt;font-family:Helvetica">"CESG" <cesg-bounces@mailman.ccsds.org></span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#AAAAAA" align="center">
</div>
<p class="MsoNormal"><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:Calibri">Nestor,</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">Since we have document numbering rules already defined in the CCSDS Org & Proc (A02x0), and these clearly define the approach for numbering published standards I assume that this comment is relevant only for
DRAFT documents that are stored as working materials in the CWE. To be frank, as long as there is some sort of identifying number and name that makes sense on these DRAFT documents, and some sort of version tracking, I really do not think we should care too
much about how these drafts are named. They are internal work products of the organization.</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">I think maybe we are trying to polish the cannonball here. As a standards organization we should be paying more attention to the quality of what goes out the door than to these minutiae of how the WGs name
their working products. </span><br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">Regards, Peter</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<b><span style="font-family:Calibri">From: </span></b><span style="font-family:Calibri">CESG <cesg-bounces@mailman.ccsds.org> on behalf of Nestor Peccia <Nestor.Peccia@esa.int><b><br>
Date: </b>Tuesday, September 13, 2016 at 7:50 AM<b><br>
To: </b>CCSDS Secretariat <Secretariat@mailman.ccsds.org>, CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><b><br>
Subject: </b>[CESG] Lack of a standardised approach for CCSDS Document Number</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:Helvetica">Dear all,</span> <br>
<span style="font-size:10.0pt;font-family:Helvetica"><br>
I was made aware by an AD (guess whom?) of the different ways a Doc number is defined in the CWE</span>
<br>
<span style="font-size:10.0pt;font-family:Helvetica"><br>
If you look at </span><a href="http://cwe.ccsds.org/fm/Lists/Projects/AllItems.aspx"><span style="font-size:10.0pt;font-family:Helvetica">http://cwe.ccsds.org/fm/Lists/Projects/AllItems.aspx</span></a>
<o:p></o:p></p>
<ul>
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3">
<span style="font-size:10.0pt;font-family:Helvetica">number only (i.e. the correct form)</span>
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3">
<span style="font-size:10.0pt;font-family:Helvetica">number with CCSDS in front</span>
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3">
<span style="font-size:10.0pt;font-family:Helvetica">number with indication of color and issue (for the color there is a dedicated field, Issue is normally/often added to the project title)</span>
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3">
<span style="font-size:10.0pt;font-family:Helvetica">number with other field and comments</span><o:p></o:p></li></ul>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:Helvetica"><br>
We can say of ourselves, as an standard organization, "the shoemaker's son always goes barefoot"</span>
<br>
<span style="font-size:10.0pt;font-family:Helvetica"><br>
Can we do anything about this ?</span> <br>
<span style="font-size:10.0pt;font-family:Helvetica"><br>
ciao</span> <span style="font-size:10.0pt;font-family:Helvetica"><br>
nestor</span> <br>
<span style="font-size:10.0pt;font-family:"Courier New"">This message and any attachments are intended for the use of the addressee or addressees only.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">content is not permitted.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">If you received this message in error, please notify the sender and delete it from your system.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">Emails can be altered and their integrity cannot be guaranteed by the sender.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New""> </span> <br>
<span style="font-size:10.0pt;font-family:"Courier New"">Please consider the environment before printing this email.<tt>_______________________________________________</tt><br>
<tt>CESG mailing list</tt><br>
<tt>CESG@mailman.ccsds.org</tt><br>
</span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</span></tt></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
<br>
</span><o:p></o:p></p>
<pre>This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre>content is not permitted.<o:p></o:p></pre>
<pre>If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Please consider the environment before printing this email.<o:p></o:p></pre>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div></div></div><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE></body></html>