[Smwg] Next draft XFDU for TGFT Tech Note

Sat Apr 22 00:02:31 UTC 2017

John,

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.

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.

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.

CSSM Colleagues,
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.

Best regards,
-Erik

From: SMWG [mailto:smwg-bounces at mailman.ccsds.org] On Behalf Of John Pietras
Sent: Wednesday, March 01, 2017 5:20 AM
To: CCSDS SMWG ML (smwg at mailman.ccsds.org) <smwg at mailman.ccsds.org>
Subject: [Smwg] Next draft XFDU for TGFT Tech Note

CSSMWG colleagues -
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.

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.

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.

Best regards,
John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20170422/e8821f61/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: XFDU_for_TGFT_TechNote-v0.3-170228-comments-eb.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 242296 bytes
Desc: XFDU_for_TGFT_TechNote-v0.3-170228-comments-eb.docx
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20170422/e8821f61/attachment.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Xfdu.XFDU.emf
Type: application/octet-stream
Size: 1205840 bytes
Desc: Xfdu.XFDU.emf
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20170422/e8821f61/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Xfdu.XFDU.png
Type: image/png
Size: 416457 bytes
Desc: Xfdu.XFDU.png
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20170422/e8821f61/attachment.png>