<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=us-ascii">
<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";}
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";}
p.emailquote, li.emailquote, div.emailquote
{mso-style-name:emailquote;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:1.0pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.m
{mso-style-name:m;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{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-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>All,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The solution to this from a standards point of view is
that we will amend the xml which uses vocabs so that the term and code will
both be included as follows:<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:10.0pt;font-family:"Tahoma","sans-serif"'>Use
the gmx:Anchor element. This element substitutes for gco:CharacterString
and works in the following way:</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><gmd:keyword></span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
<gmx:Anchor xlink:href="</span><span lang=EN-GB style='font-size:10.0pt;
font-family:"Arial","sans-serif";color:black'><a
href="http://vocab.ndg.nerc.ac.uk/term/P021/59/ZOOB">http://vocab.ndg.nerc.ac.uk/term/P021/59/ZOOB</a></span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>"></span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Zoobenthos
taxonomy-related counts</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'></gmx:Anchor></span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'></gmd:keyword></span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>instead
of:</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><gmd:keyword><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
<gco:CharacterString></span><span style='font-size:10.0pt;font-family:
"Arial","sans-serif"'>Zoobenthos taxonomy-related counts</span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'></gco:CharacterString><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'></gmd:keyword><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 should give enough information for the portal to cope with
depreciations in vocabs.<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'>Unless you are generating discovery metadata yourselves then
this will not impact you as these changes will be made in the various tools
themselves in the next month so they generate xml that is correct. Once we have
a full example xml file we will rerelease the MEDIN discovery standard guidance
document.<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 Wishes<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Mark<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 style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> medin_standards-bounces@biwebs1.nerc-liv.ac.uk
[mailto:medin_standards-bounces@biwebs1.nerc-liv.ac.uk] <b>On Behalf Of </b>Lowry,
Roy K.<br>
<b>Sent:</b> 08 November 2010 16:45<br>
<b>To:</b> medin_standards@mailman.nerc-liv.ac.uk<br>
<b>Cc:</b> Clements, David O.; Jason Sadler; Thorne, Kay<br>
<b>Subject:</b> [Medin_standards] FW: P021 keyword storage in NERC/MEDIN
metadata<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'>Houston, we may have a problem……..<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'><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 style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
steve.donegan@stfc.ac.uk [mailto:steve.donegan@stfc.ac.uk] <br>
<b>Sent:</b> 08 November 2010 16:36<br>
<b>To:</b> Lowry, Roy K.<br>
<b>Cc:</b> jds@geodata.soton.ac.uk<br>
<b>Subject:</b> RE: P021 keyword storage in NERC/MEDIN metadata<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Hi Roy,</span><span lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>I think the problem stems from the fact that MEDIN provides the
keyword value i.e. "Zoobenthos taxonomy-related counts" and with this
in the iso gmd:thesaurusName element section gives a title of "SeaDataNet
P021 parameter discovery vocabulary" - there is no specification of the
actual term id & url i.e. </span><strong><span lang=EN-GB style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:black'>http://vocab.ndg.nerc.ac.uk/term/P021/59/ZOOB</span></strong><span
class=m><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>" elsewhere in the gmd:thesaurusName section. The ingest
system doesnt touch this element at all -its the portal that takes the keyword
value and recursively looks it up in available lists to get a definition - I
think this is how it works from what I've seen - until the actual term url and
version number is specified in the metadata I dont think there's a lot that can
be done?</span></span><span lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p>
<p class=MsoNormal><span class=m><span lang=EN-GB style='font-size:10.0pt;
font-family:"Arial","sans-serif";color:blue'>cheers,</span></span><span
lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p>
<p class=MsoNormal><span class=m><span lang=EN-GB style='font-size:10.0pt;
font-family:"Arial","sans-serif";color:blue'>Steve</span></span><span
lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> Lowry, Roy K. [mailto:rkl@bodc.ac.uk] <br>
<b>Sent:</b> 08 November 2010 15:55<br>
<b>To:</b> Donegan, Steve (STFC,RAL,SSTD)<br>
<b>Cc:</b> Jason Sadler<br>
<b>Subject:</b> P021 keyword storage in NERC/MEDIN metadata</span><o:p></o:p></p>
<div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Hi
Steve,<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>I’m
currently trying to understand/overcome the consequences of the dynamic nature
of the P021 vocabulary, which has a governance that allows term broadening and
term deprecation for the MEDIN/NERC portals. Basically, what can happen
as a result is that the text associated with a given URI can change and,
if they specify P021 and just P02, they can disappear. Anything
that disappears (moves into P022) has a replacement P021 term indicated by a
1-to-1 mapping.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>In
SeaDataNet we manage this by refreshing the vocabulary in the metadata
generation tools that produce the XML. This leaves the issue of stale P021
text and deprecated codes in XML files ‘in transit’ and
metadatabases generated from the ingestion of these files. We only
ingest and store the URIs: translation to text is handled by a dynamic call to
the vocabulary server. <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>If
the URI has a version number embedded in it then this call returns the text as
it was at the time of metadata creation. Alternatively, replacing the
version number by ‘current’ in a URL or ‘::’ in a URN
causes the most up-to-date text to be displayed. We have adopted the latter
approach in SeaDataNet, but it isn’t the only approach.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Deprecation
in SeaDataNet is dealt with by a daily cron that sweeps the metadatabases and
automatically translates any deprecated URIs into their replacement.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>I’m
not sure how this issue is being dealt with in the MEDIN/NERC case, but some
code I’ve seen lately (which I think is the portal) seems to do a
verifyTerm against the current vocabulary list, which if you aren’t
refreshing content seems like an accident waiting to happen.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Any
clarification you can give me on what happens to MEDIN XML after they have been
harvested would be helpful.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Cheers,
Roy.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<p class=MsoNormal><span lang=EN-GB><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><span lang=EN-GB>-- <br>
Scanned by iCritical. <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p>
</div>
</body>
</html>