Thanks. And I think I still have some confusion here. When you say "local sensor data can also be read directly inside the soft sensor logic", do you mean soft sensor logic can receive sensor information input from other components outside IoTivity services (like an IoTivity application which directly get sensor data from kernel or by other help libraries), or you mean some IoTivity services can directly interact with physical sensors to get the data? I asked this because I did not see any code in IoTivity which have physical sensor access capabilities, so I tend to think the full path is something like IoTivity (Resource Management, Soft Sensor Manager) < -------- > Third party components (App or other non-IoTivity module) < ----------- > Physical Sensor This path is common for registering local sensor resource, getting local sensor data and enforcing local sensor manipulation command. Let me know if I have misunderstanding here. Note here I mean local sensors attached to the thin device directly, not remote sensors which need connectivity and network access. Please let me know if I have any misunderstanding here. Thanks. And, it would be great to have some detailed doc about SSM (as Thiago mentioned in another thread) as we don't find much from IoTivity website.
Best regards, James From: minji park [mailto:[email protected]] Sent: Friday, April 10, 2015 3:56 PM To: Jia, Pei P; Macieira, Thiago; iotivity-dev at lists.iotivity.org Subject: Re: Re: [dev] Question about relationship between iotivity and sensord Hi, In the module soft-sensor-manger, the manager itself gets sensor data through IoTivity network, but local sensor data can also be read directly inside the soft sensor logic. As now, the manager provides processed output data through query result, later will provide the data through IoTivity network also. best regards, Minji Park ------- Original Message ------- Sender : Jia, Pei P<pei.p.jia at intel.com<mailto:pei.p.jia at intel.com>> Date : 2015-04-10 16:37 (GMT+09:00) Title : Re: [dev] Question about relationship between iotivity and sensord Considering a constrained device with local sensor, if we treat sensor as resource, then it could be registered by registerResource(). Right? If yes, then my understanding is it is application's task to find this sensor, read sensor data, answer resource querying/setting/observation request from IoTivity. IoTivity does not touch any part for physical sensor access. Is my understanding correct? Best regards, James -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Thiago Macieira Sent: Friday, April 10, 2015 3:09 PM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] Question about relationship between iotivity and sensord On Friday 10 April 2015 06:41:07 Li, Hao H wrote: > Hi, > > https://review.tizen.org/git/?p=platform/upstream/iotivity.git;a=summa > ry > https://review.tizen.org/git/?p=platform/core/system/sensord.git;a=sum > mary > > Iotivity has modules like soft-sensor-manager etc. > > Will Iotivity plan to integrate sensord to process sensor data? Or > they are designed to work independently and provide interface with > each other if needed? IoTivity doesn't read from sensors. However, it does provide API for reporting sensors over the network and for reading those reports. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> https://lists.iotivity.org/mailman/listinfo/iotivity-dev _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> https://lists.iotivity.org/mailman/listinfo/iotivity-dev [cid:image001.gif at 01D0743F.9B7915F0] [http://ext.samsung.net/mailcheck/SeenTimeChecker?do=d083a0c0528fae5280b5099572ad7c405d330e3cf46106c7845131c3288cb0d84b72a8114dfd8109d8c023f270a836a153cb8b1934afabac2f6aaf3d92ded142cf878f9a26ce15a0] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150411/529fb3b6/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13168 bytes Desc: image001.gif URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150411/529fb3b6/attachment.gif>
