Agenda SSN meeting this week

Please find below the agenda for this week’s SSN meeting. I have deliberately not included the namespace issue yet, as I would like to focus on creating Action Items in the meeting that outline options for resolving some of the most important outstanding issues (in the integration of SSN/SOSA) on the issue tracker (postponed from last week). In those options, volunteers should then discuss how an option for the modelling of one of these issues would be affected by having one or two namespaces. I am hoping this will help us solving the namespace issue in our meeting next week.

Agenda for SSN-focused meeting 7 February 2017 21:00 UTC<http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170207T21&ah=1&msg=SSN%20Call>


  1.  Create Options for the modelling of Actuation, Actuator and its relations (https://www.w3.org/2015/spatial/track/issues/91), i.e. change due date on https://www.w3.org/2015/spatial/track/actions/215 (create Action Item)
  2.  Create Options for the modelling of Results/Values in SOSA and SSN https://www.w3.org/2015/spatial/track/issues/90 (create Action Item)
  3.  Create Options for the modelling of Processes/Procedures in SOSA and SSN https://www.w3.org/2015/spatial/track/issues/89 (create Action Item)
  4.  Create Options for alignment on Platform class (create Action Item)
  5.  O&M alignment options as of Simon's email in response to ACTION-255 (and proposal to invite Simon as editor to solve this and other issues)
  6.  Vote on how to use annotation properties for examples in SOSA/SSN, i.e.:
     *   Option 1: Use skos:example in SOSA/SSN and declare it an owl annotation property
     *   Option 2: Define our own annotation property -- e.g. sosa/ssn:example
  7.  Proposed time slots for extended phone conference mid-February

Further details and dial in instructions: https://www.w3.org/2015/spatial/wiki/Meetings:SSN-Telecon20170207



Kind regards,
Armin