<html dir="ltr"><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="GENERATOR" content="MSHTML 8.00.6001.19120">
<style title="owaParaStyle"><!--P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body ocsi="x">
<div dir="ltr"><font color="#000000" size="2" face="Tahoma">Hi John,</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">P01 is the BODC Parameter Markup Vocabulary (<a href="http://vocab.ndg.nerc.ac.uk/list/P01/">http://vocab.ndg.nerc.ac.uk/list/P01/</a>), which is a collection of 27,000+ concepts that may be used to label parameters.
If you want to browse it i suggest you use the tool at <a href="http://seadatanet.maris2.nl/v_bodc_vocab/welcome.aspx/">
http://seadatanet.maris2.nl/v_bodc_vocab/welcome.aspx/</a> You can either click on 'P011' (an older label that will be superseded by P01 in due course) or click on 'P081' and take the thesaurus tool offered, which will allow you to browse a 4-level hierarchy
(P08 to P03 to P02 to P01)</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">P06 is another vocabulary of units of measure, which can again be browsed through the SeaDataNet client (choose P061).</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">Any clearer?</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">Cheers, Roy.</font></div>
<div dir="ltr">
<hr tabindex="-1">
</div>
<div dir="ltr"><font size="2" face="Tahoma"><b>From:</b> ontgov-bounces@mailman.nerc-liv.ac.uk [ontgov-bounces@mailman.nerc-liv.ac.uk] On Behalf Of John Helly [hellyj@ucsd.edu]<br>
<b>Sent:</b> 10 October 2011 20:18<br>
<b>To:</b> NETMAR Scenario Ontology Governance<br>
<b>Subject:</b> Re: [OntGov] Building the semantics resources for NETMAR WPS chains<br>
</font><br>
</div>
<div></div>
<div>Hi Roy.
<div>What are P01, ...?<br>
<div><span class="Apple-style-span"><span class="Apple-style-span">
<div><span class="Apple-style-span">
<div><span class="Apple-style-span">
<div><span class="Apple-style-span">
<div><span class="Apple-style-span">
<div><span class="Apple-style-span">
<div><span class="Apple-style-span"><span class="Apple-style-span">
<div><span class="Apple-style-span">
<div><span class="Apple-style-span">
<div><span class="Apple-style-span"><span class="Apple-style-span">
<div style="FONT-FAMILY: Helvetica"><span style="FONT-FAMILY: Helvetica" class="Apple-style-span">Cheers.</span></div>
<div style="FONT-FAMILY: Helvetica"><span style="FONT-FAMILY: Helvetica" class="Apple-style-span">--------------</span></div>
<div><font class="Apple-style-span" face="'Synchro LET'">John Helly, University of California, San Diego / San Diego Supercomputer Center / Scripps Institution of Oceanography / 760 840 8660 mobile / stonesteps7 (Skype) / stonesteps7 (iChat) /
<a href="http://www.sdsc.edu/~hellyj" target="_blank">http://www.sdsc.edu/~hellyj</a></font></div>
</span></span></div>
</span></div>
</span></div>
</span></span></div>
</span></div>
</span></div>
</span></div>
</span></div>
</span></div>
</span></span></div>
<br>
<div>
<div>On Oct 10, 2011, at 1:58 AM, Lowry, Roy K. wrote:</div>
<br class="Apple-interchange-newline">
<span class="Apple-style-span">
<div><font size="2" face="Calibri, sans-serif">
<div>Dear All,</div>
<div> </div>
<div>I need to build the semantic resources (SKOS concept collections and schemes) to support semantic validation of WPS connections and suitable user feedback in a service chaining editor. The proposed approach is to tag data sources and service outputs with
parameter labels from the P01 vocabulary and units of measure from the P06 vocabulary (service output labels could be inherited from the service data source: depends what the service is doing). Service inputs are then tagged with the ‘expected’ input parameter
and ‘expected’ unit of measure. </div>
<div> </div>
<div>The service ‘expected input parameter’ needs to be from a much broader vocabulary than P01. For example, it’s quite possible for a service to work OK with any kind of water temperature, which means a whole host of P01 codes are acceptable. Consequently,
I think we need to set up a concept collection of ‘service input parameters’ that are then mapped to P01. This raises a couple of questions to the ontology governance.</div>
<div> </div>
<ol style="MARGIN-TOP: 0pt; MARGIN-BOTTOM: 0pt; MARGIN-LEFT: 36pt">
<li>Does anybody have any problem with this approach? </li><li>Anybody any recommendations for such a vocabulary or should we build one (maybe 10-20 concepts) through discussion on this list?</li></ol>
<div> </div>
<div>Once we have this concept collection in place we can set up a simple client service to give a green /red light on whether the P01 code labelling the ‘plug’ is a narrowMatch for the broader term labelling the ‘socket’ on the service.</div>
<div> </div>
<div>The plan with units of measure is to map the P06 concepts to SI dimensions. For example, centimetres and millimetres would map through a broadMatch to ‘[LENGTH]’ . A useful embellishment (not essential for the service chain use case) could be to make
the canonical unit mappings (e.g. [LENGTH] to m) exactMatches. A client service would then be built that gives a green light if the input and output units have the same P06 label, an amber light if the P06 labels are different but they have the same dimensionality
and a red light if they don’t.</div>
<div> </div>
<div>Again, are there any comments on this approach?</div>
<div> </div>
<div>A fun extension would be to develop a knowledge base of simple unit conversion WPS (e.g. scaling by a power of 10) with inputs and outputs labelled using P06. That way, if the units mismatch and a conversion is possible, the service chaining editor could
even ‘auto-correct’!</div>
<div> </div>
<div>Cheers, Roy.</div>
<div> </div>
</font><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>
OntGov mailing list<br>
<a href="mailto:OntGov@mailman.nerc-liv.ac.uk">OntGov@mailman.nerc-liv.ac.uk</a><br>
<a href="http://mailman.nerc-liv.ac.uk/mailman/listinfo/ontgov" target="_blank">http://mailman.nerc-liv.ac.uk/mailman/listinfo/ontgov</a><br>
</div>
</span></div>
<br>
</div>
</div>
<script id="dstb-id" language="javascript">if(typeof(dstb)!= "undefined"){ dstb();}</script>
<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>