• Google "pad": https://docs.google.com/document/edit?id=1cCzYcOtSPd9PQ9f-rcNTlOHlvO7E4n...
• Last meeting minutes: http://marinemetadata.org/community/teams/ontdevices/agendas/am20100608

Agenda

1. Logistics: Welcome, Minutes Review, Agenda Review
2. System/Process/Platform and alignment with SensorML
3. Main documentation
4. End Logistics: Next meeting, Action items, Attendees

---

Minutes

Logistics: Welcome, Minutes Review, Agenda Review

• google doc "pad": see link above
• Minutes review -
• Agenda approval

System/Process/Platform and alignment with SensorML

Changes proposed in http://marinemetadata.org/community/teams/ontdevices/dosml have been applied:

New DevOnt version: http://mmisw.org/ont/mmi/20100622T081511/device

• CalibrationValue hasType: DR_3: Remove this enumeration and instead use rdfs:Datatype as the range of hasType (domain: CalibrationValue)
• DR_2: add “destroyed”
• What if measurements are not received for a long time? This is a data management concern.
• EnvironmentalToleranceLimit.hasConsequence [DR_2] is about what would happen if some tolerance limit is not met. Device.hasFunctionalityStatus [DR_1] is about current status (the more "dynamic" aspect).
• Revise DR_1 and DR_2 overlap, that is the overlap between hasFunctionalityStatus and hasConsequence ranges.
• Consider making (new classes) SprayTolerance and SubmersionTolerance subclasses of EnvironmentalToleranceLimit
• EnvironmentalToleranceLimit: other possible cases:
  • RF tolerance (e.g. from Argos transmitters) - creates noisy data
  • Noise tolerance - probably not the correct term - may prevent a device from communicating but it may still record internally
  • Magnetic field tolerance
  • Distance from receiver - is this an EnvironmentalTolerance or an OperationalRestriction?
• EnvironmentalToleranceLimit: Similar elements as in other parts of the ontology: OperationalRange, MeasurementCapability. Basically, in EnvironmentalToleranceLimit we want to indicate a possible value (or ranges of values) to capture a certain limit for a device while saying what the consequence would be if such a limit is not met.
• TypedValue can also be used in EnvironmentalToleranceLimit.
• In general, this needs to align/use some appropriate observation models or ontologies out there, eg., SONet (https://sonet.ecoinformatics.org/); See also http://www.nceas.ucsb.edu/.

Main documentation

Updated: http://marinemetadata.org/community/teams/ontdevices/devont

End Logistics: Next meeting, Action items, Attendees

Action Items

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

• DONE [Carlos] Apply changes described at http://marinemetadata.org/community/teams/ontdevices/dosml (#12)
• DONE [Carlos] enumeration for ValueType's datatype not appropriate (#13)
• [Bob M] provide pointer to presentation.

• [Nan,Bob A] send instance example (in a CSV-like format) to Luis.
• [Carlos] complete version of ontology document

• [?] Determine license
  
• [Bob A., Carlos] look into ProcessOutput vs. MeasurementCapability related issues, especially in the context of the Multibeam ontology.
  
• [John and Reyna] Follow up on scale references

Next Telecon Time

Next telecon is Tuesday 2010.07.06 at 1500 UTC.

Attendees: