<font size=2 face="sans-serif">Peter,</font>
<br><font size=2 face="sans-serif"> the
issue is much simpler and clearly visible if you access the link.</font>
<br><font size=2 face="sans-serif">Otherwise just look at the snapshot.</font>
<br><font size=2 face="sans-serif">BTW, Delta DOR WG is fully OK
:o)</font>
<br><font size=2 face="sans-serif">Regards</font>
<br>
<br><font size=2 face="sans-serif">Gian Paolo</font>
<br>
<br><img src=cid:_1_109E1228109E0C3C00544801C125802D style="border:0px solid;">
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Shames, Peter
M (312B)" <peter.m.shames@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"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></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">13/09/2016 17:13</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [CESG] Lack
of a standardised approach for CCSDS Document Number</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"CESG"
<cesg-bounces@mailman.ccsds.org></font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="Calibri">Nestor,</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="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.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="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. </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Regards, Peter</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=3 face="Calibri"><b>From: </b>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</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="sans-serif">Dear all,</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="sans-serif"><br>
I was made aware by an AD (guess whom?) of the different ways a Doc number
is defined in the CWE</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="sans-serif"><br>
If you look at </font><a href=http://cwe.ccsds.org/fm/Lists/Projects/AllItems.aspx><font size=2 color=blue face="sans-serif"><u>http://cwe.ccsds.org/fm/Lists/Projects/AllItems.aspx</u></font></a><font size=3 face="Times New Roman">
</font>
<ul>
<li><font size=2 face="sans-serif">number only (i.e. the correct form)</font><font size=3 face="Times New Roman">
</font>
<li><font size=2 face="sans-serif">number with CCSDS in front</font><font size=3 face="Times New Roman">
</font>
<li><font size=2 face="sans-serif">number with indication of color and
issue (for the color there is a dedicated field, Issue is normally/often
added to the project title)</font><font size=3 face="Times New Roman">
</font>
<li><font size=2 face="sans-serif">number with other field and comments</font></ul><font size=2 face="sans-serif"><br>
We can say of ourselves, as an standard organization, "the shoemaker's
son always goes barefoot"</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="sans-serif"><br>
Can we do anything about this ?</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="sans-serif"><br>
ciao</font><font size=3 face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
nestor</font><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Courier New">This message and any attachments are
intended for the use of the addressee or addressees only.</font>
<br><font size=2 face="Courier New">The unauthorised disclosure, use, dissemination
or copying (either in whole or in part) of its</font>
<br><font size=2 face="Courier New">content is not permitted.</font>
<br><font size=2 face="Courier New">If you received this message in error,
please notify the sender and delete it from your system.</font>
<br><font size=2 face="Courier New">Emails can be altered and their integrity
cannot be guaranteed by the sender.</font>
<br><font size=2 face="Courier New"> </font>
<br><font size=2 face="Courier New">Please consider the environment before
printing this email.</font><tt><font size=2>_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org<br>
</font></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><tt><font size=2>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br><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>