Somebody else please who knows more about interfaces and background? Thanks
From: Gregg Reynolds [mailto:[email protected]] Sent: Tuesday, April 18, 2017 10:02 PM To: Tomcik Ondrej Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Interfaces usage On Apr 16, 2017 3:10 PM, "Ondrej Tomcik" <Ondrej.Tomcik at kistler.com<mailto:Ondrej.Tomcik at kistler.com>> wrote: Hello developers. I was studying this concept from more sources and to be honest, I don't understand it. OIC specification: An interface provides view into the resource and then defines the requests and responses permissible on that view of the Resource. One resource can support multiple interfaces - multiple views. Based on the interface provided in query, subset or all properties of that resource are replied in response. Okay, but how is interface linked with the property of the resource? If you check oneiota, definition of resource contains only list of interfaces and list of properties. There is no link between property and interface. How can be then defined and specified what property is returned for which interface/view? Another missing point is who is responsible for this functionality and mapping. Is it provided out of box? If yes, how is it mapped fwiw my reading is this: the spec mumbles sth about user-defined ifs, but nothing about how. conclusion: for now all you get is the predefined ifs. you can verify this in the oneiota stuff (oic.core.json, i think) where if is an enum. "interface" is rather poorly chosen, afaics. what an oic/ocf if really is is a kind of access control spec. baseline exposes all props, r exposes read only props, etc. iow the props exposed are based on metadata. if you want to expose some set of props based on other criteria, you use resource type, not if. hth, gregg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170419/a4d8e05d/attachment.html>
