-
Notifications
You must be signed in to change notification settings - Fork 2
/
CapabilitiesProposalOne.txt,v
295 lines (254 loc) · 5.72 KB
/
CapabilitiesProposalOne.txt,v
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
head 1.10;
access;
symbols;
locks; strict;
comment @# @;
1.10
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
branches;
next 1.9;
1.9
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
branches;
next 1.8;
1.8
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
branches;
next 1.7;
1.7
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
branches;
next 1.6;
1.6
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
branches;
next 1.5;
1.5
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
branches;
next 1.4;
1.4
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
branches;
next 1.3;
1.3
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
branches;
next 1.2;
1.2
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
branches;
next 1.1;
1.1
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
branches;
next ;
desc
@Initial revision
@
1.10
log
@Revision 10
@
text
@---+ Capabilities Proposal I
A first proposal for the CapabilitiesRequest.
---+++++ Request Example
<verbatim>
<request>
<header>
...
</header>
<capabilities CapabilitiesProposalOne>
</request>
</verbatim>
---+++++ Response Example
<verbatim>
<response>
<header>
...
</header>
<content>
<capabilities>
<configurations>
<minQueryTermLength>3</minQueryTermLength>
<maxSearchResponseRecords>100</maxSearchResponseRecords>
<maxInventoryResponseRecords>1000</maxInventoryResponseRecords>
</configurations>
<requestTypes>
<ping/>
<capabilities/>
<metadata/>
<inventory/>
<fullSearch/>
<partialSearch/>
<customSearch/>
</requestTypes>
<conceptualSchemas>
<schema namespace="http://www.altova.com"> *
<concept searchable="1" path="/abcd/efg/@@h"/> *
</schema>
</conceptualSchemas>
</capabilities>
</content>
</response>
with* indicating repeatable elements
</verbatim>
@
1.9
log
@Revision 9
@
text
@a28 3
<protocols>
<protocol schema="http://www.altova.com" CapabilitiesProposalOne> *
</protocols>
@
1.8
log
@Revision 8
@
text
@d3 2
@
1.7
log
@Revision 7
@
text
@d28 1
a28 1
<protocol schema="http://www.altova.com" name="String"/> *
a29 14
<filter>
<comparative>
<operator name="String" type="String"/> *
</comparative>
<logical>
<operator name="String" type="String"/> *
</logical>
<function>
<operator name="String" type="String"/> *
</function>
<spatial>
<operator name="String" type="String"/> *
</spatial>
</filter>
a38 3
<compression>
<method name="zip"/> *
</compression>
a43 1
<security>Text</security>
@
1.6
log
@Revision 6
@
text
@a2 24
---+++++ General Idea
We could add more information to this CapabilitiesRequest. Everything related to machine readable data describing the capabilities, abilities of a providers resource like the limit to the number of returned records. Also every concept should include a flag indicating whether it is searchable.
Information we would like to add to the capabilities:
* provider configuration parameters affecting the response:
* minQueryTermLength
* maxSearchResponseRecords
* maxInventoryResponseRecords
* type & version of the protocols supported by a software
* type of FilterOperators supported by a software
* logical
* comparative
* functions
* min, max
* len
* SpatialOperators
* type of operations or RequestMethods supported
* is ContentCompression supported ?
* ConceptualSchemas and their "mapped" concepts supported (see above)
* a slot for security related information
* access restriction
* encryption mechanisms
@
1.5
log
@Revision 5
@
text
@d68 9
a76 3
<operations>
<operation requesttype="String"/> *
</operations>
@
1.4
log
@Revision 4
@
text
@d40 43
a82 36
<capabilities>
<configurations>
<minQueryTermLength>3</minQueryTermLength>
<maxSearchResponseRecords>100</maxSearchResponseRecords>
<maxInventoryResponseRecords>1000</maxInventoryResponseRecords>
</configurations>
<protocols>
<protocol schema="http://www.altova.com" name="String"/> *
</protocols>
<filter>
<comparative>
<operator name="String" type="String"/> *
</comparative>
<logical>
<operator name="String" type="String"/> *
</logical>
<function>
<operator name="String" type="String"/> *
</function>
<spatial>
<operator name="String" type="String"/> *
</spatial>
</filter>
<operations>
<operation requesttype="String"/> *
</operations>
<compression>
<method name="zip"/> *
</compression>
<conceptualSchemas>
<schema namespace="http://www.altova.com"> *
<concept searchable="1" path="/abcd/efg/@@h"/> *
</schema>
</conceptualSchemas>
<security>Text</security>
</capabilities>
@
1.3
log
@Revision 3
@
text
@d5 1
a5 1
We could add more information to this capabilities request. Everything related to machine readable data describing the capabilities, abilities of a providers resource like the limit to the number of returned records. Also every concept should include a flag indicating whether it is searchable.
@
1.2
log
@Revision 2
@
text
@d1 1
a1 1
---+ Capabilities Response, Proposal I
@
1.1
log
@Initial revision
@
text
@d27 12
a38 1
---+++++ Example
@