<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;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
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:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Georgia",serif;
color:#1F497D;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:829103613;
mso-list-type:hybrid;
mso-list-template-ids:1267360110 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">Colin,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">I have managed to take a quick review of the updated recommendation in the schema and it looks like it is going the right direction. I do have some comments.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;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:"Georgia",serif;color:#1F497D"><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-family:"Georgia",serif;color:#1F497D">Perhaps we could consider classifying these as "geometry" (short of communication geometry) events or something like that rather than “comms”. The rationale is that eventually
we do have a future issue or issues of the PIF planned with further planning types which include data rate and volume estimates. I think something like this could perhaps be more directly considered as communication (presumably getting into things like link
margin etc.) whereas the information we have currently in the PIF is really about the geometry surrounding the communication and not so much the communication per se<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:"Georgia",serif;color:#1F497D"><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-family:"Georgia",serif;color:#1F497D">I saw the identifier element optionally included in selected event definitions in the instance example but I don't see a corresponding parameter listed in the UML model?
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:"Georgia",serif;color:#1F497D"><span style="mso-list:Ignore">3)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-family:"Georgia",serif;color:#1F497D">I don't really see the planetary surface other than earth use case being accommodated yet in the PIF. I suspect that has to do with it being back in July that this was discussed
and it isn't necessarily on the "front burner" so to speak. Attached is a PowerPoint presentation that has some suggestions for inclusion of this use case. My rationale for suggesting the inclusion of this use case is that there has been a fair amount of progress
in the SIS area with regard to DTN and I think we will need to address this use case sooner or later and as I think that that it is not that much of a stretch sooner would be better.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">Perhaps we can discuss these at the upcoming working group teleconference.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> SMWG [mailto:smwg-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Colin.Haddow@esa.int<br>
<b>Sent:</b> Tuesday, January 30, 2018 5:30 AM<br>
<b>To:</b> CCSDS SMWG ML(smwg@mailman.ccsds.org) <smwg@mailman.ccsds.org><br>
<b>Subject:</b> [Smwg] 902x2-w0.16 - Planning Information Formats - Updated draft<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear all,</span>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
I've just uploaded the latest draft of the Planning Information Formats Book to CWE, This contains the updates discussed at San Antonio and Den Haag. I've also uploaded the updated UML model and Schemas. Note that the UML model and the schemas
also contain the updates required for the revised Service Management Common Data Entities Book.
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Also included in the Schemas are a couple of examples for the Planning Information, along with the extra schema required to get the extended Planning Information to work.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
The Planning Information Formats document, model and schemas can be found at the following URLs.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Document: </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.16%20-%20Planning%20Information%20Formats.doc"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.16%20-%20Planning%20Information%20Formats.doc</span></a><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Model: </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.16%20-%20Planning%20Information%20Formats%20-%20UmlModel.zip"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.16%20-%20Planning%20Information%20Formats%20-%20UmlModel.zip</span></a><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Schemas: </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.16%20-%20Planning%20Information%20Formats%20-%20Schema.zip"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.16%20-%20Planning%20Information%20Formats%20-%20Schema.zip</span></a><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Cheers for now,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Colin</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
<br>
---------------------------------------------------------------------------------------------------------<br>
Dr. Colin R. Haddow,<br>
HSO-GI, European Space Agency,<br>
European Space Operations Centre,<br>
Robert-Bosch-Str 5,<br>
64293 Darmstadt,<br>
Germany.<br>
<br>
Phone; +49 6151 90 2896<br>
Fax; +49 6151 90 3010<br>
E-Mail; <a href="mailto:colin.haddow@esa.int">colin.haddow@esa.int</a><br>
---------------------------------------------------------------------------------------------------------<br>
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
<br>
</span><o:p></o:p></p>
<pre>This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre>content is not permitted.<o:p></o:p></pre>
<pre>If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Please consider the environment before printing this email.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
</div>
</body>
</html>