<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=iso-8859-1">
<meta name="Generator" content="Microsoft Word 12 (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: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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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:0cm;
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;}
p
{mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"Préformaté HTML Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Texte de bulles Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.PrformatHTMLCar
{mso-style-name:"Préformaté HTML Car";
mso-style-priority:99;
mso-style-link:"Préformaté HTML";
font-family:Consolas;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
{mso-style-name:"HTML Preformatted";
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
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.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma","sans-serif";}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1073896410;
mso-list-template-ids:487128798;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:1686058198;
mso-list-template-ids:1793879466;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2
{mso-list-id:1687631784;
mso-list-template-ids:-772773066;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</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="FR" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Dear all,<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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I was out of the office for a couple of days, my answer thus comes a bit tardy.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">If all ships would have an IMO number or other unique hull identifier, we would have gone that way. As we all know, this is not the case, and it
is in particular not the case for a number of ships of opportunity which play a crucial role in the observing system: we have numerous (mostly smaller) vessels which sail off the main shipping routes and help to i) deploy instruments or ii) gather data with
onboard instrumentation in e.g. the Southern Ocean.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">When we were tasked to design a new identifier scheme for the JCOMM Ship Observations Team, the ICES ship code seemed to be the best existing base
to do it. We (plan to) take the currently valid ICES ship code, and add 3 characters to identify the different instrument packages onboard (we have some terminology issues here between the different involved groups... for us, those instrument packages are
called platforms....). The maximum length of such an ID must not exceed 9 characters (given that the ICES ship code now has a max of 6 were are fine). However, it is indeed crucial for us to track the history of the hull for a number of reasons, some were
mentioned below. If the ICES ship code was ABCDEF in year n and a weather station was installed in n by e.g. NOAA, the ID of that weather station could be ABCDEF001. Even if a new ICES ship codes is assigned in let’s say n+1, e.g. XYZABC, we would not change
that station ID ABCDEF001, as the ID gives us information on the status of the ship at the time of the instrument installation - and the installation itself or the operator NOAA has not changed. However, if NOAA de-recruits the ship, and Meteo-France would
recruit it in n+1, the new Meteo-France installation would have a station ID like XYZABC001. And if Meteo-France would de-recruit the ship in n+2, and the ICES code has not changed, and e.g. DWD recruits the ship then, we would just increment the ID: XYZABC002.
It would be important for DWD at the moment of the recruitment to be aware of the history with NOAA and Meteo-France (installation issues, e.g. wiring, sea valves .. all that normally does not change over the lifetime).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Multiple ICES codes over the lifetime of a ship give us the opportunity to track changes on the ship side a little easier, at the same time they
make the tracking of the hull history a little bit more difficult. We had now started to implement the ICES ship code procedure the way it was, but our system is still young and we could probably still adapt to such changes. It would however be important to
take a decision in the next few weeks, given that a SOT working group will meet in April to work on the ID scheme.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’ll be happy to discuss this with those of you who are on site at Ifremer in a first step – let me know how you wish to proceed.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Many thanks and best regards<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Martin</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">--<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Martin KRAMP<o:p></o:p></span></b></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Ship Coordinator<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">JCOMMOPS (IOC-UNESCO / WMO)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Technopole / Campus Ifremer
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">1625 Route de Sainte Anne<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Z.I. Pointe du Diable<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Blaise Pascal Hall (209.S1.21)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">29280 PLOUZANE (FRANCE)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><br>
E-mail: mkramp@jcommops.org<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="DE" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Tel: +33 2 29 00 85 87<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="DE" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Web: www.jcommops.org<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><img width="110" height="28" id="Image_x0020_1" src="cid:image002.png@01D16E30.A2DA0DE0" alt="JCOMMOPS_LOGO_NEW-map"><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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">De :</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Neil Holdsworth [mailto:NeilH@ices.dk]
<br>
<b>Envoyé :</b> vendredi 12 février 2016 14:52<br>
<b>À :</b> Lowry, Roy K.; Gilbert MAUDIRE; Ann</span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">e Che-Bohnenstengel; platforms@mailman.nerc-liv.ac.uk; Michèle Fichaut; Loic Petit de la Villeon; Kramp Martin (JCOMMOPS); Lize Anthonin (JCOMMOPS);
Belbeoch Mathieu (JCOMMOPS)<br>
<b>Cc :</b> Hjalte Parner; Mehdi Abbasi<br>
<b>Objet :</b> [Platforms] Proposal for revision of platform governance (initiated by ICES)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Dear Platform Group,</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thank you for the spirited discussion, if we achieve nothing else we can be happy that the governance network is responsive and constructive in
its approach to the operational issues we face.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Following from Gilberts message, we will await further input from the colleagues at JCOMMOPS (now copied in) and NOAA before we return and try
and sum up and plot a way forward with this. We are facing a unique challenge to satisfy our traditional user base, and the new (and expanding) user base from the operational oceanography community, and we need to do this without breaking the link to the legacy
data or creating new legacy issues for the next generation of governance.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">And with that thought I will wish you a good weekend!</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best, Neil</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">
<hr size="2" width="98%" align="center">
</span></div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> Lowry, Roy K. [<a href="mailto:rkl@bodc.ac.uk">mailto:rkl@bodc.ac.uk</a>]
<br>
<b>Sent:</b> 09 February 2016 17:24<br>
<b>To:</b> Gilbert MAUDIRE <<a href="mailto:Gilbert.Maudire@ifremer.fr">Gilbert.Maudire@ifremer.fr</a>><br>
<b>Cc:</b> Anne Che-Bohnenstengel <<a href="mailto:Anne.Che-Bohnenstengel@bsh.de">Anne.Che-Bohnenstengel@bsh.de</a>>; Neil Holdsworth <<a href="mailto:NeilH@ices.dk">NeilH@ices.dk</a>>;
<a href="mailto:platforms@mailman.nerc-liv.ac.uk">platforms@mailman.nerc-liv.ac.uk</a>; Michèle Fichaut <<a href="mailto:michele.fichaut@ifremer.fr">michele.fichaut@ifremer.fr</a>>; Loic Petit de la Villeon <<a href="mailto:Loic.Petit.de.la.Villeon@ifremer.fr">Loic.Petit.de.la.Villeon@ifremer.fr</a>><br>
<b>Subject:</b> Re: Fwd: Re: [Platforms] Proposal for revision of platform governance (initiated by ICES)</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
<div id="divtagdefaultwrapper">
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">Hi Gilbert,</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">Just brain-dumping in search of mutually convenient solutions, not attempting to bulldoze you into any decision.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">Following this 'strategy' here's another musing. You say the problem with the IMO is that not all hulls are assigned an IMO. This has been a recognised problem
for a decade, which is why IMOs haven't been adopted as an identifier by the oceanographic community. So, rather than cause disruption by partially remodelling the platform code into a hull identifier, why not go down the road of having separate hull identifiers
maintained by ICES to fulfill the community's needs? This would simply be another attribute on the platform code but would have the effect of turning the existing system into a multi-faceted system, with one facet being an implementation of Bob Arko's suggestion
for a separate hulls vocabulary. Having at as an attribute automatically provides a hull code to platform code mapping and vice versa.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">Cheers, Roy.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<div id="Signature">
<div id="divtagdefaultwrapper">
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">Please note that I partially retired on 01/11/2015. I am now only working 7.5 hours a week and can only guarantee e-mail response on Wednesdays, my day in
the office. All vocabulary queries should be sent to <a href="mailto:enquiries@bodc.ac.uk">
enquiries@bodc.ac.uk</a>. Please also use this e-mail if your requirement is urgent.</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center;background:white">
<span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">
<hr size="2" width="98%" align="center">
</span></div>
<div id="divRplyFwdMsg">
<p class="MsoNormal" style="background:white"><b><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">From:</span></b><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> Gilbert MAUDIRE
<<a href="mailto:Gilbert.Maudire@ifremer.fr">Gilbert.Maudire@ifremer.fr</a>><br>
<b>Sent:</b> 09 February 2016 15:27<br>
<b>To:</b> Lowry, Roy K.<br>
<b>Cc:</b> Anne Che-Bohnenstengel; Neil Holdsworth; <a href="mailto:platforms@mailman.nerc-liv.ac.uk">
platforms@mailman.nerc-liv.ac.uk</a>; Michele FICHAUT; Loic Petit de la Villeon<br>
<b>Subject:</b> Re: Fwd: Re: [Platforms] Proposal for revision of platform governance (initiated by ICES)</span><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">
</span><span lang="EN-GB"><o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">Dear Roy,<br>
<br>
Thank you for your proposal which seems to be convincing to me at least for large ships of opportunity.
<br>
<br>
However, I am not fully aware of all types of ships of opportunity to be managed. So I prefer to wait for my Ifremer and JCOMMOPS colleagues up to next week.It is winter holidays here in Brittany. We will go back to you and Neil thereafter.<br>
<br>
Cheers<br>
Gilbert.<br>
<br>
Le 09/02/2016 16:11, Lowry, Roy K. a écrit : </span><span lang="EN-GB"><o:p></o:p></span></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div id="divtagdefaultwrapper">
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">Hello Gilbert,</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">I don't think that splitting vocabularies by platform type is a good idea. Inevitably, a vessel will be used in a manner that causes problems - for example,
a commercial vessel that has delivered data as a 'ship of opportunity' then gets chartered for a research cruise. If we proceed as you suggest, the ship code for this vessel will get embedded in a CSR database and as this code maps to multiple names existing
systems will not be able to translate it into the correct name. Significant problems could also result from confusion in legacy where some of your VOS hulls have already been assigned multiple platform codes.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">Let's think a little laterally. What you require for your 'platform' field is an identifier to tag hulls of large commercial vessels. There is already a hull-specific
identifier that could do this job in the form of the IMO. If ICES were to maintain the status quo then it would be perfectly possible for ICES to provide a couple of useful services that either deliver a hull history (effectively a set of platform codes with
the time ranges for which they apply) in return for an IMO number or a single platform code and its associated attributes if supplied with an IMO number plus a date.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">How does that sound? It would solve your problem without breaking systems based on the assumption that the platform code represents a hull+name+flag. Note
that if you follow that course I feel it is essential that the work currently underway in ICES to assign platform codes for the JCOMMops list should be completed.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">Cheers, Roy.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<div id="Signature">
<div id="divtagdefaultwrapper">
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">Please note that I partially retired on 01/11/2015. I am now only working 7.5 hours a week and can only guarantee e-mail response on Wednesdays, my day in
the office. All vocabulary queries should be sent to </span><span lang="EN-GB"><a href="mailto:enquiries@bodc.ac.uk"><span style="font-family:"Calibri","sans-serif"">enquiries@bodc.ac.uk</span></a></span><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">.
Please also use this e-mail if your requirement is urgent.</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center;background:white">
<span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">
<hr size="2" width="98%" align="center">
</span></div>
<div id="divRplyFwdMsg">
<p class="MsoNormal" style="background:white"><b><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">From:</span></b><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> Gilbert MAUDIRE
</span><span lang="EN-GB"><a href="mailto:Gilbert.Maudire@ifremer.fr"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><Gilbert.Maudire@ifremer.fr></span></a></span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><br>
<b>Sent:</b> 09 February 2016 14:29<br>
<b>To:</b> Anne Che-Bohnenstengel; Lowry, Roy K.; Neil Holdsworth; </span><span lang="EN-GB"><a href="mailto:platforms@mailman.nerc-liv.ac.uk"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">platforms@mailman.nerc-liv.ac.uk</span></a></span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><br>
<b>Cc:</b> Michele FICHAUT; Loic Petit de la Villeon; MAUDIRE<br>
<b>Subject:</b> Re: Fwd: Re: [Platforms] Proposal for revision of platform governance (initiated by ICES)</span><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">
</span><span lang="EN-GB"><o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">Dear Anne, Roy and Neil,<br>
<br>
We perfectly understand Roy's and Anne's concern. However, the management of Ships of Opportunity is now really difficult.<br>
<br>
We know that, for example, the name and flag of a vessel with a hull mounted TSG can change during the life of the instrument. However, it is of interest to know that it is the same hull and the same instrument for all measurements because potential problems
like sensor drift will be estimated for the whole life of the instrument (even if the ship name has changed).<br>
<br>
Obviously, this kind of name+flag change occurs a lot less frequently for research vessels (and probably FerryBox) than for ships of opportunity.<br>
<br>
In addition, it is of high interest if the couple (call sign , ship code in the vocabulary) could be permanently maintained in "near real time". That could be much easier if the procedure (decision tree) was simplified.<br>
<br>
So, it is of high interest to find out a solution. Could this solution be to set up two procedures (and vocabularies) : one for research vessels (for CSR, POGO...) which is much more stable and one for Ships of opportunity, taking in account the platform type.<br>
<br>
An alternate solution could be to keep track of instruments such as TSG, without taking in account the platform. But, in this case, we will loose the information about the hull (and possible biases due to the mount of the instrument).<br>
<br>
So, before answering to this question, we would like to discuss with people who manage data from Ship of Opportunity like Loïc who is responsible of GOSUD international data base and who is on leave until next week.<br>
<br>
Best regards,<br>
Michèle & Gilbert.<br>
<br>
<br>
<br>
</span><span lang="EN-GB"><o:p></o:p></span></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"><br>
<br>
-------- Message transféré -------- </span><span lang="EN-GB"><o:p></o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td nowrap="" valign="top" style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal" align="right" style="text-align:right"><b>Sujet : </b><o:p></o:p></p>
</td>
<td style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal">Re: [Platforms] Proposal for revision of platform governance (initiated by ICES)<o:p></o:p></p>
</td>
</tr>
<tr>
<td nowrap="" valign="top" style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal" align="right" style="text-align:right"><b>Date : </b><o:p></o:p></p>
</td>
<td style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal">Tue, 9 Feb 2016 09:44:23 +0000<o:p></o:p></p>
</td>
</tr>
<tr>
<td nowrap="" valign="top" style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal" align="right" style="text-align:right"><b>De : </b><o:p></o:p></p>
</td>
<td style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal"><span lang="DA">Anne Che-Bohnenstengel </span><a href="mailto:Anne.Che-Bohnenstengel@bsh.de"><span lang="DA"><Anne.Che-Bohnenstengel@bsh.de></span></a><o:p></o:p></p>
</td>
</tr>
<tr>
<td nowrap="" valign="top" style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal" align="right" style="text-align:right"><b>Pour : </b><o:p></o:p></p>
</td>
<td style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal">Lowry, Roy K. <a href="mailto:rkl@bodc.ac.uk"><rkl@bodc.ac.uk></a>, Neil Holdsworth
<a href="mailto:NeilH@ices.dk"><NeilH@ices.dk></a>, <a href="mailto:platforms@mailman.nerc-liv.ac.uk">
platforms@mailman.nerc-liv.ac.uk</a> <a href="mailto:platforms@mailman.nerc-liv.ac.uk">
<platforms@mailman.nerc-liv.ac.uk></a><o:p></o:p></p>
</td>
</tr>
<tr>
<td nowrap="" valign="top" style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal" align="right" style="text-align:right"><b>Copie à : </b><o:p></o:p></p>
</td>
<td style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal">'<a href="mailto:param_admin@mailman.nerc-liv.ac.uk">param_admin@mailman.nerc-liv.ac.uk</a>' (<a href="mailto:param_admin@mailman.nerc-liv.ac.uk">param_admin@mailman.nerc-liv.ac.uk</a>)
<a href="mailto:param_admin@mailman.nerc-liv.ac.uk"><param_admin@mailman.nerc-liv.ac.uk></a><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="background:white"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Hi Neil,<br>
<br>
Sorry for the late reply. I am out of office and could not check the emails for 2 weeks.<br>
<br>
I support Roy's concern over your proposal. The Cruise Summary Report inventory for SeaDataNet, ODIP/POGO and Eurofleets is one of the major clients requiring the ICES platform codes. Your proposed modification would cause immense impact on the CSRs as we have
been using the platform codes as an <b>unique</b> identifier for the "ship" involved during the described cruise. Your proposal would mean a step backwards from what SDN has been working on during the last years, aside from the labour we have to invest on
our CSR applications for the proposed changes.</span><span lang="EN-GB"><o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="background:white"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><br>
I am sorry that BSH cannot agree to the proposed platform code changes. I do undertstand the issue you have with the strongly increasing number of codes with the additional JCOMMOP vessels.<br>
<br>
Best regards,<br>
Anne</span><span lang="EN-GB"><o:p></o:p></span></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">---------------------------------------------------------<br>
Bundesamt fuer Seeschifffahrt und Hydrographie (BSH)<br>
Anne Che-Bohnenstengel (M4201 + M4181)<br>
Bernhard-Nocht-Str. 78 Tel: +49 (0) 40 3190-3421<br>
20359 Hamburg Fax: +49 (0) 40 3190-5000<br>
</span><span lang="EN-GB"><a href="http://www.bsh.de/"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">http://www.bsh.de/</span></a></span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
email: </span><span lang="EN-GB"><a href="mailto:anne.che-bohnenstengel@bsh.de"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">anne.che-bohnenstengel@bsh.de</span></a></span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><br>
--------------------------------------------------------- </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<div>
<div class="MsoNormal" align="center" style="text-align:center;background:white">
<span lang="EN-GB" style="color:black">
<hr size="2" width="100%" align="center">
</span></div>
<div id="divRpF88556">
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><b><span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Von:</span></b><span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
</span><span lang="EN-GB"><a href="mailto:platforms-bounces@mailman.nerc-liv.ac.uk"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">platforms-bounces@mailman.nerc-liv.ac.uk</span></a></span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
[</span><span lang="EN-GB"><a href="mailto:platforms-bounces@mailman.nerc-liv.ac.uk"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">platforms-bounces@mailman.nerc-liv.ac.uk</span></a></span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">]"
im Auftrag von "Lowry, Roy K. [</span><span lang="EN-GB"><a href="mailto:rkl@bodc.ac.uk"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">rkl@bodc.ac.uk</span></a></span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">]<br>
<b>Gesendet:</b> Freitag, 29. Januar 2016 16:54<br>
<b>An:</b> Neil Holdsworth; </span><span lang="EN-GB"><a href="mailto:platforms@mailman.nerc-liv.ac.uk"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">platforms@mailman.nerc-liv.ac.uk</span></a></span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><br>
<b>Cc:</b> '</span><span lang="EN-GB"><a href="mailto:param_admin@mailman.nerc-liv.ac.uk"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">param_admin@mailman.nerc-liv.ac.uk</span></a></span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">'
(</span><span lang="EN-GB"><a href="mailto:param_admin@mailman.nerc-liv.ac.uk"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">param_admin@mailman.nerc-liv.ac.uk</span></a></span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">)<br>
<b>Betreff:</b> Re: [Platforms] Proposal for revision of platform governance (initiated by ICES)</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<div id="divtagdefaultwrapper">
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">Hello Neil,</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">This amounts to a fundamental change in the definition of entity represented by the platform code, switching it from 'hull with a given name + flag' to 'hull'.
The reason for the current definition is down to legacy. Essentially a fix designed in 2004 for the issue that the entity was originally the name followed by inconsistent behaviour in various places to the issue that ships changed names and different ships
shared the same name.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">The implications of your suggestion are huge. Currently, the URI based on the platform code is guaranteed to resolve to the ship name through the well-known
semantic linkage of 'preferredLabel'. This applies whatever the namespace of the URI. If your suggestion is adopted, then a client requiring the name will need the URI, the date, and the ability to analyse the RDF document delivered by the URI to work out
which of the alternative names to use. It will also require large-scale deprecation of platform codes to reduce the valid code set to one per hull and large-scale editing of data and metadata to eliminate the deprecated codes. </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">Note that you can't ignore legacy without pulling the rug from the semantic interoperability infrastructure currently under construction in many arenas. The
fundamental assumption of these systems is that concept entity definitions are fixed - you cannot have something sometimes meaning one thing and at other times meaning something else. </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">I therefore vote 'No' to your proposal and strongly urge you to widen consultation beyond the platforms group to include the user groups it will affect, particularly
SeaDataNet/EMODNET, ODIP and possibly others such as SenseOcean and AtlantOS.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">Cheers, Roy.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<div id="Signature">
<div id="divtagdefaultwrapper">
<p style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">Please note that I partially retired on 01/11/2015. I am now only working 7.5 hours a week and can only guarantee e-mail response on Wednesdays, my day in
the office. All vocabulary queries should be sent to </span><span lang="EN-GB"><a href="mailto:enquiries@bodc.ac.uk"><span style="font-family:"Calibri","sans-serif"">enquiries@bodc.ac.uk</span></a></span><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">.
Please also use this e-mail if your requirement is urgent.</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center;background:white">
<span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">
<hr size="2" width="98%" align="center">
</span></div>
<div id="divRplyFwdMsg">
<p class="MsoNormal" style="background:white"><b><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">From:</span></b><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">
</span><span lang="EN-GB"><a href="mailto:platforms-bounces@mailman.nerc-liv.ac.uk"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">platforms-bounces@mailman.nerc-liv.ac.uk</span></a></span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">
</span><span lang="EN-GB"><a href="mailto:platforms-bounces@mailman.nerc-liv.ac.uk"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><platforms-bounces@mailman.nerc-liv.ac.uk></span></a></span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">
on behalf of Neil Holdsworth </span><span lang="EN-GB"><a href="mailto:NeilH@ices.dk"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><NeilH@ices.dk></span></a></span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><br>
<b>Sent:</b> 29 January 2016 15:17<br>
<b>To:</b> </span><span lang="EN-GB"><a href="mailto:platforms@mailman.nerc-liv.ac.uk"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">platforms@mailman.nerc-liv.ac.uk</span></a></span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><br>
<b>Subject:</b> [Platforms] Proposal for revision of platform governance (initiated by ICES)</span><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">
</span><span lang="EN-GB"><o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Dear Platform Group,</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Please respond to this proposal with a “Yes” to accept the proposal or “No” to reject the proposal by close of business February 12. No reply
will be considered as a “Yes”.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">ICES has been assigning codes for JCOMMOP vessels for the past 4 months. This has given us the opportunity to test and re-evaluate the effectiveness
of the Platform code system now that the predominant platform class has moved from research vessels to ships of opportunity. We are finding that these vessels are changing name, flag, and owner much more often than research vessels and according to the current
Platform Decision Tree, some vessels will need 5-6 codes in their data collecting lifetime. We believe that this is an unnecessary complication, especially for vessels which have IMO numbers since IMO numbers never change and can be used for tracking.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><i><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">We would like to propose focusing on identification of a given platform which follows the hull and not the country of any governance (flag,
owner or institute). We will keep track of the governance histories of the platform in the platform request system.</span></i><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><i><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:#1F497D"> </span></i><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">In order to do this, we propose:</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="margin-left:36.0pt;text-indent:-18.0pt;background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:Symbol;color:black">·</span><span lang="EN-GB" style="font-size:11.0pt;color:black"> </span><span lang="EN-GB" style="font-size:11.0pt;font-family:Symbol;color:black">
</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">a new attribute for “Operational Governance”. It will allow multiples and will be based on EDMO codes.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="margin-left:36.0pt;text-indent:-18.0pt;background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:Symbol;color:black">·</span><span lang="EN-GB" style="font-size:11.0pt;color:black"> </span><span lang="EN-GB" style="font-size:11.0pt;font-family:Symbol;color:black">
</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">replace the decision tree with a simplified process</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="margin-left:36.0pt;text-indent:-18.0pt;background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:Symbol;color:black">·</span><span lang="EN-GB" style="font-size:11.0pt;color:black"> </span><span lang="EN-GB" style="font-size:11.0pt;font-family:Symbol;color:black">
</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">an update to vocab.ices.dk to offer a clear linking between related platform codes</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="margin-left:36.0pt;text-indent:-18.0pt;background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:Symbol;color:black">·</span><span lang="EN-GB" style="font-size:11.0pt;color:black"> </span><span lang="EN-GB" style="font-size:11.0pt;font-family:Symbol;color:black">
</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">to only create codes based on a random generated unique identifier (see development history)
</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">The decision process will be as follows:</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black">If there is an IMO number:</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="margin-left:36.0pt;text-indent:-18.0pt;background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:Symbol;color:black">·</span><span lang="EN-GB" style="font-size:11.0pt;color:black"> </span><span lang="EN-GB" style="font-size:11.0pt;font-family:Symbol;color:black">
</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Attribute “Country”, i.e. Flag of country where platform is registered, is mandatory.
</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="margin-left:36.0pt;text-indent:-18.0pt;background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:Symbol;color:black">·</span><span lang="EN-GB" style="font-size:11.0pt;color:black"> </span><span lang="EN-GB" style="font-size:11.0pt;font-family:Symbol;color:black">
</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">The flag and call sign will be set for the current registration of the platform.
</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black">If there is no IMO number:</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="margin-left:36.0pt;text-indent:-18.0pt;background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:Symbol;color:black">·</span><span lang="EN-GB" style="font-size:11.0pt;color:black"> </span><span lang="EN-GB" style="font-size:11.0pt;font-family:Symbol;color:black">
</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Attribute “Operational Governance” is mandatory and designated by EDMO codes.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="margin-left:36.0pt;text-indent:-18.0pt;background:white"><span lang="EN-GB" style="font-size:10.0pt;font-family:Symbol;color:black">·</span><span lang="EN-GB" style="font-size:10.0pt;color:black"> </span><span lang="EN-GB" style="font-size:10.0pt;font-family:Symbol;color:black">
</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">When the flag/call sign/MMSI/Notes etc. changes, the attributes will be updated. Name changes will be documented in the “Note” attribute as “Built as name, became
name 2 in xxxx, name 3 in yyyy, name 4 in zzzz etc.". The “Previous name” attribute will have the latest previous name. The previous flag/call sign attributes will be “unaccepted” but kept on the Attribute History page to aid user searching and kept on the
Action History page for tracking</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black">.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black">For both cases above:</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="margin-left:36.0pt;text-indent:-18.0pt;background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:Symbol;color:black">·</span><span lang="EN-GB" style="font-size:11.0pt;color:black"> </span><span lang="EN-GB" style="font-size:11.0pt;font-family:Symbol;color:black">
</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">A code will be assigned as a random generated unique identifier and it will not change.
</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Kind regards,</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Neil</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><b><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Development history</span></b><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">When ICES first started assigning platform codes, the majority of codes were for research vessels which were collecting nationally funded
monitoring data or project data. The system was based on the assumption that these national data were collected by their national vessels so the first two digits of the codes designated country.
</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">ICES then became part of the SeaDataNet project, new attributes were added and a decision tree was developed to determine what was needed
to assign a code. The decision tree was accepted by the SeaDataNet Platform Governance Group after many discussions:</span><span lang="EN-GB"><o:p></o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo1;background:white">
<span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">should there be a country part of the code?</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
</span><span lang="EN-GB"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo1;background:white">
<span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">what type of governance should determine the country part of the platform code: owner of the vessel, Institute collecting the data, flag of the country where the vessel was registered?</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
</span><span lang="EN-GB"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo1;background:white">
<span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Should an IMO code be added for identification when most research vessels can’t receive an IMO number?</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
</span><span lang="EN-GB"><o:p></o:p></span></li></ul>
<p style="background:white"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Among other attributes, it was decided that
</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">the vessels' flag should determine the country part of the code and IMO codes should be added when available.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">As more platform classes were added to L06 (and therefore added to the platform request system), new situations and questions came up:</span><span lang="EN-GB"><o:p></o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo2;background:white">
<span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">what is the country when multiple Institutes from different countries share the vessel during the year or even share during the same cruise? See the </span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">POGO
initiative </span><span lang="EN-GB"><a href="http://www.pogo-oceancruises.org/content/content.asp?pageid=4" target="_blank" id="LPlnk141265"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0563C1">http://www.pogo-oceancruises.org/content/content.asp?pageid=4</span></a></span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
</span><span lang="EN-GB"><o:p></o:p></span></li></ul>
<div style="margin-bottom:15.0pt;overflow:auto" id="LPBorder_GT_14540810543180.06417669868096709">
<table class="MsoNormalTable" border="1" cellspacing="0" cellpadding="0" width="90%" style="width:90.0%;margin-left:36.0pt;background:white;border-top:dotted #C8C8C8 1.0pt;border-left:none;border-bottom:dotted #C8C8C8 1.0pt;border-right:none">
<tbody>
<tr>
<td width="250" valign="top" style="width:187.5pt;border:none;padding:15.0pt 15.0pt 15.0pt .75pt">
<div style="margin-top:5.0pt;margin-bottom:5.0pt;display:table" id="LPImageContainer_14540810543160.9042769635561854">
<p class="MsoNormal" style="margin-top:15.0pt;background:white"><a href="http://www.pogo-oceancruises.org/content/content.asp?pageid=4" target="_blank"><span style="border:solid windowtext 1.0pt;padding:0cm;text-decoration:none"><img border="0" width="200" height="153" id="Picture_x0020_5" src="cid:image001.jpg@01D16E2D.114B5B70" alt="Image removed by sender."></span></a><o:p></o:p></p>
</div>
</td>
<td valign="top" style="border:none;padding:0cm 0cm 0cm 0cm;display:table-cell" id="TextCell_14540810543170.6851617572829127">
<div id="LPTitle_14540810543170.589737230213359">
<p class="MsoNormal" style="margin-top:15.0pt"><a href="http://www.pogo-oceancruises.org/content/content.asp?pageid=4" target="_blank"><span style="text-decoration:none">Pogo</span></a><o:p></o:p></p>
</div>
<div id="LPMetadata_14540810543180.7435189427342266">
<p class="MsoNormal" style="margin-top:15.0pt"><a href="http://www.pogo-oceancruises.org">www.pogo-oceancruises.org</a><o:p></o:p></p>
</div>
<div id="LPDescription_14540810543180.5867947789374739">
<p class="MsoNormal" style="margin-top:15.0pt">The recommendations of the committee were discussed at the POGO-7 meeting in January 2006 and the POGO Members endorsed the plan to assemble, distribute and maintain ...<o:p></o:p></p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo3;background:white">
<span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-GB"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo3;background:white">
<span lang="EN-GB" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">what is the country when multiple countries own the platform?</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
</span><span lang="EN-GB"><o:p></o:p></span></li></ul>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">In preparation for running out of codes and removing semantics from codes, in March 2010 it was decided by the platform group that the country
part of the code could be abandoned and the codes extended although in practice we have continued to use the country as the first two digits of the four digit code.
</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">In 2015, additional changes were made to accommodate JCOMMOPs vessels. It was decided that the codes would be extended to 6 digits once the
current 4 digit system ran out of codes for a particular country, additional attributes were added and the possibility to add multiple countries was incorporated into the request program. Almost 2000 platforms have since been requested by JCOMMOPs of which
98% are Vessels of Opportunity. This has changed the predominant platform class of the platform code system.
</span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<table class="MsoNormalTable" border="0" cellpadding="0">
<tbody>
<tr>
<td colspan="2" style="padding:0cm 0cm 0cm 0cm">
<p><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:dimgray">Neil Holdsworth</span></b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:gray"><br>
Head of Data and Information<br>
International Council for the Exploration of the Sea </span><o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:3.75pt 0cm 0cm 0cm">
<p><span lang="DA" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:gray">E:
</span><a href="mailto:neil.holdsworth@ices.dk" target="_blank"><span lang="DA" style="font-size:7.5pt;font-family:"Arial","sans-serif"">neil.holdsworth@ices.dk</span></a><o:p></o:p></p>
</td>
<td style="padding:3.75pt 0cm 0cm 0cm">
<p><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:gray">W: </span>
<a href="http://www.ices.dk/" target="_blank"><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">www.ices.dk</span></a><o:p></o:p></p>
</td>
</tr>
<tr style="height:12.75pt">
<td style="padding:0cm 0cm 3.75pt 0cm;height:12.75pt">
<p><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:gray">T: +45 3338 6718
</span><o:p></o:p></p>
</td>
<td style="padding:0cm 0cm 3.75pt 0cm;height:12.75pt">
<p><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:gray">M: +45 5362 6718</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td colspan="2" style="padding:0cm 0cm 0cm 0cm">
<p><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:gray">H.C. Andersens Boulevard 44-46<br>
1553 Copenhagen V. Denmark</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="background:white"><span lang="EN-GB" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#7C7C7C">Follow ICES on
</span><span lang="EN-GB"><a href="http://www.linkedin.com/groups?gid=1153507" target="_blank"><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">LinkedIn</span></a><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center;background:white">
<span lang="EN-GB" style="color:black">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="background:white"><span lang="EN-GB" style="font-size:10.0pt;color:black">This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any
reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system</span><span lang="EN-GB" style="color:black">.
</span><span lang="EN-GB"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center;background:white">
<span lang="EN-GB" style="color:black">
<hr size="2" width="100%" align="center">
</span></div>
</div>
</div>
</div>
<p class="MsoNormal" style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"><br>
<br>
<br>
</span><span lang="EN-GB"><o:p></o:p></span></p>
<pre style="background:white"><span lang="EN-GB" style="color:black">-- </span><span lang="EN-GB"><o:p></o:p></span></pre>
<pre style="background:white"><span lang="EN-GB" style="color:black"> </span><span lang="EN-GB"><o:p></o:p></span></pre>
<pre style="background:white"><span lang="EN-GB" style="color:black">________________________________________________________________________</span><span lang="EN-GB"><o:p></o:p></span></pre>
<pre style="background:white"><span lang="EN-GB" style="color:black">Michele FICHAUT - +33 (0)298 22 46 43</span><span lang="EN-GB"><o:p></o:p></span></pre>
<pre style="background:white"><span lang="EN-GB"><a href="http://annuaire.ifremer.fr/cv/16035/en">http://annuaire.ifremer.fr/cv/16035/en</a><o:p></o:p></span></pre>
<pre style="background:white"><span lang="EN-GB"><a href="http://www.seadatanet.org">http://www.seadatanet.org</a><o:p></o:p></span></pre>
<pre style="background:white"><span lang="EN-GB"><a href="http://www.ifremer.fr/sismer/">http://www.ifremer.fr/sismer/</a><o:p></o:p></span></pre>
<pre style="background:white"><span lang="EN-GB" style="color:black">________________________________________________________________________</span><span lang="EN-GB"><o:p></o:p></span></pre>
<p class="MsoNormal" style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="background:white"><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black"> </span><span lang="EN-GB"><o:p></o:p></span></p>
</blockquote>
</div>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center;background:white">
<span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="background:white"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black">This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and
the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system</span><span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">.
</span><span lang="EN-GB"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center;background:white">
<span lang="EN-GB" style="font-family:"Calibri","sans-serif";color:black">
<hr size="2" width="100%" align="center">
</span></div>
</blockquote>
</div>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center"><span lang="EN-GB">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt">This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC
unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system</span><span lang="EN-GB">.
<o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span lang="EN-GB">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-GB" style="background:white"><o:p> </o:p></span></p>
<p align="center" style="text-align:center"><span lang="EN-GB" style="background:white">Cliquez
<a href="https://www.mailcontrol.com/sr/g7HfnvXN7uzGX2PQPOmvUkjDae7bB5Ig9or0vhFqCAFENkiGpoy4mu8tIJzLK950ebpOo395LBWVGm43FW9a3A==">
ici</a> si ce message est indésirable (pourriel).<o:p></o:p></span></p>
</div>
<hr>
<p><span style="font-size: x-small; font-family: arial, helvetica, sans-serif;"><em>Ce message et toutes les pièces jointes (ci-après le "message") sont établis à l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par
erreur ou s'il ne vous est pas destiné, merci de le détruire ainsi que toute copie de votre système et d'en avertir immédiatement l'expéditeur. Toute lecture non autorisée, toute utilisation de ce message qui n'est pas conforme à sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite. L'Internet ne permettant pas d'assurer l'intégrité de ce message électronique susceptible d'altération, l’expéditeur (et ses filiales) décline(nt) toute responsabilité au titre de ce message dans l'hypothèse
où il aurait été modifié ou falsifié.</em></span></p>
<p><span style="font-size: x-small; font-family: arial, helvetica, sans-serif;"><em>This message and any attachments (the "message") is intended solely for the intended recipient(s) and is confidential. If you receive this message in error, or are not the intended
recipient(s), please delete it and any copies from your systems and immediately notify the sender. Any unauthorized view, use that does not comply with its purpose, dissemination or disclosure, either whole or partial, is prohibited. Since the internet cannot
guarantee the integrity of this message which may not be reliable, the sender (and its subsidiaries) shall not be liable for the message if modified or falsified. </em></span></p>
</body>
</html>