Changes between Version 13 and Version 14 of Taskforces/FCS/FCS-Specification-Draft

Timestamp:

10/23/15 09:15:23 (9 years ago)

Author:

Oliver Schonefeld

Comment:

--

Taskforces/FCS/FCS-Specification-Draft

@@ -383 +383 @@
 }}}
 
-=== "Versioning and Extensions"
-==== "Backwards compatibility statements"
-{{{
-#!div style="border: 1px solid #000000; font-size: 75%"
-Say something about backwards compatibility with "basic-search". \\
-Clients should also be compatible with FCS 1.0 (= SRU 1.2) and use heuristic to determine, if an endpoint is still using FCS 1.0.
-}}}
+=== Versioning and Extensions
+==== Backwards Compatibility
+{{{
+#!div style="border: 1px solid #000000; font-size: 75%"
+TODO: check and proof-read
+}}}
+Endpoints `SHOULD` also be compatible to CLARIN-FCS 1.0, thus support the SRU 1.2 protocol.
+
+Clients `MUST` be compatible to CLARIN-FCS 1.0, thus must implement SRU 1.2. If a Client uses CLARIN-FCS 1.0 to talk to an Endpoint, it `MUST NOT` use features beyond the Basic Search capability. Clients `MUST` implement a heuristic to automatically determine which CLARIN-FCS protocol version, i.e. which version of the SRU protocol, can be used talk an Endpoint.
+
+Pseudo algorithm for version detection heuristic:
+ * Send ''explain'' request without `version` and `operation` parameter
+ * Check SRU response for content of the element `<sru:explainResponse>/<sru:version>`
+
 ==== Endpoint Custom Extensions
 Endpoints can add custom extensions, i.e. custom data, to the Result Format. This extension mechanism can for example be used to provide hints for an (XSLT/XQuery) application that works directly on CLARIN-FCS, e.g. to allow it to generate back and forward links to navigate in a result set.