<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)">
<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;}
/* 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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle18
{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;}
--></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">Jessica,<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 think this is fine. I read the 3<sup>rd</sup> paragraph as essentially book keeping. In general, I think we have another instance of the “loose-leaf binder” approach if/when the NAVWG defines a new type of
trajectory data format. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><br>
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">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> smwg-bounces@mailman.ccsds.org [mailto:smwg-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Reinert, Jessica (GRC-LSA0)<br>
<b>Sent:</b> Tuesday, May 05, 2015 9:10 AM<br>
<b>To:</b> CCSDS Service Mgmt WG (smwg@mailman.ccsds.org)<br>
<b>Subject:</b> [Smwg] Email documenting discussion towards closure of AI 2015-0325-2<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Greetings,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As a part of the May 5 telecom, we discussed whether or not the bilateralTrajectorySegment class should be explicitly defined as a subclass within the TrajectoryPredictionInformation. During the spring meeting two options had been proposed:
either retaining this subclass or just mentioning the potential use of a bilaterally agreed upon format in place of the defined ccsdsTrajectorySegment.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">During the telecom I believe it was agreed that we should go with the latter option of mentioning the use of a bilateral trajectory segment within the text, but not defining the class. The standard header trajectoryPredictionInformation
and the Service Management Standard Header are still required if a bilaterally agreed upon format is used.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There is a potential that new CCSDS Standard Trajectory segments will be defined by the Navigation Data Group, in addition to those currently defined, the use of a bilaterally agreed upon format will be mentioned in the document when this
potential is mentioned.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Any suggestions or clarification regarding this matter are appreciated.<o:p></o:p></p>
<p class="MsoNormal"><br>
Regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jessica<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#44546A">Jessica Reinert<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#44546A">Systems Definition and Communications Branch<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#44546A">NASA Glenn Research Center<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#44546A">Phone: 216-433-6249<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>