<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: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: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:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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:447092640;
mso-list-type:hybrid;
mso-list-template-ids:-1635767566 -704772768 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:301;
mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1
{mso-list-id:1907178306;
mso-list-template-ids:829486462;}
@list l1:level1
{mso-level-start-at:3;
mso-level-text:%1;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:30.0pt;
text-indent:-30.0pt;}
@list l1:level2
{mso-level-start-at:5;
mso-level-text:"%1\.%2";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-30.0pt;}
@list l1:level3
{mso-level-text:"%1\.%2\.%3";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:84.0pt;
text-indent:-.5in;}
@list l1:level4
{mso-level-start-at:2;
mso-level-text:"%1\.%2\.%3\.%4";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.5in;
text-indent:-.5in;}
@list l1:level5
{mso-level-text:"%1\.%2\.%3\.%4\.%5";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:150.0pt;
text-indent:-.75in;}
@list l1:level6
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:174.0pt;
text-indent:-.75in;}
@list l1:level7
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.0in;
text-indent:-1.0in;}
@list l1:level8
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:240.0pt;
text-indent:-1.0in;}
@list l1:level9
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:282.0pt;
text-indent:-1.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Dear SAWG members,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I have obtained and reviewed ISO 8601:2004. To answer your earlier questions:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">ISO 8601 only addresses textual representations of time. Binary encoding methods are not mentioned at all.<o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">I don’t know if there is any relevant ISO standard comparable to the CCSDS binary formats, and haven’t tried to find out.<o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">The two ASCII formats given in CCSDS 301.0-B-4, “Time Code Formats” are ISO 8601-compliant, although ISO expresses a preference for using the comma over the period to separate fractional units. The
relevant sections are:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:.5in"><span style="color:#1F497D">3.5.1.1 ASCII TIME CODE A, Month/Day of Month Calendar Variation<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.5in;mso-list:l1 level4 lfo2">
<![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">3.5.1.2<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">ASCII TIME CODE B, Year/Day of Year Calendar Variation<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">301.0-B-4 correctly notes this fact way down in section B3.4: “…The two ASCII time code variations (A, day of month, and B, day of year) include the most widely used human-readable presentations. Both
variations are subsets of ISO 8601 (reference [2]).”<o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">301.0-B-4 lists ISO 8601:2004 as an informative reference; there are no normative references in the document.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Craig <o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#201747"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#201747"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#201747">Craig Biggerstaff | Leidos</span></b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#7030A0">
<br>
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:gray">Senior Systems Engineering Staff | Civil<br>
phone: 281.483.2027<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#201747"><a href="mailto:craig.biggerstaff@nasa.gov"><span style="color:#201747">craig.biggerstaff@nasa.gov</span></a></span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:gray">
| </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#201747"><a href="http://www.leidos.com/civil"><span style="color:#201747">leidos.com/civil</span></a></span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:gray"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><br>
</span><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#1F497D"><img border="0" width="218" height="53" style="width:2.2708in;height:.552in" id="Picture_x0020_1" src="cid:image001.png@01D2103B.51ED3260" alt="cid:image001.png@01D1F9ED.EA7FBB60"></span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> SEA-SA [mailto:sea-sa-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Estefan, Jeff A (3940)<br>
<b>Sent:</b> Friday, September 09, 2016 3:03 PM<br>
<b>To:</b> sea-sa@mailman.ccsds.org<br>
<b>Subject:</b> Re: [Sea-sa] FW: [CESG] Proposed modification to CCSDS time-code format<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Peter,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Only a preview of the
<a href="https://www.iso.org/obp/ui/#iso:std:iso:8601:ed-3:v1:en">ISO 8601:2004</a> is freely available. As typical with the ISO and ISO/IEC standards many have a cost associated with obtaining copies. I suppose this is one advantage to an open standards specs
such as those from CCSDS. Nevertheless, harmonization should be performed. It should be noted that ISO 8601 is also not new not even as new as the latest rev published in 2004. It goes back to 1988 so close to around the CCSDS spec came about. In any event,
sending this to your distribution list so that hopefully somebody from your team will do the reconciliation.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Cheers!<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> - Jeff<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">Peter Shames <<a href="mailto:Peter.M.Shames@jpl.nasa.gov">Peter.M.Shames@jpl.nasa.gov</a>><br>
<b>Date: </b>Friday, September 9, 2016 at 8:42 AM<br>
<b>To: </b>Jeff Estefan <<a href="mailto:Jeffrey.A.Estefan@jpl.nasa.gov">Jeffrey.A.Estefan@jpl.nasa.gov</a>>, "<a href="mailto:sea-sa@mailman.ccsds.org">sea-sa@mailman.ccsds.org</a>" <<a href="mailto:sea-sa@mailman.ccsds.org">sea-sa@mailman.ccsds.org</a>><br>
<b>Subject: </b>Re: [Sea-sa] FW: [CESG] Proposed modification to CCSDS time-code format<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:black">Hi Jeff,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">The CCSDS time code standard is intended for use everywhere, on the ground and in space. It permits very high resolution time expression, where that is required, but also permits truncation of the time and calendar
fields where the data field size is a concern.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">To be frank, I have not looked at the ISO spec. If you have it and wish to do a comparison, I would welcome that contribution. I will point out that the CCSDS spec has been around since 1987. This is not something
new.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Thanks, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <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="color:black">From: </span></b><span style="color:black">SEA-SA <<a href="mailto:sea-sa-bounces@mailman.ccsds.org">sea-sa-bounces@mailman.ccsds.org</a>> on behalf of Jeffrey Estefan <<a href="mailto:jeffrey.a.estefan@jpl.nasa.gov">jeffrey.a.estefan@jpl.nasa.gov</a>><br>
<b>Date: </b>Friday, September 9, 2016 at 7:53 AM<br>
<b>To: </b>SEA-SA <<a href="mailto:sea-sa@mailman.ccsds.org">sea-sa@mailman.ccsds.org</a>><br>
<b>Subject: </b>Re: [Sea-sa] FW: [CESG] Proposed modification to CCSDS time-code format<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif;color:black"> </span><span style="color:black"><o:p></o:p></span></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"><span style="font-size:10.5pt;color:black">Peter. Just happened to be on your distribution list but had a couple of questions for you. First, do you know if the intended scope of this Blue book standard is for space ground systems or flight
systems or both? We tend to have problems especially with fractional seconds where not only are there inconsistencies in how fractional seconds are treated across the functional areas of our ground systems and applications but even more apparent on the flight
side, particularly how flight software handles this and little consistency among missions. Second, and a more fundamental question. What advantage does the CCSDS Time Code Formats Blue book standard offer over the ubiquitous and heavily reference ISO 8601:2004
standard? I see the latter is referenced in the Blue book but what are the differentiators? Do we need yet another industry standard for time code formats? Just curious. Thanks in advance! - Jeff</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">SEA-SA <<a href="mailto:sea-sa-bounces@mailman.ccsds.org">sea-sa-bounces@mailman.ccsds.org</a>> on behalf of Peter Shames <<a href="mailto:Peter.M.Shames@jpl.nasa.gov">Peter.M.Shames@jpl.nasa.gov</a>><br>
<b>Date: </b>Thursday, September 8, 2016 at 10:33 AM<br>
<b>To: </b>SEA-SA <<a href="mailto:sea-sa@mailman.ccsds.org">sea-sa@mailman.ccsds.org</a>><br>
<b>Subject: </b>[Sea-sa] FW: [CESG] Proposed modification to CCSDS time-code format<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:black">Dear SAWG Colleagues,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">In CCSDS it is typical that cross cutting topics get handled by the SEA Area. Time codes are one such topic and the key CCSDS document defining these now needs to be reviewed. The CESG has asked SEA to do this
and the obvious WG to do this right now is the SAWG.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">The current document, and a proposed page edit with some modifications that make explanatory updates, is attached. The document itself, in its current published form is also attached. Note that the most recent
publication date is Nov 2010. This is a relatively short document, at 43 pages in length, and the normative materials are only 8 of those pages. Aside from it being time to re-confirm this document, what prompted this review was a confusion as to what
was a valid truncation of the time code field, as described on pgs 3-6 and 3-7. This has been discussed and resolved in the CESG. The result was to agree that the document spec was correct as stated, and to acknowledge that it does allow a variety of truncations,
but to clarify what is acceptable by adding the non-normative examples on the “ProposedMods” pages.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">What I would like is to request some help from one of you. Would one of you be willing to take on the task of reviewing this document, and the proposed modifications, and determine if there is anything else in
this document that should be updated? The only other item we know of is a reference in sec 3.5.1.d, pg 3-8, to “the need to accommodate the upcoming century rollover in only 11 years”. Clearly that is now in the past and should be removed.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">If there are only these sort of editorial changes these can easily be accommodated in a Corrigendum or as an editorial matter, but we need someone to review the document and make that determination.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Can I get a volunteer to do this so that we may discuss it, hopefully quickly, during the upcoming working meeting?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Thanks, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <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="color:black">From: </span></b><span style="color:black">CESG <<a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a>> on behalf of Erik Barkley <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>><br>
<b>Date: </b>Tuesday, September 6, 2016 at 4:07 PM<br>
<b>To: </b>CCSDS Engineering Steering Group - CESG Exec <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><br>
<b>Subject: </b>[CESG] Proposed modification to CCSDS time-code format<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif;color:black"> </span><span style="color:black"><o:p></o:p></span></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="color:black">CESG Colleagues,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Based on the interactions/e-mails from Gippo, Mario, and Peter, attached please find a proposal for update of the timecode blue book. By way of summary, I found that the language, upon close reading, was essentially
okay and that it really already allows for fractional seconds to be optional in either timecode A or timecode B and in fact abbreviations/omissions in other respects as well. I took advantage of the examples offered by Mario as I believe these help to make
to illustrate more clearly how the rules of abbreviation can be applied. I look forward to discussing this at the CESG telecon/webex tomorrow.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-Erik<o:p></o:p></span></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</body>
</html>