Devices Ontology WG Mtg 2009.09.01
Agenda
- Logistics: Welcome, Minutes Review, Agenda Review, Chat Room
- W3C SSN updates
- Review updates and proposed changes to ontology
- Review pending items in facets outline
- Status of action items
- End Logistics: Next meeting, Action items, Attendees
Minutes
Logistics: Welcome, Minutes Review, Agenda Review, Chat Room
Minutes review.
- How to capture date of a CalibrationProcudure (actually OperationalProcedure, in general)? With a 'date' property or with an "ontology instantiation snapshot" approach as suggested by Bob A. a few meetings ago?
- Nan asks, ""how does one become listed as a contributor to the ontology?"
- MMI ORR features to navigate and browse the ontology
Agenda approval.
W3C SSN updates
- In last SSN meeting, JG asked about partition topics; still preliminary. Goal is to determine which areas would better fit/benefit our ontology.
- Their ontology is going to point to other ontologies, eg., Units. Not clear how this can be done.
- CR: Approach should be similar to what we are somehow anticipating with the Platform class in our current version; that is, as some kind of "extension point," where the concept (Platform in this case, but Units and others as well) are abstract yet you can use it in other dependent parts of your ontology.
- But there is an interface (operations), which in the case of units may be different from one concrete units ontology to other.
- BA: the appeal of the MMI device ontology is that it's [supposed to be] self-contained; no need for a user to understand 10 other external ontologies.
Review updates and proposed changes to ontology
Updates ( + = addition; * = modification; - = deletion)
* updated property processID, with domain Process: it was an rdf:Property, now an owl:FunctionalProperty and also owl:InverseFunctionalProperty; now with name hasProcessID and label: processID
* updated property platformID, with domain Platform: it was an rdf:Property, now an owl:FunctionalProperty and also owl:InverseFunctionalProperty; now with name hasPlatformID and label: platformID
+ class CalibrationValue
+ object property: CalibrationProcedure producesCalibrationValue (0..n) CalibrationValue
+ datatype property: CalibrationValue hasCalibrationValueName (label: hasName) string (0..n or functional?)
+ datatype property: CalibrationValue hasCalibrationValueType (label: hasType) ??
perhaps an enumeration with the possible concrete types..
+ datatype property: CalibrationValue hasCalibrationValueCount (label: hasCount) integer (functional)
.. not sure yet how to enforce the m values in an OWL way.
Updated: [√] facets list; [√] Pending mods
Updated ontology: http://mmisw.org/ont/mmi/20090901T010052/device
NOTE: I have updated the link to the device ontology in the Key Links
block, on your right, to open the HTML presentation
of the latest version of the ontology using the MMI ontology portal. In this interface, you can browse the metadata and the contents of the ontology. It
also gives options to retrieve the ontology in various formats
including RDF/XML and N3.
Updated diagram:
Proposed additions and other changes
- Absolute physical limits.
- NG: Survival limits are different than normal operational limits.
- CR: We can have a subclass AsolutePhysicalLimit of OperationalRestriction (or actually a subclass of Restriction, which is already defined in the ontology) for these absolute physical limits.
- There are important limits imposed during a deployment (things that are temporary and cannot be anticipated)
- BM: An instrument may be reporting measurements but how do I know they are correct?
- Do we want to capture those dynamic restrictions/limitations?
- CR: Seems more feasible to capture static restrictions in our ontology
- NG: Distinction between static and dynamic is fuzzy.
- NG: Suggest using separate 'min' and 'max' properties instead of a range for the restrictions
Review pending items in facets outline
Not discussed.
Status of Action Items
- [Nan] Model 1.d Absolute physical limitations/restrictions, perhaps including 3.c.7 Water or wave tolerance, RF tolerance, other interference problems -> under discussion.
- [John?] Model 3.b Interfaces.
- [Carlos] Include CalibrationValue class -> Done.
- [Luis] Update observation ontology -> .
- [Bruce] Review data processing facets; send comments/proposed modifications to email list -> discussed today. Will continue developing this facet.
- [Bob A] Review facets 2.d Output provided, 2.e Measurement technique, 3.c Operational restrictions, and send comments/proposed modifications to email list ->
- [all] Review instructions and facets outline and pick pending items (and/or suggest new ones) for inclusion in ontology. Send questions/suggestions to the mailing list -> ongoing
End Logistics: Action items, Attendees, Next meeting
New Action Items
- [carlos] send email with summary of issues from today's telecon.
Attendees:
- Bob Arko
- Nan Galbraith
- John Graybeal
- Bob Morris
- Carlos Rueda
Regrets: -
Chat room messages: -
Next Telecon Time
Next telecon is Tuesday 2009-09-15 at 1500 UTC. (1600 UTC in winter)
