On Dec 2, 2017 6:42 AM, "Wang, Xin" <[email protected]> wrote:
Hi, I have a question regarding to the “Resource Identity” in OCF core spec 1.3. Any comments is appreciated here. I understand the “href” as discovered in the response of /oic/res can be used as unique identifier of a resource instance. So usually we query the resource by using the “href” as uri in the request. Not necessarily. OCF makes a distinction between address and identity. See section 6. Not sure how this works out in practice. One thing I can imagine is multiple devices on one OCF server. Obviously the spec writers has something in mind but decline to let us in on the secret. The other scenario I can imagine is when you might change URL s dynamically. The resource would retain its identity but its address could change. hth Gregg Then what is the point to use the “id” common property in the response payload? Or multiple resource instances can have the same “href”, so the query response will contain an array of resource instances? I pasted the “resource identify” from the spec below: 7.3.2.6 Resource Identity 1326 The Resource Identity Property shall be a unique (across the scope of the host Server) instance 1327 identifier for a specific instance of the Resource. The encoding of this identifier is device and 1328 implementation dependent as long as the uniqueness constraint is met, noting that an 1329 implementation may use a uuid as defined in section 3.4. The Resource Identity Property is as 1330 defined in Table 3. _______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
