<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 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: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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
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;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
p.h1, li.h1, div.h1
{mso-style-name:h1;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:10.5pt;
font-family:"Tahoma","sans-serif";
color:black;
font-weight:bold;}
p.h2, li.h2, div.h2
{mso-style-name:h2;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:9.0pt;
font-family:"Tahoma","sans-serif";
color:black;
font-weight:bold;}
p.p, li.p, div.p
{mso-style-name:p;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:9.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
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 Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Neil,<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Best practice for legacy data is of course to upgrade it to the
latest standards/structures. However, there is always a balance to maintain
between aspirations and reality as I know all too well with work on our cruise
metadata repository. After five years I think we have just about purged multiple-ship
“cruises” from the system, in one case spawning no fewer than 20 new cruise
records for a week-long MAFF young fish survey. This is painstaking,
time-consuming work that not everybody has the will or resources to undertake. <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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>We have to support legacy. Therefore I would never suggest cleaning
out the ICES ship code list. The whole idea of the C174 list was to subdivide
the full ICES list into codes that passed quality scrutiny for inclusion in SeaDataNet
CSRs and codes needed to support legacy data. However, I would question the
wisdom of expanding the latter.<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The case that triggered this discussion was a request from a
SeaDataNet partner for a new ‘multiple ships of a nation’ code, which I presume
is to support the creation of a CSR for SeaDataNet. This rang my alarm bells.
Not only is it setting up data model extension through vocabulary population,
but it is leading to a CSR covering many “cruises” by many vessels. We are working
hard to eliminate these and the last thing I want to see is new ones being
created. Hence my reaction to the new code proposal.<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>In my opinion, ‘cruise’ is a specialisation of a ‘data collection
activity’ class and the CSR is a metadata model designed to describe that specialisation.
Now it is perfectly possible to have oceanographic data collection activities
that are not a good fit into the ‘cruise’ model such as a Ferrybox route
(would require one CSR per sailing: possible but inelegant). These represent a
different specialisation and what we should be doing is profiling our metadata
model to accommodate their attributes (e.g. fields like sailing duration and
sailing frequency) rather than redefining what is meant by a ‘cruise’.<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Cheers, Roy.<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>
<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";color:windowtext'>From:</span></b><span lang=EN-US
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> Neil
Holdsworth [mailto:NeilH@ices.dk] <br>
<b>Sent:</b> 03 November 2010 08:57<br>
<b>To:</b> Lowry, Roy K; Dick M.A. Schaap<br>
<b>Cc:</b> Accessions; platforms@biwebs1.nerc-liv.ac.uk;
sdn-tech@seadatanet.org<br>
<b>Subject:</b> RE: [Platforms] ROMANIA - MULTIPLE SHIPS OF ROMANIA<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Dear Roy,<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>You are right that fixing limitations in data models by other
means is not the best thing to do. However, i think we need to make a
distinction between what we can agree will be <o:p></o:p></span></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>A)</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> best practice for new and future data and the use of
vocabularies and what we need to have in place to deal with <o:p></o:p></span></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>B)</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> existing historical data in our systems and historical data
that will need to be processed through our systems. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Certainly the latter does not conform to an ideal data model,
and never will so we need to do something to handle this without losing
information.<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The situation is we have 150 or so platform codes of the type
“unknown” in one form or another in the platform management system, but
assigned to a country. These platforms are linked to data and it is therefore
not possible to switch them to “ZZ99”. Furthermore, not all of these data are
related to a CSR and never will be (historical biological sampling, multiple
ship samples etc.), therefore we would not be able to retain this information
about country unless we make dummy CSR’s, which i think is even more of a
stretch of the data model principles. It should always be possible to
reevaluate historical data using the available meta-data to provide clues as to
sources of information, and while this may not be the focus for SeaDataNet it
is an important part of the data stewardship that ICES and other organisations
provide.<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>So i think to expand the CSR model, even if it was agreed by the
SDN TTT is not the solution, certainly not to the whole problem and will not
mean that these 150 codes will cease to exist. I therefore think we need to
proceed on the idea of a split in historical recording and current and future
recording, there are of course a number of ways we could do this and i think
that’s what we should be discussing as although it is important to agree what
is desirable, we also need to deal with what is practical and workable.<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Sorry for delay in between responses, trying to juggle a few
tasks but realise this discussion is important to keep alive.<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Neil<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>
<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";color:windowtext'>From:</span></b><span lang=EN-US
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>
Lowry, Roy K [mailto:rkl@bodc.ac.uk] <br>
<b>Sent:</b> 01 November 2010 16:12<br>
<b>To:</b> Neil Holdsworth; Dick M.A. Schaap<br>
<b>Cc:</b> Accessions; platforms@biwebs1.nerc-liv.ac.uk;
sdn-tech@seadatanet.org<br>
<b>Subject:</b> RE: [Platforms] ROMANIA - MULTIPLE SHIPS OF ROMANIA<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hello Neil,<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This discussion hinges on whether vocabulary population should
be used in imaginative ways to patch limitations in data models, such as having
a vocabulary entry that is a list to implement a one-to-many relationship where
the data model dictates one-to-one. I have argued vociferously over the past
ten years that this is vocabulary abuse and should be avoided and have put a
lot of effort into rebuilding metadata where that practice has been used in the
past.<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>In an ideal world any platform code database should have a hull
or equivalent as its fundamental entity to which are attached a series of
time-limited attributes such as name, platform class, callsign and flag.
The attributes considered important for cruise reporting may be determined from
the original ROSCOP form section A02 as ship name (now represented by a ship
code) and the platform type. Callsign was added as an attribute when the
ROSCOP was revised into the CSR. My thinking is that if the ship name cannot be
elucidated then we need an unambiguous way of expressing that fact, which is
what ZZ99 delivers. This is not bucket term usage.<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The question you now raise is whether the flag of the platform
is an attribute excluded from the original ROSCOP/CSR that we now feel has
sufficient significance for it to be included in the CSR data model. My
vote would be ‘no’, but if the majority feel the answer is ‘yes’ then we should
be looking to extend the CSR data model rather than implementing a vocabulary
quick fix.<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Cheers, Roy.<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>
<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";color:windowtext'>From:</span></b><span lang=EN-US
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>
Neil Holdsworth [mailto:NeilH@ices.dk] <br>
<b>Sent:</b> 01 November 2010 13:58<br>
<b>To:</b> Dick M.A. Schaap; Lowry, Roy K<br>
<b>Cc:</b> Accessions; platforms@biwebs1.nerc-liv.ac.uk;
sdn-tech@seadatanet.org<br>
<b>Subject:</b> RE: [Platforms] ROMANIA - MULTIPLE SHIPS OF ROMANIA<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Dick, Roy,<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I disagree with your approach, i know this discussion has
surfaced in the past and we seem to be at the same sticking point. The
‘unknown’ term is fine if it is in fact the case that no information is known
about the vessel, but in these cases something is known and being deliberately
overlooked in order to keep from adding new entries. I don’t like using ZZ99 as
a ‘bucket code’ to place everything in that doesn’t meet with the simple model
approach. This will cause us some headaches in the future with CSR’s if we
simply use ZZ99, as the country listed in the CSR is not necessarily the
country where the vessel was chartered from – and we will lose this
information. <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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>So before you agree to lose this information, i want you to
think about whether this is valuable information for someone looking at the
historical data to have access to.<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks, Neil.<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><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>
<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";color:windowtext'>From:</span></b><span lang=EN-US
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>
Dick M.A. Schaap [mailto:dick@maris.nl] <br>
<b>Sent:</b> 01 November 2010 13:10<br>
<b>To:</b> Lowry, Roy K<br>
<b>Cc:</b> Accessions; platforms@biwebs1.nerc-liv.ac.uk;
sdn-tech@seadatanet.org<br>
<b>Subject:</b> Re: [Platforms] ROMANIA - MULTIPLE SHIPS OF ROMANIA<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Dear Roy,<br>
<br>
I rather go for a general 'Unknown' term in the Vessel vocabulary than starting
a whole list of:<br>
MULTIPLE SHIPS OF ROMANIA<br>
MULTIPLE SHIPS OF BULGARIA <br>
etc<br>
etc<br>
etc<br>
<br>
So I encourage using the ZZ99 term and not diluting the Vessel directory with
all new entries.<br>
<br>
Hope all colleagues agree.<br>
<br>
Greetings,<br>
<br>
Dick M.A. Schaap<br>
SeaDataNet Technical Coordinator<br>
<br>
<br>
On 01/11/2010 11:44, Lowry, Roy K wrote: <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Dear
All,</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>In
cases such as these we should simply use the generic ‘unknown’ ship code
(ZZ99). What guarantee do we have that the flags of these ships were
Romanian?</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I’ve
copied this message to the SeaDataNet TTT list so discussion of this issue
doesn’t need to wait until December. </span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Cheers,
Roy.</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p>
<div>
<div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0cm 0cm 0cm;
border-color:-moz-use-text-color -moz-use-text-color'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <a
href="mailto:platforms-bounces@biwebs1.nerc-liv.ac.uk">platforms-bounces@biwebs1.nerc-liv.ac.uk</a>
[<a href="mailto:platforms-bounces@biwebs1.nerc-liv.ac.uk">mailto:platforms-bounces@biwebs1.nerc-liv.ac.uk</a>]
<b>On Behalf Of </b><a href="mailto:accessions@ices.dk">accessions@ices.dk</a><br>
<b>Sent:</b> 01 November 2010 10:32<br>
<b>To:</b> <a href="mailto:platforms@biwebs1.nerc-liv.ac.uk">platforms@biwebs1.nerc-liv.ac.uk</a><br>
<b>Subject:</b> [Platforms] ROMANIA - MULTIPLE SHIPS OF ROMANIA</span><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal> <o:p></o:p></p>
<p style='margin-bottom:12.0pt'>Dear Platform Group,<br>
<br>
The code MULTIPLE SHIPS OF ROMANIA from ROMANIA has been added according to the
old definitions of "90" and "99" codes for unknown vessels.
The topic of handling "unknown" codes has to be resolved by
discussions at SeaDataNet at their next technical meeting.<br>
<br>
<b>Original Requester : Gabriel Ion (<a href="mailto:gion@geoecomar.ro">gion@geoecomar.ro</a>)</b><br>
<br>
Code : 7390<br>
Name : MULTIPLE SHIPS OF ROMANIA<br>
Flag : ROMANIA - RO (ISO Country Code)<br>
Platform Class : Vessel of opportunity<br>
<br>
<b>General Comments:</b><br>
We named UVOO_1 for any Unknown Vessel Of Opportunity used by GeoEcoMar prior
to year 2002 <br>
(added by: Gabriel Ion - 20/10/2010 00:00:00)<br>
<br>
<br>
Kind regards,<br>
The ICES Data Centre<br>
<br>
International Council for the Exploration of the Sea <br>
Email: <a href="mailto:accessions@ices.dk">accessions@ices.dk</a><br>
Web: <a href="http://www.ices.dk">http://www.ices.dk</a><br>
<br>
Tel: +45 3338 6718 Fax: +45 3393 4215<br>
H.C. Andersens Boulevard 44-46<br>
1553 Copenhagen V. Denmark<br>
<br>
<a href="http://www.ices.dk/datacentre/requests" target="_new">ICES Platform
Code Requests Application</a><br>
Read the latest ICES Data Centre e-News <a
href="http://www.ices.dk/datacentre/updates/DC_update.htm" target="_new">online</a><o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p>This email has been generated by the ICES Platform Code Requests Application<o:p></o:p></p>
<p class=MsoNormal><br>
-- <br>
This message (and any attachments) is for the recipient only. NERC <br>
is subject to the Freedom of Information Act 2000 and the contents <br>
of this email and any reply you make may be disclosed by NERC unless <br>
it is exempt from release under the Act. Any material supplied to <br>
NERC may be stored in an electronic records management system. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='color:windowtext'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>Denne
mail er blevet scannet af </span><span style='color:windowtext'><a
href="http://www.comendo.com"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>http://www.comendo.com</span></a></span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'> og
indeholder ikke virus!</span><span style='color:windowtext'><o:p></o:p></span></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><span
style='color:windowtext'>
<hr size=2 width="100%" align=center>
</span></div>
</div>
<div class=MsoNormal align=center style='text-align:center'><span
style='color:windowtext'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>Denne
mail er blevet scannet af </span><span style='color:windowtext'><a
href="http://www.comendo.com"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>http://www.comendo.com</span></a></span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'> og
indeholder ikke virus!</span><span style='color:windowtext'><o:p></o:p></span></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><span
style='color:windowtext'>
<hr size=2 width="100%" align=center>
</span></div>
</div>
</div>
</body>
</html>