<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: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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
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;}
/* List Definitions */
@list l0
{mso-list-id:751197401;
mso-list-template-ids:1772367942;}
@list l1
{mso-list-id:2007903294;
mso-list-template-ids:451291410;}
@list l1:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Peter,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">A few comments:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">1) yes, by all means let's get the RFC out to the IETF ASAP. The cross support services area will, in the very near future, start sub-namespacing (how's that
for a new verb? – or “SNIDing” to go with the RFC), as we are rapidly approaching blue-1 documents that will need to have namespaces associated with them. The intention is to utilize the definitions in the RFC as our starting point.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">2) The google recommendations, comments are good as far as they go, but there are, I believe some deeper concerns – the “short” is good for Russian Doll design
does not really get into other issues such as allowing for late binding (although the way to run-time extensibility) vs., how tight the control over schema is to be. These kind of considerations should also factor into schema design. There may be similar
concerns when dealing with RelaxNG and/or JSON, etc<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">3) I suspect the real issue is not so much SIG vs WG (although I agreed with and supported the CESG consensus to move to a WG to help get a better focus) as it
really is availability of key folks in CCSDS vs their chairing other efforts etc. That’s ultimately a budget issue, but perhaps if we agree to the XSG meeting now at, say 3:30 – 5 pm on Monday March 23 (first day of spring meetings) we can start factoring
that into the other calendars.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;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><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"> sea-xsg-bounces@mailman.ccsds.org [mailto:sea-xsg-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Shames, Peter M (312B)<br>
<b>Sent:</b> Wednesday, November 26, 2014 2:15 PM<br>
<b>To:</b> SEA-XSG<br>
<b>Subject:</b> [SEA-XSG] Updates to CCSDS CWE for XML SIG<br>
<b>Importance:</b> High<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Dear XML SIG colleagues,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">I have just updated the entries in the CWE to reflect the work that was done on the XML SIG. The files include the working notes, an analysis of the XML Guidelines
issues (separate from the XML namespace), and the updated versions of the CCSDS XML Namespace RFC and the XML Namespace guidelines. These may all be found here:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><a href="http://cwe.ccsds.org/sea/docs/Forms/AllItems.aspx?RootFolder=%2fsea%2fdocs%2fSEA-XSG%2fMeeting%20Materials%2f2014%2fFall%202014%20London&FolderCTID=&View=%7b50B434A7-BB62-4E03-A971-45271E7C0B86"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">http://cwe.ccsds.org/sea/docs/Forms/AllItems.aspx?RootFolder=%2fsea%2fdocs%2fSEA-XSG%2fMeeting%20Materials%2f2014%2fFall%202014%20London&FolderCTID=&View={50B434A7-BB62-4E03-A971-45271E7C0B86</span></a><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">}<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">The two XML namespace documens have been sent to Marc Blanchet. He has the originals and is on the hook to produce the edits to these, ready for submission to
the CESG & CMC, by 5 Dec 2014. Once these edits are done we will do the following:<o:p></o:p></span></p>
</div>
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3">
<span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Send the docs to the CESG with a recommendation that they be submitted to the IETF for their approval<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3">
<span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Once this is done send the docs to the CMC for approval<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3">
<span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Once that is done, Marc will forward the docs to the IETF for their approval and publication<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3">
<span style="font-size:10.5pt;font-family:"Calibri",sans-serif">That will, once accomplished, register the CCSDS namespace in the Internet<o:p></o:p></span></li></ol>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">During the CESG and CMC discussions I proposed closing the XML SIG and moving the last topic, that of CCSDS XML Guidelines, to the SEA System Architecture WG (SAWG)
that is now proposed to be re-started. That technical topic is probably better dealt with in a standing working group than in a SIG that gets scant attention from its members. The CESG & CMC agreed that the XML guidelines work was better handled in a full
WG, but asked that the XSG SIG be preserved as what will be effectively a CCSDS XML expert group that will monitor all XML technical and policy changes.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Accordingly I will send a Resolution to the CESG that the XML SIG be re-chartered to include only the CCSDS XML Namespace project and to be re-cast as a standing
SIG that will monitor all of the CCSDS XML technical and policy work. I see the main role of the SIG to provide coordination across the several WG that have XML interests. I believe that we can do that work using a combination of email echanges and telecons.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">If any of you have issues or concerns with this approach please voice them now.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Best regards and good wishes for a happy holiday season.<o:p></o:p></span></p>
</div>
</div>
</body>
</html>