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

Agenda

1. Logistics: Welcome, Minutes Review, Agenda Review
2. Status, main documentation
3. Pending facets
4. Material (link w/ external ontology)
5. hasServiceAccessPoint
6. CalibrationValue
7. End Logistics: Next meeting, Action items, Attendees

Minutes

Note: Meeting started 30 mins later because of schedule conflicts of some participants.

Logistics: Welcome, Minutes Review, Agenda Review

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

Status and main documentation

Description updated: http://marinemetadata.org/community/teams/ontdevices/devont

Current DevOnt version: http://mmisw.org/ont/mmi/20100623T004300/device

Latest changes:

• CalibrationValue: removed hasType property and its data range enumeration. It now has a hasValue property with range TypedValue.
  • What are the following existing properties about, hasCount and hasName?
• EnvironmentalToleranceLimit: 
  • + added "destroyed" to hasConsequence's data range enumeration.
  • + new subclasses SprayTolerance and SubmersionTolerance (these were datatype properties previously).
  • - Removed property hasOtherEnvironmentalToleranceLimit
    Rationale: capturing some "other" env tolerance limit (ie. one that has not explicit class in DevOnt) can be done by instantiating EnvironmentalToleranceLimit itself.
• + New class ValuedPhysicalProperty (subClassOf ValuedPhysicalProperty)
• * ValueType: hasUnitsOfMeasure's range is now rdfs:Resource
• * Buoyancy is now subclass of ValuedPhysicalProperty
• * Range: minValue and MaxValue props's range is now rdfs:Resource

Pending facets

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

Please help revise the pending facets and propose approaches to incorporate them in ontology, or perhaps discard.

• John: incorporate all that are straightforward or that do not require much input.
• 3.b. Interfaces – Not so much important.
• 7.d.i. Current Location (for un-deployed devices?)
• 7.d.iii.1: √ Calibrations (related with CalibrationProcedure class) -- John: please check this is the right place here [facets outline].

Material 

Perhaps link with SWEET's substance ontology? See #23.

Should Material be a subclass of ValuedPhysicalProperty, that is, to be able to say that a certain device has a certain material with some value associated, presumably a percent of that material in the composition of the device?

• Not discussed.

hasServiceAccessPoint

Mechanism to access the data generated by instruments in a deployment:
   Deployment hasServiceAccessPoint anyUri ?
What about separation of data management concerns from the base DevOnt (see issue #10)?

• Not discussed.

CalibrationValue.hasCount

hasCalibrationValueCount (label: hasCount) domain: CalibrationValue, range: integer [0..1]
What is this property about?

• Not discussed.

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.08.10 at 1500 UTC.

Attendees: