<span style=" font-size:10pt;font-family:sans-serif">Hi Hugh,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
ok I've just
had another look and your right. Corrected version of the book uploaded
to CWE and can be found at;</span>
<br>
<br><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Magenta/Service%20Management%20Common%20Data%20Entities/Red%20Book/Drafts/902x12r1_01.2%20-%20Service%20Management%20Common%20Data%20Entities.doc?Web=1"><span style=" font-size:10pt;color:blue;font-family:sans-serif">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Magenta/Service%20Management%20Common%20Data%20Entities/Red%20Book/Drafts/902x12r1_01.2%20-%20Service%20Management%20Common%20Data%20Entities.doc?Web=1</span></a>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Changes are;</span>
<br>
<ul>
<li><span style=" font-size:10pt;font-family:sans-serif">Correct typo in
Ref. [3] version</span>
<li><span style=" font-size:10pt;font-family:sans-serif">Correct sections
A.2.2, A.2.3 and A.2.4 to use Ref. [4] instead of [3]. </span>
<li><span style=" font-size:10pt;font-family:sans-serif">Correct section
A.2.2 to refer to section 3.11 (c) of Ref. [3]</span></ul>
<br><span style=" font-size:10pt;font-family:sans-serif">Thanks for the
sanity check</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Cheers for now,</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Colin<br>
<br>
---------------------------------------------------------------------------------------------------------<br>
Dr. Colin R. Haddow,<br>
HSO-GI, European Space Agency,<br>
European Space Operations Centre,<br>
Robert-Bosch-Str 5,<br>
64293 Darmstadt,<br>
Germany.<br>
<br>
Phone; +49 6151 90 2896<br>
Fax; +49 6151 90 3010<br>
E-Mail; colin.haddow@esa.int<br>
---------------------------------------------------------------------------------------------------------<br>
</span>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">"Hugh
Kelliher" <hugh.kelliher@spaceconnexions.com></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif"><Colin.Haddow@esa.int></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif"><erik.j.barkley@jpl.nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">30/01/2020
11:34</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">RE:
[cssm] Updates:- Abstract Event Definition Book, Service Management Common
data Entities Book, SMURF Book, UML Model, XML Schema.</span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Hi
Colin,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Thanks
for the quick reply. I can see now that I was getting mixed up between
ref[3] and ref[4].</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">My
new question is, should the text be changed:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">From
</span><span style=" font-size:12pt;font-family:Times New Roman">In accordance
with reference [3], section 3.11 (c), updates to this registry are at the
discretion of CCSDS member agencies or registered organizations, via the
registered agency or organization representative.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">To
</span><span style=" font-size:12pt;font-family:Times New Roman">In accordance
with reference [4], section 3.11 (c), .....</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#424282;font-family:Calibri">Just
in passing, I see that reference [3], section 2.3 (c) is the same as reference
[4], section 3.11 (c).</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#424282;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#424282;font-family:Calibri">In
order to not restrict the register for orginatingOrganization to just a
service provider, could we reference section 3.3 rather than section 3.3.2.3
and leave it to the organization to chose which subsection is the most
relevant to them?</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Cheers,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Hugh</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Tahoma"><b>From:</b>
Colin.Haddow@esa.int [</span><a href=mailto:Colin.Haddow@esa.int><span style=" font-size:10pt;font-family:Tahoma">mailto:Colin.Haddow@esa.int</span></a><span style=" font-size:10pt;font-family:Tahoma">]
<b><br>
Sent:</b> 30 January 2020 10:06<b><br>
To:</b> Hugh Kelliher<b><br>
Cc:</b> erik.j.barkley@jpl.nasa.gov<b><br>
Subject:</b> RE: [cssm] Updates:- Abstract Event Definition Book, Service
Management Common data Entities Book, SMURF Book, UML Model, XML Schema.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">Hi
Hugh,</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
reference
[3] in the CDE is</span><span style=" font-size:12pt;font-family:Times New Roman">
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"><i>[3]
CCSDS SANA Registry Management Policy</i>. Issue 2. CCSDS Record (Yellow
Book), CCSDS 313.1-Y-2. Washington, D.C.: CCSDS, May 2016. </span><span style=" font-size:10pt;font-family:Arial"><br>
This actually contains a typo as the published version is actual Issue
1, so the reference should be</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
<i><br>
[3] CCSDS SANA Registry Management Policy</i>. Issue </span><span style=" font-size:12pt;color:red;font-family:Times New Roman">1</span><span style=" font-size:12pt;font-family:Times New Roman">.
CCSDS Record (Yellow Book), CCSDS 313.1-Y-</span><span style=" font-size:12pt;color:red;font-family:Times New Roman">1</span><span style=" font-size:12pt;font-family:Times New Roman">.
Washington, D.C.: CCSDS, May 2016. </span><span style=" font-size:10pt;font-family:Arial"><br>
In this section 3.3.2.3 states;</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
<b><br>
3.3.2.3 Service Provider Registry</b> <b><br>
3.3.2.3.1 </b>The subset of the CCSDS Organization Registry comprising
Service Providers <br>
may be referred to as the Service Provider Registry. <b><br>
3.3.2.3.2 </b>The Review Authority for the Service Provider Registry shall
be the SSG. <b><br>
3.3.2.3.3 </b>The Registration Rule for the Service Provider Registry shall
be c) Change <br>
requires no engineering review, but the request must come from the Secretariat
or an official <br>
representative of a space agency that is a member of the CCSDS (cf. reference
[5]). <b><br>
3.3.2.3.4 </b>Only an AR with the Service Provider PoC role shall be permitted
to create, <br>
update, or delete Service Provider Registry entries for that organization.
<b><br>
3.3.2.3.5 </b>Each CCSDS Agency or CCSDS Affiliate Organization that provides
services <br>
shall register in the CCSDS Organization Registry. <b><br>
3.3.2.3.6 </b>Each Service Provider organization will have a unique ISO
OID assigned by the <br>
organization registration procedure. <b><br>
3.3.2.3.7 </b>Each Service Provider organization may have one or more service
sites. <b><br>
3.3.2.3.8 </b>Each service site shall be registered in the Service Site
and Aperture Registry. <b><br>
3.3.2.3.9 </b>Each Service Provider should provide a pointer (URN) for
their Service Catalog. <b><br>
3.3.2.3.10 </b>Each Service Provider should provide a reference to their
organizational PoC that <br>
can provide information and commit to services. <b><br>
3.3.2.3.11 </b>The organizational PoC shall be registered in the Contacts
Registry<b>.</b> <br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
I think this is the relevant part to reference although I guess you could
argue that if you are submitting a request, via the SMURF for example,
for a service then you are not necessarily also a service <i>provider</i>.
That being said I can't find a more suitable section in the Yellow book
to reference.The published version of the yellow book that I've got from
the CCSDS website doesn't have a section 3.11.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
</span><span style=" font-size:12pt;font-family:Times New Roman"><br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Erik, do you want me to correct the reference in the CDE book, or will
you do it (or is it the sort of thing that Tom catches) ?</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Cheers for now,</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Colin</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
---------------------------------------------------------------------------------------------------------<br>
Dr. Colin R. Haddow,<br>
HSO-GI, European Space Agency,<br>
European Space Operations Centre,<br>
Robert-Bosch-Str 5,<br>
64293 Darmstadt,<br>
Germany.<br>
<br>
Phone; +49 6151 90 2896<br>
Fax; +49 6151 90 3010<br>
E-Mail; colin.haddow@esa.int<br>
---------------------------------------------------------------------------------------------------------</span><span style=" font-size:12pt;font-family:Times New Roman"><br>
<br>
<br>
<br>
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
From: </span><span style=" font-size:9pt;font-family:Arial">"Hugh
Kelliher" <hugh.kelliher@spaceconnexions.com></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
To: </span><span style=" font-size:9pt;font-family:Arial"><Colin.Haddow@esa.int></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Date: </span><span style=" font-size:9pt;font-family:Arial">29/01/2020
20:26</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Subject: </span><span style=" font-size:9pt;font-family:Arial">RE:
[cssm] Updates:- Abstract Event Definition Book, Service Management Common
data Entities Book, SMURF Book, UML Model, XML Schema.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span></p>
<div align=center>
<hr noshade></div>
<p style="margin-top:0px;margin-Bottom:240px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Hi
Colin,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Did
you also want to change the wording of CDE A.2.2</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">From
</span><span style=" font-size:12pt;font-family:Times New Roman">The policy
that governs updates to the Organizational Roles registry is that defined
in subsection 3.3.2.3 of reference [3].</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">To
</span><span style=" font-size:12pt;font-family:Times New Roman">In accordance
with reference [3], section 3.11 (c), updates to this registry are at the
discretion of CCSDS member agencies or registered organizations, via the
registered agency or organization representative.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#104160;font-family:Calibri">Cheers,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#104160;font-family:Calibri">Hugh</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#104160;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:9pt;color:#004080;font-family:Arial"><b>Hugh
Kelliher</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:9pt;color:#004080;font-family:Arial">Space
ConneXions Ltd | </span><a href=http://www.spaceconnexions.com/><span style=" font-size:9pt;color:blue;font-family:Arial"><u>www.spaceconnexions.com</u></span></a><span style=" font-size:9pt;color:#004080;font-family:Arial">
| +44 (0)1582 712418</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:9pt;color:#004080;font-family:Arial">Registered
office: 10 Nettles Terrace, Guildford, Surrey, GU1 4PA, United Kingdom</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#104160;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Tahoma"><b>From:</b>
SMWG [</span><a href="mailto:smwg-bounces@mailman.ccsds.org"><span style=" font-size:10pt;color:blue;font-family:Tahoma"><u>mailto:smwg-bounces@mailman.ccsds.org</u></span></a><span style=" font-size:10pt;font-family:Tahoma">]
<b>On Behalf Of </b>Colin.Haddow@esa.int<b><br>
Sent:</b> 23 January 2020 13:54<b><br>
To:</b> CCSDS Service Mgmt WG<b><br>
Subject:</b> [cssm] Updates:- Abstract Event Definition Book, Service Management
Common data Entities Book, SMURF Book, UML Model, XML Schema.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">Dear
all, <br>
I've just uploaded
the following updates to CWE;</span><span style=" font-size:12pt;font-family:Times New Roman">
</span></p>
<ul>
<li><span style=" font-size:10pt;font-family:Arial">Abstract Event Definition
Book:
Contains all RID updates + changes to schema naming convention
+ SANA Registry paths. Subject to AD review should be ready for publication.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span>
<li><span style=" font-size:10pt;font-family:Arial">Service Management
Common Data Entities Book: Contains all RID
updates + changes to schema naming convention + SANA Registry paths. Subject
to AD review should be ready for publication.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span>
<li><span style=" font-size:10pt;font-family:Arial">SMURF Book
Contains changes to Basic
start and duration constraints as discussed at last telecon (i.e. merge
into one constraint), change use of start and end time to optional in ICS
table + changes to schema naming convention + SANA Registry paths. Does
<b><i>not </i></b> (yet) contain any updates at the individual request
type level stating how the start and end times in the header should be
used. I think this update is perhaps best left until we're a bit further
into the prototyping.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span>
<li><span style=" font-size:10pt;font-family:Arial">XML Schemas:
Contains the schemas
updated for the new naming convention and changes to the above books.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span>
<li><span style=" font-size:10pt;font-family:Arial">UML Model
Contains
the UML model consistent with the changes to the above books.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span>
<li><span style=" font-size:12pt;font-family:Times New Roman"> </span></ul><span style=" font-size:10pt;font-family:Arial">These
can be found at the following URLs</span><span style=" font-size:12pt;font-family:Times New Roman">
</span>
<ul>
<li><span style=" font-size:10pt;font-family:Arial">Abstract Event Definition
Book:
</span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Magenta/Abstract%20Event%20Definition/Red%20Book/Drafts/902x13r1_01.1%20-%20Abstract%20Event%20Definition.doc"><span style=" font-size:10pt;color:blue;font-family:Arial"><u>https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Magenta/Abstract%20Event%20Definition/Red%20Book/Drafts/902x13r1_01.1%20-%20Abstract%20Event%20Definition.doc</u></span></a><span style=" font-size:12pt;font-family:Times New Roman">
</span>
<li><span style=" font-size:10pt;font-family:Arial">Service Management
Common Data Entities Book</span><span style=" font-size:10pt;color:blue;font-family:Arial">
</span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Magenta/Service%20Management%20Common%20Data%20Entities/Red%20Book/Drafts/902x12r1_01.1%20-%20Service%20Management%20Common%20Data%20Entities.doc"><span style=" font-size:10pt;color:blue;font-family:Arial"><u>https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Magenta/Service%20Management%20Common%20Data%20Entities/Red%20Book/Drafts/902x12r1_01.1%20-%20Service%20Management%20Common%20Data%20Entities.doc</u></span></a><span style=" font-size:12pt;font-family:Times New Roman">
</span>
<li><span style=" font-size:10pt;font-family:Arial">SMURF Book</span><span style=" font-size:10pt;color:blue;font-family:Arial">
</span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Service%20Management%20Utilization%20Request%20Format/White%20Book/Drafts/902x9w0_10%20-%20Service%20Management%20Utilization%20Request%20Formats.doc"><span style=" font-size:10pt;color:blue;font-family:Arial"><u>https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Service%20Management%20Utilization%20Request%20Format/White%20Book/Drafts/902x9w0_10%20-%20Service%20Management%20Utilization%20Request%20Formats.doc</u></span></a><span style=" font-size:12pt;font-family:Times New Roman">
</span>
<li><span style=" font-size:10pt;font-family:Arial">XML Schemas
</span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Schemas/902Schema%2020200123.zip"><span style=" font-size:10pt;color:blue;font-family:Arial"><u>https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Schemas/902Schema%2020200123.zip</u></span></a><span style=" font-size:12pt;font-family:Times New Roman">
</span>
<li><span style=" font-size:10pt;font-family:Arial">UML Model
</span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/UML%20Model/902UmlModel%2020200123.zip"><span style=" font-size:10pt;color:blue;font-family:Arial"><u>https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/UML%20Model/902UmlModel%2020200123.zip</u></span></a></ul><span style=" font-size:10pt;font-family:Arial">Note
that I've not updated the CPIF with the new schema naming convention and
SANA Registry paths. As thats currently out for Agency review that should
be handled via a RID.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Cheers for now,</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Colin</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
---------------------------------------------------------------------------------------------------------<br>
Dr. Colin R. Haddow,<br>
HSO-GI, European Space Agency,<br>
European Space Operations Centre,<br>
Robert-Bosch-Str 5,<br>
64293 Darmstadt,<br>
Germany.<br>
<br>
Phone; +49 6151 90 2896<br>
Fax; +49 6151 90 3010<br>
E-Mail; colin.haddow@esa.int<br>
---------------------------------------------------------------------------------------------------------</span><span style=" font-size:12pt;font-family:Times New Roman">
</span>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">This
message is intended only for the recipient(s) named above. It may contain
proprietary information and/or</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">protected
content. Any unauthorised disclosure, use, retention or dissemination is
prohibited. If you have received</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">this
e-mail in error, please notify the sender immediately. ESA applies appropriate
organisational measures to protect</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">personal
data, in case of data privacy queries, please contact the ESA Data Protection
Officer (dpo@esa.int).</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">This
message is intended only for the recipient(s) named above. It may contain
proprietary information and/or</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">protected
content. Any unauthorised disclosure, use, retention or dissemination is
prohibited. If you have received</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">this
e-mail in error, please notify the sender immediately. ESA applies appropriate
organisational measures to protect</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">personal
data, in case of data privacy queries, please contact the ESA Data Protection
Officer (dpo@esa.int).</span></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p><PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE>