Changes between Version 65 and Version 66 of Taskforces/FCS/FCS-Specification-Draft
- Timestamp:
- 06/13/17 14:22:56 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Taskforces/FCS/FCS-Specification-Draft
v65 v66 930 930 931 931 == Operation ''searchRetrieve'' #searchRetrieve 932 {{{ 933 #!div style="border: 1px solid #000000; font-size: 75%" 934 Align with newly introduced section "Search Phase" \\ 935 Define String for SRU query-lanaguge paramater ("fcs") 936 }}} 937 The ''searchRetrieve'' operation of the SRU protocol is used for searching in the Resources that are provided by the Endpoint. The SRU protocol defines the serialization of request and response formats in [#REF_SRU_20 OASIS-SRU-20] for SRU version 2.0 and [#REF_SRU_12 OASIS-SRU-12] for SRU version 1.2. An Endpoint `MUST` respond in the correct format, i.e. when Endpoint also supports SRU 1.2 and the request is issued in SRU version 1.2, the response must be encoded accordingly. 932 The ''searchRetrieve'' operation of the SRU protocol is used for searching in the Resources that are provided by the Endpoint. The SRU protocol defines the serialization of request and response formats in [#REF_SRU_20 OASIS-SRU-20] for SRU version 2.0 and [#REF_SRU_12 OASIS-SRU-12] for SRU version 1.2. An Endpoint `MUST` respond in the correct format, i.e. when Endpoint also supports SRU 1.2 and the request is issued in SRU version 1.2, the response must be encoded accordingly. For SRU 2.0 we introduce the ''queryType'' parameter to tell which query language to use. For Contextual Query Language the value is ''cql'' and for FCS-QL the value is ''fcs''. 938 933 939 934 In SRU, search result hits are encoded down to a record level, i.e. the `<sru:record>` element, and SRU allows records to be serialized in various formats, so called ''record schemas'' Endpoints `MUST` support the CLARIN-FCS record schema (see section [#resultFormat Result Format]) and `MUST` use the value `http://clarin.eu/fcs/resource` for the ''responseItemType'' ("record schema identifier"). … … 989 984 }}} 990 985 991 Moving to a SRU 2.0. We introduce the `queryType` parameter. The same querywould then become:986 Moving to SRU 2.0 have the introduced `queryType` parameter. The same query as seen with SRU 1.2 above would then become: 992 987 * HTTP GET request: Client → Endpoint: 993 988 {{{#!sh … … 1034 1029 }}} 1035 1030 1036 And for ''queryType'' with value ''fcs'' using FCS-QLwe get a request and response to the ''searchRetrieve'' request with queryType ''fcs'' and query ''[word = "användning"]'':1031 Using FCS-QL using ''queryType'' with value ''fcs'' we get a request and response to the ''searchRetrieve'' request with queryType ''fcs'' and query ''[word = "användning"]'': 1037 1032 * HTTP GET request: Client → Endpoint: 1038 1033 {{{#!sh