<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:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" 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=utf-8"><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:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-GB link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='mso-fareast-language:EN-US'>FYI<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> Shames, Peter M (US 312B) <peter.m.shames@jpl.nasa.gov> <br><b>Sent:</b> 07 October 2021 18:39<br><b>To:</b> david@giaretta.org; Mario Merri <Mario.Merri@esa.int>; Thomas Gannett <thomas.gannett@tgannett.net>; Barkley, Erik J (US 3970) <erik.j.barkley@jpl.nasa.gov>; Holger Dreihahn <holger.dreihahn@esa.int><br><b>Cc:</b> 'John Garrett' <garrett@his.com>; Hughes, J S (US 398B) <john.s.hughes@jpl.nasa.gov>; Mike Kearney <kearneysolutions@gmail.com><br><b>Subject:</b> Re: [EXTERNAL] CCSDS policy on software<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US>Hi David,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>I know that the CSS guys (and possibly others) are using, or have wanted to use, Github to manage some of their models, support software, and other artifacts. There is a desire to add some sort of CCSDS sponsored server, but for now I think they are using ESA or NASA paid services. Let’s start a thread on that with Erik and Holger in the loop, I added them here. IMHO it is worthy of further discussion.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>As for publishing a Java code API as part of a Blue Book, that’s not the way this works. If you want to publish a protocol interface spec, one that defines actual PDUs, info models, and behavior, and peer to peer interactions in some unambiguous form, then that would fit into a CCSDS Blue Book as these are defined. You can look at the Nav standards or at the CSS SM standards for XML data format examples. You can look at the CSS Area SLE and CSTS specs for protocol and PDU examples, or at any of the link layer specs. I would not recommend the MOIMS SM&C specs because they are far too complicated, layered, and abstract. Something simpler, that directly leverages HTTP/REST, would be my recommendation.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>CCSDS does publish some API standards, but these are defined to be Magenta Books. The CSS/SLE set of specs includes some of these. These are classed as MB, rather than BB, because they really only offer portability of software and do not guarantee interoperability in the general case. Unless, of course, you offer a software package on all of the possible OS platforms and EVERYONE uses that package. I classify that as “conditional interoperability” since it only really works if everyone uses the same software package. Contrast that with a proper protocol spec where it does not matter what OS, or language, is used to do the implementation, the interoperability comes from strict compliance of all implementations with an unambiguous spec. All of the Internet works this way and all of the formal CCSDS protocol specs do too.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>I hope this clarifies these concerns. Happy to discuss further.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Cheers, Peter<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:12.0pt;color:black'>From: </span></b><span style='font-size:12.0pt;color:black'>David Giaretta <<a href="mailto:david@giaretta.org">david@giaretta.org</a>><br><b>Date: </b>Thursday, October 7, 2021 at 3:38 AM<br><b>To: </b>Mario Merri <<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>>, Tom Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>>, Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br><b>Cc: </b>John Garrett <<a href="mailto:garrett@his.com">garrett@his.com</a>>, Steve Hughes <<a href="mailto:john.s.hughes@jpl.nasa.gov">john.s.hughes@jpl.nasa.gov</a>>, Mike Kearney <<a href="mailto:kearneysolutions@gmail.com">kearneysolutions@gmail.com</a>><br><b>Subject: </b>[EXTERNAL] CCSDS policy on software<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><span lang=EN-US>Mario, Tom, Peter<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>In DAI we are beginning to develop some initial prototype java code and realized that we were not clear whether there was a policy about “CCSDS blessed” software, in particular for interface specifications which would be part of a BB.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>For example we thought that “org.ccsds.oais….” would be a likely package structure, and a CCSDS owned repository in GITHUB a likely place to put it. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>However we cannot find guidance on this and <a href="https://urldefense.us/v3/__https:/public.ccsds.org/Lists/Software/AllItems.aspx__;!!PvBDto6Hs4WbVuu7!bggzS9SDEQHkBj9NaVqNbI5haQgQB75Vt95lSl4T0zMkmNZMXLY-TPDti_HeeIa7msk4YpU$">https://public.ccsds.org/Lists/Software/AllItems.aspx</a> does not lead to any examples.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>If there is no policy then I guess we will use GITHUB under NASA and ESA etc, with org.ccsds.oais… as the package structure for now.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Any help will be much appreciated.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Regards<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>..David<o:p></o:p></span></p></div></body></html>