Agenda

1. Logistics: Welcome, Minutes Review, Agenda Review, Chat Room
2. W3C SSN updates
3. Review updates and proposed changes to ontology
4. Review pending items in facets outline
5. Are cameras devices?
6. Status of action items
7. End Logistics: Next meeting, Action items, Attendees

Minutes

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

Minutes review. No comments.

Agenda approval.

W3C SSN updates

• Uses cases proposed by MMI, in particular "discovery of data". See http://www.w3.org/2005/Incubator/ssn/wiki/Favorite_Use_Cases_List

• Bob looking into uses cases involving reasoning about anomalous data, relation with the device ontology, in particular, detection of device failure. They have submitted a proposal for distributed data quality control.

Review updates and proposed changes to ontology

Several updates

+ class OperationalProcedure

+ datatype property: OperationalProcedure hasOperationalProcedureUniqueId (1) string
    label: hasUniqueId

+ datatype property: OperationalProcedure hasOperationalProcedureLabel (0..n) string
    label: hasLabel

+ datatype property: OperationalProcedure hasOperationalProcedureDescription (0..n) string
    label: hasDescription

+ datatype property: OperationalProcedure producesOperationalProcedureLog (0..n) string
    label: producesLog

+ datatype property: OperationalProcedure hasOperationalProcedureCompletion (1) string
   enumeration: {"successful", "unsuccessful", "unknown", "incomplete" }

+ class CalibrationProcedure subClassOf OperationalProcedure

+ class CalibrationAdjustment

+ class PhysicalModification subClassOf CalibrationAdjustment

+ class ApplicationOfCalibrationValue subClassOf CalibrationAdjustment

+ object property: CalibrationProcedure resultsInCalibrationAdjustment (0..n) CalibrationAdjustment
   label: resultsIn 

+ class PhysicalProperty (1.c)

* class Dimension subClassOf PhysicalProperty (1.c.1)

+ datatype property Dimension hasDimensionName string (1)   label: hasName
+ datatype property Dimension hasDimensionUnits  string (1)    label: hasUnits
+ datatype property Dimension hasDimensionValue float (1)     label: hasValue 

+ class Weight subClassOf PhysicalProperty (1.c.2)
+ datatype property Weight hasWeightUnits string (1)    label: hasUnits
+ datatype property Weight hasWeightValue float (1)     label: hasValue

+ object property System hasSystemWeight Weight (1)
   label: hasWeight

+ class Buoyancy subClassOf PhysicalProperty (1.c.3)

+ object property System hasSystemBuoyancy Buoyancy (1)
   label: hasBuoyancy

Updated: [√] facets list;  [√] Pending mods

Updated ontology: http://mmisw.org/ont/mmi/20090818T043834/device [NOTE: I have updated the link to the device ontology in the Key Links block, on your right, to open the HTML version of the ontology using the MMI ontology portal, where you have various options to 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

See Pending mods to ontology. 

• CalibrationValue: How to incorporate?
  • There are two aspects: i) some intrinsic values (typically in firmware), and ii) values that are produced when a calibration procedure is applied.
  • Yes, this can be captured as a class
• OperationalProcedure: make it a subclass of Process? -- not discussed.

Review pending items in facets outline

• 1.d Absolute physical limitations/restrictions: no, these are not covered by 3.c. Nan will model these facets.

• 1.e Component mfgrs, models (JBG: these fold into sub-device's properties). Need to re-check, but the composite aspect is already captured with the hasComponent property (domain: System, range: System). 
  

• 3.b Interfaces: Who can work on this one?

• 3.e Data processing requirements: When going to use an instrument, you need software, quality control procedures. It has been suggested that the name of this facet be changed (eg. storage reqs, usage reqs, ..). Consider aspects like multiple outputs from the same device, storage media.  Bruce will elaborate on this.

Are cameras devices?

See this thread.

• Yes, they are devices, and as such, are in the scope of our ontology.
• Consider image aquisition instruments in general, not only for pictures (eg., multi-spectral satellite instruments, etc.).
• and yes, they produce measurements (the images themselves are measurements --observations).
• Image metadata: besides the images as data themselves, there is the aspect of associated metadata (cf. Metadata Specification for Environmental Images: http://marinemetadata.org/community/teams/imagemd-censeam/censeammetadat...)

Status of Action Items

End Logistics: Action items, Attendees, Next meeting

New Action Items

Attendees:

• Bruce Andrews
• Nan Galbraith
• Bob Morris
• Carlos Rueda

Regrets: John Graybeal, Luis Bermudez.

Chat room messages:

[8:02] Bob Morris: just checking...will phone in shortly
[8:12] ngalbraith: SSN use cases are at http://www.w3.org/2005/Incubator/ssn/wiki/Favorite_Use_Cases_List
[8:21] Carlos Rueda (MBARI): http://marinemetadata.org/community/teams/ontdevices/ontdevpend
[8:44] ngalbraith: http://marinemetadata.org/community/teams/ontdevices/facetoutline
[8:44] Carlos Rueda (MBARI): http://marinemetadata.org/community/teams/ontdevices/facetoutline
[9:21] Carlos Rueda (MBARI): Found this, unfortunately the document is not found: http://marinemetadata.org/community/teams/censeam-imagemd/generaldocumen...
[9:21] Carlos Rueda (MBARI): is this related with what you are talking about, Bob?
[9:24] ngalbraith: Metadata Specification for Environmental Images: http://marinemetadata.org/community/teams/imagemd-censeam/censeammetadat....

Next Telecon Time

Next telecon is Tuesday 2009-09-01 at 1500 UTC.  (1600 UTC in winter)