Hi IoTivity Developers: I'm interesting to the mapping of Bluetooth profiles to OCF specification.
According to the following mail, does it mean that the mapping is already existed? If yes, where could I get the mapping of Bluetooth profiles? Or, it just means developers are able to design their own mapping method using current IoTivity framework? (like Resource Container?) Thank you. Best Regards, Annie -----Original Message----- From: [email protected] [mailto:iotivity-dev-bounces at lists.iotivity.org] On Behalf Of Dave Thaler via iotivity-dev Sent: Thursday, August 04, 2016 10:52 PM To: Thiago Macieira; iotivity-dev at lists.iotivity.org; jihwan.seo at samsung.com; JinHyeock Choi Subject: Re: [dev] OCF Endpoint Implement on iotivity Windows also has address-to-string conversion routines when using Bluetooth sockets. That said, BLE is not an "OCF" supported transport, and personally I see no need for it to be, given there's two other alternatives that already exist today: a) run OCF protocols over IP over BLE b) use a bridge to map to existing Bluetooth profiles -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160810/f8f406c8/attachment.html>
