Hi Jay, sorry for the late response. I think its related to the current discussion about storing the device id. IoTivity shouldn't define these values, just provide a framework to configure. A vendor releasing a product based on IoTivity has to set it. https://jira.iotivity.org/browse/IOT-876, https://jira.iotivity.org/browse/IOT-875 are related issues you might watch their status. Best regards Markus
------- Original Message ------- Sender : Jung-Hyun Oh<junghyun.oh at samsung.com> S5/Senior Engineer/IoT Lab(S/W??)/Samsung Electronics Date : Nov 25, 2015 11:26 (GMT+09:00) Title : [dev] What does the Attributes of the /oic/d stands for? Hi all, I found there?re 4 attributes in the reserved URI /oic/d (Device Resource) in the IoTivity Stack. Those are ?n?, the device name, ?di?,. the device ID, ?lcv?, the spec version url and ?dmv", the data model. The attributes ?n? & ?di? are relatively easy to understand what they stand for, however, it is bit difficult to understand What ?lcv? and ?dmv" are, and they are even hard coded inside the ?octypes.h?. It seems like Release Management Function Leader may have to update those attribute values when the OIC QA team verifies whether the stack meets the Specific OIC version or not which I?m not sure. Does anyone who knows about these attributes could inform us what is the usage of them and how to manage them? Thank you. Jay. -------------- next part -------------- A non-text attachment was scrubbed... Name: Attach1.1.txt Type: application/octet-stream Size: 167 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20151203/488151f2/attachment.obj>
