In the IoTivity there are several API sets as follows including currently being implemented.
There are several API sets as follow in IoTivity. Standard IoTivity - csdk C API (Tested from IoTivity QA) - resource(base) C++ API (Tested from IoTivity QA) ? Dependency with csdk API - resource(base) Java API (Tested from IoTivity QA) ? Dependency with C++ API - Resource Encapsulation C++ API (Tested from IoTivity QA) ? Dependency with C++ API - Resource Encapsulation Java API (Tested from IoTivity QA) ? Dependency with C++ API - IPCA C API (being implemented) - Dependency with C++ API - Smart Home API (being implemented) ? Dependency with csdk API Constraint IoTivity - C API (not Tested from IoTivity QA yet) We need to select which API set is officially guaranteed for user to use and what else is the optional set. There is Discrepancy across different API set. Currently, Some APIs in the higher level are not implemented yet. For example, C API set has some functionalities but C++/Java does not have it, even if these are quite important features. They should be managed well from API review team. One comment, dropping specific API set should consider dependency also. BR, Uze Choi From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Gregg Reynolds Sent: Friday, March 03, 2017 7:52 AM To: Thiago Macieira Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] API Review function On Mar 2, 2017 4:29 PM, "Thiago Macieira" <thiago.macieira at intel.com> wrote: On quinta-feira, 2 de mar?o de 2017 14:16:26 PST Thiago Macieira wrote: > Hello all > > Finally getting to my action items from previous meetings of the Steering > Group. I will send an email on each of the two, new proposed functions, > detailing what is expected. We're looking for volunteers to assume the > position of Function Lead for organising IoTivity's API as well as > Buildsystem. We're asking for candidates since there is no natural > candidate. The first of the two proposed functions is the API Review one. We need a person or a team to be willing to look into any API we design that is meant to be used by anyone except ourselves, and make sure that the API is consistent. Soon, we'd also like to make sure that our API is backwards compatible, so applications written with IoTivity version X will continue to compile and work with IoTivity version Y, provided Y >= X. This team will probably be tasked with reviewing the existing API as well, proposing changes, and establishing guidelines on how to review. The latter point will impact releasing: when is the API review supposed to happen, relative to the feature freeze and the releases? When is the API frozen for a given release? (note that Dino's release suggestion timetable had some elements of this) This is a technical function and the Function Lead is expected to be knowledgeable of C and C++ API designs[*]. [*] the team may propose dropping the C++ API. +1001 -- 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 -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170303/538f0a7a/attachment.html>
