forked from iudx/iudx-api-doc-server
-
Notifications
You must be signed in to change notification settings - Fork 0
/
cat.yaml
executable file
·611 lines (581 loc) · 27.9 KB
/
cat.yaml
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
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
title: "Catalogue Server API-Doc"
categories:
- category:
name: "IUDX Catalogue Server Interface"
desc: "The information resource catalogue contains the meta-data of resources along with auxiliary descriptions, API endpoints, data models and other meta-information like discovery hints, location details, providers etc. A useful analogy is an online shopping catalogue, where a consumer can browse through the available products and then decide to purchase a subscription. The resource catalogue plays a similar role for the consumer applications in the context of smart city data resources. <br> <br> Authentication and Authorization for the catalogue interface is achieved through the use of client side certificates, issued by the IUDX Certificate Authority. This is required only for some of the APIs where there is an explicit mention. Furthermore, the APIs that do require the client side certificates for authentication and authorization, also require the certificates to belong to class 3 of the IUDX certificate classes. Any API that requires this kind of authentication and authorization mechanism will mention “IUDX certificate - class 3” in their access mechanism."
api-categories:
- category:
name: "Items"
desc: "Any entry in the catalogue is an item. An item can be of multiple item-types as mentioned in the IUDX Reference Architecture document. The list of different itemTypes (referred to as ‘item-types’ in the context of APIs) and details for each can be found in Section 3.4.1 of the IUDX Reference Architecture document."
apis:
- api:
title: "Create Item"
endpoint: "/catalogue/v1/items"
method: "POST"
api-desc: "Creates an item of type item-type in catalogue"
parameters:
- parameter:
key: "type"
value: "One of <ul> <li> resourceItem </li> <li> resourceGroup </li> <li> provider </li> <li> resourceServer </li> </ul>"
desc: "List items of a particular item-types available in catalogue."
type: "query"
- parameter:
key: "item"
value: "catalogue item"
desc: "Item to be uploaded to the catalogue as JSON-LD document"
type: "body"
response-content-type: "application/json"
responses:
- response:
code: 201
desc: "Success"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/search.js"
- api:
title: "Update Item"
endpoint: "/catalogue/v1/items/{id}"
method: "PUT"
api-desc: "Creates an item of type item-type in catalogue"
parameters:
- parameter:
key: "id"
value: "catalogue item id"
desc: "ID of the item in the catalogue."
type: "path"
- parameter:
key: "item"
value: "catalogue item"
desc: "Update an existing item of an item-type in the catalogue."
type: "body"
response-content-type: "application/json"
responses:
- response:
code: 201
desc: "Success"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/search.js"
- api:
title: "Delete Item"
endpoint: "/catalogue/v1/items/{id}"
method: "DELETE"
api-desc: "Delete a registered item in catalogue."
parameters:
- parameter:
key: "id"
value: "catalogue item id"
desc: "Update an existing item of an item-type in the catalogue."
type: "path"
response-content-type: "application/json"
responses:
- response:
code: 204
desc: "No Content"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/search.js"
- api:
title: "Retrieve Item"
endpoint: "/catalogue/v1/items/{id}"
method: "GET"
api-desc: "Read or Retrieve an item using an item-id in catalogue."
parameters:
- parameter:
key: "id"
value: "catalogue item id"
desc: "Retrieves an item of type item-type in catalogue"
type: "path"
response-content-type: "application/json"
responses:
- response:
code: 200
desc: "No Content"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/search.js"
- category:
name: "Search"
desc: "A search operation allows applications to discover items in the catalogue using complex queries and filters. <br> Catalogue allows ‘attribute’, ‘text’ and ‘geo’ search functionalities. This should be used with the ‘search-type’ query parameter to perform a specific type of search. <ul> <li> Attribute search can find items that match a specific ‘attribute’ query. For example, to find items with ‘tags’=’water’, where ‘tags’ is a known attribute. This is typically expected to be used when certain attributes are known to be present in items. </li> <li> Text search can find items that match a given string in some part of a catalogue item. </li> <li> Geo search can find items that is within a given geographical boundary. </li> </ul>"
apis:
- api:
title: "List Item Types"
endpoint: "/catalogue/v1/search"
method: "GET"
api-desc: "Lists all the ‘item-types’ in the catalogue"
parameters:
- parameter:
key: "type"
value: "item-types"
desc: "List items of a particular item-types available in catalogue."
type: "query"
response-content-type: "application/json"
responses:
- response:
code: 200
desc: "Success"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/search.js"
- api:
title: "List Items of an Item Type"
endpoint: "/catalogue/v1/search"
method: "GET"
api-desc: "Lists all the items of a particular ‘item-type’ in the catalogue"
parameters:
- parameter:
key: "item-type"
value: "One of <ul> <li> resourceItem </li> <li> resourceGroup </li> <li> provider </li> <li> resourceServer </li> </ul>"
desc: "List items of a particular item-types available in catalogue."
type: "query"
response-content-type: "application/json"
responses:
- response:
code: 200
desc: "Success"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/search.js"
- api:
title: "Attribute Search"
endpoint: "/catalogue/v1/search"
method: "GET"
api-desc: "An attribute search allows applications to perform search on items for an exact match on attributes. Searches the catalogue for the given attribute query. In case the ‘attribute-value’ is an array the query returns all items with ‘attribute-name’ matching ‘ANY’ of the values specified in the ‘attribute-value’ array."
parameters:
- parameter:
key: "item-type"
value: "One of <ul> <li> resourceItem </li> <li> resourceGroup </li> <li> provider </li> <li> resourceServer </li> </ul>"
desc: "List items of a particular item-types available in catalogue."
type: "query"
- parameter:
key: "attribute-name"
value: "name"
desc: "Name of the attribute in the catalogue."
type: "query"
- parameter:
key: "attribute-value"
value: "name"
desc: "Value of the attribute in the catalogue."
type: "query"
response-content-type: "application/json"
responses:
- response:
code: 200
desc: "Success"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/search.js"
- api:
title: "Spatial Search - (Circle)"
endpoint: "/catalogue/v1/search"
method: "GET"
api-desc: "A geo search allows one to search through catalogue items within a given geographical boundary. This helps in restricting the search query to items belonging to a certain geo-spatial boundary. The search queries and parameters are as per the KVP encoding for query constraints as per the OGC Catalogue Services 3.0 Specification - HTTP Protocol Binding."
parameters:
- parameter:
key: "item-type"
value: "One of <ul> <li> resourceItem </li> <li> resourceGroup </li> <li> provider </li> <li> resourceServer </li> </ul>"
desc: "List items of a particular item-types available in catalogue."
type: "query"
- parameter:
key: "lat"
value: "latitude"
desc: "Specifies the latitude value for the point."
type: "query"
- parameter:
key: "lon"
value: "longitude"
desc: "Specifies the longitude value for the point."
type: "query"
- parameter:
key: "radius"
value: "radius"
desc: "Specifies the radius of the query in meters."
type: "query"
response-content-type: "application/json"
responses:
- response:
code: 200
desc: "Success"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/s/search.js"
- api:
title: "Spatial Search - (Polygon)"
endpoint: "/catalogue/v1/search"
method: "GET"
api-desc: "A geo search allows one to search through catalogue items within a given geographical boundary. This helps in restricting the search query to items belonging to a certain geo-spatial boundary. The search queries and parameters are as per the KVP encoding for query constraints as per the OGC Catalogue Services 3.0 Specification - HTTP Protocol Binding."
parameters:
- parameter:
key: "item-type"
value: "One of <ul> <li> resourceItem </li> <li> resourceGroup </li> <li> provider </li> <li> resourceServer </li> </ul>"
desc: "List items of a particular item-types available in catalogue."
type: "query"
- parameter:
key: "geometry"
value: "polygon(p1,p2,p3,p4,p1)"
desc: "A closed polygon whose first and last point must match, thus requiring n + 1 vertices to create an n-sided polygon and a minimum of 4 vertices."
type: "query"
response-content-type: "application/json"
responses:
- response:
code: 200
desc: "Success"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/s/search.js"
- api:
title: "Spatial Search - (Bounding Box)"
endpoint: "/catalogue/v1/search"
method: "GET"
api-desc: "A geo search allows one to search through catalogue items within a given geographical boundary. This helps in restricting the search query to items belonging to a certain geo-spatial boundary. The search queries and parameters are as per the KVP encoding for query constraints as per the OGC Catalogue Services 3.0 Specification - HTTP Protocol Binding."
parameters:
- parameter:
key: "item-type"
value: "One of <ul> <li> resourceItem </li> <li> resourceGroup </li> <li> provider </li> <li> resourceServer </li> </ul>"
desc: "List items of a particular item-types available in catalogue."
type: "query"
- parameter:
key: "bbox"
value: "x1,y1,x2,y2"
desc: "A bounding box is expressed to be used as a spatial predicate."
type: "query"
response-content-type: "application/json"
responses:
- response:
code: 200
desc: "Success"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/s/search.js"
- api:
title: "Text Search"
endpoint: "/catalogue/v1/search"
method: "GET"
api-desc: "A text search query allows one to search through the catalogue items for a given text string."
parameters:
- parameter:
key: "item-type"
value: "One of <ul> <li> resourceItem </li> <li> resourceGroup </li> <li> provider </li> <li> resourceServer </li> </ul>"
desc: "List items of a particular item-types available in catalogue."
type: "query"
- parameter:
key: "q"
value: "text to search"
desc: "Can be any free form text query to search the catalogue."
type: "query"
response-content-type: "application/json"
responses:
- response:
code: 200
desc: "Success"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/search.js"
- api:
title: "Response Filter"
endpoint: "/catalogue/v1/search"
method: "GET"
api-desc: "Filter acts as the API Presentation layer for applications. Applications can use filters to decide the attributes that needs to be responded for a search query."
parameters:
- parameter:
key: "item-type"
value: "One of <ul> <li> resourceItem </li> <li> resourceGroup </li> <li> provider </li> <li> resourceServer </li> </ul>"
desc: "List items of a particular item-types available in catalogue."
type: "query"
- parameter:
key: "attribute-filter"
value: "Array of attributes"
desc: "Restricts the response to contain only the attributes requested."
type: "query"
response-content-type: "application/json"
responses:
- response:
code: 200
desc: "Success"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/s/search.js"
- category:
name: "Count"
desc: "A count operation allows applications to discover the number of items in the catalogue using complex queries and filters. <br> Catalogue allows ‘attribute’, ‘text’ and ‘geo’ search functionalities. This should be used with the ‘search-type’ query parameter to perform a specific type of search. <ul> <li> Attribute search can find items that match a specific ‘attribute’ query. For example, to find items with ‘tags’=’water’, where ‘tags’ is a known attribute. This is typically expected to be used when certain attributes are known to be present in items. </li> <li> Text search can find items that match a given string in some part of a catalogue item. </li> <li> Geo search can find items that is within a given geographical boundary. </li> </ul>"
apis:
- api:
title: "Count Items of an Item Type"
endpoint: "/catalogue/v1/count"
method: "GET"
api-desc: "Lists all the items of a particular ‘item-type’ in the catalogue"
parameters:
- parameter:
key: "item-type"
value: "One of <ul> <li> resourceItem </li> <li> resourceGroup </li> <li> provider </li> <li> resourceServer </li> </ul>"
desc: "List items of a particular item-types available in catalogue."
type: "query"
response-content-type: "application/json"
responses:
- response:
code: 200
desc: "Success"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/search.js"
- api:
title: "Count using Attribute Search"
endpoint: "/catalogue/v1/count"
method: "GET"
api-desc: "A count on attribute search allows applications to perform search on items for an exact match on attributes. Searches the catalogue for the given attribute query. In case the ‘attribute-value’ is an array the query returns all items with ‘attribute-name’ matching ‘ANY’ of the values specified in the ‘attribute-value’ array."
parameters:
- parameter:
key: "item-type"
value: "One of <ul> <li> resourceItem </li> <li> resourceGroup </li> <li> provider </li> <li> resourceServer </li> </ul>"
desc: "List items of a particular item-types available in catalogue."
type: "query"
- parameter:
key: "attribute-name"
value: "name"
desc: "Name of the attribute in the catalogue."
type: "query"
- parameter:
key: "attribute-value"
value: "name"
desc: "Value of the attribute in the catalogue."
type: "query"
response-content-type: "application/json"
responses:
- response:
code: 200
desc: "Success"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/search.js"
- api:
title: "Count using Spatial Search - (Circle)"
endpoint: "/catalogue/v1/count"
method: "GET"
api-desc: "A geo count allows one to search through catalogue items within a given geographical boundary. This helps in restricting the search query to items belonging to a certain geo-spatial boundary. The search queries and parameters are as per the KVP encoding for query constraints as per the OGC Catalogue Services 3.0 Specification - HTTP Protocol Binding."
parameters:
- parameter:
key: "item-type"
value: "One of <ul> <li> resourceItem </li> <li> resourceGroup </li> <li> provider </li> <li> resourceServer </li> </ul>"
desc: "List items of a particular item-types available in catalogue."
type: "query"
- parameter:
key: "lat"
value: "latitude"
desc: "Specifies the latitude value for the point."
type: "query"
- parameter:
key: "lon"
value: "longitude"
desc: "Specifies the longitude value for the point."
type: "query"
- parameter:
key: "radius"
value: "radius"
desc: "Specifies the radius of the query in meters."
type: "query"
response-content-type: "application/json"
responses:
- response:
code: 200
desc: "Success"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/s/search.js"
- api:
title: "Count using Spatial Search - (Polygon)"
endpoint: "/catalogue/v1/count"
method: "GET"
api-desc: "A geo count allows one to search through catalogue items within a given geographical boundary. This helps in restricting the search query to items belonging to a certain geo-spatial boundary. The search queries and parameters are as per the KVP encoding for query constraints as per the OGC Catalogue Services 3.0 Specification - HTTP Protocol Binding."
parameters:
- parameter:
key: "item-type"
value: "One of <ul> <li> resourceItem </li> <li> resourceGroup </li> <li> provider </li> <li> resourceServer </li> </ul>"
desc: "List items of a particular item-types available in catalogue."
type: "query"
- parameter:
key: "geometry"
value: "polygon(p1,p2,p3,p4,p1)"
desc: "A closed polygon whose first and last point must match, thus requiring n + 1 vertices to create an n-sided polygon and a minimum of 4 vertices."
type: "query"
response-content-type: "application/json"
responses:
- response:
code: 200
desc: "Success"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/s/search.js"
- api:
title: "Count using Spatial Search - (Bounding Box)"
endpoint: "/catalogue/v1/count"
method: "GET"
api-desc: "A geo count allows one to search through catalogue items within a given geographical boundary. This helps in restricting the search query to items belonging to a certain geo-spatial boundary. The search queries and parameters are as per the KVP encoding for query constraints as per the OGC Catalogue Services 3.0 Specification - HTTP Protocol Binding."
parameters:
- parameter:
key: "item-type"
value: "One of <ul> <li> resourceItem </li> <li> resourceGroup </li> <li> provider </li> <li> resourceServer </li> </ul>"
desc: "List items of a particular item-types available in catalogue."
type: "query"
- parameter:
key: "bbox"
value: "x1,y1,x2,y2"
desc: "A bounding box is expressed to be used as a spatial predicate."
type: "query"
response-content-type: "application/json"
responses:
- response:
code: 200
desc: "Success"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/s/search.js"
- api:
title: "Text Search"
endpoint: "/catalogue/v1/search"
method: "GET"
api-desc: "A count on a text search query allows one to search through the catalogue items for a given text string."
parameters:
- parameter:
key: "item-type"
value: "One of <ul> <li> resourceItem </li> <li> resourceGroup </li> <li> provider </li> <li> resourceServer </li> </ul>"
desc: "List items of a particular item-types available in catalogue."
type: "query"
- parameter:
key: "q"
value: "text to search"
desc: "Can be any free form text query to search the catalogue."
type: "query"
response-content-type: "application/json"
responses:
- response:
code: 200
desc: "Success"
- response:
code: 404
desc: "Not found"
examples:
- example:
lang: "Java"
file: "api-examples/search.java"
- example:
lang: "Javascript"
file: "api-examples/search.js"