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
