[OntGov] Building the semantics resources for NETMAR WPS chains

[John Helly]

Hi Roy.
What are P01, ...?
Cheers.
--------------
John Helly, University of California, San Diego / San Diego Supercomputer Center / Scripps Institution of Oceanography / 760 840 8660 mobile / stonesteps7 (Skype) / stonesteps7 (iChat) / http://www.sdsc.edu/~hellyj

On Oct 10, 2011, at 1:58 AM, Lowry, Roy K. wrote:

Dear All,
 
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. 
 
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.
 
Does anybody have any problem with this approach? 
Anybody any recommendations for such a vocabulary or should we build one (maybe 10-20 concepts) through discussion on this list?
 
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.
 
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.
 
Again, are there any comments on this approach?
 
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’!
 
Cheers, Roy.
 

-- 
This message (and any attachments) is for the recipient only. NERC 
is subject to the Freedom of Information Act 2000 and the contents 
of this email and any reply you make may be disclosed by NERC unless 
it is exempt from release under the Act. Any material supplied to 
NERC may be stored in an electronic records management system. _______________________________________________
OntGov mailing list
OntGov at mailman.nerc-liv.ac.uk
http://mailman.nerc-liv.ac.uk/mailman/listinfo/ontgov

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.nerc-liv.ac.uk/pipermail/ontgov/attachments/20111010/70f7ae0c/attachment.html