OCF enforce data type for each resource / property very specifically. For luminance sensor it is supposed to be floating point value and not the integer.
Regards Dwarka ---------------------------------------------------------------------------------- Software R&D Center | Convergence 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:[email protected]] On Behalf Of ??? (Uze Choi) Sent: Wednesday, November 16, 2016 7:22 PM To: 'Tonny Tzeng'; iotivity-dev at lists.iotivity.org Subject: Re: [dev] OCF data model question Hi Tony, Type checking capability in advance is the one of the missing part which IoTivity does not have. Could you provide more detail happening. If possible, it will be best to put it into jira.iotivity.org to assign the appropriate person. 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 Tonny Tzeng Sent: Wednesday, November 16, 2016 6:52 PM To: iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] OCF data model question Hi, My Iotivity Android client observes updates from a illuminance resource, but it crashes sometimes when the received illuminance value is a java.lang.Integer. Is it the wrong implementation in the server or should I examine the type attribute (java.lang.Interger or Double) before casting the property to the desired value? Does OCF spec enforce strict data type during transmitting CBOR binaries? Thanks. Best Regards, Tonny -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161116/d37ac4da/attachment.html>
