<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 12px; font-family: Courier, sans-serif;">
<div><br>
</div>
<div>Dave:</div>
<div><br>
</div>
<div>Thanks for your comments. I appreciate it.</div>
<div><br>
</div>
<div>1. No one of us can deprecate the OMM. Your position is noted. We will discuss this at the Darmstadt meetings in November.</div>
<div><br>
</div>
<div>2. The Orbit Hybrid Message (proposed name) is a direct result of a decision by the CCSDS Navigation WG during the CCSDS-mandated 5 year review of the ODM standard. This review process has 3 outcomes: reconfirm, retire, revise. "Retire" was obviously
inappropriate, and we had several requests for revisions, so "reconfirm" was also not appropriate. "Revise" was the consensus decision. We are currently very early in the revision process and I believe it is impossible at this point to correctly predict
exactly what will emerge from the process. As you have noted, several of my comments suggest discussion of specific points at Darmstadt... I don't see this as any kind of weakness whatsoever. It means that I think it will be more productive to entertain
a face-to-face discussion on those matters rather than an email discussion.</div>
<div><br>
</div>
<div>3. You are of course welcome to discuss and present the ODM revision drafts within SC14/WG3, and to forward the working draft to WG3. Given that the revision drafts of the ODM are being prepared by Dan Oltrogge (WG3 member), and the fact that you are
a member of both WGs (along with Reinhard Kiehling and Ma Chaowei per the WG3 roster), I believe that to a certain extent the negotiation process to which you refer is at least partially underway.</div>
<div><br>
</div>
<div>Regards,</div>
<div>David</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>David Finkleman <<a href="mailto:finklemand@skysentry.net">finklemand@skysentry.net</a>><br>
<span style="font-weight:bold">Date: </span>Sunday, June 28, 2015 at 12:51 PM<br>
<span style="font-weight:bold">To: </span>"<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>>, David Berry <<a href="mailto:David.S.Berry@jpl.nasa.gov">David.S.Berry@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [MOIMS-NAV-EXEC] Re: ODM v.2.30 Draft for your review...<br>
</div>
<div><br>
</div>
<div>
<div bgcolor="#FFFFFF" text="#000000">My comments are broad and cannot be expressed with respect to specific clauses.<br>
<br>
First, the Mean Elements Message should be deprecated. The intent was to supplant the Two Line Element Set with more efficient and widely applicable format. Russia, for example, uses a different mean element model, and several providers use models descended
from Paul Cefola's DSST model based on equinoctical elements. The goal was not achieved. TLE's persist and are incontrovertibly institutionalized despite their well demonstrated deficiencies.<br>
<br>
Second, the Orbit Hybrid Message should be omitted. There are many substantive comments on the proposed Hybrid message whose resolution is to defer until the next meeting. In addition, a standard with a preponderance of optional elements is not a standard.
We faced a similar issue with the CDM. What is required is consensus on the minimum necessary for effective use. The credibility of a provider is questionable when essential information is missing. Optional elements are not the prerogative of the provider.
They must be negotiated between provider and recipient. This not a standard; it is an ICD. Anything private between two parties is not a standard. In fact, 26699 states that it is a guide for those who wish private agreements.<br>
<br>
Finally, SC14/WG3 is the designated parallel developer, demonstrated by the agreement between SC13 and SC14 that led to the ISO registration with an SC14 designator. This must be negotiated among SC14/WG3 members.<br>
<br>
Respectfully,<br>
<br>
Dave Finkleman<br>
<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 6/28/2015 11:59 AM, Berry, David S (3920) wrote:<br>
</div>
<blockquote cite="mid:D1B57C53.9659D%25david.s.berry@jpl.nasa.gov" type="cite">
<div><br>
</div>
<div>Dan:</div>
<div><br>
</div>
<div>I've attached my review comments of the ODM P2.30, primarily for sections 2 and 6, with a few Mfor Annex A. A number of the suggested changes could affect section 7, so I excluded that from consideration at this time.</div>
<div><br>
</div>
<div>Regards,</div>
<div>David</div>
<div><br>
</div>
<div>P.S.: To all in the WG... please try to complete your ODM review assignment as soon as possible (Section 2, 6, and Annex A... we can deal with other sections in future drafts). I'm not sure how much feedback Dan has received to date but our target date
was 15-Jun-2015 (YES, I'm late too...).</div>
<div><br>
</div>
<div>Thanks!</div>
<div>DSB</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt;
text-align:left; color:black; BORDER-BOTTOM: medium none;
BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT:
0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;
BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>"Oltrogge, Daniel" <<a moz-do-not-send="true" href="mailto:doltrogge@agi.com">doltrogge@agi.com</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, April 9, 2015 at 8:43 AM<br>
<span style="font-weight:bold">To: </span>"<a moz-do-not-send="true" href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a>" <<a moz-do-not-send="true" href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Cc: </span>David Berry <<a moz-do-not-send="true" href="mailto:David.S.Berry@jpl.nasa.gov">David.S.Berry@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Subject: </span>ODM v.2.30 Draft for your review...<br>
</div>
<div><br>
</div>
<div xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<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-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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]-->
<div link="#0563C1" vlink="#954F72" lang="EN-US">
<div class="WordSection1">
<p class="MsoNormal">Per my ODM revision action item, here is draft ODM v.2.30 which incorporates all of the 15 suggested revisions that you kindly provided me at the Pasadena CCSDS meeting.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal"><br>
Dan<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Daniel L. Oltrogge<o:p></o:p></p>
<p class="MsoNormal">SDC Program Manager & Senior Research Astrodynamicist<o:p></o:p></p>
<p class="MsoNormal">Center for Space Standards and Innovation<o:p></o:p></p>
<p class="MsoNormal">Analytical Graphics Incorporated<o:p></o:p></p>
<p class="MsoNormal">Voice: 719-660-5142; E-mail: <a moz-do-not-send="true" href="mailto:oltrogge@agi.com">
oltrogge@agi.com</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</span><br>
<fieldset class="mimeAttachmentHeader"></fieldset> <br>
<pre wrap="">_______________________________________________
MOIMS-NAV-EXEC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:MOIMS-NAV-EXEC@mailman.ccsds.org">MOIMS-NAV-EXEC@mailman.ccsds.org</a><a class="moz-txt-link-freetext" href="http://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-nav-exec">http://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-nav-exec</a></pre>
</blockquote>
<br>
</div>
</div>
</span>
</body>
</html>