Re "Ideally, this work should go through refactor and consume OCF's new bridging spec"
I believe that answers my question that the intent really is (a) Bridging/translating OCF schemas <-> ZigBee profiles, in order to talk to existing ZigBee devices that know nothing about OCF/iotivity? Assuming so, then I agree with Joey's statement above. And right, it's likely this won't happen anytime soon (1-3 months+). Dave From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Morrow, Joseph L Sent: Friday, August 19, 2016 9:44 AM To: Gladish, Jacob <Jacob_Gladish at comcast.com>; iotivity-dev at lists.iotivity.org; karthikeyanprakash at outlook.com Subject: Re: [dev] Iotivity with Zigbee +IoTivity-dev, +Karthikeyan Hi Jacob, As per the time this mapping occurred, the mapping happened under an earlier OIC version which didn't have any notion of bridging or mapping. This was an IoTivity sponsored activity that was external from specification from OIC because of the lack of any specification around this (to create new and exciting demos!). Ideally, this work should go through refactor and consume OCF's new bridging spec and become a work item owned by that group. Should this happen, the correct work flows (as you've stated and I agree with) would/should occur around the ZigBee stuff in IoTivity. However, it is more likely the case that this won't happen anytime soon (1-3 months+) from the interest I've been seeing on this topic in the mailing lists. I'm not saying no one wants to do this work, there's just higher priority work items currently on the table. If you are an OCF member and a member of the Bridging Task Group, you can see the current areas of interest around their bridging/mapping efforts there. Aside from this, anyone can contribute to IoTivity and do clean-up on code and refactor, add new features and capabilities. If licensing fits, anyone can even add new plugins to the model the ZigBee_Wrapper in IoTivity is doing. Karthikeyan, I don't know if you're an OCF member, so I will end this email with the following distinction clarified: - anyone (with a free Linux Foundation username/password) can contribute to IoTivity - only OCF (usually paid; see openinterconnect.org<http://openinterconnect.org> for all options) members can contribute to OCF directly - specifications/rules from OCF don't always apply to IoTivity and vice versa (because one is a closed group and the other is an open group) Another clarification: - OIC changed their name to OCF. When this happened, spec versions started back at 1.0 (OIC's latest/last pending release is at version 1.1, while OCF is drafting 1.0 now, which inherits from OIC 1.1). What you see in IoTivity today is largely based on OIC 1.1, not OCF. Thanks, Joey Morrow On Aug 19, 2016, at 9:14 AM, Gladish, Jacob <Jacob_Gladish at comcast.com<mailto:Jacob_Gladish at comcast.com>> wrote: I think there should be an official OCF document that calls out the mapping between HA 1.2 and Smart Home. Assuming Smart Home is the right spec. From: Morrow, Joseph L [mailto:[email protected]] Sent: Friday, August 19, 2016 12:05 PM To: Gladish, Jacob <Jacob_Gladish at cable.comcast.com<mailto:Jacob_Gladish at cable.comcast.com>> Subject: Re: Iotivity with Zigbee Hi Jacob, Idk if it's explicitly stated anywhere, but the mapping is between ZigBee Home Automation (HA1.2) and OIC Smart Home 1.1. The wiki goes farther and shows us this is only a partial mapping and can be extended to fully mapped with some work. (I don't know of any plans of doing further work ATM.) The wiki only shows that 5 or 6 mappings are currently being done and one of the mappings is invalid. Thanks, Joey Morrow On Aug 19, 2016, at 8:55 AM, Gladish, Jacob <Jacob_Gladish at comcast.com<mailto:Jacob_Gladish at comcast.com>> wrote: Back to one of Dave's questions. What's the state of any official mapping between OCF schemas and ZigBee profiles? To me, that's the most important part. From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Morrow, Joseph L Sent: Friday, August 19, 2016 11:50 AM To: Karthikeyan P <karthikeyanprakash at outlook.com<mailto:karthikeyanprakash at outlook.com>> Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] Iotivity with Zigbee Hi Karthikeyan, At this time, things work the other way around: IoTivity is supporting "ZigBee manufacturer OEMs" (as of now: only Telegesis Dongle previously mentioned on IoTivity wiki). AFAIK, there is no work currently occurring to bring in any other ZigBee 'modules' other than this. To get native support from ZigBee OEMs, the OEM themselves would need to contribute to IoTivity (and likely become members of OCF). As I had earlier mentioned that in all the cases I am aware: the API licenses of these other ZigBee 'modules' aren't friendly with IoTivity's open-source license. Because of these licensing clashes, the open-source IoTivity project has to be careful with what closed-source libraries (I.e. ZigBee OEM API) it uses and how it uses them. This is required to avoid legal issues. Afaik, these legal issues are too large of an issue to simply provide the support in IoTivity. I am not a legal expert, so you may want to review IoTivity's licenses with the ZIgBee OEM APIs and consider this for yourself. FYI: when I say "license", I am referring to the license header on top of all the source code files. Thanks, Joey On Aug 18, 2016, at 10:03 PM, Karthikeyan P <karthikeyanprakash at outlook.com<mailto:karthikeyanprakash at outlook.com>> wrote: Hello Joey, Thank you for the reply and clarifying ZigBee with Iotivity implementation. Is it expected that any of the ZigBee manufacturer OEMs to support Iotivity in near future?. As we are a startup and trying to implement Iotivity framework in our product, We would like to get native support from the ZigBee OEMs. Regards, Karthikeyan ________________________________ From: Morrow, Joseph L <joseph.l.morrow at intel.com<mailto:[email protected]>> Sent: 19 August 2016 02:13 To: Karthikeyan P; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: Iotivity with Zigbee Hello Karthikeyan, Currently, the only implementation of ZigBee is against ZigBee Home Automation spec 1.2 using Telegesis AT Command Set API (AT Command Set is documented here: ). This API is up-leveled and abstracted at [IOTIVITY]/plugins/zigbee_wrapper. If you wanted to bring in support for other ZigBee modules, you will need to write a sister module to "[IOTIVITY]/plugins/zigbee_wrapper/telegesis_wrapper" (for example, for 'xbee' you would have to create "[IOTIVITY]/plugins/zigbee_wrapper/xbee_wrapper" module entirely). As for your firmware questions, you will have to perform some analysis of the way the module "Zigbee_Wrapper" abstracts the "Telegesis_Wrapper" module. From there you will need to do further analysis on how this abstraction may/may not apply to XBee/SILabs APIs and conclude what changes may be needed to either Firmware of XBee/SILabs or what changes may be needed in the "Zigbee_Wrapper module. From here, you would need to document and request the community to make these changes or you can go ahead and contribute the changes in a review at any time. As of now, the implementation in IoTivity for ZigBee is specific to Telegesis, but was architected to allow for other module types as you've stated. AFAIK, The addition of other modules has been ignored for the timebeing as the APIs for the other module types (XBee/SILabs APIs) don't meld well with IoTivity's open source license type (this difference in license types could affect IoTivity releases to the general public). Thanks, Joey From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Karthikeyan P Sent: Thursday, August 18, 2016 5:23 AM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] Iotivity with Zigbee Hi Iotivity Team, I would like to know about implementation of Iotivity with ZigBee. I tried looking at few documents and finally got this<https://wiki.iotivity.org/zigbee_plugin_-_using_plugin_interface_module>. I would like to know whether ordinary ZigBee modules such as XBee or Silicon Labs EM35X series could be used to implement Iotivity. If yes, What type of implementation required in firmware part?. Regards, Karthikeyan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160819/54197d94/attachment.html>
