<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;}
@font-face
{font-family:Monaco;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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.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;}
--></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">Holger,<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">Thanks for reviewing the schema. A couple of comments in return. Please see below.<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>Holger.Dreihahn@esa.int<br>
<b>Sent:</b> Tuesday, December 19, 2017 12:45 AM<br>
<b>To:</b> smwg@mailman.ccsds.org<br>
<b>Subject:</b> [Smwg] Response to Action Item 2017-1106-03 - Verify TGFT schema<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear WG Colleagues,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Reviewing the XFDU schema I have no major comments, in general it looks OK to me. It has an own namespace, which believe is in line with the current namespace policy.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">More detailed, I have the following observations / comments:</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">HD-1: The reference to the file itself is just a string:
</span><span style="font-size:10.0pt;font-family:"Monaco",serif;color:teal"><</span><span style="font-size:10.0pt;font-family:"Monaco",serif;color:#3F8080">xsd:attribute</span><span style="font-size:10.0pt;font-family:"Monaco",serif">
<span style="color:purple">name</span>=<i><span style="color:#4200FF">"href"</span></i>
<span style="color:purple">type</span>=<i><span style="color:#4200FF">"xsd:string"</span></i><span style="color:teal">/></span></span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I do not know if the use of xlink has been considered, in my mind it is the standard XML way of linking files:
</span><a href="https://en.wikipedia.org/wiki/XLink"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">https://en.wikipedia.org/wiki/XLink</span></a>
<span style="color:#1F497D"><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">eb> That seems like a very reasonable approach. Given that the TGFT schema is essentially a restriction on the XFDU schema I have to wonder if this would "break" anything from a larger
XFDU point of view. And it may be that the XFDU schema in general was developed before XLink existed or simply unaware of its existence. For those interested the complete specification is fairly detailed and can be found at
<a href="https://www.w3.org/TR/xlink11/">https://www.w3.org/TR/xlink11/</a><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">If we adopt this approach I think we will have to double check with regard to XFDU usage in general.<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"><o:p> </o:p></span></p>
<p class="MsoNormal"><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">HD-2: The mime types are defined as a string, basically everything is allowed here from a schema point of view. Especially for cross support I wonder if it has been considered to enumerate the supported
mime types? See here:</span> <br>
<span style="font-size:10.0pt;font-family:"Monaco",serif;color:teal"><</span><span style="font-size:10.0pt;font-family:"Monaco",serif;color:#3F8080">xsd:simpleType</span><span style="font-size:10.0pt;font-family:"Monaco",serif">
<span style="color:purple">name</span>=<i><span style="color:#4200FF">"mimeTypeType"</span></i><span style="color:teal">></span></span>
<br>
<span style="font-size:10.0pt;font-family:"Monaco",serif"> <span style="color:teal">
<</span><span style="color:#3F8080">xsd:restriction</span> <span style="color:purple">
base</span>=<i><span style="color:#4200FF">"xsd:string"</span></i><span style="color:teal">/></span></span>
<br>
<span style="font-size:10.0pt;font-family:"Monaco",serif;color:teal"></</span><span style="font-size:10.0pt;font-family:"Monaco",serif;color:#3F8080">xsd:simpleType</span><span style="font-size:10.0pt;font-family:"Monaco",serif;color:teal">></span>
<span style="color:#1F497D"><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">eb> I take it that you are suggesting to put the mime types inside the TGFT schema? If I have interpreted that correctly, I am curious as to how this works relative to the proposed
SANA registry for the various file types that TGFT is envisioned for handling. Any further thoughts and comments you have will be appreciated.<o:p></o:p></span></p>
<p class="MsoNormal"><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Best regards,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Holger</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Holger Dreihahn<br>
European Spacecraft Operations Centre | European Space Agency | S-431<br>
+49 6151 90 2233 | </span><a href="http://www.esa.int/esoc"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">http://www.esa.int/esoc</span></a><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>