Changes between Version 3 and Version 4 of Taskforces/FCS/FCS-Specification-Draft

Timestamp:

10/20/15 08:44:20 (9 years ago)

Author:

Oliver Schonefeld

Comment:

--

Taskforces/FCS/FCS-Specification-Draft

@@ -165 +165 @@
 
 = CLARIN-FCS Interface Specification
+The CLARIN-FCS Interface Specification defines a set of capabilities, an extensible result format and a set of required operations. CLARIN-FCS is built on the SRU/CQL standard and additional functionality required for CLARIN-FCS is added through SRU/CQL's extension mechanisms.
+
+Specifically, the CLARIN-FCS Interface Specification consists of two major parts, a set of formats, and a transport protocol. The ''Endpoint'' component is a software component that acts as a bridge between a ''Client'' and a ''Search Engine'' and passes the requests sent by the ''Client'' to the ''Search Engine''. The ''Search Engine'' is a custom software component that allows the search of language resources in a Repository. The ''Endpoint'' implements the ''Transport Protocol'' and acts as a mediator between the CLARIN-FCS specific formats and the idiosyncrasies of ''Search Engines'' of the individual Repositories. The following figure illustrates the overall architecture:
+{{{
+                   +---------+
+                   |  Client |
+                   +---------+
+                       /|\
+                        |
+                        | SRU / CQL
+                        | w/CLARIN-FCS extensions
+                        |
+                       \|/
+ +----------------------------------------------+
+ |           |      Endpoint       /|\          |
+ |           |                      |           |
+ |  -------------------    -------------------  |
+ | | translate request |  | translate result  | |
+ |  -------------------    -------------------  |
+ |           |                      |           |
+ |          \|/                     |           |
+ +----------------------------------------------+
+                       /|\
+                        |
+                        | Search Engine specific protocols/formats
+                        |
+                       \|/
+          +---------------------------+
+          |       Search Engine       |
+          +---------------------------+
+}}}
+In general, the work flow in CLARIN-FCS is as follows: a Client submits a query to an Endpoint. The Endpoint translates the query from CQL or FCS-QL to the query dialect used by the Search Engine and submits the translated query to the Search Engine. The Search Engine processes the query and generates a result set, i.e. it compiles a set of hits that match the search criterion. The Endpoint then translates the results from the Search Engine-specific result set format to the CLARIN-FCS result format and sends them to the Client.
+
 == "Discovery Phase"
 === Capabilities