Agenda SSN meeting this week

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


  1.  Commit Workflow for Editor’s draft
  2.  O&M alignment “normative” or “non-normative”
  3.  Proposal to align sosa:Platform and ssn:Platform from Krzysztof, taking into account virtual sensors (https://www.w3.org/TR/sdw-ucr/#VirtualObservations) as of ISSUE 88 (carried from https://www.w3.org/2016/12/06-sdwssn-minutes#item05) and ACTION-251
     *   Proposed new rdfs:comment as in SOSA and in the mapping table (https://www.w3.org/2015/spatial/wiki/Mapping_Table) for ssn and sosa:Platform
     *   “A device, (computational) system, or agent (including humans). A platform carries at least one Sensor, Actuator, or Sampling Device to produce observations, actuations, or samples, by following a Procedure. In case of virtual sensors, a platform can be a computing system which hosts software implementations, e.g., simulations”
  4.  ISSUE-140 https://www.w3.org/2015/spatial/track/issues/140: sosa:hasvalue is different to ssn:hasValue and similar ISSUE-138, sosa:hasResult https://www.w3.org/2015/spatial/track/issues/138

  5.  SOSA classes/properties to be super classes of SSN, i.e. SSN new imports SOSA https://www.w3.org/2015/spatial/track/issues/37?


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



Re 1: There was a preference for the following workflow going forward. I have clarified it a bit where necessary.


1.       All commits to the Editor's Draft + the ontologies the Editor’s draft depends upon regardless if you are editor or not need to be committed to your own branch

2.       Pull requests need to be issued assigning all editors but yourself, but multiple commits can be made in each PULL request. Each commit should be atomic enough to make it easy for the approver to recognise the diff.

3.       The Pull request needs to be approved by ONE editor other than the one who made the change.

4.       This means that once you have committed your changes and a PULL request, until your PULL request is accepted, you need to again create a new Branch from the main branch in your local repository. Preferably, though, the PULL request should be accepted quickly and prior to you needing to make a new branch.

Kind regards,
Armin