Hi Dwarka, Can you elaborate or point to a summary of how collections are not aligned with the spec yet?
Thanks, Joey Morrow From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Dwarkaprasad Dayama Sent: Wednesday, June 8, 2016 1:19 AM To: 'Maxi Wu' <maxi.wu at u-media.com.tw>; iotivity-dev at lists.iotivity.org Subject: Re: [dev] iotivity cloud question regarding OIC core spec Dear Maxi, IoTivity collections is not aligned with Spec yet. Other than this, "if" and "rt" values are now array in OIC 1.1, hence it is correct. If you are interested to look into RD more, please join OSWG - Spec Coordination TG, soon you will some presentations uploaded related to this topic. Regards Dwarka ---------------------------------------------------------------------------------- Software R&D Center | Software Platform Team | IoT Lab Open Connectivity Foundation - OSWG - Spec Coordination TG Chair Iotivity Steering Group - Advisory Committee From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Maxi Wu Sent: Wednesday, June 08, 2016 5:04 PM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] iotivity cloud question regarding OIC core spec Hi everyone, I am testing cloud RD server (through CI), when I test publishing resources, some questions arise. 1. Does RD server only accept publishing resources in a collection with tag? Even if I am publishing only 1 resource with a unique URI? 2. From OIC core spec, value type of rt is string, but cloud RD server is requiring a Array List, is there a conflict between the spec and iotivity implementation? The same goes with if (interface) 3. The core spec describe polity as property name 'p' with value type string. But when I publish resource to RD, the policy is actually "bm":<octet>, I am so confused. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160608/da0aaf4b/attachment.html>
