Hello Mohammed,

I recommend you to read the core specs in order to understand the resource 
model proposed by OIC[0].

To answer your actual question: there are standard interfaces 
(BASELINE(default), LL, BATCH, GROUP). For more details, inspect the source 
files in ?resource/csdk/stack/src/*?.

As for the last question: there are no properties belonging to any interface, 
because an interface itself is a property (a basic one). The other stuff you 
get by issuing a GET request is just a bunch of user-defined properties which 
can be manipulated by using one of the available interfaces. To get this 
straight, please read the core specs first.

Hope this helped.

Best Regards,
Cosmin

[0] http://openinterconnect.org/developer-resources/specs/

From: iotivity-dev-bounces at lists.iotivity.org 
[mailto:[email protected]] On Behalf Of Mohammed Javid 
via iotivity-dev
Sent: Thursday, September 17, 2015 7:47 PM
To: iotivity-dev at lists.iotivity.org
Subject: [dev] Need some info or documentation

Hi,

I am trying to understand the representation of a resource in iotivity stack. 
Can anybody point me to some documentation about the details.

One specific question I have is:

I see a resource exposed by the sample simpleserver application as

URI: /a/light
SID: 37 03 84 96 9B D8 B8 45 B7 89 4F AE 63 0C F2 75
Resource Types: core.light, core.brightlight
Interfaces: oic.if.baseline, oic.if.ll
Bitmap: 3
Secure?: false
Port: 0

I would like to know the details about the above mentioned fields. Also, are 
there standard resource types and interfaces defined by the protocol? Where can 
I find the details?
What is the Port?

Even though I see multiple resource types and interfaces, when I do the GET, I 
get the values:
name(string): John's light
power(int): 0;
state(bool): false

How do I know, what values belong to what interface?

Thanks,
Javid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150921/1bb6c7b7/attachment.html>

Reply via email to