<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";
color:black;}
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.Appendix2, li.Appendix2, div.Appendix2
{mso-style-name:"Appendix 2";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:12.0pt;
margin-left:.3in;
text-align:justify;
text-indent:-.3in;
page-break-after:avoid;
mso-list:l0 level1 lfo1;
font-size:12.0pt;
font-family:Arial;
font-variant:small-caps;
color:black;
font-weight:bold;}
span.EmailStyle18
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Courier;
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:62260251;
mso-list-template-ids:-2069711860;}
@list l0:level1
{mso-level-style-link:"Appendix 2";
mso-level-text:%1;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.3in;
text-indent:-.3in;}
@list l0:level2
{mso-level-text:"%1\.%2";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.4in;
text-indent:-.4in;}
@list l0:level3
{mso-level-text:"%1\.%2\.%3";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.5in;
text-indent:-.5in;}
@list l0:level4
{mso-level-text:"%1\.%2\.%3\.%4";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.6in;
text-indent:-.6in;}
@list l0:level5
{mso-level-text:"%1\.%2\.%3\.%4\.%5";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.7in;
text-indent:-.7in;}
@list l0:level6
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.8in;
text-indent:-.8in;}
@list l0:level7
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.9in;
text-indent:-.9in;}
@list l0:level8
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.0in;
text-indent:-1.0in;}
@list l0: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:1.1in;
text-indent:-1.1in;}
@list l1
{mso-list-id:368724916;
mso-list-template-ids:184567062;}
@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:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@list l2
{mso-list-id:1933388943;
mso-list-template-ids:1018827186;}
@list l2: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 l2: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 l2: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 l2: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 l2: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 l2: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 l2: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 l2: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 l2: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>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:Courier;color:windowtext">All:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier;color:windowtext">Second of 2 emails related to event definitions for the CCSDS.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier;color:windowtext">David<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier;color:windowtext"><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">From: </span></b><span style="font-family:Calibri">"Barkley, Erik J (3970)" <erik.j.barkley@jpl.nasa.gov><br>
<b>Date: </b>Tuesday, September 6, 2016 at 5:20 PM<br>
<b>To: </b>Sam Cooper <sam@brightascension.com>, Colin Haddow <Colin.Haddow@esa.int>, Mehran Sarkarati <Mehran.Sarkarati@esa.int>, "Berry, David S (3920)" <david.s.berry@jpl.nasa.gov><br>
<b>Cc: </b>Mario Merri <Mario.Merri@esa.int>, Dan Smith <danford.s.smith@nasa.gov><br>
<b>Subject: </b>RE: CCSDS Events for Nav, CSS, and MO<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D">Dear Sam,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D">There has been a bit of development/refinement on the CSSM side with regard to the event definition. Please see below.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D">The key items to note are the ability to make the uncertainty window around an event asymmetric and the ability to allow for agency specific extensions in a controlled/flexible
manner while retaining a core inter-operable data format. This is essentially what is addressed via the abstract parameter definition with several simple types for simple extensions and a complex type should an agency really need to state something involved.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D">With regard to your observation that this is aimed at future/predicted event definitions that is correct. In general I suspect that when dealing with a stream of actual events,
there really would no longer be an uncertainty window (then again, on board clocks often drift – especially for spacecraft in deep space).
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D">The Rome meetings for me are rather difficult to arrange as I have other unmovable commitments such that I will only be attending from Wednesday on of the technical week.
Nonetheless, perhaps you, Colin, and David (whom I have asked via separate email), could get together for a joint session at the Rome meetings. Alternatively, considering that planning for various working groups/agendas is already likely quite advanced, we
could arrange to have a telecon, post Rome, leading to a joint session at the San Antonio (spring ’17) meetings.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D">Best regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D">-Erik</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><a name="_Toc447576515"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D"><img width="598" height="550" id="Picture_x005f_x0020_1" src="cid:image001.png@01D221FF.93D3E400"></span></a><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:Calibri;color:windowtext">From:</span></b><span style="font-size:11.0pt;font-family:Calibri;color:windowtext"> Sam Cooper [mailto:sam@brightascension.com]
<br>
<b>Sent:</b> Monday, July 04, 2016 4:21 AM<br>
<b>To:</b> Barkley, Erik J (3970) <erik.j.barkley@jpl.nasa.gov>; Colin Haddow <Colin.Haddow@esa.int>; Mehran Sarkarati <Mehran.Sarkarati@esa.int>; Berry, David S (3920) <david.s.berry@jpl.nasa.gov><br>
<b>Cc:</b> Mario Merri <Mario.Merri@esa.int>; Dan Smith <danford.s.smith@nasa.gov><br>
<b>Subject:</b> CCSDS Events for Nav, CSS, and MO</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Dear All,<br>
<br>
I took the task in Cleveland to review the information sent out on the definition of an Event from joint sessions between Nav and CSS. This was with respect to how MO defines and uses events.<br>
<br>
The diagram I am working from is this one:<br>
<br>
<img width="510" height="375" id="_x0000_i1025" src="cid:image002.png@01D221FF.93D3E400"><br>
<br>
The first thing that occurs to me is that these events seem to be focussed on predicted, future, events (which is understandable) whereas MO events are things that have happened as it is event reporting rather than event prediction.<br>
<br>
Using a similar approach, our events contain (this is a simplified view):<o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level1 lfo4">
Timestamp of event (absolute)<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level1 lfo4">
Source of Event<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level1 lfo4">
Event type number<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level1 lfo4">
Event instance number<o:p></o:p></li></ul>
<p class="MsoNormal" style="margin-bottom:12.0pt">Then the body of the event is specific to that event type.<br>
<br>
So our definition of event is a little lower level than either of the existing event definitions. We also have a specific "type" of event called an Alert which extends the event specification to have a body which contains a set of Name/Value argument pairs
(whether you call them arguments or parameters is moot, they achieve the same effect).<br>
<br>
So, for me the next step is probably for you to send me any more information you have on any more work done by you in this area. If this is still the current state then I think it would be interesting to have a short teleconference to discuss what we think
the next steps could be. It looks like we all have a basic similar outlook on events ( a timestamped "thing") but probably have different ideas on their usage (MO is for reporting, whereas Nav is probably more predicted?).<br>
<br>
I would also encourage the MOIMS Planning WG to have an opinion on this as they are certainly going to be a heavy user of both any Nav events but also CSS events for tracking any contact information.<br>
<br>
How does this look to everybody?<br>
<br>
Best regards,<br>
Sam.<o:p></o:p></p>
</div>
</body>
</html>