<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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Webdings;
panose-1:5 3 1 2 1 5 9 6 7 3;}
/* 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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
p.Textebrut, li.Textebrut, div.Textebrut
{mso-style-name:"Texte brut";
mso-style-link:"Texte brut Car";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.TextebrutCar
{mso-style-name:"Texte brut Car";
mso-style-priority:99;
mso-style-link:"Texte brut";
font-family:"Calibri",sans-serif;}
span.EmailStyle23
{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:70.85pt 70.85pt 70.85pt 70.85pt;}
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:#2E75B6;mso-style-textfill-fill-color:#2E75B6;mso-style-textfill-fill-alpha:100.0%">Dear Claudia,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#2E75B6;mso-style-textfill-fill-color:#2E75B6;mso-style-textfill-fill-alpha:100.0%">It was certainly the intent that any extensions to the TGFT manifest schema must be done through the
</span><b><span style="color:#2E75B6;mso-style-textfill-fill-color:#2E75B6;mso-style-textfill-fill-alpha:100.0%">TgftXfduExtensionType</span></b><span style="color:#2E75B6;mso-style-textfill-fill-color:#2E75B6;mso-style-textfill-fill-alpha:100.0%"> complex
schema type, which is applied to the (structured) extension element. However, the TGFT XFDU specification currently does not forbid any user-application-specific use of the (unstructured) xmlData elements. Are you proposing that user applications (e.g., a
validated radiometric data service) be forbidden from using the xmlData elements, or simply that the wording perhaps be strengthened to emphasize that the TGFT-standard XFDU will never be changed to include extension via the xmlData elements? (Another topic
for discussion next week?)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#2E75B6;mso-style-textfill-fill-color:#2E75B6;mso-style-textfill-fill-alpha:100.0%"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#2E75B6;mso-style-textfill-fill-color:#2E75B6;mso-style-textfill-fill-alpha:100.0%">Best regards,
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#2E75B6;mso-style-textfill-fill-color:#2E75B6;mso-style-textfill-fill-alpha:100.0%">John
</span><span style="color:#2E75B6;mso-style-textfill-fill-color:#2E75B6;mso-style-textfill-fill-alpha:100.0%"><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> Ciocirlan Claudia [mailto:Claudia.Ciocirlan@cnes.fr]
<br>
<b>Sent:</b> Tuesday, March 20, 2018 5:54 AM<br>
<b>To:</b> John Pietras <john.pietras@gst.com>; Colin Haddow/esoc/ESA <Colin.Haddow@esa.int>; CCSDS Service Mgmt WG <smwg@mailman.ccsds.org><br>
<b>Subject:</b> [Smwg] TGFT environmentInfo and new TestPlan version<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="FR">Hello,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR"><o:p> </o:p></span></p>
<p class="MsoPlainText">Sorry for sending you several small emails, I have yet another minor remark on the specification.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">XFDU defines an extension mechanism based on environmentInfo elements.
<o:p></o:p></p>
<p class="MsoPlainText">One such element is mandatory for a TGFT manifest (section 4.2.5.6.1).
<o:p></o:p></p>
<p class="MsoPlainText">The extension subelement of this element must be typed as a TgftXfduExtensionType element.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">An environmentInfo element may also hold xmlData elements, for unstructured XML. I believe that the choice of using a structured element in extension should lead to not using the xmlData fields.
<o:p></o:p></p>
<p class="MsoPlainText">However this is not forbidden by the XFDU specification, and nothing is said about this in the TGFT specification. I would suggest to add a constraint in the TGFT specification, that the environmentInfo element holding the tgft extension
does not hold any xmlData elements. What would you think,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have just uploaded a new version of the TGFT test plan with minor changes on cwe.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal"><span lang="FR">Claudia<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span lang="IT" style="font-size:9.0pt;font-family:"Arial",sans-serif;mso-fareast-language:FR">Claudia Ciocirlan
</span></b><span lang="IT" style="font-size:9.0pt;font-family:"Arial",sans-serif;mso-fareast-language:FR">CNES/DNO/OP/SSO<b><o:p></o:p></b></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;mso-fareast-language:FR">Mission Operations Ground Segment<br>
phone : +33 (0)5 61 28 17 11<br>
email : </span><span lang="FR" style="font-size:9.0pt;font-family:"Arial",sans-serif;mso-fareast-language:FR"><a href="mailto:claudia.ciocirlan@cnes.fr"><span lang="EN-US" style="color:blue">claudia.ciocirlan@cnes.fr</span></a></span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;mso-fareast-language:FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="FR" style="font-size:14.0pt;font-family:Webdings;color:green;mso-fareast-language:FR">P</span><span lang="FR" style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black;mso-fareast-language:FR">
</span><i><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:green;mso-fareast-language:FR">Save a tree ! Think before printing
</span></i><b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;mso-fareast-language:FR"><o:p></o:p></span></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>