This thread seems to have strayed from Ziran's original question which was about how to indicate iotivity version number. I don't think any option number is appropriate for this. It would be fine to have a property on some resource (e.g., /oic/d) to hold the iotivity version number. That's what AllJoyn did (the AJSoftwareVersion field in the About data).
From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Ziran Sun Sent: Thursday, December 8, 2016 8: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 -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161209/cc9d06e4/attachment.html>
