<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="ProgId" content="PowerPoint.Slide">
<meta name="Generator" content="Microsoft PowerPoint 14">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div style="font-family: Calibri, sans-serif; font-size: 14px; ">Dear SEA Exec & SA WG,</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; "><br>
</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; ">Please see the attached final version of the System Engineering Area (SEA) viewgraphs as reviewed and agreed by the CCSDS Engineering Steering Group (CESG). Tomorrow we will show these to the
CCSDS Management Council (CMC). If anything changes I will signal you, but the CESG was good with this version.</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; "><br>
</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; "><u>Please check the following notes for
<b><i>actions on you and me</i></b></u>:</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; "><br>
</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; "><b>Sec WG</b></div>
<ul style="font-family: Calibri, sans-serif; font-size: 14px; ">
<li>All had issues with changing the Org & Proc to state that draft Charters and documents would be sent to the SecWG for review. They have a horror of slowing down the process.</li><li>All had NO issue with me, as SEA AD, sending you these documents as a part of my review of them, and providing your feedback as part of my review. <b><i>So I will do that</i></b>.</li></ul>
<div style="font-family: Calibri, sans-serif; font-size: 14px; "><b>D-DOR</b></div>
<ul style="font-family: Calibri, sans-serif; font-size: 14px; ">
<li>There was some consternation that the D-DOR WG would invent it's own Service Management XML approach. <b><i>Before you do that we should consult with the SM WG.</i></b></li><li>The SM WG is also responsible for the GFT standard. They are floating a draft of that and there are some notes from one of the members that I will pass along. <b><i>Please review this approach and provide any feedback you can on what your particular rquirements
are for RDEF transfers.</i></b></li></ul>
<div style="font-family: Calibri, sans-serif; font-size: 14px; "><b>TDE BoF</b></div>
<ul style="font-family: Calibri, sans-serif; font-size: 14px; ">
<li>There was quite a bit of discussion about the TDE BoF, but in the end I think that the concept of doing it as an Orange Book may pass review. The CESG recognizes that an Orange Book carries no formal weight, and that it is just a CCSDS experimental spec.</li><li><b><i>Please make a plan to do the work to create a draft spec. I will work with you on the exact form it should take.</i></b></li><li><b><i>I will edit the charter and draft a resolution asking to create a WG with just that OB as a product.</i></b></li><li>Some of the discussion had to do with the use of certain terms, like "timeline" itself. It appears that ESA uses the word "timeline" to mean a command uplink stream. We'll have to deal with how to disambiguate these terms.</li></ul>
<div style="font-family: Calibri, sans-serif; font-size: 14px; "><b>System Architecture WG (SAWG)</b></div>
<ul style="font-family: Calibri, sans-serif; font-size: 14px; ">
<li>There was quite a bit of discussion about the SAWG re-start as well, but overall there was also quite a lot of support. I think enough of the WG have run into glossary and terminology problems that they are ready to see this tackled. The ECSS acceptance
of this issue cannot have hurt either. And the CMC request for a "CCSDS Reference Architecture" is a strong incentive.</li><li><b><i>The agreement is to first create the "cartoon" version of the CCSDS Reference Architecture, using the RASDS and SCCS-ADD models that are already in hand and adding the pieces for MOIMS and SOIS.</i></b> I did a rough cut to sketch these on pgs 9-11.
Soing a more complete "sketch" in this style should not take too much time, but it will need to be vetted with the other WG and that may be time consuming, especially where unexplored interfaces are involved.</li><li>There is pretty total agreement that what we really need is a SysML/UML CCSDS Reference Model that can actually be manipulated and updated. That is a lot more work and it should only be done after the RASDS SysML/ UML work has been done, so I would defer
it. </li><li><b><i>I have put a WAG estimate of real work months on Pg 8, please take a look and tell me if I am crazy.</i></b></li><li>They all agreed that the ontology had to be done next, that we need to get our terms sorted out. There was a stated opinion that doing this work would be 3-4 man years. I think it could stretech that long if we try to do everything, but I want to first
limit the scope to the core concepts, built upon RASDS and QUDV, to extend that out to include the most fundamntal CCSDS standards, link and cross support, and only when that is done add on a domain extensions. SOIS is the obvious domain extension because
they are already developing a domain ontology. We'll provide the other domains with a concept framework and process that we can help them work through.</li><li>Some of the XML work can also proceed in parallel, as Mike A has proposed. <b><i>He suggested doing first an XML validator that would check both structure AND content of the existing schema.</i></b> He thinks that can be done pretty quickly using available
tools. We can leverage that to extract terms from the schema and rack them up against the ontology. </li><li>A next step is to carve out of the existing schema the common / core elements and to put them in their own namespaces that can be referenced. We can do this by creating new evaluation versions of the schema and see if they produce the same results and
validation. One tool builds on another. The last step is the more radical one of aligning terminology. I think we may need to build in some alias matching as well, but I am no XML expert.</li></ul>
<div>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; ">
<b><font class="Apple-style-span" face="Calibri" size="3">XML SIG</font></b></p>
<ul>
<li><b><i>I'll send the revised RFC & Policy docs to Marc Blanchet, he will edit them and send then back to me to be sent into the CCSDS system for approval.</i></b> The CESG wants to get this done so they will help.</li><li>The CESG will review and approve, then we send them to the CMC and off to the IETF. There is no expectation of any issues, but you never know.</li></ul>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; ">
<b><font class="Apple-style-span" face="Calibri" size="3">SANA</font></b></p>
<ul>
<li><span style="color: rgb(0, 0, 0); font-style: normal; font-weight: normal; text-decoration: none; ">The CESG likes that the programmatic interface is available, but wants to tell people how to access and use it.</span></li><li><span style="color: rgb(0, 0, 0); text-decoration: none; "><b><i>Please put a description on the SANA website of the programmatic interface and mak it visible, even if it is marked "TEST" or "EVALUATION".</i></b></span></li></ul>
<div><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: 14px; font-weight: bold; text-decoration: none; ">SEA Resolutions</span></div>
<ul>
<li><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: 14px; font-style: italic; font-weight: bold; text-decoration: none; ">Please look at pg 15 and see if there is anything you wish to have re-stated in these resolutions. I will tick my way
through them as soon as I have all the necessary inputs.</span></li></ul>
<div><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: 14px; text-decoration: none; ">Thanks for all the support during the meetings. Now the hard work starts, and we really need to make progress. I'd really like some good progress to report
first week in Feb at the next CESG telecon.</span></div>
<div><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: 14px; text-decoration: none; "><br>
</span></div>
<div><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: 14px; text-decoration: none; ">And by the way, I sent this email to the SEA Exec (WG chairs) and also to those who actively supported the SAWG discussions during the week. If you are not
on the SAWG mailing list and wish to be added go to:</span></div>
<div><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: 14px; text-decoration: none; "><br>
</span></div>
<div><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: 14px; text-decoration: none; "><a href="http://mailman.ccsds.org/mailman/listinfo/sea-sa">http://mailman.ccsds.org/mailman/listinfo/sea-sa</a></span></div>
<div><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: 14px; text-decoration: none; "><br>
</span></div>
<div><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: 14px; text-decoration: none; ">Best regards, Peter</span></div>
<div><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: 14px; text-decoration: none; "><br>
</span></div>
<div><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: 14px; text-decoration: none; "><br>
</span></div>
<p style="font-family: Calibri, sans-serif; font-size: 14px; margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; ">
<span class="Apple-style-span" style="font-size: 16px; font-family: 'Times New Roman'; "><b><i><br>
</i></b></span></p>
<!--StartFragment--><!--EndFragment--></div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; "><br>
</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; "><br>
</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; "><br>
</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; "><br>
</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; "><br>
</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; "><br>
</div>
</body>
</html>