<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Segoe UI",sans-serif;}
p.Textedebulles, li.Textedebulles, div.Textedebulles
{mso-style-name:"Texte de bulles";
mso-style-link:"Texte de bulles Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma",sans-serif;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle28
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></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 bgcolor="white" lang="EN-GB" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">Hi all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">My contribution elaborating on top of Alain’s document.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">I have tried to remove the many ORs to provide something a bit more terse. The many options address many details but in the end I got somehow lost in the branching. I think that what
I have provided tackles all options in Alain’s document and dare say that the scheme covers all possibilities in one way or another by formulating the requirements in a different manner. The text in blue in the requirements is added around Alain’s to address
some of these aspects and get rid of the many ORs.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">Of course it is my view on the matter, hence XML/UML oriented somehow. For this I have also read Dan’s and Cheryl’s emails. Not everything is address but just what I believe is relevant
for the discussion with CSSM (e.g. Cheryl’s cross-strapping of times is not whereas Dan’s concerns about referencing to common/relative/absolute times is covered).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">I attach Alain’s document with the mentioned evolutions and comments to the final section that I think is of general interest.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">I am also attaching an example with comments of a possible events file (I use the term container in the document for generality) that I think is compatible with everybody’s (most everybody
I hope) comments. I already provided a first version to Alain, Dale and Dan at the meeting in Rome but we did not have the chance to look at it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">Fran<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> MOIMS-NAV-EXEC [mailto:moims-nav-exec-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Lamy Alain<br>
<b>Sent:</b> viernes, 4 de noviembre de 2016 09:51<br>
<b>To:</b> moims-nav-exec@mailman.ccsds.org<br>
<b>Subject:</b> Re: [MOIMS-NAV-EXEC] ARE: Notional Events requirements from NAV WG<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Hi, <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">So here is my proposal:
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">“slightly” different from what Dan initially proposed, but I tried to make each requirement as atomic as possible.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">I tried to list all possibilities, so some options will have to be removed (depending on what you think).
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">I also highlighted a few words in order to make the reading easier.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">What do you think ?
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Of course you may change/adapt as you like to make things clearer or if you think elements are missing.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Alain<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New";color:#1F497D">Alain Lamy<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New";color:#1F497D">CNES DCT/SB/MS - Bpi 1324<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New";color:#1F497D">18, Av. Edouard Belin | Tel : 05 61 27 35 61<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR" style="font-size:10.0pt;font-family:"Courier New";color:#1F497D">31401 Toulouse Cedex 9 | Fax : 05 61 28 25 40<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR" style="font-size:10.0pt;font-family:"Courier New";color:#1F497D">France | Email :
<a href="mailto:Alain.Lamy@cnes.fr"><span style="color:blue">Alain.Lamy@cnes.fr</span></a></span><span lang="FR" style="color:#1F497D"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="FR" style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif">De :</span></b><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> MOIMS-NAV-EXEC [<a href="mailto:moims-nav-exec-bounces@mailman.ccsds.org">mailto:moims-nav-exec-bounces@mailman.ccsds.org</a>]
<b>De la part de</b> Lamy Alain<br>
<b>Envoyé :</b> jeudi 20 octobre 2016 14:22<br>
<b>À :</b> Gramling, Cheryl J. (GSFC-5950); Oltrogge, Daniel<br>
<b>Cc :</b> <a href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a><br>
<b>Objet :</b> [MOIMS-NAV-EXEC] ARE: Notional Events requirements from NAV WG<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Just one comment : <o:p>
</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Having more than one (absolute or relative) time is associated with an event may cause confusion :
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">The time associated with an event enables defining an “order”.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">But if there are 2 different time references, you may have :
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR" style="color:#1F497D">T1(event a) < T1(event b)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR" style="color:#1F497D">T2(event a) > T2(event b)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">This would be not consistent.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">(to avoid this, T1 and T2 would have to be guaranteed equivalent, which is difficult to achieved).
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">But I suppose there are other ways :
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">It should (and this could be a new requirement) to add information (that is to say data) to an event.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">This could for instance allow adding timing information or anything else that may be useful to the user of the event
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">(in some particular context).
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">PS: I’ll answer the 1<sup>st</sup> message from Dan later<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Alain<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="FR" style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif">De :</span></b><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> MOIMS-NAV-EXEC [<a href="mailto:moims-nav-exec-bounces@mailman.ccsds.org">mailto:moims-nav-exec-bounces@mailman.ccsds.org</a>]
<b>De la part de</b> Gramling, Cheryl J. (GSFC-5950)<br>
<b>Envoyé :</b> jeudi 20 octobre 2016 14:05<br>
<b>À :</b> Oltrogge, Daniel; <a href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a><br>
<b>Objet :</b> Re: [MOIMS-NAV-EXEC] Notional Events requirements from NAV WG<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="FR"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Ah, well, now you raise a good point. <o:p>
</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I wasn’t thinking of 2 different absolute time scales or even 2 different absolute time epochs, associated w 2 (or more) relative times; merely 2 different relative time scales referenced to the same absolute scale/epoch.
In my case [1@ABS:2@REL], you could identify RELTIME_1,….RELTIME_n.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">If we try to address your point, it seems you’d need a way to define cross-strapping of the systems. ABSTIME_1,…ABSTIME_n to each of RELTIME_1,…RELTIME_n :<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> RELTIME_1_1<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> RELTIME_1_2<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> :<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> RELTIME_1_n<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> RELTIME_2_1<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> RELTIME_2_2<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> :<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> RELTIME_2_n<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> :<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">where the second number refers to the ABSTIME.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">How often would more than one ABSTIME [SYS or SCAL] be used? I can’t think of any examples. However, I do think at least 2 different RELTIME [SYS] would be used somewhat frequently.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Cheryl<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="color:black">From: </span></b><span lang="EN-US" style="color:black">"Oltrogge, Daniel" <<a href="mailto:doltrogge@agi.com">doltrogge@agi.com</a>><br>
<b>Date: </b>Thursday, October 20, 2016 at 1:46 PM<br>
<b>To: </b>"Gramling, Cheryl J. (GSFC-5950)" <<a href="mailto:cheryl.j.gramling@nasa.gov">cheryl.j.gramling@nasa.gov</a>>, "<a href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a>" <<a href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a>><br>
<b>Subject: </b>RE: [MOIMS-NAV-EXEC] Notional Events requirements from NAV WG</span><span lang="EN-US" style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">You raise a very good point. And that’s fundamentally different that what I’d assembled below.</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Any suggestions on how we could potentially reference the different relative times to their respective absolute times in a non-confusing, rigorous way ?</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Thanks,</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><br>
Dan</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Daniel L. Oltrogge</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">SDC Program Manager & Senior Research Astrodynamicist</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Center for Space Standards and Innovation</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Analytical Graphics Incorporated</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR" style="color:#1F497D">Voice: 719-482-4552; E-mail:
</span><span lang="EN-US" style="color:#1F497D"><a href="mailto:oltrogge@agi.com"><span lang="FR">oltrogge@agi.com</span></a></span><span lang="FR"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="FR" style="color:#1F497D"> </span><span lang="FR"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Gramling, Cheryl J. (GSFC-5950) [<a href="mailto:cheryl.j.gramling@nasa.gov">mailto:cheryl.j.gramling@nasa.gov</a>]
<br>
<b>Sent:</b> Thursday, October 20, 2016 5:07 AM<br>
<b>To:</b> Oltrogge, Daniel <<a href="mailto:doltrogge@agi.com">doltrogge@agi.com</a>>;
<a href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a><br>
<b>Subject:</b> Re: [MOIMS-NAV-EXEC] Notional Events requirements from NAV WG<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Dan,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I think we need a requirement that more than one relative time may optionally be associated with an event [e.g. the case of UTC relative time and Spacecraft Clock relative time].<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Should it explicitly be stated that both an absolute and a relative time may optionally be associated with an event, or does the “or” in Req 3.a adequately cover that?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Thanks for putting this together.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Cheryl<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="color:black">From: </span></b><span lang="EN-US" style="color:black">MOIMS-NAV-EXEC <<a href="mailto:moims-nav-exec-bounces@mailman.ccsds.org">moims-nav-exec-bounces@mailman.ccsds.org</a>> on behalf of "Oltrogge,
Daniel" <<a href="mailto:doltrogge@agi.com">doltrogge@agi.com</a>><br>
<b>Date: </b>Wednesday, October 19, 2016 at 4:57 PM<br>
<b>To: </b>"<a href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a>" <<a href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a>><br>
<b>Subject: </b>[MOIMS-NAV-EXEC] Notional Events requirements from NAV WG</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Times New Roman",serif"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">Particularly for Fran, Dale and Alain (but feedback from all welcomed):<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Here’s a rough draft of the NAV WG requirements for us to send to Colin regarding the events message…<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span lang="EN-US">(1)</span><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">The elements of information that are *<b>not</b>* associated with timing systems that are in the current rough draft Events Message look okay;<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span lang="EN-US">(2)</span><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">In a parent segment, a global absolute reference epoch <u>
may</u> be specified.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt"><span lang="EN-US">a.</span><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">For this reference epoch, the <b>optional</b> capability is required to specify the time scale upon which this absolute reference epoch is based. If not specified, then the global absolute reference epoch’s time scale shall default
to UTC.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span lang="EN-US">(3)</span><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">Multiple events can be declared within a global object.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt"><span lang="EN-US">a.</span><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">For each of these events, the event’s timing <b>may optionally</b> be specified as relative or absolute. If not specified, the event’s timing defaults to absolute.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt"><span lang="EN-US">b.</span><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">When absolute timing is used:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-9.0pt"><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">i.</span><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">The timescale of that event-unique absolute time <b>may optionally</b> be set. If not specified, then the event-unique absolute reference epoch’s time scale shall default to UTC.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt"><span lang="EN-US">c.</span><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">When relative timing is used:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-9.0pt"><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">i.</span><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">An event-unique absolute reference epoch to which this relative timing is measured
<b>may optionally</b> be specified.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-9.0pt"><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">ii.</span><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">If an event-unique absolute reference epoch is specified, then the time scale upon which that event-unique absolute reference epoch is based
<b>may optionally</b> be specified. If not specified, then the event-unique absolute reference epoch’s time scale shall default to UTC.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-9.0pt"><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">iii.</span><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">If an event-unique absolute reference epoch is not specified, then it is
<b>mandatory</b> that a global absolute reference epoch is specified.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-9.0pt"><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">iv.</span><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">If both a global and an event-unique absolute reference epoch are specified, the event-unique absolute reference epoch shall
<b>override</b> the global absolute reference epoch for that event.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-9.0pt"><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">v.</span><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span lang="EN-US">The timescale of the event relative time <b>may optionally</b> be set. If not specified, then the timescale shall default to UTC seconds.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><br>
Dan<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Daniel L. Oltrogge<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">SDC Program Manager & Senior Research Astrodynamicist<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Center for Space Standards and Innovation<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Analytical Graphics Incorporated<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Voice: 719-482-4552; E-mail: <a href="mailto:oltrogge@agi.com">
oltrogge@agi.com</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<span style=""><br>
</span><span style="font-size:18.0pt; line-height:125%; font-family:Webdings; color:green">P<span style=""></span>
<span style="font-size:7.0pt; line-height:125%; font-family:"Arial","sans-serif"; color:green">
Please consider the environment before printing this e-mail.</span></span><span style=""></span>
<p>
<! English>
<font size=1 color=gray face=Arial><span style='font-size:
8.0pt;font-family:Arial;color:gray'><hr size=2 width='100%' align=center>
This message including any attachments may contain confidential information,
according to our Information Security Management System, and intended solely
for a specific individual to whom they are addressed. Any unauthorised copy,
disclosure or distribution of this message is strictly forbidden. If you have
received this transmission in error, please notify the sender immediately and delete it.
</span></font>
<! Spanish>
<font size=1 color=gray face=Arial><span style='font-size:
8.0pt;font-family:Arial;color:gray'><hr size=2 width='100%' align=center>
Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener
informacin clasificada por su emisor como confidencial en el marco de su
Sistema de Gestin de Seguridad de la Informacin siendo para uso
exclusivo del destinatario, quedando prohibida su divulgacin copia o
distribucin a terceros sin la autorizacin expresa del remitente.
Si Vd. ha recibido este mensaje errneamente, se ruega lo notifique al
remitente y proceda a su borrado.
</span></font><font size=1 color=gray face=Arial><span lang=EN-GB
style='font-size:8.0pt;font-family:Arial;color:gray'>Gracias por su
colaboracin.<o:p></o:p></span></font>
<! Portuguese>
<font size=1 color=gray face=Arial><span style='font-size:
8.0pt;font-family:Arial;color:gray'><hr size=2 width='100%' align=center>
Esta mensagem, incluindo qualquer ficheiro anexo, pode conter informao confidencial,
de acordo com nosso Sistema de Gesto de Segurana da Informao, sendo para uso exclusivo
do destinatrio e estando proibida a sua divulgao, cpia ou distribuio a terceiros
sem autorizao expressa do remetente da mesma. Se recebeu esta mensagem por engano,
por favor avise de imediato o remetente e apague-a.
</span></font><font size=1 color=gray face=Arial><span lang=EN-GB
style='font-size:8.0pt;font-family:Arial;color:gray'>Obrigado pela sua colaborao.
<o:p></o:p></span></font>
<hr size=2 width='100%' align=center></p>
</body>
</html>