<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Tom,
<div class=""><br class="">
</div>
<div class="">I have no object at all to your proposed approach. Sounds great to me.</div>
<div class=""><br class="">
</div>
<div class="">Rick</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jul 24, 2015, at 9:33 AM, Thomas Gannett <<a href="mailto:tomg@aiaa.org" class="">tomg@aiaa.org</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">Dear CESG Members:<br class="">
<br class="">
The SOIS Dictionary of Terms document was delivered to the Secretariat as a proposed Magenta Book and apparently started life as such. At some point in its development, however, the WG apparently decided it should instead be on a Blue Book track but never changed
any of the boilerplate in the draft. Thus we have a discrepancy between what the Framework project claims the book is and what the draft document itself claims to be.<br class="">
<br class="">
The problem now is that the document went through CESG polling with "Proposed Draft Recommended Practice" on its cover and without expected Blue Book elements like an ICS, and a CMC members since has indicated he thinks it is really supposed to be a Blue Book.
The question is, would the CESG poll have ended differently if the document had had "Proposed Draft Recommended Standard" on its cover?<br class="">
<br class="">
It would be nice not to have to delay review of the document at this point by returning to the beginning of the polling process. Since the CMC approved a Blue Book project, and since no doubt the WG is already hard at work hammering out the details of interoperability
testing to be performed in concert with the review, etc., I propose allowing the book to go to review as a draft Recommended Standard, allowing any question of whether that is the appropriate track to be deferred until the review has concluded. If anyone
objects to that approach, please advise.<br class="">
<br class="">
Best regards,<br class="">
Tom Gannett<br class="">
<br class="">
-----Original Message-----<br class="">
From: <a href="mailto:secretariat-bounces@mailman.ccsds.org" class="">secretariat-bounces@mailman.ccsds.org</a> [<a href="mailto:secretariat-bounces@mailman.ccsds.org" class="">mailto:secretariat-bounces@mailman.ccsds.org</a>] On Behalf Of T. Shigeta<br class="">
Sent: Friday, July 24, 2015 1:14 AM<br class="">
To: <a href="mailto:NickT@aiaa.org" class="">NickT@aiaa.org</a>; <a href="mailto:Nestor.Peccia@esa.int" class="">
Nestor.Peccia@esa.int</a><br class="">
Cc: 戸張 直子; <a href="mailto:CMC-exec@mailman.ccsds.org" class="">CMC-exec@mailman.ccsds.org</a><br class="">
Subject: [Secretariat] [CMC Alert] Question about CCSDS 876.1-R-1 & 876.0-R-1<br class="">
<br class="">
Dear Nestor-san and Nick-san,<br class="">
<br class="">
In reference to the CMC poll for the following two SOIS documents, I would like to have your advice before voting on the CMC poll for<br class="">
CMC-P-2015-07-003 and CMC-P-2015-07-004.<br class="">
<br class="">
- XML SPECIFICATION FOR ELECTRONIC DATA SHEETS FOR ONBOARD<br class="">
DEVICES（CCSDS 876.0-R-1）<br class="">
- SPECIFICATION FOR DICTIONARY OF TERMS FOR ELECTRONIC DATA SHEETS FOR ONBOARD COMPONENTS（CCSDS 876.1-R-1）<br class="">
<br class="">
Concerning the CCSDS 876.1-R-1, JAXA has a question about whether this book is Magenta as proposed by CMC poll or Blue as stated by the Project Charter and CESG Report. On page ii, statement text for the Blue Book remains there. So far as we see the content
of this document, we consider it a Blue book. While we do not see any particular report in the CESG Report about changing from Blue to Magenta, is there any discussion in this regard?<br class="">
<br class="">
On the other hand, title of this document shows “ONBOARD COMPONENTS”, while the accompanying document of CCSDS 876.0-R-1 shows “ONBOARD DEVICES”. We are not certain whether this difference is intentional. CWE Project site introduces this document as Component
while the CESG report says Device.<br class="">
<br class="">
Latter subject can be pointed out during the Agency Review, however, we would like to know about the former subject for JAXA’s voting on the CMC poll.<br class="">
<br class="">
Regards ---- Shigeta<br class="">
<br class="">
_______________________________________________<br class="">
CMC-exec mailing list<br class="">
<a href="mailto:CMC-exec@mailman.ccsds.org" class="">CMC-exec@mailman.ccsds.org</a><br class="">
http://mailman.ccsds.org/mailman/listinfo/cmc-exec<br class="">
<br class="">
_______________________________________________<br class="">
Secretariat mailing list<br class="">
Secretariat@mailman.ccsds.org<br class="">
http://mailman.ccsds.org/mailman/listinfo/secretariat<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
CESG mailing list<br class="">
CESG@mailman.ccsds.org<br class="">
http://mailman.ccsds.org/mailman/listinfo/cesg<br class="">
</div>
</blockquote>
</div>
<br class="">
<div apple-content-edited="true" class=""><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="">Dr. Richard Barton, Ph.D.</div>
<div class="">Wireless Communication Engineer</div>
<div class="">Wireless and Communication Systems Branch</div>
<div class="">NASA Johnson Space Center</div>
<div class="">2101 NASA Parkway, Mail Code EV811</div>
<div class="">Houston, TX 77058</div>
<div class="">281-483-1444 (office)</div>
<div class="">281-483-5830 (fax)</div>
<div class="">713-818-4076 (cell)</div>
<div class=""><a href="mailto:richard.j.barton@nasa.gov" class="">richard.j.barton@nasa.gov</a></div>
<div class=""><br class="">
</div>
</div>
</span><br class="Apple-interchange-newline">
</div>
</span><br class="Apple-interchange-newline">
</div>
</span><br class="Apple-interchange-newline">
<br class="Apple-interchange-newline">
</div>
<br class="">
</div>
</body>
</html>