<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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>After the discussion about language binding books in our telecon this morning, I thought I’d send the links to the SM&C documents, to show the way they handled them. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> <a href="https://public.ccsds.org/Pubs/520x0g3.pdf" target="_blank">CCSDS 520.0-G-3</a> Mission Operations Services Concept (Green)<o:p></o:p></p><p class=MsoNormal> <a href="https://public.ccsds.org/Pubs/521x0b2e1.pdf" target="_blank">CCSDS 521.0-B-2</a> Mission Operations Message Abstraction Layer (Magenta)<o:p></o:p></p><p class=MsoNormal> <a href="https://public.ccsds.org/Pubs/522x1b1.pdf" target="_blank">CCSDS 522.1-B-1</a> Mission Operations Monitor & Control Services (Blue)<o:p></o:p></p><p class=MsoNormal> <a href="https://public.ccsds.org/Pubs/523x1m1.pdf" target="_blank">CCSDS 523.1-M-1</a> Mission Operations Message Abstraction Layer--JAVA API (Magenta)<o:p></o:p></p><p class=MsoNormal> <a href="https://public.ccsds.org/Pubs/523x2m1.pdf" target="_blank">CCSDS 523.2-M-1</a> Mission Operations Message Abstraction Layer--C++ API (Magenta)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The Language APIs are Magenta books, which surprised me. I would have thought they were testable, and would be blue. The general rule is Normative but not testable is Magenta, and normative and testable is blue. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>But I’ve always said that we need to write the books with the content that is needed, and we can decide later what color they are. But to avoid rework, keep separate Informative, Normative and Testable. Like a layered architecture, it’s good practice. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#002060'> -=- Mike<o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'><o:p> </o:p></span></p><p class=MsoNormal>Mike Kearney<span style='color:#002060'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'>Huntsville, Alabama, USA <o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>