<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:mv="http://macVmlSchemaUri" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<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:Arial;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 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";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Courier;}
span.EmailStyle19
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle20
{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:1001546555;
mso-list-template-ids:610706310;}
@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:1446073202;
mso-list-template-ids:-433811634;}
@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;}
@list l2
{mso-list-id:1549417542;
mso-list-type:hybrid;
mso-list-template-ids:-601079204 67698711 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
{mso-level-number-format:alpha-lower;
mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">In English this is what we call “a tempest in a teapot”. This is all in one spec, in three clauses, one of which has six sub-clauses. Various of us seem to have:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l2 level1 lfo4"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">a)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">Not read all three clauses<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l2 level1 lfo4"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">b)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">Only quoted parts of one sub-clause, not even the whole of it<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l2 level1 lfo4"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">c)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">And this leads to confusion …<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">As with all CCSDS specs you do need to read, understand, and comply with all normative parts of the spec. At least here the ASCII Segmented Time Code is stated in 2.5 pages of one rather
modest spec and does not require a stack of three dense specs to get to an understanding of what is required. And it is a spec that has been around and in successful use since 1987. It just cannot be a huge problem or source of confusion or it would have
surfaced years ago.<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">My concrete suggestion for “fixing” this was to add a few non-normative examples so that the meaning of the spec is made even more clear. I provided what I thought was a reasonable set
of example that touch upon the major inflection points where valid subsets can be created.<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">If anyone has an alternative concrete suggestion, please offer it up so we can all return to more substantive issues.<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">Thanks, Peter<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>
<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">Mario Merri <Mario.Merri@esa.int><br>
<b>Date: </b>Saturday, August 6, 2016 at 11:52 PM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int>, CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Subject: </b>Re: [CESG] CCSDS 301.0-B-4 propsed pink sheet (Time Code B) / Backward compatibility?<o:p></o:p></span></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-right:0in" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<div>
<p class="MsoNormal">It is so clear that we have been discussing a week ...<br>
<br>
__Mario<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On 6 Aug 2016, at 02:17, Shames, Peter M (312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I think the standard is quite clear enough as it is if you read all the clauses, just like most of our specs. However, I would support the addition of a non-normative corrigendum that
provides some examples. I do not think that that can be an exhaustive set of examples because in spite of there being clear rules there are too many possible combinations. I only showed a subset of the possible ones.</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">Regards, 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>
<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 <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>><br>
<b>Date: </b>Friday, August 5, 2016 at 3:08 AM<br>
<b>To: </b>Mario Merri <<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>><br>
<b>Cc: </b>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>, CCSDS Engineering Steering Group - CESG Exec <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><br>
<b>Subject: </b>Re: [CESG] CCSDS 301.0-B-4 propsed pink sheet (Time Code B) / Backward compatibility?</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>
<div>
<p class="MsoNormal">Mario, you are basically repeating my proposal; i.e. working on section 3.5.1.3 instead of adding the optional field in section 3.5.1.2. :-)<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">If we can do that just adding a NOTE we might go for an editorial corrigendum as the addition would be non normative. <o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">I go back to rest now<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">Gippo<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><br>
<br>
Sent from my iPhone<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On 05 Aug 2016, at 09:45, <a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Arial">Peter,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:Arial">my proposal would be:</span> <br>
<br>
<span style="font-size:10.0pt;font-family:Arial">1. No change is needed to accommodate Erik's request as this is already foreseen by the standard</span>
<br>
<span style="font-size:10.0pt;font-family:Arial">2. Improve the text in the standard to make the rules for subsetting clearer.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:Arial">For 2. for instance, it is implicit and possibly open to interpretation that, regardless whether one removes subsets from the left or from the right, this must be done on contiguous subsets and one cannot take
out for example "mm" and have YYYY-DDDThh:ss (although I admit not very meaningful). In other words to the left or to the right of what? I know, it is a little bit pedantic, but CCSDS should strive for fully unambiguous text. My proposal here is to further
refine the text of clause c and add the exhaustive list of allowed subset formats.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:Arial">I am also a little bit puzzled by the fact that the "Z" terminator is declared optional. I guess the logic is that the parser will consider the time code finished when it encounters a character different from
a numerical digit. What if, to save bits, the next field that happens to be numeric is collapsed to the time code? Wouldn't be cleaner to make "Z" terminator mandatory if the time subset is present?</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:Arial">Regards,</span> <br>
<br>
<span style="font-size:10.0pt;font-family:Arial">__Mario</span> <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)" <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>></span>
<br>
<span style="font-size:7.5pt;font-family:Helvetica;color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:Helvetica">"<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>" <<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>>,
"Barkley, Erik J (3970)" <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>></span>
<br>
<span style="font-size:7.5pt;font-family:Helvetica;color:#5F5F5F">Cc: </span><span style="font-size:7.5pt;font-family:Helvetica">"<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>" <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>></span>
<br>
<span style="font-size:7.5pt;font-family:Helvetica;color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:Helvetica">04/08/2016 23:42</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] CCSDS 301.0-B-4 propsed pink sheet (Time Code B) / Backward compatibility?</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">Hi Mario,</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">I’m not clear what you are proposing. In one paragraph you say that the standard is “ok”. In the next paragraph you say that the standard forces use of ICDs because it is ambiguous. Which is it? And, if
you think it is a problem, just what would you propose to change?</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">I agree that this could probably be stated even more clearly, but, as you point out, it does provide both a clear specification of the full set of sub-fields and rules for dropping sub-fields if they are not
needed. If you had quoted the complete text of sec 3.5.1.3.c you would see the following:</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:13.5pt">c) Calendar or time subsets may contain all the defined subfields, or may be abbreviated to the span of interest by deleting the unneeded subfields, either on the left or on the right. However, when subfields are deleted on the
LEFT, all separators that had delimited the deleted subfields must be retained (except for the ‘T’ which, by rule b, is dropped if the subset is used alone.) When subfields are deleted on the RIGHT, the separators that had delimited the deleted subfields are
dropped. </span><span style="font-family:"MS Mincho"">?</span> <br>
<span style="font-size:10.0pt;font-family:Calibri">Between this rule (and the other three in Sec 3.5.1.3), the explicit use of required separators and the rules for keeping or dropping them, it is possible to construct a simple but robust parser that will not
have any ambiguities. In fact, any parser that is supposed to be compliant with this spec that has a problem with parsing any truncated calendar, or time, or combined “calendarTtime” format would have to be judged non-compliant with the spec.</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">According to the rules any of the following constructs should be acceptable:</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:13.5pt">YYYY-DDDThh:mm:ss.d</span><span style="font-size:13.5pt;font-family:Calibri">→</span><span style="font-size:13.5pt">dZ
</span><br>
<span style="font-size:13.5pt">YYYY-DDDThh:mm:ss.d</span><span style="font-size:13.5pt;font-family:Calibri">→</span><span style="font-size:13.5pt">d
</span><br>
<span style="font-size:13.5pt">-DDDThh:mm:ss </span><br>
<span style="font-size:13.5pt">-DDDThh:mm</span> <br>
<span style="font-size:13.5pt">hh:mm:ss.d</span><span style="font-size:13.5pt;font-family:Calibri">→</span><span style="font-size:13.5pt">dZ
</span><br>
<span style="font-size:13.5pt">YYYY-DDD</span> <br>
<span style="font-size:10.0pt;font-family:Calibri">Perhaps a non-normative set of examples like this would have helped?</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">Thanks, 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 <<a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a>> on behalf of Mario Merri <<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>><b><br>
Date: </b>Thursday, August 4, 2016 at 1:52 AM<b><br>
To: </b>Erik Barkley <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>><b><br>
Cc: </b>CCSDS Engineering Steering Group - CESG Exec <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><b><br>
Subject: </b>Re: [CESG] CCSDS 301.0-B-4 propsed pink sheet (Time Code B) / Backward compatibility?</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:Arial">Hi Erik,</span> <br>
<span style="font-size:10.0pt;font-family:Arial"><br>
I believe your proposed change is not needed as it is already covered by the standard, in particular by clause 3.5.1.3.c. In fact, there it is clearly stated that:</span>
<o:p></o:p></p>
<ul type="disc">
<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:Arial">[...] time subsets [...] may be abbreviated to the span of interest by deleting the unneeded subfields, either on the left or on the right.
<span style="color:blue">This implies that one can delete the "d→d" subfield</span></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:Arial">When subfields are deleted on the RIGHT, the separators that had delimited the deleted subfields are dropped.
<span style="color:blue">This implies that one can delete the decimal dot</span></span><o:p></o:p></li></ul>
<p class="MsoNormal"><span style="font-family:Symbol">·</span> <span style="font-size:10.0pt;font-family:Arial"><br>
For the decimal dot I believe the current solution is OK. Robust implementations should parse the time code string until they find the "Z". If they find a "." before, then the time has decimal fraction of second.</span>
<br>
<span style="font-size:10.0pt;font-family:Arial"><br>
On the other hand, clause 3.5.1.3.c provides full flexibility to eliminate any subfield. This seems to me not clean and not in the spirit of standardisation as it results in the proliferation of different time formats, which require specific ICDs to make them
unambiguous.</span> <br>
<span style="font-size:10.0pt;font-family:Arial"><br>
Regards,</span> <br>
<span style="font-size:10.0pt;font-family:Arial"><br>
__Mario</span> <br>
<br>
<br>
<span style="font-size:7.5pt;font-family:Helvetica;color:#5F5F5F"><br>
From: </span><span style="font-size:7.5pt;font-family:Helvetica">"Shames, Peter M (312B)" <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>></span>
<span style="font-size:7.5pt;font-family:Helvetica;color:#5F5F5F"><br>
To: </span><span style="font-size:7.5pt;font-family:Helvetica">"Barkley, Erik J (3970)" <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>></span>
<span style="font-size:7.5pt;font-family:Helvetica;color:#5F5F5F"><br>
Cc: </span><span style="font-size:7.5pt;font-family:Helvetica">"CESG -- CCSDS-Engineering Steering Group\(<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>\)\(<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>\)" <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>></span>
<span style="font-size:7.5pt;font-family:Helvetica;color:#5F5F5F"><br>
Date: </span><span style="font-size:7.5pt;font-family:Helvetica">04/08/2016 05:04</span>
<span style="font-size:7.5pt;font-family:Helvetica;color:#5F5F5F"><br>
Subject: </span><span style="font-size:7.5pt;font-family:Helvetica">Re: [CESG] CCSDS 301.0-B-4 propsed pink sheet (Time Code B) / Backward compatibility?</span>
<span style="font-size:7.5pt;font-family:Helvetica;color:#5F5F5F"><br>
Sent by: </span><span style="font-size:7.5pt;font-family:Helvetica">"CESG" <<a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a>></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>
<br>
I agree. I think clause 3.5.1.3.c covers this case (and even the hh:mm case). I just hope that implementations are robust enough to handle it correctly.
<br>
<br>
Peter <br>
<br>
Sent from Peter's iPhone 6 <br>
<br>
Everything should be made as simple as possible, <br>
but not simpler. <br>
<br>
~Albert Einstein <br>
<br>
On Aug 3, 2016, at 6:34 PM, Barkley, Erik J (3970) <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>> wrote:<br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080"><br>
Gippo,</span> <span style="font-size:10.0pt;font-family:Calibri;color:#004080"><br>
</span> <span style="font-size:10.0pt;font-family:Calibri;color:#004080"><br>
I too noted that it might be possible to interpret 3.5.1.3 as already allowing removal of the decimal fraction/sub-second.
<br>
</span> <span style="font-size:10.0pt;font-family:Calibri;color:#004080"><br>
CESG members,</span> <span style="font-size:10.0pt;font-family:Calibri;color:#004080">
<br>
</span> <span style="font-size:10.0pt;font-family:Calibri;color:#004080"><br>
What is your taking/reading on this? Does this already allow fractional seconds to be optional? If not, why not?
<br>
</span> <span style="font-size:10.0pt;font-family:Calibri;color:#004080"><br>
Best regards,</span> <span style="font-size:10.0pt;font-family:Calibri;color:#004080">
<br>
-Erik</span> <span style="font-size:10.0pt;font-family:Calibri;color:#004080"><br>
</span> <b><span style="font-size:10.0pt;font-family:Calibri"><br>
From:</span></b><span style="font-size:10.0pt;font-family:Calibri"> </span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="font-size:10.0pt;font-family:Calibri">Gian.Paolo.Calzolari@esa.int</span></a><span style="font-size:10.0pt;font-family:Calibri">
[</span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="font-size:10.0pt;font-family:Calibri">mailto:Gian.Paolo.Calzolari@esa.int</span></a><span style="font-size:10.0pt;font-family:Calibri">]
<b><br>
Sent:</b> Monday, July 25, 2016 2:26 AM<b><br>
To:</b> Barkley, Erik J (3970) <</span><a href="mailto:erik.j.barkley@jpl.nasa.gov"><span style="font-size:10.0pt;font-family:Calibri">erik.j.barkley@jpl.nasa.gov</span></a><span style="font-size:10.0pt;font-family:Calibri">><b><br>
Cc:</b> CESG -- CCSDS-Engineering Steering Group (</span><a href="mailto:cesg@mailman.ccsds.org"><span style="font-size:10.0pt;font-family:Calibri">cesg@mailman.ccsds.org</span></a><span style="font-size:10.0pt;font-family:Calibri">) (</span><a href="mailto:cesg@mailman.ccsds.org"><span style="font-size:10.0pt;font-family:Calibri">cesg@mailman.ccsds.org</span></a><span style="font-size:10.0pt;font-family:Calibri">)
<</span><a href="mailto:cesg@mailman.ccsds.org"><span style="font-size:10.0pt;font-family:Calibri">cesg@mailman.ccsds.org</span></a><span style="font-size:10.0pt;font-family:Calibri">><b><br>
Subject:</b> Re: [CESG] CCSDS 301.0-B-4 propsed pink sheet (Time Code B) / Backward compatibility?</span>
<br>
<span style="font-size:10.0pt;font-family:Arial"><br>
Erik,</span> <span style="font-size:10.0pt;font-family:Arial"><br>
from a purist point of view I think that it would be incorrect stating that the change is backward compatible as a former implementation would expect to find always the "</span>Decimal fraction of second<span style="font-size:10.0pt;font-family:Arial">"
and would most likely crashes when that field is absent.</span> <span style="font-size:10.0pt;font-family:Arial">
<br>
Conversely a constant setting to 0 when not used would be fully backward compatible.</span>
<span style="font-size:10.0pt;font-family:Arial"><br>
<br>
However it is also true that despite section 3.5.1.2 "ASCII TIME CODE B, Year/Day of Year Calendar Variation" defines only one optional field (i.e. the time code terminator) section 3.5.1.3 "SUBSETS OF THE COMPLETE TIME CODES" basically allows many fields
to be optional so I wonder whether it would be more correct working on section 3.5.1.3 instead of adding the optional field in section 3.5.1.2.</span>
<span style="font-size:10.0pt;font-family:Arial"><br>
In other words, the part of </span><span style="font-size:10.0pt;font-family:Calibri">3.5.1.3 clause (c)</span><span style="font-size:10.0pt;font-family:Arial"> stating that the code "may be abbreviated to the span of interest by deleting the unneeded subfields"
does already allow removing the Decimal fraction of second subfield?</span> <span style="font-size:10.0pt;font-family:Arial">
<br>
<br>
My cent.......</span> <span style="font-size:10.0pt;font-family:Arial"><br>
<br>
Gian Paolo</span> <span style="font-size:10.0pt;font-family:Arial"><br>
<br>
PS It looks to me that the sentence "</span><span style="font-size:10.0pt">the need to accommodate the upcoming century rollover in only 11 years</span><span style="font-size:10.0pt;font-family:Arial">" was somehow wrong in 2010 as it is now :o)</span>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
<br>
From: </span><span style="font-size:7.5pt;font-family:Arial">"Barkley, Erik J (3970)" <</span><a href="mailto:erik.j.barkley@jpl.nasa.gov"><span style="font-size:7.5pt;font-family:Arial">erik.j.barkley@jpl.nasa.gov</span></a><span style="font-size:7.5pt;font-family:Arial">></span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
To: </span><span style="font-size:7.5pt;font-family:Arial">"CESG -- CCSDS-Engineering Steering Group (</span><a href="mailto:cesg@mailman.ccsds.org"><span style="font-size:7.5pt;font-family:Arial">cesg@mailman.ccsds.org</span></a><span style="font-size:7.5pt;font-family:Arial">)
(</span><a href="mailto:cesg@mailman.ccsds.org"><span style="font-size:7.5pt;font-family:Arial">cesg@mailman.ccsds.org</span></a><span style="font-size:7.5pt;font-family:Arial">)" <</span><a href="mailto:cesg@mailman.ccsds.org"><span style="font-size:7.5pt;font-family:Arial">cesg@mailman.ccsds.org</span></a><span style="font-size:7.5pt;font-family:Arial">></span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
Date: </span><span style="font-size:7.5pt;font-family:Arial">22/07/2016 01:44</span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
Subject: </span><span style="font-size:7.5pt;font-family:Arial">[CESG] CCSDS 301.0-B-4 propsed pink sheet (Time Code B)</span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
Sent by: </span><span style="font-size:7.5pt;font-family:Arial">"CESG" <</span><a href="mailto:cesg-bounces@mailman.ccsds.org"><span style="font-size:7.5pt;font-family:Arial">cesg-bounces@mailman.ccsds.org</span></a><span style="font-size:7.5pt;font-family:Arial">></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" style="margin-bottom:12.0pt"><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:Calibri"><br>
<br>
CESG Colleagues,</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"><br>
Attached is the proposed pink sheet for Time Code B which makes the time code more suitable for such applications as publishing a standardized schedule of services for which mandatory fractional seconds is meaningless. (By the way does anyone know what the
original rationale was for requiring, at a minimum, 1/10 of second time statements?) The proposed change is the addition of “(optional)” which is in keeping with the method by which optional is designated for the “Z” character in the recommendation. I believe
the “.” subfield separator disappears of by application of 3.5.1.3 clause (c). If this change is made to Time Code B, we likely should apply it to Time Code A. </span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"><br>
Best regards,</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
-Erik</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"><br>
[attachment "301x0b4e1-ProposedPinkSheet.docx" deleted by Gian Paolo Calzolari/esoc/ESA]
</span><span style="font-size:10.0pt;font-family:"Courier New"">_______________________________________________<br>
CESG mailing list</span><u><span style="color:blue"><br>
</span></u><a href="mailto:CESG@mailman.ccsds.org"><span style="font-size:10.0pt;font-family:"Courier New"">CESG@mailman.ccsds.org</span></a><u><span style="color:blue"><br>
</span></u><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><span style="font-size:10.0pt;font-family:"Courier New"">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</span></a><br>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
This message and any attachments are intended for the use of the addressee or addressees only.</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
content is not permitted.</span> <span style="font-size:10.0pt;font-family:"Courier New"">
<br>
If you received this message in error, please notify the sender and delete it from your system.</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
Emails can be altered and their integrity cannot be guaranteed by the sender.</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
</span> <span style="font-size:10.0pt;font-family:"Courier New""><br>
Please consider the environment before printing this email.</span> <br>
_______________________________________________<br>
CESG mailing list<u><span style="color:blue"><br>
</span></u><a href="mailto:CESG@mailman.ccsds.org">CESG@mailman.ccsds.org</a><u><span style="color:blue"><br>
</span></u><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</a><span style="font-size:10.0pt;font-family:"Courier New"">_______________________________________________<br>
CESG mailing list<br>
<a href="mailto:CESG@mailman.ccsds.org">CESG@mailman.ccsds.org</a></span><u><span style="color:blue"><br>
</span></u><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><span style="font-size:10.0pt;font-family:"Courier New"">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</span></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
</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.</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>
</blockquote>
<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>
</blockquote>
<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>
</body>
</html>