<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=utf-8">
<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:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Helvetica Neue";
panose-1:2 0 5 3 0 0 0 2 0 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:11.0pt;
font-family:"Calibri",sans-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";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.domino-section-title
{mso-style-name:domino-section-title;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:965507858;
mso-list-type:hybrid;
mso-list-template-ids:2042798396 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
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">Hi Andrew,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I understood that what you were asking about was an ESA /ECSS workshop on Glossaries. I thought you meant to address this not in the context of CCSDS, but in some ESA workshop.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">From this email, however, it appears that you are not only wishing to address the topic of glossaries, but you (ECSS) propose to come and tell CCSDS how to create, write, produce, and review standards. This is not a topic that is suitable
for the SEA Systems Engineering WG. If you wish to address that subject I suggest that you ask to bring it to the CCSDS Engineering Steering Group as a whole.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please keep in mind that CCSDS has a nearly 40 year history of producing international and widely accepted standards for space communications, cross support, and interoperability. We also have a well documented process for doing this which
works well. Of course it could be improved, and we have made incremental changes in it over the 20 years I have been involved in the organization.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have copied the CCSDS Secretariat, who operate the CCSDS document processes, and the CCSDS Engineering Steering Group (CESG), so that they are aware of this request.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I will entertain a discussion just on the subject of glossaries in the context of the SEA SAWG meeting. I may also see if I can get some of the TC20/SC14 people who are also interested in this topic to participate at that time, during
the CCSDS working meetings.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards, Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">"Andrew.Herd@esa.int" <Andrew.Herd@esa.int><br>
<b>Date: </b>Friday, June 21, 2019 at 11:12 AM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>"Nicolas.Bobrinsky@esa.int" <Nicolas.Bobrinsky@esa.int>, "Roger.Jegou@esa.int" <Roger.Jegou@esa.int>, "Laurent.Marchand@esa.int" <Laurent.Marchand@esa.int><br>
<b>Subject: </b>Re: [EXTERNAL] ECSS work on e-Glossary - possible CCSDS synergies<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<span style="font-family:"Helvetica Neue"">Dear Peter,<br>
<br>
Great response ... you cover all the central issues associated with glossary.<br>
<br>
However to confirm, we are currently only proposing a ECSS / CCSDS glossaries focussed bilateral during the CCSDS fall meeting in Germany. This could be a dedicated meeting, or simply a 30 minute presentation during your WG activities.
<br>
<br>
At this we will present (relative to glossary)<br>
A cleaner improved set of drafting rules<br>
A new way of writing standards<br>
A new process of reviewing standards<br>
An improved way of searching ECSS<br>
A more user friendly approach for users to understand terms and documents<br>
New technology based capabilities <br>
<br>
In all of these aspects we can consider how these capabilities are a way of;<br>
Improving standardization ways of working<br>
Improving point of use support in generation of standardization documents <br>
Allowing users to compare (and select) varying definitions for terms<br>
<br>
Our presentation aims to raise awareness of the new ECSS capabilities and to ask which areas (if any) CCSDS sees the need for closer collaboration
<br>
<br>
When we recently presented to ISO SC14, the hosts British Standarda Institute (BSI) were very interested from a "product development " perspective (so not so much a content perspective).
<br>
<br>
I believe we have a relevant and interesting message and would very much hope that this offer is of interest (and is clearly on a non committal basis).<br>
<br>
Looking forward to hearing from you,<br>
<br>
Andrew<br>
<br>
<br>
<br>
Sent from IBM Verse</span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span class="domino-section-title"><span style="color:#424282">Shames, Peter M (312B) --- Re: [EXTERNAL] ECSS work on e-Glossary - possible CCSDS synergies ---
</span></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;margin-left:.5in">
<tbody>
<tr>
<td width="7%" valign="top" style="width:7.0%;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:10.0pt;color:#5F5F5F">From:</span><o:p></o:p></p>
</td>
<td width="93%" valign="top" style="width:93.0%;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:10.0pt">"Shames, Peter M (312B)" <peter.m.shames@jpl.nasa.gov></span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="7%" valign="top" style="width:7.0%;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:10.0pt;color:#5F5F5F">To:</span><o:p></o:p></p>
</td>
<td width="93%" valign="top" style="width:93.0%;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:10.0pt">Andrew.Herd@esa.int</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="7%" valign="top" style="width:7.0%;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:10.0pt;color:#5F5F5F">Cc:</span><o:p></o:p></p>
</td>
<td width="93%" valign="top" style="width:93.0%;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:10.0pt">Nicolas.Bobrinsky@esa.int, Roger.Jegou@esa.int, Laurent.Marchand@esa.int</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="7%" valign="top" style="width:7.0%;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:10.0pt;color:#5F5F5F">Date:</span><o:p></o:p></p>
</td>
<td width="93%" valign="top" style="width:93.0%;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:10.0pt">Mon, 17 Jun 2019 7:59 pm</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="7%" valign="top" style="width:7.0%;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:10.0pt;color:#5F5F5F">Subject:</span><o:p></o:p></p>
</td>
<td width="93%" valign="top" style="width:93.0%;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:10.0pt">Re: [EXTERNAL] ECSS work on e-Glossary - possible CCSDS synergies</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<div class="MsoNormal" style="margin-left:.5in">
<hr size="0" width="100%" noshade="" style="color:#8091A5" align="left">
</div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in">Dear Andrew,<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Thank you for reaching out with this information. You are correct that I am the Systems Engineering Area (SEA) Area Director, and in that role that I also have cognizance over the CCSDS SANA website and the Glossary
that we maintain. That Glossary is updated with terms that have been specified in the various CCSDS Blue Book and Magenta Book normative standards that we publish. In some cases there are even definitions that were published in an informative Green Book,
especially if these provide a useful definition that is not otherwise published elsewhere. As the ECSS Glossary Convenor I suspect that you also have a good understanding of the sorts of challenges that can be encountered in trying to keep these Glossaries
up to date, and more importantly (at least in my mind) keeping them harmonized.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">I'll be frank in pointing out that for some time now we have been trying to steer CCSDS toward doing this rather challenging "harmonization" task. I had one of my JPL guys look at this a while back and we discovered
a number of inconsistencies which were pointed out to the CCSDS Engineering Steering Group (CESG), which is made up of me and the other CCSDS ADs, and the CESG chair and deputy. There is an awareness now and several of the areas are doing the work to start
to sort out inconsistencies and overlaps. After a quick scan of your Glossary using a simple "packet" query,
<a href="https://ecss.nl/home/glossary/?qry=packet">https://ecss.nl/home/glossary/?qry=packet</a>, it appears that you have some of the same issues we do, and likely from the same sources.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Issues aside, I am not sure just what it is that you are suggesting. You have your registry of terms from ECSS documents, some of which are clearly drawn from CCSDS documents. We have our CCSDS Glossary. And,
as you appear to be aware, the TC20/SC14 is also interested in a Glossary and would like, I believe, to leverage what already exists in CCSDS, TC20/SC13. I do not know that the IOAG (not IAQG) has a Glossary of their own, but they might. I have not looked
into that. <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">I am supportive of their being a glossary of terms related to space and space exploration. I am also supportive of their being a suitably comprehensive, but also flexible, reference architecture so that these terms
all can be understood relative to a common technical framework that is grounded in an architecture. Along these lines, have you looked at the CCSDS Reference Architecture for Space Data Systems (RASDS), CCSDS 311.0-M-1? This is the architectural framework
we developed years ago. And there is a companion pair of documents, the Space Communications Cross Support Architecture, an ADD (Green Book) and an ARD Requirements document (Magenta Book). These are CCSDS 901.0-G-1 and CCSDS 901.1-M-1. Bother are to be
found on the CCSDS website at <a href="https://public.ccsds.org/Publications/default.aspx">
https://public.ccsds.org/Publications/default.aspx</a>. These use the RASDS framework to describe how some 90 of the CCSDS standards may be deployed to create interoperable communications architectures. Does ECSS have any such reference architecture that
your standards relate to?<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Are you proposing that CCSDS and these other organizations participate in this ECSS (ESA) workshop in late October? Is this to be a working meeting or mostly presentations? Did you want us to present our Glossary
and analyses to you, or were you proposing to only present to us? <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<span style="font-family:Helvetica">________________________________________________________<br>
<br>
Peter Shames<br>
CCSDS Systems 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 <a href="tel:818354-5740">818 354-5740</a>, Fax: +1 <a href="tel:818393-6871">
818 393-6871</a><br>
<br>
Internet: <a href="Peter.M.Shames@jpl.nasa.gov">Peter.M.Shames@jpl.nasa.gov</a><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</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:1.0in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">"<a href="mailto:Andrew.Herd%40esa.int">Andrew.Herd@esa.int</a>" <<a href="mailto:Andrew.Herd%40esa.int">Andrew.Herd@esa.int</a>><br>
<b>Date: </b>Thursday, June 13, 2019 at 5:06 AM<br>
<b>To: </b>Peter Shames <<a href="mailto:peter.m.shames%40jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<b>Cc: </b>"<a href="mailto:Nicolas.Bobrinsky%40esa.int">Nicolas.Bobrinsky@esa.int</a>" <<a href="mailto:Nicolas.Bobrinsky%40esa.int">Nicolas.Bobrinsky@esa.int</a>>, "<a href="mailto:Roger.Jegou%40esa.int">Roger.Jegou@esa.int</a>" <<a href="mailto:Roger.Jegou%40esa.int">Roger.Jegou@esa.int</a>>,
"<a href="mailto:Laurent.Marchand%40esa.int">Laurent.Marchand@esa.int</a>" <<a href="mailto:Laurent.Marchand%40esa.int">Laurent.Marchand@esa.int</a>><br>
<b>Subject: </b>[EXTERNAL] ECSS work on e-Glossary - possible CCSDS synergies</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"> <o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear Peter,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">As the ECSS Glossary TF Convenor, I have been asked by the ECSS Technical Authority to assess your interest in recent capabilities developed relating to e-Glossary.
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Some of these capabilities are already provided on the current public website -
<a href="http://ecss.nl">ecss.nl</a>, whilst others have yet to be released as a mobile app and as a plug-in to Microsoft Word (release expected by July 2019).</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">We understand that as you are the Area Director - SYSTEMS ENGINEERING AREA (SEA), you oversee the CCSDS Glossary (and e-based Glossary).</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There is a conference / workshop planned for late October, in Oberfaffenhoffen, and we were asking to present to you and your colleagues these capabilities to assess the opportunity for collaboration.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">We recently presented to IAQG and ISO SC14, and received positive feedback.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Many thanks for your consideration,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Andrew</span> <br>
<br>
<b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif">ESA - European Space Agency</span></b>
<br>
<br>
<span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:deepskyblue">Andrew Herd</span>
<br>
<br>
<span style="font-size:8.0pt;font-family:"Verdana",sans-serif">TEC Knowledge Management Point of Contact</span>
<br>
<span style="font-size:8.0pt;font-family:"Verdana",sans-serif">and Senior Standardization Engineer</span>
<br>
<br>
<span style="font-size:8.0pt;font-family:"Verdana",sans-serif">Standardization and Engineering Knowledge Management (TEC-QR)</span>
<br>
<span style="font-size:8.0pt;font-family:"Verdana",sans-serif">Product Assurance and Safety Department</span>
<br>
<br>
<b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif">ESTEC</span></b>
<br>
<span style="font-size:8.0pt;font-family:"Verdana",sans-serif">Keplerlaan 1, Noordwijk, 2201 AZ, The Netherlands</span>
<br>
<span style="font-size:8.0pt;font-family:"Verdana",sans-serif"><a href="mailto:andrew.herd%40esa.int">andrew.herd@esa.int</a> |
</span><a href="www.esa.int"><span style="font-size:8.0pt;font-family:"Verdana",sans-serif">www.esa.int</span></a>
<br>
<span style="font-size:8.0pt;font-family:"Verdana",sans-serif">T +31 <a href="tel:715656745">
71 5656745</a></span><o:p></o:p></p>
<pre style="margin-left:1.0in">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre style="margin-left:1.0in">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre style="margin-left:1.0in">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre style="margin-left:1.0in">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo%40esa.int">dpo@esa.int</a>).<o:p></o:p></pre>
<pre style="margin-left:.5in">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre style="margin-left:.5in">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre style="margin-left:.5in">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre style="margin-left:.5in">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).<o:p></o:p></pre>
</div>
</div>
</body>
</html>