<html dir="ltr"><head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta content="MSHTML 6.00.6000.16825" name="GENERATOR">
<style title="owaParaStyle">P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body bgcolor="#ffffff" ocsi="x">
<div dir="ltr"><font face="Tahoma" color="#000000" size="2">Hi Michele,</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">The objective of C19 is to use SeaVoX governance to overcome some of the difficulties that IHO governance has encountered moving S23 on from its 1953 version due to repreated vetos over the naming of Sea of Japan.
It is based on the latest IHO proposals with some extensions that have been requested, such as extension to include freshwater bodies.</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">C19 is largely a superset of C16, but there are some cases where the relationship between C16 and C19 isn't perfectly clean. This is because I have followed IHO, who decided that some areas required more extensive
modification than others. I have a mapping between C16 and C19 prepared by Greg Read, which I will load up into the server at some stage. Inevitably because of the way IHO have done things this will be more complex than pure synonyms.</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">I have deliberately hedged the issue of multi-lingual naming for the present. I have three options open to me. One is the kludge used in some versions of IHO I have seen with a second language in brackets such as
English Channel (La Manche). I don't like this because it implies that the French is a second class alternative to the English. Secondly, I could add entries for other languages and map them as synonyms. However, this means that the code for La Manche would
be different to English Channel, which could cause problems for tools that aren't clever enough to realise the two are mapped. The third is to investigate other technological solutions and adopt something appropriate - I particularly like the way Gemet handles
languages. This is my preferred option, but needs work. If NETMAR gets funded then that work should get done. So, for now I prefer to wait.</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">In the current implementation of C19 the maximum code length is 8 and the maximum name length is 55 bytes. I very much doubt if the code limit will be exceeded, but the name limit could possibly grow. The codes
used are those used by IHO with underscores replacing periods.</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">I appreciate the consequences for SeaDataNet. It's not just the tools that will need changing. Some partners will also have metadata or data files with C16 embedded that will need editing. The TTT obviously needs
to carefully consider whether such change is worthwhile and if so its timing, which I think would have to be a part of the next major reversioning.</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">Cheers, Roy.</font></div>
<div dir="ltr">
<hr tabindex="-1">
</div>
<div dir="ltr"><font face="Tahoma" size="2"><b>From:</b> Michele FICHAUT [Michele.Fichaut@ifremer.fr]<br>
<b>Sent:</b> 04 May 2009 09:28<br>
<b>To:</b> Lowry, Roy K; Lowry, Roy K<br>
<b>Cc:</b> seavox@mailman.nerc-liv.ac.uk; Weatherall, Pauline; francisco.hernandez@vliz.be<br>
<b>Subject:</b> Re: [Seavox] Sea Area Thesaurus<br>
</font><br>
</div>
<div></div>
<div>Dear Roy,<br>
<br>
Concerning SeaDataNet, here are some questions :<br>
- Is this change (C16 to C19) related to the new IHO policy which delegates to national representatives the naming<br>
of the local sea areas (still under discussion?)<br>
- Is the high level of C19 the same than C16 (is C16 included as a whole in C19)?<br>
- Will a mapping between C16 and C19 be provided?<br>
- Is a national language support planned (particularly for high resolution areas, Manche and English Channel for example)?<br>
- Is there a maximum length of the code, and the name?<br>
<br>
If we adapt this list for SeaDatanet there are consequences on :<br>
+ Mikado, NEMO, the XML schemas<br>
<br>
Best regards<br>
<br>
Michèle<br>
<br>
<br>
<br>
Lowry, Roy K a écrit :
<blockquote type="cite"><style>.EmailQuote {
PADDING-LEFT: 4pt; MARGIN-LEFT: 1pt; BORDER-LEFT: #800000 2px solid
}
</style><font face="Calibri, sans-serif" size="2">
<div>Dear All,</div>
<div> </div>
<div>Some life at last on planet SeaVoX!</div>
<div> </div>
<div>The first stage of the Sea Area thesaurus project is now done with the XML publication of an interlinked set of terms at
<a href="http://vocab.ndg.nerc.ac.uk/list/C191/current" target="_blank"><font color="#0000ff"><u>http://vocab.ndg.nerc.ac.uk/list/C191/current</u></font></a>. A formatted version of the terms (but not their linkages) may be found as the C191 list at
<a href="http://seadatanet.maris2.nl/v_bodc_vocab/welcome.aspx" target="_blank">http://seadatanet.maris2.nl/v_bodc_vocab/welcome.aspx</a></div>
<div> </div>
<div>The next job is to obtain suitable public domain polygon co-ordinates corresponding to the terms and arrange for them to be accessible via WFS. There are a number of potential data sources, including the 1953 S23 co-ordinates held at BODC, data served
from the VLIZ gazetteer. URLs to WFS-accessible polygons will be included as concept definitions as they become available. An interesting test of OGC interoperability might be to have these served from multiple sources!</div>
<div> </div>
<div>A meeting is planned at BODC around 14-15 May to identify additional sources of high resolution data for the C19 regions in the vicinity of the UK together with a set of finer-grained sub-regions for UK waters that would be added to the thesaurus.</div>
<div> </div>
<div>One issue for SeaDataNet colleagues on the list to consider is whether we should consider replacing C16 by C19. If so, when and how?</div>
<div> </div>
<div>Cheers, Roy.</div>
<div> </div>
</font>
<pre><hr width="90%" size="4">
_______________________________________________
Seavox mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Seavox@mailman.nerc-liv.ac.uk">Seavox@mailman.nerc-liv.ac.uk</a>
<a class="moz-txt-link-freetext" href="http://mailman.nerc-liv.ac.uk/mailman/listinfo/seavox" target="_blank">http://mailman.nerc-liv.ac.uk/mailman/listinfo/seavox</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
_
_| |_
(o o)
___________________________oOO-( )-OOo__________________________________
Michele FICHAUT - IFREMER/BREST - SISMER - B.P. 70 - 29280 PLOUZANE
TEL:(33)02.98.22.46.43/(33)02.98.22.49.16 (secr.) FAX:(33)02.98.22.46.44
Email: <a class="moz-txt-link-abbreviated" href="mailto:Michele.Fichaut@ifremer.fr">Michele.Fichaut@ifremer.fr</a> WWW : <a class="moz-txt-link-freetext" href="http://www.ifremer.fr/sismer/" target="_blank">http://www.ifremer.fr/sismer/</a>
________________________________________________________________________
</pre>
</div>
<script language="javascript" id="dstb-id">if(typeof(dstb)!= "undefined"){ dstb();}</script>
</body>
</html>