<font size=2 face="sans-serif">Dear CMC members</font>
<br>
<br><font size=2 face="sans-serif">herewith I would like to address with
you an issue that I have never seen in the past 15 years (11 as CESG Co-Chair
and 4 as CESG chair)</font>
<br>
<br><font size=2 face="sans-serif">Notwithstanding the CESG Chair recommendation
(see mail below) , the SEA AD has decided unilaterally to deliver a CCSDS
response to the OMG RFI on Vocabularies, Glossaries for the Spacecraft
Ground Systems Domain (see mail below).</font>
<br>
<br><font size=2 face="sans-serif">The following is noted</font>
<ul>
<li><font size=2 face="sans-serif">SEA AD has broken the formal steps foreseen
in the Proc & Org YB when consensus is not achieved (see the CESG Chair
mail below). There were several mails from the CESG Chair warning him on
the need of further discussions</font>
<li><font size=2 face="sans-serif">SEA AD has proceeded with the RFI submission
without having the authority to do that.</font>
<li><font size=2 face="sans-serif">SEA AD has given higher priority to
the OMG RFI due date (28th Feb 2017) than the achievement of consensus
within the CESG and CMC.</font>
<li><font size=2 face="sans-serif">SEA AD has ignored that this type of
requests has to be carried out by the nominated liaison to OMG (i.e,. MOIMS
AD)</font>
<li><font size=2 face="sans-serif">SEA AD is also giving the option to
convert this as a NASA response to the RFI. This mixes CCSDS and Agency
interests (I accept that at the end could be the same). This is particular
weird coming from the SEA AD who is one of the most ferocious defenders
of CESG ADs role without wearing the "Agency hat"</font>
<li><font size=2 face="sans-serif">SEA AD did not warn the CESG of his
intentions before the RFI due date, This is understandable, because he
would have received the same CESG Chair position</font></ul>
<br><font size=2 face="sans-serif"><b>As CESG Chair I will bring this topic
to the next CMC meeting. I will also propose some updates to the YB to
avoid this type of behaviour in the future.</b></font>
<br>
<br><font size=2 face="sans-serif">ciao</font>
<br><font size=2 face="sans-serif">nestor</font>
<br>
<br><font size=2 face="sans-serif">PS: </font>
<br><font size=2 face="sans-serif">For the sake of completeness I attach
below the main goal of this RFI</font>
<br><font size=2 color=#004080 face="Calibri">The RFI was generated based
on a <b><u>request from US Air Force</u></b> attendees to establish a common
terminology for ground system operations personnel. The SDTF is trying
to help them determine what is already established as “standard” terminology
from various industry and government sources. The results of the
RFI will help them refine the scope of what they are asking for and they
could possibly adopt one of the inputs without any further action by the
SDTF.</font>
<br>
<br>
<br><font size=2 face="sans-serif">========================================</font>
<table width=100% style="border-collapse:collapse;">
<tr height=8>
<td style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;">
<td width=100% style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;">
<table width=100% style="border-collapse:collapse;">
<tr valign=top height=8>
<td width=100% style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=2 face="sans-serif"><b>Re:
Vocabularies, Glossaries for the Spacecraft Ground Systems Domain</b></font></table>
<br>
<table width=100% style="border-collapse:collapse;">
<tr height=8>
<td style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=2 color=#e26200 face="sans-serif"><b>Nestor
Peccia </b></font>
<td style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=2 color=#8f8f8f face="sans-serif">to:</font>
<td style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=2 face="sans-serif">Peter
Shames</font>
<td width=140 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;">
<div align=right><font size=1 face="sans-serif">22/02/2017 21:24</font></div></table>
<br>
<table width=100% style="border-collapse:collapse;">
<tr height=8>
<td style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;">
<table width=100% style="border-collapse:collapse;">
<tr height=8>
<td style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=1 color=#8f8f8f face="sans-serif">Cc:</font>
<td width=100% style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=1 face="sans-serif">Mario
Merri, "CCSDS Engineering Steering Group - CESG Exec"</font></table>
<br>
<td width=140 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;">
<div align=right></div></table>
<br></table>
<br><font size=3>Peter</font>
<br><font size=3>As CESG Chair I am against to respond to the OMG RFI under
pressure</font>
<br><font size=3>I do not like this type of private mails without involving
our liaison.</font>
<br><font size=3>If OMG is really interested in our work, they can delay
the FRI due date by 1 or 2 months. </font>
<br><font size=3>Or they can go ahead without us. The world will not break
apart, unless there are other type of interests (not known to me)</font>
<br><font size=3>As there is no consensus, we must wait until the issue
is discussed at CESG and CMC level. </font>
<br><font size=3>And the exchange of info shall be via the liaison. Please
tell the US OMG colleagues to follow the liaison signed document</font>
<br>
<br><font size=3>Ciao</font>
<br><font size=3>Nestor </font>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Nestor
Peccia/esoc/ESA on 01/03/2017 14:01 -----</font>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Shames, Peter
M (312B)" <peter.m.shames@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"Nestor Peccia"
<Nestor.Peccia@esa.int>, "Mario Merri" <Mario.Merri@esa.int></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"CCSDS Engineering
Steering Group - CESG Exec" <cesg@mailman.ccsds.org>, "James
Afarin" <james.afarin@nasa.gov>, "Tai, Wallace S (9000)"
<wallace.s.tai@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">01/03/2017 02:45</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">FW: CCSDS input
to Vocabularies, Glossaries for the Spacecraft Ground Systems Domain</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="Calibri">Nestor & Mario,</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">In the interest of full disclosure, I wanted
you to be aware that I sent in the attached response to the OMG ontology
RFI. As I said at the outset, I think it is important that the OMG
be made aware of the work that we have done, and are doing, in CCSDS. </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">I was made aware that the window for RFI
submissions had closed, but that they were really interested in having
the CCSDS input to consider within their process. I chose to provide
them that input instead of standing by silently and missing the opportunity.
</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">If you continue to think this is not acceptable
we can treat it as a NASA submission, since NASA is an OMG member.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Regards, Peter</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=3 face="Calibri"><b>From: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><b><br>
Date: </b>Tuesday, February 28, 2017 at 5:34 PM<b><br>
To: </b>"rfi-responses@omg.org" <rfi-responses@omg.org><b><br>
Cc: </b>"luis@amergint.com" <luis@amergint.com>, Brad Kizzort
<bkizzort@harris.com>, Jon Siegel <siegel@omg.org>, "Steven
A. MacLaird" <maclaird@omg.org><b><br>
Subject: </b>CCSDS input to Vocabularies, Glossaries for the Spacecraft
Ground Systems Domain</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Calibri">Dear OMG,</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">As you are aware the CCSDS is an open,
consensus-based, international standards organization that develops space
standards. All of these materials are copyright CCSDS, and they are
in the public domain, openly and freely published on the web. </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">The CCSDS Glossary is a compendium of terms
that have been formally defined in the various standards that we have published
starting in the early 1980's. As such it is not an ontology, but
it does include a very broad range of carefully defined and reviewed terms
that cover space communications, from the physical layer up through the
applications layers. The XML version of that is attached. The
source registry is at </font><a href="http://sanaregistry.org/r/terms/terms-a.html"><font size=2 color=#0082bf face="Calibri"><u>http://sanaregistry.org/r/terms/terms-a.html</u></font></a><font size=2 face="Calibri">.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Since your expressly stated interest is
in ground systems & ground stations I am also sending you a CCSDS technical
note and related presentation. This was developed by one of our staffers
and it describes what are called Functional Resources. This is the
term we use to describe the set of abstract functional entities that perform
ground station comm processing for forward, return, and radiometric tracking
services. Given your focus on this subject we think you may find
it of interest, along with the related standards that have been developed
for cross support and those that are in development for planning, scheduling,
configuring and monitoring ground stations.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">We understand that the period for RFI submissions
has closed, but we think it is important for you to have access to this
information for your deliberations. Just so you are aware, if there
is interest in any sort of collaborative ontology effort with CCSDS we
will have to arrange that through the existing OMG – CCSDS Liaison route.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Regards, Peter Shames</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2>________________________________________________________<br>
<br>
Peter Shames<br>
CCSDS System Engineering Area Director<br>
<br>
Jet Propulsion Laboratory, MS 301-490<br>
California Institute of Technology<br>
Pasadena, CA 91109 USA <br>
<br>
Telephone: +1 818 354-5740, Fax: +1 818 393-6871<br>
<br>
Internet: </font><a href=Peter.M.Shames@jpl.nasa.gov><font size=2 color=blue><u>Peter.M.Shames@jpl.nasa.gov</u></font></a><font size=2><br>
________________________________________________________<br>
<br>
We must recognize the strong and undeniable influence that our language
exerts on our ways of thinking and, in fact, delimits the abstract space
in which we can formulate - give form to - our thoughts.<br>
<br>
Niklaus Wirth<br>
<br>
</font>
<br><font size=2 face="Calibri"> </font>
<br><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE>