Devices Ontology WG Mtg 2009.04.14

Agenda/minutes for Device Ontology Working Group meeting 2009.04.14

Agenda

  1. Logistics: Welcome, Minutes Review, Agenda Review, Chat Room
  2. Review of W3C Semantic Sensor Network Status
  3. Process: Concepts to Ontology
  4. Updates to Ontology
    1. Modifications
      Changes proposed based on work to date
    2. Additions
      Terms from the facets that have been added
  5. End Logistics: Next meeting, Action items, Attendees

Minutes

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

Minutes review
Agenda approval

Review of W3C Semantic Sensor Network Status

Discussion:

  • This Incubator working group (more info in 03.31 Minutes) had an initial meeting a week or two ago, mostly getting to know each other, and setting meeting times. It has participants from all over the world.
  • The charter can be found at Semantic Sensor Network Incubator Group. Our MMI DOWG team has a nice mention.
  • The first activity is an activity survey/white paper (may take as long as 6 weeks), and a key action item is for me/MMI to put forward our knowledge of projects in this area.
  • Given our recent progress, seems likely our work will be quite useful to theirs.

Process: Concepts to Ontology

Links:

Discussion:

  • Two weeks ago, we went through the process with a test case and a small number of telecon participants.  It has been edited significantly in response.
  • Last week, Carlos made a number of changes to reflect that meeting's discussion. They are reflected below.
  • In the last day or two, Carlos and John had a discussion of how to handle 'instance data,' which is more subtle than John realized.
    • A key point is that we don't need to reflect detailed instances in the Ontology; these are seen in actual implementations that use the Ontology. (See also Discussion under the Updates to Ontology, below.)
    • (Carlos) Capture the necessary details from this exchange in the instructions.

Updates to Ontology

+ Created datatype property: System hasSerialNumber string (7.a.1)

+ Created class Manufacturer (1.a)
+ Created object property: System hasManufacturer Manufacturer

+ Created class Medium (2.a, 3.a.1)
+ Created object property: System hasMeasuredMedium Medium (2.a)
+ Created object property: System hasDeployedMedium Medium (3.a.1)

+ Created class Restriction (1.d, 3.c)
+ Created class OperationalRestriction subclassOf Restriction (3.c)
+ Created object property: System hasOperationalRestriction OperationalRestriction


- Removed datatype property: Identifier serialNumber Any
- Removed datatype property: Identifier manufacturerName Any
- Removed datatype property: Identifier modelNumber Any
- Removed datatype property: Identifier longName Any
- Removed class: Identifier

Most of these changes are reflected in the following figure.


Discussion:

  • Particpants are encouraged to use a similar format as the above to report additions/deletions/changes to the ontology.
  • Proposal to remove ObservingSystem: it's confusing as a sibling of the Sensor and Sampler classes, as they are potential participants in an observing system. Ok, will be removed (although we will eventually re-incorporate it apprpriately at a later iteration).
  • What if an ADCP instrument changes in some operational way, for example, its pressure range has changed?  Note that this will be a particular event to a particular *instance* of System. Our focus is at the class level, so changes like this should only (ideally) affect the particular instantiation of the ontology, not the ontology itself.
  • Suggestion to have OperationalRange as a superclass of OperationTemperatureRange and OperationPressureRange -- good. (Bob is going to work on the operational restriction facets, btw.)
  • Agreed to 'make changes' to the ontology to reflect our assignments, by giving Carlos a list of changes in the above format, and letting him update the ontology and diagram.  (May look at collaborative ontology editor in the future.)

End Logistics: Next meeting, Action items, Attendees

Action Items

  • [All] Select an entry from the facet list and follow the proposed process:
    • [Nan] 1.b Model; 1.c: Physical properties
    • [Bob] 2.d Output provided; 2.e Measurement technique; 3.c Operational restrictions
    • [John] 4 Physical processing
    • [Bruce] 3.e Data processing requirements
  • [Roy, Carlos] Comment on related discussions in the mailing list
  • [Carlos] Update ontology and related pages during the process
    • Address how instance data is handled.
    • Include attributes in the ontology diagram, for completeness.

Next Telecon Time

Next telecon is Tuesday 2009-04-28 at 1500 GMT.

Attendees:

  • Bruce Andrews
  • Bob Arko
  • Nan Galbraith
  • John Graybeal
  • Roy Lowry
  • Carlos Rueda
AttachmentSize
device2009-04-12-class-n-prop.png76.62 KB