Hi Markus, Regarding this section in OIC standard specification, I believe source code should does not need to do anything now.
If you consider metadata to be passed thru wire by Resource browsing or access, it will requires lots of consideration. OCRespresentation is just class to display the data for resource response, then it need to follow the resource model about metadata. Standard specification can define the metadata of property, but there is no reason for the code to sync up such as read and use as parameter in the stack. Let?s just leave it(meta data) later time access or use. BR, Uze Choi From: [email protected] [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of Markus Jung Sent: Friday, March 13, 2015 2:48 PM To: iotivity-dev at lists.iotivity.org Subject: [dev] Attribute metadata Hello, the latest OIC draft defines some additional metadata on attributes (in the standard now merged with properties). An attribute can have now a value type, a unit, access mode, value rules, etc. Is there a plan how to support this in the current stack? In OCRepresentation is a class definition for AttributeItem, which might be a good candidate for extension. Further, should the metadata encoded if a resource is retrieved? If yes, a simple key/value encoding of attributes is not possible anymore and the payload might become quite big. Another way would be to use the resource type definitions based on JSON schema as proposed in the draft and to provide a separate interface to query the metadata. I am just asking because this metadata might be also useful for the primitive services. Thanks and best regards Markus Jung -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150313/d6c7ace9/attachment.html>
