Hi Glen, Please reflect the previous valuable comments from others as much as possible during development. Let me create the branch with this name.
BR, Uze Choi From: ??? [mailto:[email protected]] Sent: Monday, March 20, 2017 4:16 PM To: iotivity-dev at lists.iotivity.org; ??? Subject: Re: [dev] Smart Home API proposal. Hi all and Uze Choi, As we discussed, we'd like to start proposed Smart Home API that provides another API in IoTivity service layer. So, i have updated the wiki page for Smart Home API proposal that include problem definition and concept, features, advantage, and some example of ours. Plus, we are goint to implement Smart Home API based on required enhanced features. https://wiki.iotivity.org/proposal_for_iotivity_smart_home_api @Uze Choi We'd like to start this work in separated branch named "smarthome_api". Please create a branch for us. BR, Glen Youngjin Kim. --------- Original Message --------- Sender : ??? <uzchoi at samsung.com> Principal Engineer/IoT Lab(S/W??)/???? Date : 2017-03-08 16:01 (GMT+9) Title : RE: Re: [dev] Smart Home API proposal. Considering frequent adding and changing resource and property in the real world, code generation should be done again and again during developement which lead generated skelton code to be copied and replaced again. Furthermore code generation is a little bit old style I feel. Recently well abstrated API following less user code is more trendy( this comment does not mean Smart Home API.) According to Younggin comment design goal looks different. Whether code generation or not is othogonal from the main idea of his API proposal. Omar could you explain why IPCA is closer to code generation ? BR Uze Choi --------- Original Message --------- Sender : Omar Maabreh via iotivity-dev <iotivity-dev at lists.iotivity.org> Date : 2017-03-08 07:12 (GMT+1) Title : Re: [dev] Smart Home API proposal. Totally agree that code generation is the right solution to this problem which we'd all like to solve. The IPCA api's that are in gerrit right now are a first step in enabling this. Thanks, - Omar -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Thiago Macieira Sent: Tuesday, March 07, 2017 10:06 PM To: iotivity-dev at lists.iotivity.org; glen.kim at samsung.com Subject: Re: [dev] Smart Home API proposal. Em quarta-feira, 8 de mar?o de 2017, ?s 01:31:27 CET, ??? escreveu: > I think making RAML definition is not easy in 3rd party developer's > point of view. they need to know specification to make it again. > therefore, i think this is reasonable proposal which provides API > usability improvement and way to make OCF service and device easily. I don't think the goals are at odds. We do want the easy API. I just don't want *us* to spend time developing it for each and every resource type that OCF comes up with. I'd like us to create a code generator that does that job for us, for current as well as any future resource types. That way, developers won't need to deal with the RAML files or Swagger files. They'll use the generated API. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev -------------------------------- Glen YoungJin Kim IoT Lab | Convergence Team | Software Center SAMSUNG ELECTRONICS CO., LTD. 010-3356-9627 <mailto:glen.kim at samsung.com> glen.kim at samsung.com -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170320/b76d8dc7/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13402 bytes Desc: ?????? ?? ????????. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170320/b76d8dc7/attachment.gif>
