<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)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:1575779499;
mso-list-template-ids:486688096;}
@list l0:level1 lfo3
{mso-level-start-at:2;}
@list l0:level1 lfo4
{mso-level-start-at:3;}
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'>Hi,<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'>I’ll copy some earlier comments below.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I believe they were communicated to some people, but may not have made it back to Peter.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>We can discuss these ideas at one of our upcoming telecons.<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'><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 style='margin-bottom:12.0pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I also object to how the updates are being made to the SFDU Control Authority Blue Book.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>As I’ve said, I think if SEA wants to create a registries of Space Organizations or CCSDS Members or Contacts or whatever, I think that is great. Then once that Standard is approved, then MOIMS-DAI WG should update the SFDU Control Authority Book to make use of the SEA defined organizational and contact registries as appropriate. <o:p></o:p></span></p><p class=MsoNormal align=center style='text-align:center'><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'>I do not think we should continue to mix the two parts in a single standard.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>The Space Agency contact portion was originally only included in the CA Standard because CCSDS was not able to maintain and distribute reliable information at the time. (Remember it was early or pre-web site) We only included that portion to work with the CCSDS Secretariat to ensure that the contact information was current. We never intended that a separate registry would be set up for this since we were not trying to register all the Agencies. <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'>Also personally, I would like to rename the Standard that MOIMS-DAI would be responsible for. In my opinion it would renamed to be something like Data Format Registry. The Control Authority name has become a nuisance since people continue to misunderstand its intent.<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'>Live, Laugh, Love, and Work for Peace,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>-JOhn<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><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></a></p><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'> moims-dai-bounces@mailman.ccsds.org [mailto:moims-dai-bounces@mailman.ccsds.org] <b>On Behalf Of </b>Nestor.Peccia@esa.int<br><b>Sent:</b> Monday, July 27, 2015 4:04 AM<br><b>To:</b> moims-dai@mailman.ccsds.org<br><b>Cc:</b> cesg@mailman.ccsds.org<br><b>Subject:</b> [Moims-dai] Proposed edits to the MACAO Blue Book<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Daniele, DAI WG members and MOIMS ADs</span> <br><br><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Please discuss Peter's mail in your WG and with your AD/DAD</span> <br><br><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>The update of the SFDU CA Procedures (630-0-B-1) does not exist as a Project in the CWE Framework. No resources have been committed by the Agencies to handle it. The next 5 year review is due in May 2018. It is clear that if the WG decides to work on it, a Project has to be created and resources have to be committed by the Agencies via a CMC poll.</span> <br><br><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>In addition, the WG has to deal with three other potential 5 year review Projects (in case the WG decides to review it instead of Reconfirm them)</span> <o:p></o:p></p><ol start=1 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>XFDU BB 5 year review is due since Sept 2013</span> <o:p></o:p></li></ol><ol start=2 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>EAST BB 5 year review is due in June 2015</span> <o:p></o:p></li></ol><ol start=3 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo4'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>PAIMS MB 5 year review due in June 2015</span><o:p></o:p></li></ol><p class=MsoNormal><br><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>ciao</span> <br><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>nestor</span> <br><br><span style='font-size:7.5pt;font-family:"Arial",sans-serif;color:purple'>----- Forwarded by Nestor Peccia/esoc/ESA on 27/07/2015 09:48 -----</span> <br><br><span style='font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F'>From: </span><span style='font-size:7.5pt;font-family:"Arial",sans-serif'>"Shames, Peter M (312B)" <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>></span> <br><span style='font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F'>To: </span><span style='font-size:7.5pt;font-family:"Arial",sans-serif'>Boucon Daniele <<a href="mailto:Daniele.Boucon@cnes.fr">Daniele.Boucon@cnes.fr</a>>, </span><br><span style='font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F'>Cc: </span><span style='font-size:7.5pt;font-family:"Arial",sans-serif'>"<a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a>" <<a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a>></span> <br><span style='font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F'>Date: </span><span style='font-size:7.5pt;font-family:"Arial",sans-serif'>26/07/2015 08:05</span> <br><span style='font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F'>Subject: </span><span style='font-size:7.5pt;font-family:"Arial",sans-serif'>[Moims-dai] Proposed edits to the MACAO Blue Book</span> <br><span style='font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F'>Sent by: </span><span style='font-size:7.5pt;font-family:"Arial",sans-serif'><a href="mailto:moims-dai-bounces@mailman.ccsds.org">moims-dai-bounces@mailman.ccsds.org</a></span> <o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=3 width="100%" noshade style='color:#A0A0A0' align=center></div><p class=MsoNormal style='margin-bottom:12.0pt'><br><br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>[attachment "SANA YB 313x0y1 SEA edits 8Jul15.pdf" deleted by Nestor Peccia/esoc/ESA] </span><br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>[attachment "630x0b1_mods-8Jul15.docx" deleted by Nestor Peccia/esoc/ESA] </span><br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>[attachment "CCSDS Registry Re-engineering 10Jul15 v2.pptx" deleted by Nestor Peccia/esoc/ESA] </span><br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>[attachment "CCSDS SSG Name & Number Registries v13.pptx" deleted by Nestor Peccia/esoc/ESA] </span><br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>Dear Daniele,</span> <br><br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>I hope all is well with you. I think that during one of our conversations I mentioned that the CESG and the SANA Steering Group (SSG) were looking into the somewhat confusing state of our registries in the SANA. We have noted that there are a number of issues and overlaps, particularly in the area of organization and person type registries. The attached presentation, "CCSDS SSG Name & Number Registries", describes the problem in significant detail and also spells out how we propose to fix it. </span> <br><br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>The presentaiton "CCSDS Registry Re-engineering" is the best current description of the form of "what" we propose to do. What we discovered in analyzing the set of CCSDS registries is that there is a set of registries that have to do with the "CCSDS enterprise", the agencies, observers, affiliates, and the people that they appoint to do certain tasks or that have certain roles. But what we also discovered is that some of these registries are well formed, others less so, but that there were overlaps and gaps. </span> <br><br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>We have a proposed plan for clearing all of this up.</span> <br><br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>The reason why I am contacting you as DAI WG chair, is the "how" we propose to do it. There are several parts to this that need to have CESG review and CMC concurrence. There is one, in particular, that needs WG concurrence. In the case of your MACAO Blue Book (CCSDS 630x0b1) we wish to leverage the very good work that has already been done to define and create registries for agencies, and agency sub-elements, and for persons with certain roles. The proposed extensions add some fields for unique identifiers and also a mechanism for adding new roles for identified persons to allow them to manage other registries than just the MACAO. This is a request for your WG to review what we have proposed to see if you can concur with the proposed changes which are in the attached mark-up. </span> <br><br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>The related changes we propose require some related edits to other documents. I have drafts of all of these prepared and CESG review is just awaiting some final adjustments:</span> <br><br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>SANA YB (CCSDS 313x0y1, SEA/SSG)</span> <br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>SCID BB (CCSDS 320x0b6, CMC / Secretariat)</span> <br><br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>And the creation of a new one:</span> <br><br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>Registry Management Policy (SEA/SSG)</span> <br><br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>What these changes do is to update the SANA Yellow Book to require WGs to use (or extend) existing registries where that makes sense, and to tell the SANA, in a timely way, when they are creating any new registries or proposing changes to existing registries. The key registries are those relating to organizations (agency, observer, affiliate) and to persons (with various roles). The change to the SCID BB is to add a few fields to that spec, including unique object identifiers for spacecraft, and to extend the current definitions of Agency Representative, the person nominated by an Agency (or Observer) to request changes to the SCID registry. We want to use the general pattern for "Agency Representative" as the way to manage all persons who are assigned (one or more) roles by their agencies. Thus one person (AR) might have only one Role (</span><span style='font-size:7.5pt'>Agency Rep for SCID</span><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>) or they might have more than one Role (</span><span style='font-size:7.5pt'>Agency Rep for SCID, Agency Rep for MACAO, MACAO RP submitter).</span> <br><br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>After working over these concepts with the SSG, SANA Operator, and CCSDS website team we are convinced that a separate Registry Management Policy will be the best way to approach this overall body of work, so I have prepared a draft of that too. That still needs some final changes, so I am not sending it now, just the drafts of the SANA, SCID, and MACAO documents and the analysis and re-engineering materials.</span> <br><br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>I think you will find that the proposed changes do not affect any of the key fields, contents, or intent of what has already been defined in the MACAO. What they are intended to do it to adopt and extend the existing features so that these core enterprise registries can be re-used, and extended, by others. Please review these proposed changes with your WG at the earliest opportunity and let us know if there is an issue. We would all prefer to re-use and extend what is there instead of creating a parallel set of registries, but we can do that if it is deemed necessary.</span> <br><br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'>Very best regards, Peter</span> <br><span style='font-size:10.0pt;font-family:"Calibri",sans-serif'> </span> <br><br><br><br><br><br><br><tt><span style='font-size:10.0pt'>_______________________________________________</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>Moims-dai mailing list</tt><br><tt><a href="mailto:Moims-dai@mailman.ccsds.org">Moims-dai@mailman.ccsds.org</a></tt><br></span><a href="http://mailman.ccsds.org/mailman/listinfo/moims-dai"><tt><span style='font-size:10.0pt'>http://mailman.ccsds.org/mailman/listinfo/moims-dai</span></tt></a><o:p></o:p></p><pre>This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre><pre>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre><pre>content is not permitted.<o:p></o:p></pre><pre>If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre><pre>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Please consider the environment before printing this email.<o:p></o:p></pre></div></body></html>