-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathopenapi-sc.yaml
More file actions
779 lines (777 loc) · 30.4 KB
/
openapi-sc.yaml
File metadata and controls
779 lines (777 loc) · 30.4 KB
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
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
openapi: "3.0.0"
info:
title: Knowledge Engine REST Developer API
description:
This API describes how Smart Connectors are instantiated, Knowledge
Interactions are (un)registered and data is exchanged. Each Smart Connector
is coupled with a Knowledge Base Id, so every rest call uses this Knowledge
Base Id to identify yourself.
version: 1.2.5
paths:
/sc:
get:
summary: Either get all available Smart Connectors or a specific one if the Knowledge-Base-Id is provided.
tags:
- smart connector life cycle
parameters:
- name: Knowledge-Base-Id
in: header
required: false
description: The knowledge base id who's Smart Connector information you would like to have.
schema:
type: string
responses:
'200':
description: A list of Smart Connectors. It will have only a single element if the Knowledge-Base-Id was provided.
content:
application/json; charset=UTF-8:
schema:
type: array
items:
$ref: '#/components/schemas/SmartConnector'
'404':
description: If there is no Smart Connector for the given Knowledge-Base-Id.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
'500':
description: If a problem occurred.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
post:
summary: Create a new Smart Connector for the given Knowledge Base.
tags:
- smart connector life cycle
requestBody:
required: true
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/SmartConnector'
examples:
without lease:
value:
knowledgeBaseId: http://example.org/a-knowledge-base-id
knowledgeBaseName: Example Knowledge Base
knowledgeBaseDescription: This is a detailed description
with 60 seconds lease:
value:
knowledgeBaseId: http://example.org/a-knowledge-base-id
knowledgeBaseName: Example Knowledge Base
knowledgeBaseDescription: This is a detailed description
leaseRenewalTime: 60
description:
The created smart connector will be cleaned up automatically
after about 60 seconds. To postpone the cleanup, your
knowledge base has to call /sc/lease/renew to extend the lease
by 60 seconds.
with reasoner enabled:
value:
knowledgeBaseId: http://example.org/a-knowledge-base-id
knowledgeBaseName: Example Knowledge Base
knowledgeBaseDescription: This is a detailed description
reasonerEnabled: true
description:
The reasoner is disabled by default. If enabled, the created smart
connector will use a reasoner to orchestrate the data exchange.
This increases the flexibility, but can decrease the performance
and cause unexpected behaviour, for now. This flexibility means the
smart connector will automatically try to combine data coming
from different knowledge bases or try to convert units of measures.
If the reasoner is disabled, the smart connector will only exchange
data with other smart connectors if their graph patterns match
entirely (apart from ordering and variable names).
responses:
'200':
description: If the Smart Connector for the given Knowledge Base is successfully created.
'400':
description: If the creation of the Smart Connector for the given Knowledge Base failed.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
delete:
summary: Delete the Smart Connector belonging to the given Knowledge Base
tags:
- smart connector life cycle
parameters:
- name: Knowledge-Base-Id
in: header
required: true
description: The knowledge base id who's smart connector should be deleted.
schema:
type: string
responses:
'200':
description: If the Smart Connector for the given Knowledge Base is successfully deleted.
'404':
description: If there is no Smart Connector for the given Knowledge-Base-Id.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
/sc/lease/renew:
put:
summary: Renew the lease of a Smart Connector.
tags:
- smart connector lease
parameters:
- name: Knowledge-Base-Id
in: header
required: true
description: The ID of the Knowledge Base whose lease you wish to renew.
schema:
type: string
responses:
'200':
description: The renewed lease
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/SmartConnectorLease'
'400':
description: The request was faulty.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
'404':
description: The Knowledge Base doesn't exist (anymore), or doesn't have a lease.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
/sc/ki:
get:
summary: Get all KnowledgeInteractions for a given Knowledge-Base-Id
tags:
- knowledge interaction life cycle
parameters:
- name: Knowledge-Base-Id
in: header
required: true
description: The Knowledge Base Id that is registering a Knowledge Interaction.
schema:
type: string
responses:
'200':
description: If the Knowledge Interactions were successfully returned.
content:
application/json; charset=UTF-8:
schema:
type: array
items:
$ref: '#/components/schemas/KnowledgeInteractionWithId'
post:
summary: Register a Knowledge Interaction with the Smart Connector of the given Knowledge Base Id.
tags:
- knowledge interaction life cycle
parameters:
- name: Knowledge-Base-Id
in: header
required: true
description: The Knowledge Base Id that is registering a Knowledge Interaction.
schema:
type: string
requestBody:
required: true
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/KnowledgeInteractionBase'
examples:
ASK without prefixes:
value:
knowledgeInteractionType: AskKnowledgeInteraction
graphPattern: "?a <http://example.org/isRelatedTo> ?b ."
ASK with prefixes:
value:
knowledgeInteractionType: AskKnowledgeInteraction
graphPattern: "?a rdf:type ex:Something ."
prefixes:
rdf: "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
ex: "http://example.org/"
REACT with prefixes:
value:
knowledgeInteractionType: ReactKnowledgeInteraction
argumentGraphPattern:
?a rdf:type ex:Measurement .
?a ex:hasValueInMeters ?b .
resultGraphPattern:
?a rdf:type ex:Measurement .
?a ex:hasValueInYards ?b .
prefixes:
rdf: "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
ex: "http://example.org/"
ASK with name and prefixes:
value:
knowledgeInteractionType: AskKnowledgeInteraction
knowledgeInteractionName: books-by-shakespeare
graphPattern: "?a rdf:type ex:Book . ?a ex:hasAuthor ex:Shakespeare"
prefixes:
rdf: "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
ex: "http://example.org/"
responses:
'200':
description: If the Knowledge Interaction is successfully registered, it returns the KnowledgeInteractionId object.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/KnowledgeInteractionId'
example:
knowledgeInteractionId:
https://www.interconnectproject.eu/knowledge-engine/knowledgebase/example/a-reacting-kb/42
'400':
description: If the Knowledge Interaction is not successfully registered.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
'404':
description: If a Smart Connector for the given Knowledge-Base-Id cannot be found.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
delete:
summary: Unregister the given Knowledge Interaction with the Smart Connector of the given Knowledge Base
tags:
- knowledge interaction life cycle
parameters:
- name: Knowledge-Base-Id
in: header
required: true
description: The Knowledge Base id of the Knowledge Interaction that should be deleted.
schema:
type: string
- name: Knowledge-Interaction-Id
in: header
required: true
description: The Knowledge Interaction id of the Knowledge Interaction that should be deleted.
schema:
type: string
responses:
'200':
description: If the Knowledge Interaction is successfully unregistered.
'400':
description: If unregistering the Knowledge Interaction failed.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
'404':
description: If a Knowledge Interaction or Knowledge Interaction for
the given Knowledge-Base-Id and Knowledge-Interaction-Id cannot be
found.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
/sc/ask:
post:
summary: Execute the given Ask Knowledge Interaction with the given binding set. It is possible to target this ask to a specific Knowledge Base by including a RecipientSelector in the requestBody.
tags:
- proactive
parameters:
- name: Knowledge-Base-Id
in: header
required: true
description: The Knowledge Base Id for which to execute the ask.
schema:
type: string
- name: Knowledge-Interaction-Id
in: header
required: true
description: The Ask Knowledge Interaction Id to execute.
schema:
type: string
requestBody:
required: true
description: Either a BindingSet only or a RecipientSelector and BindingSet. The recipient selector currently only supports a single Knowledge-Base-Id, but might be extended in the future. The keys (i.e. variables) in the BindingSet are allowed to be incomplete, but they must correspond to the keys that were defined in the graph pattern of the knowledge interaction.
content:
application/json; charset=UTF-8:
schema:
oneOf:
- $ref: '#/components/schemas/RecipientAndBindingSet'
- $ref: '#/components/schemas/BindingSet'
examples:
bindingset only:
value:
- p: <http://www.tno.nl/s1>
q: <http://www.tno.nl/p1>
r: <http://www.tno.nl/o1>
recipient and bindingset:
value:
recipientSelector:
knowledgeBases:
- http://www.tno.nl/kb2
- http://www.tno.nl/kb3
bindingSet:
- p: <http://www.tno.nl/s1>
q: <http://www.tno.nl/p1>
r: <http://www.tno.nl/o1>
responses:
'200':
description: If the ask was successful it returns all found variable
bindings together with additional exchange info. The returned bindings form
a set and there is no quaranteed ordering. The exchange info shows the other
Knowledge Bases that contributed to the answer with timing, initiator information.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/AskResult'
'400':
description: If the ask failed.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
'404':
description: If a Knowledge Interaction for the given Knowledge-Base-Id and Knowledge-Interaction-Id cannot be found.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
'500':
description: If an internal server error occurs.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
/sc/post:
post:
summary: Execute the given Post Knowledge Interaction with the given binding set. It is possible to target this post to a specific Knowledge Base by including RecipientSelector in the requestBody.
tags:
- proactive
parameters:
- name: Knowledge-Base-Id
in: header
required: true
description: The Knowledge Base Id for which to execute the post.
schema:
type: string
- name: Knowledge-Interaction-Id
in: header
required: true
description: The Post Knowledge Interaction Id to execute.
schema:
type: string
requestBody:
required: true
description: Either a BindingSet only or a RecipientSelector and BindingSet. The recipient selector currently only supports a single Knowledge-Base-Id, but might be extended in the future. The keys bindings must be complete, and they must correspond to the binding keys that were defined in the knowledge interaction.
content:
application/json; charset=UTF-8:
schema:
oneOf:
- $ref: '#/components/schemas/RecipientAndBindingSet'
- $ref: '#/components/schemas/BindingSet'
examples:
bindingset only:
value:
- p: <http://www.tno.nl/s1>
q: <http://www.tno.nl/p1>
r: <http://www.tno.nl/o1>
recipient and bindingset:
value:
recipientSelector:
knowledgeBases:
- http://www.tno.nl/kb2
bindingSet:
- p: <http://www.tno.nl/s1>
q: <http://www.tno.nl/p1>
r: <http://www.tno.nl/o1>
responses:
'200':
description: If the post was successful it optionally returns all
result variable bindings together with all exchange infos. The
exchange info shows the other Knowledge Bases that contributed to
the answer with timing, initiator information.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/PostResult'
'404':
description: If a Knowledge Interaction for the given Knowledge-Base-Id and Knowledge-Interaction-Id cannot be found.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
'500':
description: If an internal server error occurs.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
/sc/handle:
get:
summary: Start waiting for a handle request for the given Knowledge Base Id.
description: Note that this is a long polling HTTP call.
It will block until the client is expected to handle something in which
case it returns. When it returns, a new request to this same endpoint
should be made to receive further handle requests. Any missed handle requests
are queued at the server-side and returned one at a time. All handle
requests (both for Answer and React Knowledge Interactions) for the
given Knowledge-Base-Id will be received via a single long polling http
connection. The Knowledge Interaction Id can be used to distinguish
between different Knowledge Interactions. The *handle request id*
(which is unique per Knowledge Base Id) should be used when sending the
result back to the server. It allows the server to know which handle
request you are reacting to in the *post* method of this path.
tags:
- reactive
parameters:
- name: Knowledge-Base-Id
in: header
required: true
description: The knowledge base id from who's smart connector we are waiting for handle request.
schema:
type: string
responses:
'200':
description: If a request to handle a particular Knowledge Interaction Id comes in with a binding set.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/HandleRequest'
example:
knowledgeInteractionId: http://example.org/ki/your-knowledge-interaction-id
handleRequestId: 1
bindingSet:
- a: <http://example.org/some-incoming-value>
b: <http://example.org/another-incoming-value>
requestingKnowledgeBaseId: http://example.org/knowledge-base-id-of-requesting-side
'202':
description: No problems, but please reinitiate the long polling request. To prevent very long open connections (which might cause problems for some systems), we regularly return with status code 202 to renew the long polling connection. Note that no handlerequests will be missed, because these are queued automatically.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
'404':
description: If a Knowledge Interaction for the given Knowledge-Base-Id and Knowledge-Interaction-Id cannot be found.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
'409':
description: Only one connection per Knowledge-Base-Id is allowed and we already have one.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
'410':
description: This long polling connection has stopped because either the server will shut down or the knowledge base is stopping, please do __not__ reinitiate this request.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
'500':
description: If a problem occurred. Please reinitiate this long polling http call.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
post:
summary: Send the answer or reaction of a specific long polling handle
request back to the Smart Connector of the given Knowledge-Base-Id. Note that an empty binding set object must be returned when the specific react knowledge interaction has no result graph pattern.
tags:
- reactive
parameters:
- name: Knowledge-Base-Id
in: header
required: true
description: The knowledge base id from who's smart connector we are sending a answer or reaction.
schema:
type: string
- name: Knowledge-Interaction-Id
in: header
required: true
description: The knowledge interaction id we react to or answer.
schema:
type: string
requestBody:
required: true
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/HandleResponse'
description: The keys bindings must be complete, and they must correspond to the binding keys that were defined in the knowledge interaction.
responses:
'200':
description: If the answer is successfully processed by your smart connector.
'400':
description: If the answer was not successfully processed by the Knowledge Base's smart connector.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
'404':
description: If a Handle Request Id or Knowledge Interaction for the
given Knowledge-Base-Id and Knowledge-Interaction-Id cannot be found.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/ResponseMessage'
/version:
get:
summary: Get version info.
tags:
- version info
responses:
'200':
description: Version info, currently only containing the artifact version of the KE REST server.
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/VersionInfo'
components:
schemas:
SmartConnector:
type: object
required: [knowledgeBaseId, knowledgeBaseName, knowledgeBaseDescription]
properties:
knowledgeBaseId:
type: string
knowledgeBaseName:
type: string
knowledgeBaseDescription:
type: string
leaseRenewalTime:
type: integer
minimum: 30
maximum: 3600
description: Include this property if you want to have your knowledge
base automatically unregistered when you don't renew your lease. Expiry
is checked periodically, so your knowledge base may actually be
valid for longer than the given time.
reasonerEnabled:
type: boolean
description: Include this optional property if you want to specify whether
the smart connector should use a reasoner or a matcher to orchestrate data
exchange. In general the reasoner increases the flexibility, but decreases
the performance. The matcher decreases the flexibility, but increases
the performance.
BindingSet:
type: array
items:
nullable: false # Enforced manually, but kept here nonetheles.
type: object
additionalProperties:
type: string
RecipientAndBindingSet:
type: object
required: [recipientSelector, bindingSet]
properties:
recipientSelector:
$ref: '#/components/schemas/RecipientSelector'
bindingSet:
$ref: '#/components/schemas/BindingSet'
RecipientSelector:
type: object
description: Include a RecipientSelector with your message to ensure it only arrives at the specified Knowledge Base(s).
properties:
knowledgeBases:
type: array
minItems: 1
description: List of Knowledge Base IDs, specifying the Knowledge Bases that can receive the message. No other Knowledge Bases will receive t
items:
type: string
singleKnowledgeBase:
deprecated: true
description: >
Knowledge Base ID of the recipient. Deprecated: Please use the `knowledgeBases` property with a list of length 1 instead.
type: string
ResponseMessage:
type: object
properties:
messageType:
type: string
message:
type: string
KnowledgeInteractionBase:
type: object
required: [knowledgeInteractionType]
discriminator:
propertyName: knowledgeInteractionType
mapping:
AskKnowledgeInteraction: '#/components/schemas/AskKnowledgeInteraction'
AnswerKnowledgeInteraction: '#/components/schemas/AnswerKnowledgeInteraction'
PostKnowledgeInteraction: '#/components/schemas/PostKnowledgeInteraction'
ReactKnowledgeInteraction: '#/components/schemas/ReactKnowledgeInteraction'
properties:
knowledgeInteractionType:
type: string
knowledgeInteractionName:
type: string
pattern: '^[a-zA-Z0-9-]*$'
communicativeAct:
$ref: '#/components/schemas/CommunicativeAct'
prefixes:
$ref: '#/components/schemas/Prefixes'
KnowledgeInteractionId:
type: object
properties:
knowledgeInteractionId:
type: string
KnowledgeInteractionWithId:
allOf:
- anyOf:
- $ref: '#/components/schemas/AskKnowledgeInteraction'
- $ref: '#/components/schemas/AnswerKnowledgeInteraction'
- $ref: '#/components/schemas/PostKnowledgeInteraction'
- $ref: '#/components/schemas/ReactKnowledgeInteraction'
- type: object
properties:
knowledgeInteractionId:
type: string
AskKnowledgeInteraction:
required: [graphPattern]
allOf:
- $ref: '#/components/schemas/KnowledgeInteractionBase'
- type: object
properties:
graphPattern:
type: string
AnswerKnowledgeInteraction:
required: [graphPattern]
allOf:
- $ref: '#/components/schemas/KnowledgeInteractionBase'
- type: object
properties:
graphPattern:
type: string
PostKnowledgeInteraction:
required: [argumentGraphPattern]
allOf:
- $ref: '#/components/schemas/KnowledgeInteractionBase'
- type: object
properties:
argumentGraphPattern:
type: string
resultGraphPattern:
type: string
ReactKnowledgeInteraction:
required: [argumentGraphPattern]
allOf:
- $ref: '#/components/schemas/KnowledgeInteractionBase'
- type: object
properties:
argumentGraphPattern:
type: string
resultGraphPattern:
type: string
CommunicativeAct:
type: object
required: [requiredPurposes, satisfiedPurposes]
properties:
requiredPurposes:
type: array
items:
type: string
satisfiedPurposes:
type: array
items:
type: string
AskResult:
type: object
required: [bindingSet, exchangeInfo]
properties:
bindingSet:
$ref: '#/components/schemas/BindingSet'
exchangeInfo:
type: array
items:
$ref: '#/components/schemas/AskExchangeInfo'
PostResult:
type: object
required: [resultBindingSet, exchangeInfo]
properties:
resultBindingSet:
$ref: '#/components/schemas/BindingSet'
exchangeInfo:
type: array
items:
$ref: '#/components/schemas/PostExchangeInfo'
ExchangeInfo:
type: object
required: [initiator, knowledgeBaseId, knowledgeInteractionId, exchangeStart, exchangeEnd, status]
properties:
initiator:
type: string
enum:
- knowledgeBase
- reasoner
knowledgeBaseId:
type: string
knowledgeInteractionId:
type: string
exchangeStart:
type: string
format: date-time
exchangeEnd:
type: string
format: date-time
status:
type: string
failedMessage:
type: string
AskExchangeInfo:
allOf:
- $ref: '#/components/schemas/ExchangeInfo'
- type: object
properties:
bindingSet:
$ref: '#/components/schemas/BindingSet'
PostExchangeInfo:
allOf:
- $ref: '#/components/schemas/ExchangeInfo'
- type: object
properties:
argumentBindingSet:
$ref: '#/components/schemas/BindingSet'
resultBindingSet:
$ref: '#/components/schemas/BindingSet'
HandleRequest:
type: object
properties:
knowledgeInteractionId:
type: string
handleRequestId:
type: integer
bindingSet:
$ref: '#/components/schemas/BindingSet'
requestingKnowledgeBaseId:
type: string
HandleResponse:
type: object
required: [handleRequestId, bindingSet]
properties:
handleRequestId:
type: integer
bindingSet:
$ref: '#/components/schemas/BindingSet'
SmartConnectorLease:
type: object
properties:
knowledgeBaseId:
type: string
expires:
type: string
format: date-time
Prefixes:
type: object
additionalProperties:
type: string
pattern: url
description:
If you include a Prefixes object when registering a knowledge interaction,
you are allowed to use those prefixes in the graph pattern(s) that the
knowledge interaction contains. Keep in mind that the prefixes can only
be used in your graph pattern during registration, and not within bindings.
VersionInfo:
type: object
properties:
version:
type: string