iEtherpad

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

Agenda

1. Logistics: Welcome, Minutes Review, Agenda Review
2. Modeling accuracy - take 2 (Carlos, Luis)
3. Modeling a certain instrument model
4. Units and definitions
5. End Logistics: Next meeting, Action items, Attendees

Minutes

Logistics: Welcome, iEtherpad, Minutes Review, Agenda Review

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

Modeling accuracy - take 2

Updates to DevOnt:

Object property added: hasMeasurementCapabilityCondition with domain and range MeasurementCapability.

ValueType individuals mPerSec and percent added. Note: These instances will eventually be defined in a separated ontology.

The resulting ontology (click to open full resolution in a new window):

Accuracy example updated

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

• Please note that the VaisalaWM30 example may need to show how wind direction accuracy will depend on measured wind speed. That may be a much more complex exampe. (I'm adding this in case I miss the discussion. - Nan)

Modeling a certain instrument model

• Via subclassing the Sensor (or Sampler) class and adding appropriate restrictions as in the VaisalaWM30 example above.

Units and definitions

• To clarify, we have two kinds of definitions: i) definitions for the concepts in the ontology (eg., for the classes System, Deployment, Platform, ValueType, etc.), and ii) definitions associated with particular measurements, parameters, etc. that may vary across different instruments. In this topic we focus on the latter case though the capturing mechanism may be the same.
• Need to determine the mechanism to link definitions. This can be accomplished by including rdfs:isDefinedBy (or other appropriate exisiting) property associations to the relevant elements. The referred resources would ideally be common vocabularies to facilitate semantic interoperability. For example, CF terms or OGC definitions...
• How can one refer to definitions in the DevOnt ontology in a SensorML document? This will depend on the kind of definition as mentioned above. In particular, for case ii), the SensorML document would actually point to the external vocabulary terms and not necessarily to the DevOnt (or other derived) ontology. Of course, if the reference is to a concept in the ontology itself, or to an instance derived from the ontology (eg., a particular CalibrationSchedule), then the document may point directly to it.
• This topic needs elaboration.

Others

Scale References

Competency questions

• Ref: http://code.google.com/p/ala-bie/wiki/OntologyCompetency
• Good model?
• Having questions (and corresponding queries) in our context is certainly relevant. We can develop some queries linking various DeOnt concepts and different instruments.
  

End Logistics: Next meeting, Action items, Attendees

Action Items

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

• DONE [Carlos] include this property and update instantiation example
• [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.05.11 at 1500 UTC.

Attendees:

Regrets: Bob Arko, Luis Bemudez