<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)">
<style><!--
/* Font Definitions */
@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:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@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";}
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:12.0pt;
font-family:"Times New Roman",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:12.0pt;
font-family:"Times New Roman",serif;}
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:"Georgia",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:1642881592;
mso-list-template-ids:-2102480182;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:1726446687;
mso-list-type:hybrid;
mso-list-template-ids:1560056958 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
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-family:"Georgia",serif;color:#1F497D">Hello Colin,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">I have taken a look and verified that the zip file “works” re use of Oxygen XML editor. Looks good. I have a few comments/questions. Perhaps this can be part of the discussion
at the next WG telecon. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-family:"Georgia",serif;color:#1F497D"><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-family:"Georgia",serif;color:#1F497D">For prototyping, assuming the WG agrees, we would presumably start using this XML file structuring sooner than later. In particular, I assume for PIF prototyping we can
use the schema in the 902x02 sub-directory. <o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-family:"Georgia",serif;color:#1F497D"><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-family:"Georgia",serif;color:#1F497D">I noticed you gave the zip file a November 2<sup>nd</sup> date – “20181102”. Do we wish to include any kind of manifest in some “home” sub-directory or immediately in the
“root” directory (like a readme file) that indicates what version(s) of the “component” schemas are in the dated collection? Seems like we probably want something like this and some sort of control over the “yyyymmdd” naming as to what version of what schemas
this includes?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">-Erik
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"> <o:p></o:p></span></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"> SMWG <smwg-bounces@mailman.ccsds.org>
<b>On Behalf Of </b>Colin.Haddow@esa.int<br>
<b>Sent:</b> Friday, November 2, 2018 07:47<br>
<b>To:</b> CCSDS SMWG ML(smwg@mailman.ccsds.org) <smwg@mailman.ccsds.org><br>
<b>Cc:</b> Wolfgang.Frase@dlr.de<br>
<b>Subject:</b> [Smwg] Refactored, Renamed and Updated Schemas and UML Model for Service Management<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">Dear all,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> those of you who were in Berlin will recall there was discussion about naming conventions for various items (files, attributes, etc.). I've just uploaded updated schemas and UML
models into SANA which reflect these changes and also include the other updates that were discussed in Berlin. For the Schema naming I've adopted the following convention;</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Directory structure</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">902 Schema All service management books are in the 902 series (except for TGFT)</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> 902x01 Schema files for Simple Schedule</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> 902x02 Schema files for Planning Information Formats</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> 902x03 Currently unassigned</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> 902x04 Schema files for Service Package Data Formats</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> 902x05 Schema files for Service Agreement and Configuration Profile Data Formats</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> 902x06 Schema files for Space Link Event Sequence Data Format</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> 902x07 Schema files for Service Catalog</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> 902x08 Schema files for Service Accounting</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> 902x09 Schema files for Service Management Utilization Request Formats</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> 902x10 Schema files for Management Services</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> 902x11 Schema files for Best Practices</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> 902x12 Schema files for Service Management Common Data Entities</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> 902x13 Schema files for Abstract Event Definition
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">For the naming convention of the schema files themselves I've adopted the following</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">902xNNcM[_OO][pP]-SchemaNameInCamelCase.xsd where</span>
<o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">NN is the book number in the 902 series. Note that this is 2 digits with a leading "0" if required.</span>
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">c is the colour of the book, i.e.</span>
<o:p></o:p>
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">w for White</span> <o:p>
</o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">r for Red</span> <o:p>
</o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">m for Magenta</span>
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">b for Blue</span><o:p></o:p></li></ul>
</li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">M is the issue of the book</span>
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">[_OO] is an optional minor version prefixed with an underscore, only applies to white and red drafts. Note again this is 2 digits with a leading "0" if required.</span>
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">[pP] is used if the schema has been updated because of a pink sheet, only applies to blue and magenta.</span>
<o:p></o:p>
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">p indicates it is an update due to a pink sheet</span>
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">P is the number of the pink sheet</span><o:p></o:p></li></ul>
</li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A minus sign "-" is used to seprate the identifer part from the alphabetic part of the name.</span>
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">"Schema" is always the first part of the name</span>
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The alphabetic part of the name is written in camel case.</span>
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There is no white space in the file name (This is because when including the schema name in an xml file using the
</span><span style="font-size:10.0pt;font-family:Consolas;color:purple">xsi:schemaLocation</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> attribute white space in the file name caused problems. (I haven't been able to find a way around
this but if anybody knows one please let me know.)</span> <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<o:p> </o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<o:p> </o:p></li></ul>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">This results in names as shown below;</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">902x01b1p1-SchemaCssmSimpleSchedule.xsd This is Blue Book Version 1 of the Simple Schedule, updated with Pink Sheet 1 (which does not exist - yet...)</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">902x02w0_20-SchemaCssmPlanningInformationFormats.xsd This is White Book Draft 0.20 of the Planning Information Formats.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">For the UML Model I've adopted a similiar approach to the directory and naming conventions (obviously without the use of "Schema" in the file names)</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The zip files containg the schemas and UML models can be found at the URLs below. Note that in these I've included a slightly modified version of the Simple Schedule schema and UML model that fits
in with the directory and file naming conventions outlined above. This is labeled as 902x01b1p1-...</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Schema zip file: </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Schemas/902%20Schema%2020181102.zip"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Schemas/902%20Schema%2020181102.zip</span></a>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">UML model zip file: </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/UML%20Model/902%20UML%20Model%2020181102.zip"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/UML%20Model/902%20UML%20Model%2020181102.zip</span></a>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">We can discuss any comments/critiscims about this appraoch at the next WebEx.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The ".project" files in the schema sub-directories are Eclipse project files. I use Eclipse for editing and validating the schema files.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">One final thing to point out is that those of you who look at the SMURF schema will notice that it has the following include statements</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:Consolas"> <span style="color:teal">
<</span><span style="color:#3F8080">xsd:include</span> <span style="color:purple">
schemaLocation</span>=<i><span style="color:#4200FF">"../902x06/902x06w0_00-SchemaCssmSpaceLinkEventSequenceDataFormat.xsd"</span></i><span style="color:teal">/></span></span>
<br>
<span style="font-size:10.0pt;font-family:Consolas"> <span style="color:teal">
<</span><span style="color:#3F8080">xsd:include</span> <span style="color:purple">
schemaLocation</span>=<i><span style="color:#4200FF">"../902x05/902x05w0_00-SchemaCssmServiceAgreementAndConfigurationProfileDataFormats.xsd"</span></i><span style="color:teal">/></span></span>
<br>
<span style="font-size:10.0pt;font-family:Consolas"> <span style="color:teal">
<</span><span style="color:#3F8080">xsd:include</span> <span style="color:purple">
schemaLocation</span>=<i><span style="color:#4200FF">"../902x04/902x04w0_00-SchemaCssmServicePackageDataFormats.xsd"</span></i><span style="color:teal">/></span></span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">i.e. it has dependencies on the Schema files for Service Package Data Formats, Service Agreement and Configuration Profile Data Formats and Space Link Event Sequence Data Format. This is because
the SMURF is required to be able to submit complete Service Packages, Configuration Profiles and Event Seqeunces. In view of this I suggest that we leave these dependencies rather than making them common data structures beacuase if we make them common data
structures the common data structures book will efectivly need to contain be the Service Package Data Formats, Service Agreement and Configuration Profile Data Formats and Space Link Event Sequence Data Format Books. Not a good idea...</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">You will note that I've made some assumptions about what these 3 schemas will be called, if the Book Captains for these books would prefer the main schema name to be changed please let me know and
I'll update things accordingly...</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Cheers for now,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Colin</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><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; <a href="mailto:colin.haddow@esa.int">colin.haddow@esa.int</a><br>
---------------------------------------------------------------------------------------------------------</span><o:p></o:p></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></pre>
</div>
</body>
</html>