<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style id=owaTempEditStyle>
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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:11.0pt;
font-family:"Calibri","sans-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";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{mso-style-name:msochpdefault;
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
span.balloontextchar0
{mso-style-name:balloontextchar;
font-family:"Tahoma","sans-serif";}
span.emailstyle20
{mso-style-name:emailstyle20;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.emailstyle21
{mso-style-name:emailstyle21;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle22
{mso-style-name:emailstyle22;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle25
{mso-style-name:emailstyle25;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle28
{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 lang=EN-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'>Hi again,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>If somebody is willing to
design/build an administrative units classification, then I will happily serve
it through the NVS. Once served, it can be set up as an additional keyword
source for MEDIN documents. As with the Crown Estate vocabularies,
entries can be mapped to the parent P02 term. This means that metadata
marked up with specific administrative unit types will be found by
semantically-aware search clients looking for ‘Administrative units’
(which might possibly become ‘Administrative and legislative units’.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'> What is needed is a straw
man (James seems to be volunteering) that we can circulate and amend on this
list. All that’s required is a two-column table containing
administrative unit category labels and their definitions. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Cheers, Roy.<o:p></o:p></span></p>
<p class=MsoNormal><span style='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"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> James Dargie
[mailto:James.Dargie@snh.gov.uk] <br>
<b>Sent:</b> 30 May 2012 10:17<br>
<b>To:</b> Lowry, Roy K.; Becky Seeley<br>
<b>Cc:</b> Cotton, David P.<br>
<b>Subject:</b> RE: keyword issue<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Hi,</span><span lang=EN-US style='font-size:12.0pt;font-family:
"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I
can validate the data, as Becky kindly suggested I use <span style='color:blue'>'Horizontal
spatial co-ordinates' which does link through to an INSPIRE topic, it may not
be the most appropriate keyword term for trying to give meaningful description
to the dataset (the whole point of keywording) but it has allowed me to at
l3east get a valid xml metadata record which I'm content to run with for now.
So in terms of urgency I can let live for now, but MEDIN do need to take on
board that if we want medtadata that is effective as well as compliant, then we
do need appropriate term lists.</span></span><span lang=EN-US style='font-size:
12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>So,
yes I can see that it would be useful work for the MEDIN standards group to
define an administrative units classification. If we are wanting a list of
Administrative units to form a domain-specific vocab of </span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>‘<b>Conservation
zone extents</b>’</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:black'>, i.e the different types of zone extents </span><span
lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>then I'm
sure I can assist ensuring the detailed designation types are listed.</span><span
lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>James</span><span
lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
</div>
<div class=MsoNormal align=center style='text-align:center'><span lang=EN-US
style='font-size:12.0pt;font-family:"Times New Roman","serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><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"'> Lowry,
Roy K. [mailto:rkl@bodc.ac.uk] <br>
<b>Sent:</b> 29 May 2012 21:46<br>
<b>To:</b> Becky Seeley; James Dargie<br>
<b>Cc:</b> Cotton, David P.<br>
<b>Subject:</b> RE: keyword issue</span><span lang=EN-US style='font-size:12.0pt;
font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>Right,<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>Let's start to gather/exchange some basic information.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>First, the P02 vocabulary is a collection of terms that describes
the parameters in a dataset in such a way that it facilitates the discovery of
that dataset when attached to that dataset as keywords. In no way is it a
resource that describes the dataset to which it is linked.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>Secondly, it was initially designed to annotate datasets
comprising individual ocean geographic features. In other words, as soon
as the mapping to the INSPIRE topic OGF breaks down it starts to move outside
its comfort zone.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>There have been two precedents in MEDIN where we have sidestepped
this issue by setting up a P02 keyword that is very generic which is then
backed up by one or more keywords from domain-specific vocabularies. This
has been partially done for marine archeology (but I await the
domain-specific vocabs to load into NVS) and the Crown Estates datasets (where
I have just set up two new vocabularies (M03 and M04) to Crown
Estates specification) that accompany the very bland P02 term 'Man-made structures'.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>We could do the same for James and other datasets of this type -
set up something bland in P02 whose primary function is to map the dataset to
the INSPIRE theme 'Administrative Units' and then define an additional
keyword vocab to classify administrative unit under MEDIN governance that
could be used to tag metadata in addition to the P02 keyword.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>So, what do people think?<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>Could developing an administrative units classification be a job
for the MEDIN standards group?<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>If we go for a P02 'Administrative Units' term, which P03 terms
(NOT term) would it map to? Does this exist or does P03 need extending?<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>What kind of time pressures are we under for James to publish the
metadata that is currently failing verification?<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>Cheers, Roy.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<div id=divRpF291315>
<div class=MsoNormal align=center style='text-align:center'><span lang=EN-US
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span lang=EN-US
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>From:</span></b><span
lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'> Becky Seeley [bese@MBA.ac.uk]<br>
<b>Sent:</b> 29 May 2012 16:57<br>
<b>To:</b> Lowry, Roy K.<br>
<b>Cc:</b> Cotton, David P.<br>
<b>Subject:</b> FW: keyword issue<o:p></o:p></span></p>
</div>
<div>
<div>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Hi Roy, </span><span
lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>See James’
response below, it’s never simple… </span><span lang=EN-US
style='font-family:Wingdings;color:#1F497D'>J</span><span lang=EN-US
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>I think there may
also be a role for your </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>Conservation zone extents keyword in describing the formalised
extents at the end of the process e.g we already have some layers of SSSI or
SAC extents which would fall under the term you described. But James makes the
point at the moment they are not formalised so this is inappropriate and
politically controversial for the layers he is describing.</span><span
lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>My feeling is that we may also need an additional P03 keyword to
cover this type of data as habitat is not really an appropriate home for it.</span><span
lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>Many thanks for your help.</span><span lang=EN-US
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>Bex</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <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:black'>From:</span></b><span lang=EN-US
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> James
Dargie [mailto:James.Dargie@snh.gov.uk] <br>
<b>Sent:</b> 29 May 2012 16:42<br>
<b>To:</b> Becky Seeley<br>
<b>Cc:</b> Ben James<br>
<b>Subject:</b> RE: keyword issue</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Interesting wrt t</span><span lang=EN-US style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>he
‘administration’ terms in P03; no wonder I didnae find a value that
suited my purposes!</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>I'm agreed that relevant keywords for Search location
boundaries need to relate to the INSPIRE ‘Administrative units’
topic. </span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>wrt the P03 term ‘Habitat’, the MPA Search location
boundaries are units within which the Scottish MPA project will examine the
evidence basis (species or habitats, large scale features, geodiversity
features) for designating an MPA somewhere within the Search location (the
final boundaries not necessarily equating to the search location boundary). As
such these boundaries are not the habitats; they do not fit well
within P03 'Habitat'.</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>I like the sound of a P02 term: </span><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>‘<b>Conservation
zone extents</b>’, though whether it best sits under P03 'Habitats' I
think is far more questionable. When we get round to drawing actual MPA
boundaries this term would suit them well and I'd welcome its presence as a
keyword somewhere in the hierarchy.</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>However, I cannot describe the Search location boundaries as
'Conservation zone extents'; in fact it would be extremly controversial if SNH
were to be seen to describe them as a conservation zones, they are merely part
of the process of defining the conservation zones that will pop out at the end
of the process. I'd suggest a P02 level term something down the lines
of:</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><strong><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>'Conservation process extents'</span></strong><span lang=EN-US
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>‘The geographic boundaries of areas within which the
scientific evidence base is examined for suitability for designation as a
Conservation zone of some description’<strong><span style='font-family:
"Arial","sans-serif"'>,</span></strong> I'm open better suggestions for the
term name or descriptor....</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>sorry....</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Best wishes</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>James</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span lang=EN-US
style='font-size:12.0pt;font-family:"Times New Roman","serif";color:black'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span lang=EN-US
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>From:</span></b><span
lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'> Becky Seeley [<a href="mailto:bese@MBA.ac.uk">mailto:bese@MBA.ac.uk</a>]
<br>
<b>Sent:</b> 29 May 2012 12:10<br>
<b>To:</b> James Dargie<br>
<b>Subject:</b> FW: keyword issue</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Any comments on this
as a solution, not convinced that habitat is the correct root? Obviously we can
send you an interim xml file as this will take over a week to clear.</span><span
lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Cheers </span><span
lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Bex </span><span
lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <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:black'>From:</span></b><span lang=EN-US
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> Lowry,
Roy K. [<a href="mailto:rkl@bodc.ac.uk">mailto:rkl@bodc.ac.uk</a>] <br>
<b>Sent:</b> 29 May 2012 11:19<br>
<b>To:</b> Becky Seeley<br>
<b>Cc:</b> Cotton, David P.; Leoni Adams; Lowry, Roy K.<br>
<b>Subject:</b> RE: keyword issue</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Hi Becky,</span><span
lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>First of all, the
‘administration’ in P03 means parameter administration (things like
auxiliary variables) and ‘dimensions’ means co-ordinate
variables. Nothing to do with regulation or legislation. Funny how many
different ways there are to interpret meaning as usage moves away from original
context. Basically, the whole ‘administration and dimensions’ group
shouldn’t be used in simple discovery metadata like MEDIN. The only
reason it exists is to provide a pathway in user interfaces to this type of
information.</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Right, to James’s
problem. Obviously what is needed is something new, that maps to the
INSPIRE ‘Administrative units’ topic. Looking at what already
exists, we have the P03 term ‘Habitat’. How about putting the
following new P02 term under that?</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>‘<b>Conservation zone
extents</b>’</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>‘The geographic boundaries
of areas in which human activity is regulated for the preservation of flora and
fauna or the habitat they require’ </span><span lang=EN-US
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Comments on the definition
welcome – possibly include James in the loop – as this certainly
isn’t my area of expertise. Once we’re happy within MEDIN,
I’ll put the addition to the SeaDataNet governance and if they’re
happy (usually no problem) then I’ll make the change.</span><span
lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Not sure what
‘urgent’ means. If I get the e-mail off to SeaDataNet this
week then I should be able to have the change done week beginning June 11 (on
leave next week). Would that be OK?</span><span lang=EN-US
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Cheers, Roy.</span><span
lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<p><span lang=EN-US style='color:black'>**********************************************************************<br>
This email and any files transmitted with it are confidential and <br>
intended solely for the use of the individual or entity to whom they <br>
are addressed. If you have received this email in error please <br>
notify the system manager or the sender. <br>
<br>
Please note that for business purposes, outgoing and incoming <br>
emails from and to SNH may be monitored.<br>
<br>
<br>
<br>
Tha am post-dealain seo agus fiosrachadh sam bith na chois <br>
d`iomhair agus airson an neach no buidheann ainmichte a-<br>
mh`ain. Mas e gun d' fhuair sibh am post-dealain seo le <br>
mearachd, cuiribh fios dhan manaidsear-siostaim no neach-<br>
sgr`iobhaidh. <br>
<br>
Thoiribh an aire airson adhbharan gnothaich, 's d`ocha gun t`eid <br>
s`uil a chumail air puist-dealain a' tighinn a-steach agus a' dol a-<br>
mach bho SNH<br>
<br>
<br>
**********************************************************************<o:p></o:p></span></p>
</div>
</div>
</div>
<p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'><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></span></p>
<p>**********************************************************************<br>
This email and any files transmitted with it are confidential and <br>
intended solely for the use of the individual or entity to whom they <br>
are addressed. If you have received this email in error please <br>
notify the system manager or the sender. <br>
<br>
Please note that for business purposes, outgoing and incoming <br>
emails from and to SNH may be monitored.<br>
<br>
<br>
<br>
Tha am post-dealain seo agus fiosrachadh sam bith na chois <br>
d`iomhair agus airson an neach no buidheann ainmichte a-<br>
mh`ain. Mas e gun d' fhuair sibh am post-dealain seo le <br>
mearachd, cuiribh fios dhan manaidsear-siostaim no neach-<br>
sgr`iobhaidh. <br>
<br>
Thoiribh an aire airson adhbharan gnothaich, 's d`ocha gun t`eid <br>
s`uil a chumail air puist-dealain a' tighinn a-steach agus a' dol a-<br>
mach bho SNH<br>
<br>
<br>
**********************************************************************<o:p></o:p></p>
</div>
</body>
</html>