-
Notifications
You must be signed in to change notification settings - Fork 2
/
link.yml
182 lines (182 loc) · 7.65 KB
/
link.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
TD_COAP_LINK_01:
obj: Access to well-known interface for resource discovery
cfg: CoAP_CFG_BASIC
ref: "[LINK]"
pre:
- Client and server supports CoRE Link Format
- Server supports /.well-known/core resource and the CoRE Link Format
seq:
- s: 'Client is requested to retrieve Server’s list of resource '
- c: Client sends a GET request to Server for /.well-known/core resource
- c:
- 'Server sends response containing:'
- Content-format option indicating 40 (application/link-format)
- Code indicating 2.05 (Content)
- Payload indicating all the links available on Server
- v: Client displays the list of resources available on Server
TD_COAP_LINK_02:
obj: Use filtered requests for limiting discovery results
cfg: CoAP_CFG_BASIC
ref: "[LINK] 4.1"
pre:
- Client supports CoRE Link Format
- Server supports CoRE Link Format
- Server offers different types of resources (Type1, Type2, ...; see Note)
seq:
- s: Client is requested to retrieve Server’s list of resource of a specific type
Type1
- c: Client sends a GET request to Server for /.well-known/core resource containing
URI-Query indicating “rt=Type1”
- c:
- 'Server sends response containing:'
- Content- format option indicating 40 (application/link-format) Payload indicating
only the links of type Type1 available on Server
- v: Client displays the list of resources of type Type1 available on Server
not: Type1, Type2, ... refer to real resource types available on Server and shall
be extracted from Server’s /.well-known/core resource
TD_COAP_LINK_03:
obj: Handle empty prefix value strings
cfg: CoAP_CFG_BASIC
ref: "[LINK] 4.1 §2"
pre:
- Client supports Core Link Format
- Server supports Core Link Format
- Server offers different types of resources (Type1, Type2, ...; see Note)
- Server offers resources with no type (i.e. no rt attribute)
seq:
- s: Client is requested to retrieve Server’s list of resources matching an rt empty
value
- c: Client sends a GET request to Server for /.well-known/core resource containing
URI-Query indicating rt=“*”
- c:
- 'Server sends response containing:'
- Content-format option indicating 40 (application/link-format)
- Payload indicating only the links having an rt attribute
- v: Client displays the list of resources with rt attribute available on Server
not: Type1, Type2, ... refer to real resource types available on Server and shall
be extracted from Server’s /.well-known/core resource
TD_COAP_LINK_04:
obj: Filter discovery results in presence of multiple rt attributes
cfg: CoAP_CFG_BASIC
ref: "[LINK] 3.1, 4.1 §2"
pre:
- Client supports Core Link Format
- Server supports Core Link Format
- - 'Server offers 4 groups of resources:'
- - Resources with rt=“Type1 Type2”
- Resources with rt=“Type2 Type3”
- Resources with rt=“Type1 Type3”
- Resources with rt=“”
seq:
- s: Client is requested to retrieve Server’s list of resources of a specific type
Type2
- c: Client sends a GET request to Server for /.well-known/core resource containing
URI-Query indicating rt=“Type2”
- c:
- 'Server sends response containing:'
- Content-format option indicating 40 (application/link-format)
- Payload indicating only the links of groups 1 and 2
- v: Client displays the list of resources of type Type2 available on Server
TD_COAP_LINK_05:
obj: Filter discovery results using if attribute and prefix value strings
cfg: CoAP_CFG_BASIC
ref: "[LINK] 3.2, 4.1 §5"
pre:
- Client supports Core Link Format
- Server supports Core Link Format
- - 'Server offers 4 groups of resources:'
- - Resources with if=“If1”
- Resources with if=“If2”
- Resources with if=“foo”
- Resources with no if attribute
seq:
- s: Client is requested to retrieve Server’s list of resources matching the interface
description pattern “If*”
- c: Client sends a GET request to Server for /.well-known/core resource containing
URI-Query indicating if=“If*”
- c:
- 'Server sends response containing:'
- Content-format option indicating 40 (application/link-format)
- Payload indicating only the links of groups 1 and 2
- v: Client displays the retrieved list of resources
TD_COAP_LINK_06:
obj: Filter discovery results using sz attribute and prefix value strings
cfg: CoAP_CFG_BASIC
ref: "[LINK] 3.3, 4.1 §5"
pre:
- Client supports Core Link Format
- Server supports Core Link Format
- Server offers resource with sz attribute
- Server offers resources with no sz attribute
seq:
- s: Client is requested to retrieve Server’s list of resources having a sz attribute
- c: Client sends a GET request to Server for /.well-known/core resource containing
URI-Query indicating sz=“*”
- c:
- 'Server sends response containing:'
- Content-format option indicating 40 (application/link-format)
- Payload indicating only the links having a sz attribute
- v: Client displays the retrieved list of resources
TD_COAP_LINK_07:
obj: Filter discovery results using href attribute and complete value strings
cfg: CoAP_CFG_BASIC
ref: "[LINK] 4.1"
pre:
- Client supports Core Link Format
- Server supports Core Link Format
- Server offers resources /link1 /link2 and /link3
seq:
- s: Client is requested to retrieve the link-value anchored at /link1
- c: Client sends a GET request to Server for /.well-known/core resource containing
URI-Query indicating href=“/link1”
- c:
- 'Server sends response containing:'
- Content-format option indicating 40 (application/link-format)
- Payload indicating only the link for /link1
- v: Client displays the retrieved list of resources
TD_COAP_LINK_08:
obj: Filter discovery results using href attribute and prefix value strings
cfg: CoAP_CFG_BASIC
ref: "[LINK] 4.1"
pre:
- Client supports Core Link Format
- Server supports Core Link Format
- Server offers resources /link1 /link2 and /link3
- Server offers resource /test
seq:
- s: Client is requested to retrieve the link-value anchored at /link*
- c: Client sends a GET request to Server for /.well-known/core resource containing
URI-Query indicating href=“/link*”
- c:
- 'Server sends response containing:'
- Content-format option indicating 40 (application/link-format)
- Payload indicating only the link matching /link*
- v: Client displays the retrieved list of resources
TD_COAP_LINK_09:
obj: Arrange link descriptions hierarchically
cfg: CoAP_CFG_BASIC
ref: "[LINK] 5 §4"
pre:
- Client supports Core Link Format
- Server supports Core Link Format
- Server offers an entry located at /path with ct=40
- Server offers sub-resources /path/sub1, /path/sub2, … (see Note)
seq:
- s: Client is requested to retrieve one of the sub-resources
- c: 'Client sends a GET request to Server for /.well-known/core resource '
- c:
- 'Server sends response containing:'
- Content-format option indicating 40 (application/link-format) Payload indicating
the link description for /path
- c: Client sends a GET request for /path to Server
- c:
- 'Server sends response containing:'
- Content-format option indicating 40 (application/link-format) Payload indicating
the link description for /path/sub1, /path/sub2, …
- c: Client sends a GET request for /path/sub1
- c:
- Server sends 2.05 (Content) response.
- Payload contains /path/sub1
- v: Client displays the retrieved sub-resource.
not: "/path/sub1, /path/sub2, … refer to real resources available on Server and
shall be extracted from Server’s /.well-known/core resource"