iEtherpad

http://ietherpad.com/devont20100413  (note: ietherpad, not etherpad)

Agenda

1. Logistics: Welcome, Minutes Review, Agenda Review
2. Accuracy specification and related aspects (Carlos, Luis)
3. Status of collaboration with W3C SSN (Luis)
4. Case Studies (all)
5. Summary of approach for multibeam ontology extension (Bob A.)
6. End Logistics: Next meeting, Action items, Attendees

Minutes

Logistics: Welcome, Minutes Review, Agenda Review, Etherpad

• Minutes review
• Agenda approval
• iEtherpad: see link above.

Accuracy specification and related aspects

See http://marinemetadata.org/community/teams/ontdevices/devontssn.

• Example is about this instrument:http://www.vaisala.com/instruments/products/wm30.html
   
• Use this link: http://mmisw.org/browser/manage/?action=load&clear=true&uri=http://mmisw.org/ont%3Fform=owl%26uri=http://mmisw.org/ont/mmi/devontssn
   
• This link is direct to this instance:  http://mmisw.org/browser/individuals/1100099319/
• Need to better capture dependencies to individual measurement capabilities. In this example, for the same sensed variable, wind speed, we have two different accuracies depending on the measurement range:
  
  • A particular measurement capability, wind speed measurement range 10 to 60 m/s, has a particular measurement capability, accuracy of < 2%
  • Another particular measurement capability, wind speed measurement range up to 10 m/s, has a particular measurement capability, accuracy ±0.3 m/s.
  • In the current ontology, measurement capabilities are associated with the instrument (System), but there is no way to explicitly relate their possible interdependencies.
• We agreed on including a condition property for measurement capabilities as follows:
  • MeasurementCapability hasCondition MeasurementCapability
• Action item: [Carlos] include this property and update instantiation example.

Status of collaboration with W3C SSN

• Continue the link with them, leverage whatever is appropriate.
  

Case Studies

• It is proposed that each Case Study:
  • be documented in a MMI page
  • respective ontology(ies) be registered in the ORR
  • related publication(s) be prepared

• We will continue focusing on the multibeam ontology as a prototypical case study for now. Hopefully others will follow.

Summary of approach for multibeam ontology extension

The Poster at OS'10

http://mmisw.org/ont/r2r/multibeam

• Controlled vocabulary definitions
  
  • Need to link the classes with definitions in controlled vocabularies.
  • Solution: Add a property in appropriate base places.
  • Prefer to use URIs for those definitions. Force it? best practice?

• Overlapping/mix of concepts?
  
  • ProcessInput and ProcessOutput used as the main "extension points" for this multibeam ontology.
  • These elements have not been revised for some time now, and it seems there is some overlapping between them and other classes in the ontology, in particular, MeasurementCapability. We need to clarify the distinction and their respective roles.

• Action item: [Bob A., Carlos] Look into these issues.

End Logistics: Next meeting, Action items, Attendees

Action Items

DevOnt tracker: http://code.google.com/p/devont/issues/list

• [Carlos] include this property and update instantiation example
• [Bob A., Carlos] determine approach for capturing controlled definitions
• [Bob A., Carlos] look into ProcessOutput vs. MeasurementCapability related issues
  

Next Telecon Time

Next telecon is Tuesday 2010.04.27 at 1500 GMT.

Attendees:

• Bob Arko
• Bruce Andrews
• Nan Galbraith
• Luis Bermudez
• John Graybeal
• Carlos Rueda