- From: Frans Knibbe <frans.knibbe@geodan.nl>
- Date: Fri, 2 Sep 2016 14:33:11 +0200
- To: SDW WG Public List <public-sdw-wg@w3.org>
- Message-ID: <CAFVDz43aPeVxx=Y1gH18H6nytLXHc2qQ60W2EicdX-G9jcgmZg@mail.gmail.com>
Hi there! Action-196 <https://www.w3.org/2015/spatial/track/actions/196> is about adding two requirements for the SSN deliverable to the UC&R document. This is a proposal for the second of those two requirements. This <https://lists.w3.org/Archives/Public/public-sdw-wg/2016Sep/0022.html> is the thread for the other one. I propose to add the following requirement: *Tasking/programming and actuation.* *Requirement: *It should be possible to model tasking/programming and actuation of sensing devices. The terms tasking and programming are taken to mean the same: the assembly and transmission of instructions intended to control the behaviour of a sensing device. Actuation of a sensing device is its ability to change something in its environment upon receiving a signal. *Related deliverable: *SSN *Related use cases:* Driving To Work In The Snow <http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html#DrivingToWorkInTheSnow> <http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html#DrivingToWorkInTheSnow> Intelligent Transportation System <http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html#IntelligentTransportationSystem> Optimizing Energy Consumption, Production, Sales And Purchases In Smart Grids <http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html#OptimizingEnergyConsumptionProductionSalesAndPurchasesInSmartGrids> Smart Cities <http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html#SmartCities> Again I should note that so far I have tried the existing pool of use cases to support this requirement. If necessary, we could add use case from the set of use cases that underpinned the first version of SSN <https://www.w3.org/2005/Incubator/ssn/XGR-ssn-20110628/#Motivating_Use_cases_.28Sensor_Web_and_Sensor_Networks.29>. My thought was that there are many use cases already, so if a new use case does not bring unique requirements to the table we should not add it. If you have any comments or suggestions, please make them known. The aim is to include this new requirement in the UCR version that will be frozen before TPAC, so there is not much time. Greetings, Frans
Received on Friday, 2 September 2016 12:33:40 UTC