- From: Armin Haller <armin.haller@anu.edu.au>
- Date: Mon, 13 Feb 2017 06:11:33 +0000
- To: "Simon.Cox@csiro.au" <Simon.Cox@csiro.au>, "janowicz@ucsb.edu" <janowicz@ucsb.edu>, "public-sdw-wg@w3.org" <public-sdw-wg@w3.org>
I will raise the question of Sampling in the core in the discussion around Actuation in our next telco. In terms of Actuation we have several use cases that require actuation: https://www.w3.org/TR/sdw-ucr/#ModelActuation I believe we need to have a strong argument why to not include it in the core. Personally, I think Actuation should be in SOSA as many IoT applications on the Web will include Actuation. Even many of the IoT home devices available in Apple Stores include actuation (turning light on, recording your favourite show over Siri, Cortana, Amazon Echo, changing the thermostat etc.). On 13/2/17, 11:50 am, "Simon.Cox@csiro.au" <Simon.Cox@csiro.au> wrote: Thanks Jano. The proposal is exactly in line with expectations. However, I am concerned that we should clarify the scope (and size) of SOSA. Specifically, 1. do the requirements for SOSA include a basic actuation model? If that is the case then 2. should the Sampling side of the system also need to be fleshed out? I could make a proposal for this, but had been holding back because I had assumed that was probably out of scope for most SOSA users, and should rather be the subject of a vertical (richer axiomatization) + horizontal (additional scope) extension to SOSA. In developing SOSA until now we have generally leaned towards parsimony - lets minimise the number of concepts in SOSA to a core that might be useful to schema.org folk. BTW - I'm OK with the answers to these two questions being 1. Yes, and 2. No, but wanted to put the issue on the table so we are all clear about what is being ruled in, and what is out. And just in case there is any question, even if it is "2. No", Sample still belongs in SOSA, as it is critical for many (most?) observations. It would just be sampling and sample preparation that would be delegated elsewhere. Simon -----Original Message----- From: Krzysztof Janowicz [mailto:janowicz@ucsb.edu] Sent: Monday, 13 February, 2017 10:50 To: Cox, Simon (L&W, Clayton) <Simon.Cox@csiro.au>; armin.haller@anu.edu.au; public-sdw-wg@w3.org Subject: Actuation and Actuators in SOSA (issue-91) Dear all, I added a wiki pages that shows a concept map for the changes to be made on the Actuator and Actuation side of SOSA. The proposed changes address some shortcomings of the current model and are also in preparation for a deeper axiomatization in SSN. There are two major (but in no sense dramatic changes) to SOSA, namely a proposal to add the SOSA:actuatedProperty role and a class called SOSA:ActuableProperty. These are in line with previous work and requests made on this list. I hope you can look at the concept map and the notes on the wiki page as I hope we can get this resolved during our next teleconference. Please keep in mind that everything that is not shown in a dashed style is already part of SOSA. https://www.w3.org/2015/spatial/wiki/Actuation_in_SOSA Best, Jano
Received on Monday, 13 February 2017 06:12:11 UTC