<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style><style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1" dir="ltr">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">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.<br>
<div><font size="2"><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
</font><font size="2">JCOMMOP vessels.<br>
<br>
Best regards,<br>
Anne<br>
</font>
<div style="font-family:Tahoma; font-size:13px">
<div style="font-family:Tahoma; font-size:13px">
<div class="BodyFragment"><font size="2"><span style="font-size:10pt">
<div class="PlainText">---------------------------------------------------------<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>
http://www.bsh.de/ email: anne.che-bohnenstengel@bsh.de<br>
--------------------------------------------------------- </div>
</span></font></div>
</div>
</div>
</div>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF88556"><font face="Tahoma" color="#000000" size="2"><b>Von:</b> platforms-bounces@mailman.nerc-liv.ac.uk [platforms-bounces@mailman.nerc-liv.ac.uk]" im Auftrag von "Lowry, Roy K. [rkl@bodc.ac.uk]<br>
<b>Gesendet:</b> Freitag, 29. Januar 2016 16:54<br>
<b>An:</b> Neil Holdsworth; platforms@mailman.nerc-liv.ac.uk<br>
<b>Cc:</b> 'param_admin@mailman.nerc-liv.ac.uk' (param_admin@mailman.nerc-liv.ac.uk)<br>
<b>Betreff:</b> Re: [Platforms] Proposal for revision of platform governance (initiated by ICES)<br>
</font><br>
</div>
<div></div>
<div>
<div id="divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Hello Neil,</p>
<p><br>
</p>
<p>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.</p>
<p><br>
</p>
<p>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. </p>
<p><br>
</p>
<p>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. </p>
<p><br>
</p>
<p>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.</p>
<p><br>
</p>
<p>Cheers, Roy.</p>
<p><br>
</p>
<div id="Signature">
<div id="divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>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 enquiries@bodc.ac.uk. Please also use this e-mail
if your requirement is urgent.</p>
</div>
</div>
<br>
<br>
<div style="color:rgb(0,0,0)">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> platforms-bounces@mailman.nerc-liv.ac.uk <platforms-bounces@mailman.nerc-liv.ac.uk> on behalf of Neil Holdsworth <NeilH@ices.dk><br>
<b>Sent:</b> 29 January 2016 15:17<br>
<b>To:</b> platforms@mailman.nerc-liv.ac.uk<br>
<b>Subject:</b> [Platforms] Proposal for revision of platform governance (initiated by ICES)</font>
<div> </div>
</div>
<div>
<div>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
Dear Platform Group,</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
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”.</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
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.</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="color:#1F497D"> </span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<i>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.</i></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<i><span style="font-size:12.0pt; color:#1F497D"> </span></i></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
In order to do this, we propose:</p>
<p style="text-indent:-18pt; margin:0cm 0cm 0.0001pt 36pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-family:Symbol; color:black"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:black">a new attribute for “Operational Governance”. It will allow multiples and will be based on EDMO codes.</span></p>
<p style="text-indent:-18pt; margin:0cm 0cm 0.0001pt 36pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-family:Symbol; color:black"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:black">replace the decision tree with a simplified process</span></p>
<p style="text-indent:-18pt; margin:0cm 0cm 0.0001pt 36pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-family:Symbol; color:black"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:black">an update to vocab.ices.dk to offer a clear linking between related platform codes</span></p>
<p style="text-indent:-18pt; margin:0cm 0cm 0.0001pt 36pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-family:Symbol; color:black"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:black">to only create codes based on a random generated unique identifier (see development history)
</span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:10.0pt; font-family:"Tahoma",sans-serif; color:black"> </span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
The decision process will be as follows:</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:10.0pt; color:black">If there is an IMO number:</span></p>
<p style="text-indent:-18pt; margin:0cm 0cm 0.0001pt 36pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-family:Symbol; color:black"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:black">Attribute “Country”, i.e. Flag of country where platform is registered, is mandatory.
</span></p>
<p style="text-indent:-18pt; margin:0cm 0cm 0.0001pt 36pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-family:Symbol; color:black"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:black">The flag and call sign will be set for the current registration of the platform.
</span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:10.0pt; color:black"> </span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:10.0pt; color:black">If there is no IMO number:</span></p>
<p style="text-indent:-18pt; margin:0cm 0cm 0.0001pt 36pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-family:Symbol; color:black"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:black">Attribute “Operational Governance” is mandatory and designated by EDMO codes.</span></p>
<p style="text-indent:-18pt; margin:0cm 0cm 0.0001pt 36pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:10.0pt; font-family:Symbol; color:black"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="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 style="font-size:10.0pt; color:black">.</span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:10.0pt; color:black"> </span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:10.0pt; color:black">For both cases above:</span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:10.0pt; color:black"> </span></p>
<p style="text-indent:-18pt; margin:0cm 0cm 0.0001pt 36pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-family:Symbol; color:black"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:black">A code will be assigned as a random generated unique identifier and it will not change.
</span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
Kind regards,</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
Neil</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<b>Development history</b></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
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. </p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
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:</p>
<ul style="margin-bottom:0cm" type="disc">
<li style="color:black; margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:10.0pt; font-family:"Tahoma",sans-serif">should there be a country part of the code?</span></li><li style="color:black; margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span 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></li><li style="color:black; margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span 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></li></ul>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:10.0pt; font-family:"Tahoma",sans-serif; color:black">Among other attributes, it was decided that
</span>the vessels' flag should determine the country part of the code and IMO codes should be added when available.</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
As more platform classes were added to L06 (and therefore added to the platform request system), new situations and questions came up:<span style="font-size:10.0pt; font-family:"Tahoma",sans-serif; color:black"></span></p>
<ul style="margin-bottom:0cm" type="disc">
<li style="color:black; margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span 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>POGO initiative <span style="color:windowtext"><a href="http://www.pogo-oceancruises.org/content/content.asp?pageid=4" id="LPlnk141265" style="color:rgb(5,99,193); text-decoration:underline" target="_blank">http://www.pogo-oceancruises.org/content/content.asp?pageid=4</a></span>
<div id="LPBorder_GT_14540810543180.06417669868096709" style="margin-bottom:20px; overflow:auto; width:100%; text-indent:0px">
<table id="LPContainer_14540810543140.821906509809196" style="width:90%; position:relative; overflow:auto; padding-top:20px; padding-bottom:20px; margin-top:20px; border-top-width:1px; border-top-style:dotted; border-top-color:rgb(200,200,200); border-bottom-width:1px; border-bottom-style:dotted; border-bottom-color:rgb(200,200,200); background-color:rgb(255,255,255)" cellspacing="0">
<tbody>
<tr style="border-spacing:0px" valign="top">
<td id="ImageCell_14540810543160.8852862941566855" colspan="1" style="width:250px; position:relative; display:table-cell; padding-right:20px">
<div id="LPImageContainer_14540810543160.9042769635561854" style="height:153px; position:relative; margin:auto; display:table; width:200px; background-color:rgb(255,255,255)">
<a id="LPImageAnchor_14540810543160.16597923915833235" href="http://www.pogo-oceancruises.org/content/content.asp?pageid=4" style="display:table-cell; text-align:center" target="_blank"><img src="http://www.pogo-oceancruises.org/pictures/pogo/html_page/newlogo_seadatanet.gif" style="display:inline-block; margin-left:auto; margin-right:auto; max-width:250px; max-height:250px; height:153px; width:200px; border-width:0px; vertical-align:bottom" height="153" width="200"></a></div>
</td>
<td id="TextCell_14540810543170.6851617572829127" colspan="2" style="vertical-align:top; position:relative; padding:0px; display:table-cell">
<div id="LPRemovePreviewContainer_14540810543170.3028105820994824"></div>
<div id="LPTitle_14540810543170.589737230213359" style="top:0px; color:rgb(0,120,215); font-weight:normal; font-size:21px; font-family:wf_segoe-ui_light,'Segoe UI Light','Segoe WP Light','Segoe UI','Segoe WP',Tahoma,Arial,sans-serif; line-height:21px">
<a id="LPUrlAnchor_14540810543170.040304274298250675" href="http://www.pogo-oceancruises.org/content/content.asp?pageid=4" style="text-decoration:none" target="_blank">Pogo</a></div>
<div id="LPMetadata_14540810543180.7435189427342266" style="margin:10px 0px 16px; color:rgb(102,102,102); font-weight:normal; font-family:wf_segoe-ui_normal,'Segoe UI','Segoe WP',Tahoma,Arial,sans-serif; font-size:14px; line-height:14px">
www.pogo-oceancruises.org</div>
<div id="LPDescription_14540810543180.5867947789374739" style="display:block; color:rgb(102,102,102); font-weight:normal; font-family:wf_segoe-ui_normal,'Segoe UI','Segoe WP',Tahoma,Arial,sans-serif; font-size:14px; line-height:20px; max-height:100px; overflow:hidden">
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 ...</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
<span style="font-size:10.0pt; font-family:"Tahoma",sans-serif"></span></li><li style="color:black; margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:10.0pt; font-family:"Tahoma",sans-serif">what is the country when multiple countries own the platform?</span></li></ul>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
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 style="font-size:10.0pt; font-family:"Tahoma",sans-serif; color:black">
</span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
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.
</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
</p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
</p>
<table class="MsoNormalTable" border="0" cellpadding="0">
<tbody>
<tr>
<td colspan="2" style="padding:0cm 0cm 0cm 0cm">
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<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><span style="font-size:7.5pt; font-family:"Arial",sans-serif; color:gray"></span></p>
</td>
</tr>
<tr>
<td style="padding:3.75pt 0cm 0cm 0cm">
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:7.5pt; font-family:"Arial",sans-serif; color:gray" lang="DA">E:
</span><span style="font-size:7.5pt; font-family:"Arial",sans-serif; color:gray"><a href="mailto:neil.holdsworth@ices.dk" style="color:rgb(5,99,193); text-decoration:underline" target="_blank"><span style="color:blue" lang="DA">neil.holdsworth@ices.dk</span></a></span><span style="font-size:7.5pt; font-family:"Arial",sans-serif; color:gray" lang="DA"></span></p>
</td>
<td style="padding:3.75pt 0cm 0cm 0cm">
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:7.5pt; font-family:"Arial",sans-serif; color:gray">W: <a href="http://www.ices.dk/" style="color:rgb(5,99,193); text-decoration:underline" target="_blank">
<span style="color:blue">www.ices.dk</span></a></span><span style="font-size:7.5pt; font-family:"Arial",sans-serif; color:gray"></span></p>
</td>
</tr>
<tr style="height:12.75pt">
<td style="padding:0cm 0cm 3.75pt 0cm; height:12.75pt">
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:7.5pt; font-family:"Arial",sans-serif; color:gray">T: +45 3338 6718
</span><span style="font-size:7.5pt; font-family:"Arial",sans-serif; color:gray"></span></p>
</td>
<td style="padding:0cm 0cm 3.75pt 0cm; height:12.75pt">
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:7.5pt; font-family:"Arial",sans-serif; color:gray">M: +45 5362 6718</span><span style="font-size:7.5pt; font-family:"Arial",sans-serif; color:gray"></span></p>
</td>
</tr>
<tr>
<td colspan="2" style="padding:0cm 0cm 0cm 0cm">
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<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><span style="font-size:7.5pt; font-family:"Arial",sans-serif; color:gray"></span></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:7.5pt; font-family:"Arial",sans-serif; color:#7C7C7C">Follow ICES on
<a href="http://www.linkedin.com/groups?gid=1153507" style="color:rgb(5,99,193); text-decoration:underline" target="_blank">
<span style="color:blue">LinkedIn</span></a></span><span style="font-family:"Arial",sans-serif" lang="DA"></span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
</p>
</div>
</div>
</div>
</div>
<hr>
<small>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</small>.
<hr>
</div>
</div>
</div>
</body>
</html>