Hi Jihun, Sequence point of view, existing sequence is for prefixed setting for devices and scenes but your idea considers dynamic setting. I think your proposal is practically required for scene realization.
Anyway, Could you propose your idea for each question. It will be better to review your idea rather than spec guy propose from draft. Mark, Do you have any concern for my idea? BR, Uze Choi From: [email protected] [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of ??? Sent: Monday, January 18, 2016 7:40 PM To: Mark Trayer Cc: iotivity-dev at lists.iotivity.org; cftg at openinterconnect.org Subject: [dev] Request to update the OIC specification on *Scene* resource model Hi. Mark, I'm Jihun Ha who had discussed with you few month ago about scene or group action concept. Now, I'm currently working on implementing a *Scene Manager* in Iotivity to help developers to easily create/manage SceneCollection and SceneMember resources and trying to make it compliant to the resource models in OIC Core spec. Shortly, I summarize a API call flow of the Scene Manager to form SceneCollection/SceneMember resources below: 1. Create SceneCollection resource 2. Add SceneValue to SceneCollection resource 3. Add SceneMember resource to SceneCollection resource 4. Add an scene mapping item (one of all scene mapping items) to the SceneMember resource For that, I'm requesting you and CFTG some additions to OIC specification, especially, *Scene* resource model part. 1. Allow to add a new sceneValue after a SceneCollection resource is initially created. - I think, users possibly wants to add a new sceneValue to an existing SceneCollection resource. But, in the Spec., there is no mention about it. - How to add a new sceneValue is needed. 2. Allow to add a new item of scene mapping in SceneMember resource after a SceneMember resource is initially created. - Similar reason with the above request: Users possibly wants to add a new item of scene mapping in SceneMember resource. But, in the spec., there is no mention about it. - How to add a new item of scene mapping is needed. (like what is a target resource of the request, SceneCollection resource? or SceneMember resource?) 3. Let me clear of all response payload formats against requests of resource creation, update, and execution. - In the current Spec., there is an ambiguity of response payload formats. The formats in Figure 38 and 39 and RAML definition are differ to each other. Can I refer to only a RAML description in the Spec.? (D.11~13) - And I want to know response payload formats after adding a new SceneValue and a new item of scene mapping. 4. Interface type should be specified for all operations. - In the current Spec.(D.11~13), all resource for *Scene* can have 2 interface types: "oic.if.a" and "oic.if.ll". But it is not specified when each interface is used anywhere. - For example, when oic client want to create a SceneCollection resource at remote, should the client use "oic.if.ll" interface type? - OR I know that there is a "link batch" interface in the Spec. Should the client use that? Please feel free to ask me if you have any question on my requests. Thank you in advance. ?????. ??? ??. 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 <http://ext.samsung.net/mailcheck/SeenTimeChecker?do=213efb02e5f841dc30b533b 72d635699c6cf2914a8d64751a9b245bbf05ab6f693b88b5cdcaca3638c238075770efdd88a3 bd3da7f658eba62e1ac75b522795a07805447a154a46fcf878f9a26ce15a0> -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160119/ab232c90/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13168 bytes Desc: ?????? ?? ????????. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160119/ab232c90/attachment.gif>
