Hi Jihun & Uze, Thanks for taking the initiative here and for generating the detailed sequence diagrams. I?ll put this on the agenda for the SHTG call initially (as while it is in the Core spec SHTG generated the contribution); we?ll discuss this week and then at the F2F if need be. My initial thoughts are that I agree with the needs/spec gaps that you have identified below and on first pass the sequence diagrams you have shared look good. We talked about the use of link-batch when we were first drafting the Spec text; my gut feel is that your view that we may need to use this for creation is correct, but will discuss with other TG members on the call as mentioned. Best, Mark.
From: cftg at openinterconnect.org [mailto:[email protected]] On Behalf Of ??? Sent: Tuesday, January 19, 2016 5:17 AM To: ???; Mark Trayer Cc: iotivity-dev at lists.iotivity.org; cftg at openinterconnect.org Subject: Re: [cftg] RE: [dev] Request to update the OIC specification on *Scene* resource model Hi. Uze and Mark, By Uze's request, I've made some draft diagrams for the first 2 questions: Diagrams for adding a new SceneValue and a new SceneMapping item. (Note that, it looks better to make a SceneMember resource accept a request to add a new SceneMapping item. I found that a SceneMember resource's CRUDN behavior allows only READ, not UPDATE in the current spec. I think it should be updated) Please find my attached files and review them. And I think that we may need a "Link Batch" interface specified in OIC spec.(in Section 7.1.6.3.3 Intefaces for collections) for creating SceneCollection/SceneMember resource by a remote OIC client. What is your opinion? Thank you. BR, Jihun Ha ------- Original Message ------- Sender : ???<uzchoi at samsung.com<mailto:uzchoi at samsung.com>> S6(??)/??/IoT Lab(S/W??)/???? Date : 2016-01-19 13:51 (GMT+09:00) Title : [cftg] RE: [dev] Request to update the OIC specification on *Scene* resource model 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: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of ??? Sent: Monday, January 18, 2016 7:40 PM To: Mark Trayer Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>; cftg at openinterconnect.org<mailto: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 ?????. ??? ?????. ?????. ??? ??. 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 [cid:image001.gif at 01D152C4.890A5B40] [http://ext.samsung.net/mailcheck/SeenTimeChecker?do=213efb02e5f841dca897d844618ab8d81c9e8b4636ee16656294b5f8c4c7517d727781ba1657a70b421b1fafb670b67e7d1393888abc1868a728c55b39cc59eacf878f9a26ce15a0] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160119/f75b477b/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/20160119/f75b477b/attachment.gif>
