Subject: [core] resource-directory-03

From: peter van der Stok <[email-masked]>
Date: Wed, 30 May 2012 16:55:47 +0200

Hi Zach,

I like to comment on some aspects of RD that I did not fully 
understand.
In section 1 you do not mention "service discovery". I assume that this 
is intentional?

What is a Resource Directory Function Set? is that the Function Set we 
discussed earlier? Why the resource directory prefix?
You call rt "end-point type" while it is called resource type in 
link-format document. Please, remain consistent
resource type of End-point is OK with me.
In section 4.3 rt is mentioned in the URI template, but in the example 
also specified in the payload. What is the difference?
In section 4.3 example you write ins="Indoor". ins is not defined in 
link-format, and not in this document.
In sectiuon 4.5 the first phrase seems to assume that removal is only 
done by registered device. I can imagine the registration and removal is 
done by third device (phone, commissioning device, etc...)
In section 5 in example GET/rd-lookup/res?rt=Temperature
the return is <coap://{ip:port}/temp>;rt=........
should this not be <coap://node1/temp>;rt=......

Some perceived typos

resource descriptions instead of resources descriptions
section 1, last alinea: and to register, maintain, look up and remove 
resource descriptions on the RD. (3 TYPOS)

section2 Resource directory
A web entity...
Domain
All end-points within a domain MUST be uniquely identified.
End-point
Specification (aiton)

section 3
An end-point is a web server (identified by an IP address)

section 3.1
submitting  (submiting)

section 3.2
commission (commision)

section 4.1 Upon success, .....for each RD discovered on the responding 
server,......

section 4.3 Parameters (paremeters)

Hope this helps,

peter

-- 
Peter van der Stok
mailto: [email-masked]
www: www.vanderstok.org
tel NL: +31(0)492474673     F: +33(0)966015248