<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)">
<base href="x-msg://762/">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle19
{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 style='word-wrap: break-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi John,<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'>Broad categories are held in L05 and mapped to L221 by
narrowMatch relationships. The only ‘broadening’ within the list is
where names are known to different levels of detail.<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'>Putting a semantic model behind the naming is a good idea: it’s
what I’ve done with parameters. But as you say, it’s work and
unless a volunteer steps forward, it’s unlikely to happen to existing
content this year. However, in the mean time I’ll make sure that if
content containing this level of structure is supplied then it will be
preserved. Getting the MBARI list with structured names would be good for both
content extension and providing an example of the structuring.<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'>My purpose for the list is to provide a vocabulary for tagging
data objects with their ‘data production tool or tools’. Our system
uses this vocabulary in a structure with ordered workflow so a series can be
tagged ‘water bottle then autoanalyser’. However, I’m
guessing others may have additional applications. <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"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> John Graybeal
[mailto:jbgraybeal@mindspring.com] <br>
<b>Sent:</b> 29 September 2010 16:36<br>
<b>To:</b> Lowry, Roy K<br>
<b>Cc:</b> seavox@mailman.nerc-liv.ac.uk<br>
<b>Subject:</b> Re: [Seavox] Devices: a new vocabulary for SeaVoX<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Yes, with some caveats:<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>It wasn't clear from the email, but a casual look at the
list suggests it *only* contains instrument names, not any broader instrument
categories. I think that's important to keep those two lists separate, to
avoid conflating them.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I think each name corresponds to these things: (a)
manufacturer; (b) model; (c) casual name that blends (a) and (b) with a
function. The list becomes more useful if (a), (b), and the function all
come from controlled vocabularies, and are separately described within each
term. I know that's work, I'm just predicting it's work that will be done
sooner or later, and normalizing the formation of the list now will save you
(or many others) time later.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>MBARI has a list of such instruments broken down in this
way, it could probably be provided as well, which gets back to Nan's point
about the purpose of the list and the methods for contributing to it.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>John<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>.<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal>On Sep 29, 2010, at 00:57, Lowry, Roy K wrote:<o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Dear
All,<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>SeaVoX
traffic resembles buses. Nothing for ages then two messages come
together!<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>There
has been a project in BODC over the past couple of years to tag data with more
detailed device metadata, using actual instrument names rather than instrument
categories to populate ‘data production tool’ fields in
metadata. Thus ‘Aanderaa RCM4/5’ is now used instead of
‘Savonious rotor current meter’. When I looked at the
metadatabase we were building to support this it became apparent that it fitted
very comfortably into the vocabulary data model and that the concepts in it
could be mapped to the ‘SeaDataNet device categories’ (the
L05x group of lists) to form quite a handy thesaurus, which I have exposed
through the NERC Vocabulary Server as<span class=apple-converted-space> </span><a
href="http://vocab.ndg.nerc.ac.uk/list/L221">http://vocab.ndg.nerc.ac.uk/list/L221</a><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>In
parallel, the IODE GE-BiCh expert group – largely the work of Mary
Kennedy - has compiled a comprehensive list of nets and plankton samplers
that would fit neatly together with the BODC list. Mary and Hernan Garcia of
USNODC have also recently been working on compiling a catalogue of water
samplers, which could be included.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>So,
my proposal is that the L221 vocabulary be transferred from BODC to SeaVoX
governance, merged with the GE-BiCh contributions and further developed as a
joint effort by SeaVoX. Is this an acceptable proposition?<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Cheers,
Roy.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif"'><br>
--<span class=apple-converted-space> </span><br>
This message (and any attachments) is for the recipient only. NERC<span
class=apple-converted-space> </span><br>
is subject to the Freedom of Information Act 2000 and the contents<span
class=apple-converted-space> </span><br>
of this email and any reply you make may be disclosed by NERC unless<span
class=apple-converted-space> </span><br>
it is exempt from release under the Act. Any material supplied to<span
class=apple-converted-space> </span><br>
NERC may be stored in an electronic records management system.<br>
--<span class=apple-converted-space> </span><br>
This message (and any attachments) is for the recipient only. NERC<span
class=apple-converted-space> </span><br>
is subject to the Freedom of Information Act 2000 and the contents<span
class=apple-converted-space> </span><br>
of this email and any reply you make may be disclosed by NERC unless<span
class=apple-converted-space> </span><br>
it is exempt from release under the Act. Any material supplied to<span
class=apple-converted-space> </span><br>
NERC may be stored in an electronic records management system.<span
class=apple-converted-space> </span>_______________________________________________<br>
Seavox mailing list<br>
<a href="mailto:Seavox@mailman.nerc-liv.ac.uk">Seavox@mailman.nerc-liv.ac.uk</a><br>
<a href="http://mailman.nerc-liv.ac.uk/mailman/listinfo/seavox">http://mailman.nerc-liv.ac.uk/mailman/listinfo/seavox</a><o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'><br>
--------------<o:p></o:p></span></p>
</div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black'>I have my new work email
address: <a href="mailto:jgraybeal@ucsd.edu">jgraybeal@ucsd.edu</a></span><o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'>--------------</span><o:p></o:p></p>
</div>
<p class=MsoNormal><span class=apple-style-span><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'>John Graybeal <<a href="mailto:jgraybeal@ucsd.edu">mailto:jgraybeal@ucsd.edu</a>>
</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'>phone: 858-534-2162<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'>System Development Manager<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'>Ocean Observatories Initiative Cyberinfrastructure Project: <a
href="http://ci.oceanobservatories.org">http://ci.oceanobservatories.org</a><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'>Marine Metadata Interoperability Project: <a
href="http://marinemetadata.org">http://marinemetadata.org</a> <o:p></o:p></span></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
<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.</body>
</html>