Hi All,
OCF has decided to submit the OCF specification into ISO/IEC. OCF specification needs verification from open source implementation prior to submission deadline, May. Once it is verified from implementation perspective, OCF need to have IPR review. In conclusion, OCF specification should be verified thru cross check between open source implementation and OCF certification tool by Fed. OCF requested a testable IoTivity code including additional features from OCF1.0 such as versioning, introspection, endpoint and some security updates. Let me check whether these features are coming inside into the IoTivity by Jan. Then I?ll create the tag on master branch. BR, Uze Choi From: ??? (Uze Choi) [mailto:[email protected]] Sent: Wednesday, January 18, 2017 9:11 PM To: iotivity-dev at lists.iotivity.org Subject: Feature list request for Upcomming IoTivity release. Hi IoTivity feature developers, This year IoTivity has a release milestone one is in April and the other is in Oct except patch version release. One is for alignment for OCF1.0 spec and OCF CTT (beta or other version) and The other is for OCF 1.1 spec including spec compliant easy-setup, cloud and some new features. According to the IoTivity Release process (https://wiki.iotivity.org/release_process), I?d like to receive the feature list by this week. Please update it on https://wiki.iotivity.org/2.0_release_plan and register into jira(some items are already done) BR, Uze Choi -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170120/d10c6258/attachment.html>
