Hi Habib,


I figured out this error happed from 1.0.1 release, to remove the specification 
GAP.

Due to you contribution, 1.0.1 has been released successfully.

Normal Resource (not common resource) can reply as follows.





However, collection resource case, some error happen as follows. Due to error 
from getChild( ) and cbor converting, it represent as 1.0.1 below.

Could you update some code to follow the 1.1.0 format?

In Detail, Collection response payload should have array [, ] brace. Child 
resource representation should have href property also.







BR, Uze Choi

From: ???(Uze Choi) [mailto:[email protected]] 
Sent: Thursday, February 18, 2016 2:12 PM
To: 'jihun.ha at samsung.com'; 'Kesavan, Vijay S'
Cc: 'iotivity-dev at lists.iotivity.org'; '???'
Subject: RE: RE: [dev] mulfunction report for information retrieve of children 
resources Client API



Hi Jihun



Your requirement is to improve the capability of 
?OCRepresentation.addChild(OCRepresentation &)? to support multi-level depth.

Thank you for clarification. And I fully agree with you.



However, default collection entity handler may not support this multiple depth 
level complexity, which needs to be out of scope.



BR, Uze Choi

From: Jihun Ha [mailto:[email protected]] 
Sent: Thursday, February 18, 2016 2:06 PM
To: ???; 'Kesavan, Vijay S'
Cc: iotivity-dev at lists.iotivity.org; ???
Subject: Re: RE: [dev] mulfunction report for information retrieve of children 
resources Client API



Hi. Uze,



Please find my replies for your question inline.



BR, Jihun Ha.



------- Original Message -------

Sender : ???<uzchoi at samsung.com> S6(??)/??/IoT Lab(S/W??)/????

Date : 2016-02-18 13:43 (GMT+09:00)

Title : RE: [dev] mulfunction report for information retrieve of children 
resources Client API



Jihun, Two Questions I have,



Initially depth was restricted for implementation simplicity.



Q1. Anyway, all these resources should be related in the same local device.

What is the use case for this depth.  House ? Room ? Light? All they are same 
device?



[JH] As you know, I'm currently implemention Scene Manager which has a 3-depth 
resource structure:

SceneList, SceneCollection, and SceneMember resources. And these are in a same 
device, not distributed to several device.

Q2. Do you want to say about the specification of collection operation or

collection default entity handler implementation or

something supporting logic for application specific custom collection entity 
handler?

[JH] Currently, an application developer can build the more than 3-depth 
representation by calling addChild(OCRepresentation &) in OCRepresentation 
class. I just want to say that if a developer wants to build such a 
representation in an application entity handler, IoTivity base stack should 
support that.



BR, Uze Choi

From: ??? [mailto:[email protected]] 
Sent: Thursday, February 18, 2016 1:12 PM
To: ???; Kesavan, Vijay S
Cc: iotivity-dev at lists.iotivity.org; ???
Subject: Fwd: [dev] mulfunction report for information retrieve of children 
resources Client API



Hi Vijay and Uze,



I think that we may think the case where a depth of collection resource is more 
than 2 like 3 depth.

For example, we have 3 resources: top/middle/leaf resources. Top resource is a 
collection for the middle resource and the middle resource is also a collection 
for the leaf resource. And the top and middle resources both support BATCH 
interface.

In that case, I think the response of GET request to the top collection 
resource(i.e. 1st res)  with batch interface could include representations of 
the leaf resources (i.e. 3rd res) as well as the middle resource's (i.e. 2rd 
res). 



How do you think about it?



BR, Jihun Ha.



------- Original Message -------

Sender : ???<uzchoi at samsung.com> S6(??)/??/IoT Lab(S/W??)/????

Date : 2016-02-18 11:02 (GMT+09:00)

Title : [dev] mulfunction report for information retrieve of children resources 
Client API



Hi Vijay



>From the IoTivity 1.0.1 there is bug from collection scenario.

https://jira.iotivity.org/browse/IOT-926 .

This API is used from our Scene Manager development. Scene Manager development 
is stuck due to this issue.



Could you check this stuff and resolve ASAP?

You can check the functionality from room sample with collection API. (Detail 
from Jira)



BR, Uze Choi



?????. ??? ?????. 





?????. ??? ??.



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 








-------------- next part --------------
HTML ?????? ??????????????...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160219/ba59c066/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.gif
Type: image/gif
Size: 13168 bytes
Desc: ?????? ?? ????????.
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160219/ba59c066/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 25021 bytes
Desc: ?????? ?? ????????.
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160219/ba59c066/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 90632 bytes
Desc: ?????? ?? ????????.
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160219/ba59c066/attachment-0001.png>

Reply via email to