Hi Ziran,
I?m also supportive, iotivity should have its own version on the other optional field. However, even though we have a version, without policy this information is useless. Even more, core resource may have a implementation following the policy. BR, Uze Choi From: [email protected] [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of Ziran Sun Sent: Friday, December 09, 2016 1:28 AM To: iotivity-dev at lists.iotivity.org Subject: [dev] [Versioning] Add option number for IoTivity version Hi All, As you may be aware that a new feature on versioning has been introduced in OCF spec. Versioning in the specification and design .ppt is just Spec/content encoding as per OCF Spec. However, under the same OCF version, we have more than one IoTivity versions. I wonder if we could suggest to extend the versioning section in the spec to include versioning for Iotivity as well. Basically, we will handle Iotivity versioning similar but separately from OCF versioning, which means that a separate versioning header option might required for Iotivity as well. If you have any thoughts/suggestions, we?d be much appreciated to hear from you! Best regards, Ziran -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161209/4ad9977a/attachment.html>
