Hi Jihun, I figured out this is not easy to identify SceneList, SceneCollection, SceneMember and SceneValue from each other. I believe these terminologies can mislead the scene concept. Could you propose updated terminology which can bring clear identification equivalent to its role when possible?
BR, Uze Choi From: [email protected] [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of ??? Sent: Wednesday, January 06, 2016 2:33 PM To: iotivity-dev at lists.iotivity.org Subject: [dev] Open discussion on Scene Manager Hi. I'm currently working on a design and implmentation of Scene Manager which is one of IoTivity services. At this time, I want to share this with you and ask your comments like additional requirements and use cases which I have not thought of. This manager will help developers who want to control multiple resources in a *group control* manner by providing APIs to create scene-related resources and manage attribute values in the resources. (Let's call a "scene execution" rather than "group control", from now) OIC specification already defines the scene-related resource models in OIC core framework specification: - SceneList resoure, SceneCollection resource, and SceneMember resource. Shortly, SceneCollection resource is a representative resource to provide a "scene execution" service and has a number of SceneMember resources which store an scene execution information to be used when a scene is executed. If you want to know details of these resources, please refer to OIC core framework specification document (Explanatory section: Section 11.6, Resource model: D11, D12, D13) The following describes a list of features of Scene Manager service: (basic feature) 1. Compatible to Scene-releated resource models and behaviors in OIC Core Spec. - Please, refer to SceneList, SceneCollection, and SceneMember resource models in OIC spec. document 2. One can create a SceneCollection resource having a set of scenes to update multiple resources of (a) homogeneous/heterogeneous resource type(s) 3. One can make a SceneCollection resource discoverable in a network so that other authenticated OIC client can send a request to execute a scene provided by the resource 4. By means of CoAP request(i.e. POST), one can create a SceneCollection and add a SceneMember to the SceneCollection at other remote OIC server (additional feature) 5. Provide a way to import a SceneCollection?s configuration (description) from a XML file - One can easily form or reproduce a Scene Collection resource with the configuration file I've attached an introduction slide for Scene Manager. And you can find the OIC spec. document at http://openinterconnect.org/developer- resources/specs/. Please find the attachment and feel free to share your comments with me if you have. Best Regards, Jihun Ha (???/???, Ph.D.) IoT, IoTivity, OIC | IoT Lab Software R&D Center | Samsung Electronics Co., Ltd Mobile +82 10 2533 7947 jihun.ha at samsung.com | jhha85 at gmail.com -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160106/c41ec55a/attachment.html>
