<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</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>Hi David,</div>
<div><br>
</div>
<div>If Marc returns the docs on the date requested (he has been silent so far on this) then I think we can get it into Gannett's hands for "tech writer polishing" immediately. I do not know how busy Tom is right now, will ask. </div>
<div><br>
</div>
<div>Item 1) I think that the CESG agreed that this could be only a 2 week review period, but that will run smack into Xmas, so I am guessing the first week of Jan is more realistic (but still optimistic). I doubt that there will be issues, but one never knows.</div>
<div><br>
</div>
<div>Item 2) Assuming the cESG goes well the CMC should be a slam dunk, but that means at least another two weeks, say end of Jan to get that wrapped up.</div>
<div><br>
</div>
<div>Item 3) The docs should go directly to the iETF after that. There is no reason I am aware of to delay. I'm not sure what the time frame is for the IETF review. I think Marc said a month.</div>
<div><br>
</div>
<div>Item 4) If all goes according to this schedule then we should have the CCSDS namespace registered by end of Feb 2015. But someone more familiar with the timing of the RFC process might have a better idea if that is realistic.</div>
<div><br>
</div>
<div>Thanks, Peter</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><Berry>, David Berry <<a href="mailto:David.S.Berry@jpl.nasa.gov">David.S.Berry@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, November 26, 2014 2:27 PM<br>
<span style="font-weight:bold">To: </span>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>, SEA-XSG <<a href="mailto:sea-xsg@mailman.ccsds.org">sea-xsg@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [SEA-XSG] Updates to CCSDS CWE for XML SIG<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 12px; font-family: Courier, sans-serif;">
<div><br>
</div>
<div>Peter:</div>
<div><br>
</div>
<div>What are the target dates for list items 2 through 4 (I assume #1 is 05-Dec-2014 or shortly thereafter.</div>
<div><br>
</div>
<div>Thanks!</div>
<div>David</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><Shames>, "Peter M (312B)" <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, November 26, 2014 at 2:15 PM<br>
<span style="font-weight:bold">To: </span>SEA-XSG <<a href="mailto:sea-xsg@mailman.ccsds.org">sea-xsg@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Subject: </span>[SEA-XSG] Updates to CCSDS CWE for XML SIG<br>
</div>
<div><br>
</div>
<div>
<div 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>Dear XML SIG colleagues,</div>
<div><br>
</div>
<div>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:</div>
<div><br>
</div>
<div><a href="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">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</a>}</div>
<div><br>
</div>
<div>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:</div>
<ol>
<li>Send the docs to the CESG with a recommendation that they be submitted to the IETF for their approval</li><li>Once this is done send the docs to the CMC for approval</li><li>Once that is done, Marc will forward the docs to the IETF for their approval and publication</li><li>That will, once accomplished, register the CCSDS namespace in the Internet</li></ol>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>If any of you have issues or concerns with this approach please voice them now.</div>
<div><br>
</div>
<div>Best regards and good wishes for a happy holiday season.</div>
</div>
</div>
</span></div>
</div>
</blockquote>
</span>
</body>
</html>