wiki-archive/twiki/data/TAPIR/CapabilitiesResponseProposa...

68 lines
2.2 KiB
Plaintext
Raw Normal View History

---+ Capabilities Response, Proposal I
---+++++ General Idea
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.
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
---+++++ Example
<verbatim>
<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>
with* indicating repeatable elements
</verbatim>