Agenda

1. Logistics: Welcome, Minutes Review, Agenda Review, Chat Room
2. Status of Action Items
3. Updates to Ontology
   1. Modifications: Changes proposed based on work to date
   2. Additions: Terms from the facets that have been added
4. Exercising the ontology in practical applications
5. End Logistics: Next meeting, Action items, Attendees

Minutes

Logistics: Welcome, Minutes Review, Agenda Review, Chat Room

Minutes review.

Agenda approval

We had a round of self-introductions and welcome especially our new participants Reyna Jenkyns, Bob Morris, and Matt Calder.

Status of Action Items

Updates to Ontology

+ object property: System hasComponent System (0..n)

+ class: OperationRange subClassOf OperationalRestriction (3.c)
* class: OperationalTemperatureRange subClassOf OperationRange (3.c.2)
* class: OperationalPressureRange subClassOf OperationRange (3.c.1)
+ class: PowerRequirement subClassOf OperationalRestriction (3.c.3)
+ class: DataStorageCapacity subClassOf OperationalRestriction (3.c.4)
+ class: SelfPoweredOperationTime subClassOf OperationalRestriction (3.c.5)
+ class: MinimumOnTime subClassOf OperationalRestriction (3.c.6)

+ object property: System canBeDeployedOn Platform (0..n)  (not in current facet list)
+ object property: System hasDeployment Deployment (functional)   (not in current facet list)
+ data property: Deployment startDate dateTime (functional)     (not in current facet list)
+ data property: Deployment endDate dateTime (functional) (not in current facet list)

+ data property: System isConsumable boolean (5.b and 5.c)

This is the resulting version: http://mmisw.org/ont/mmi/20090609T064417/device and here is the corresponding diagram:

Discussion:

1. Carlos gave a summary of the recent changes.
   
   1. Slight reorganization of the OperationalRestriction hierarchy.
   2. Concept of "composite system" captured via a hasComponent object property (with System as both domain and range).
   3. canBeDeployedOn: A system *can be* deployed on 0, 1, or multiple platforms.
   4. hasDeployment: Upon deployment, a particular system is actually deployed on a single platform, and that's why this property is functional. Bob Morris notes that deployment on multiple "virtual" platforms may be possible (he will be sending more information about this to the list).
   5. startDate/endDate: datatype properties with domain Deployment. Nan notes that other properties pertaining to deployments are necessary, for example, location. See also CESN ontology in the "ontology diagrams" page.
   6. (not discussed in the call) The data property: System isConsumable boolean (boolean) reflects the items 5.b and 5.c in the facet list. In particular, note that 5.c is accomplished by the interplay of this property along with the fact that a system can be composed of multiple (sub)systems -- see hasComponent above).
2. Roy and Nan exposed issues regarding possible ways to categorize a particular list of instruments. See document attached in this thread.
3. Clarification about the meaning of the arrows in the diagram: Open arrows mean "subClassOf" and green arrows represent object properties. From the diagram, for example, we see that Sensor and Sampler are subclasses of System.
4. Do we want to capture "instrument", "device," and other similar artefacts (eg., "transducer", "detector") as explicit classes in the ontology? No, not at least for now; we are going to continue using "System" as our central entity in our ontology. Elaboration will come later if needed. For now, we may say "instrument" or "device" as a synonym of "system." Note that relationships with other important entities ("observations", "platforms") are of course necessary but those entities are not in principle to be analyzed in detail in this ontology.
5. Don't samplers also have calibrations, measurement capabilities? No.
6. Luis described his initial version of an observation ontology and its relation with the device ontology.
7. Reminder about the instructions to reflect entries in the facets outline into the ontology. Please pick pending entries and/or suggest new entries or changes. Use the mailing list.

Exercising the ontology in practical applications

1. Need to create some representative instantiations.
2. Should continue the thread started by Roy.

End Logistics: Next meeting, Action items, Attendees

Action Items

Next Telecon Time

Next telecon is Tuesday 2009-06-23 at 1500 UTC.  (or 1600 UTC?)

Attendees:

• Bob Arko
• Luis Bermudez
• Matt Calder
• Nan Galbraith
• Reyna Jenkyns
• Roy Lowry
• Bob Morris
• Carlos Rueda

Chat room messages:

[8:09] Carlos Rueda: Hi Bob and Matt, are you joining the phone call as well?
[8:09] Roy Lowry: Nan, the definitions are on http://marinemetadata.org/community/teams/ontdevices/deviceontterms
[8:09] Bob Morris: yes, but from separate places. I have to use skype out... need number
[8:10] Roy Lowry: I need to give relationship between 'device' and 'system' some thought
[8:11] ngalbraith: Thanks, Roy. The def of device is quite ... terse.
[8:16] Roy Lowry: and I can't find theword 'device' on the ontology diagram...
[8:54] Carlos Rueda: http://marinemetadata.org/community/teams/ontdevices/obsont
[9:02] Carlos Rueda: list of facets: http://marinemetadata.org/community/teams/ontdevices/facetoutline
[9:05] Carlos Rueda: instructions: http://marinemetadata.org/community/teams/ontdevices/f2o
[9:10] Luis Bermudez: Carlos, sorry, I need to leave... I will update the obs ontology to reflect today's discussion
[9:11] Bob Morris: (newbie question): is the chat persistent and findable?
[9:11] Luis Bermudez: bye all
[9:15] Carlos Rueda: hi Bob: No, teh chat goes away after some inactivity.  I will save it sometwhere