<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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">John,<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 finally had a chance to look at this. Attached, are some comments. In general, I think this is a very good write-up re XFDU and considerations re TGFT.<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">Re the write-up itself, I am not sure that limiting ourselves to one data object is really what we want, although I agree that is a good starting point.
<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">More in general, in reading through this I had sort of an odd conclusion in that the text descriptions all generally made sense and I think the analysis you have offered is good. But when I put the picture together
and take a look at the sample I'm not necessarily convinced that all of the “surrounding” information is that useful. Of course, a lot of this is because this is what the XFDU offers and the XFDU, as you have noted, is a solution to a much larger problem
than that being tackled by TGFT. <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">CSSM Colleagues,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I think it will be useful in San Antonio for agencies to discuss to use cases (and requirements) to help us decide if and how much XFDU we incorporate. Please see the attached for a pictorial representation of
the instance sample of the XFDU (in .emf and .png formats) from John’s write-up (I tend to find the picture helps in identifying the types of information in the proposed XFDU for TGFT). The main question I have is does this really help anybody in terms of
doing file operations – I'm perfectly okay with the answer being "yes" but I'd like to hear from the membership what “yes” really means for the particular agencies.<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">Best regards,<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>
<p class="MsoNormal"><span style="color:#1F497D"><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"><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 [mailto:smwg-bounces@mailman.ccsds.org] <b>
On Behalf Of </b>John Pietras<br>
<b>Sent:</b> Wednesday, March 01, 2017 5:20 AM<br>
<b>To:</b> CCSDS SMWG ML (smwg@mailman.ccsds.org) <smwg@mailman.ccsds.org><br>
<b>Subject:</b> [Smwg] Next draft XFDU for TGFT Tech Note<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">CSSMWG colleagues –<o:p></o:p></p>
<p class="MsoNormal">Attached is the next draft version of the XFDU for TGFT Tech Note. I am delivering it as an attachment rather than the normal posting to the CWE bacause the CWE is unavailable for uploads until the end of this week.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This draft refines and modifies some of the material in the previous version. One addition that I hope that you will find useful is a set of diagrams that illustrate both the “full” XFDU schema elements and attributes and the simplified
subset that applies to TGFT. Also, this version includes the proposed normative construction rules for TGFT XFDUs. Lastly, Annex A contains an example XFDU Package, with an XFDU Manifest XML document for that XFDU Package. The XFDU Manifest file does validate
against the XFDU schema. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Again, I want to emphasize that at this point this represents my findings and proposals, and there are still a number of open issues, which I hope I have flagged adequately throughout the document. I request the review comments be provided
back to me by April 1 (one month from tomorrow), so that I might have adequate time to reflect on them, respond accordingly, and fold the results into a next version of the Tech Note and the draft TGFT specification (as appropriate) in time for the San Antonio
meeting.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">John <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>