Agenda

1. Logistics: Welcome, Minutes Review, Agenda Review, Chat Room
2. Action item tracker
   • Proposed to use the general mmisw project tracker.  Specific label 'OntDev' created: http://code.google.com/p/mmisw/issues/list?can=2&q=label=OntDev
   • Please let Carlos know your Google account so you can be added to the mmisw project.
3. Device Ontology instantiations
   • Related: Overview of ORR-enabled SensorML generator tool
   • Mechanisms to create the instances (Protégé / TopBraid Composer)
   • Review of the planned instantiations (Nan's, Bob's).
4. Review proposed changes to ontology
   • Realm extensions (from mailing list)
   • See proposed modifications to ontology  
5. End Logistics: Action items, Next meeting, Attendees

Minutes

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

Minutes review.

Agenda review.

No comments.

Action item tracker

• Approved. http://code.google.com/p/mmisw/issues/list?can=2&q=label=OntDev

Device Ontology instantiations

• Overview of the ORR-enabled SensorML generator tool.
• Ontology instantiations. Captured in ontology representation. Suggest to use a tool (like Protégé or TopBraid Composer) to create a simple instantiation so as to better appreciate the process. The actual mechanism to create the instances may be more automatic, for example from a database (as in Bob's case) using some scripts. Consensus to use templates (ie., files with instances of the ontology; see attached example file) as a basis for a more programmatic mechanism to create the instances.
• Review of the planned instantiations.
• The "granularity" issue: how to organize the instances, one single file, multiple files, etc.? particularly important aspect for versioning. Note that, regardless of the granularity (just organize the instances in the way want), everything will be handle as a single whole (with the appropriate framework) for purposes of queries and faceted search.
• There are toolkits that allow to expose a relational database as RDF resources.
• Strategy for demonstrating the use of the OntDev: i) if necessary, create an ontology that extends the OntDev (ie., create a new ontology that imports concepts from it); and ii) create isntantiations integrating concepts from the two ontologies as appropirate.  This strategy applies to the cases being prepared by Bob and Nan.
• The Capabilities class looks like one of the appropriate "extension points"
• As you develop your instantiations, report on missing elements in the device ontlogy or any suggested changes.

Review proposed changes to ontology

Not discussed

End Logistics: Action items, Attendees, Next meeting

Action Items

http://code.google.com/p/mmisw/issues/list?can=2&q=label=OntDev

Attendees:

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

Regrets: Bob Morris, John Graybeal

Chat room messages:

[8:09] ngalbraith: http://marinemetadata.org/community/teams/ont/tutorials/tutorprotegeowl

Next Telecon Time

Next telecon is Tuesday 2009-11-24 at 1600 UTC.