Changes between Version 16 and Version 17 of Taskforces/FCS/FCS-Specification-Draft


Ignore:
Timestamp:
10/26/15 10:01:13 (9 years ago)
Author:
Oliver Schonefeld
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Taskforces/FCS/FCS-Specification-Draft

    v16 v17  
    165165
    166166The following XML namespace names and prefixes are used throughout this specification. The column "Recommended Syntax" indicates which syntax variant `SHOULD` be used by the Endpoint to serialize the XML response.
    167 ||=Prefix =||=Namespace Name                                 =||=Comment                          =||=Recommended Syntax =||
    168 || `fcs`   || `http://clarin.eu/fcs/resource`                 || CLARIN-FCS Resources              || prefixed ||
    169 || `ed`    || `http://clarin.eu/fcs/endpoint-description`     || CLARIN-FCS Endpoint Description   || prefixed ||
    170 || `hits`  || `http://clarin.eu/fcs/dataview/hits`            || CLARIN-FCS Generic Hits Data View || prefixed ||
    171 || `adv`   || `http://clarin.eu/fcs/dataview/advanced`        || CLARIN-FCS Advanced Data View     || prefixed ||
    172 || `sru`   || `http://www.loc.gov/zing/srw/`                  || SRU                               || prefixed ||
    173 || `diag`  || `http://www.loc.gov/zing/srw/diagnostic/`       || SRU Diagnostics                   || prefixed ||
    174 || `zr`    || `http://explain.z3950.org/dtd/2.0/`             || SRU/ZeeRex Explain                || prefixed ||
    175 {{{
    176 #!div style="border: 1px solid #000000; font-size: 75%"
    177 Careful with the SRU Namespaces; they probably need to be adjusted SRU 2.0 (=> OASIS).
     167||=Prefix =||=Namespace Name                                       =||=Comment                          =||=Recommended Syntax =||
     168|| `fcs`   || `http://clarin.eu/fcs/resource`                       || CLARIN-FCS Resources              || prefixed ||
     169|| `ed`    || `http://clarin.eu/fcs/endpoint-description`           || CLARIN-FCS Endpoint Description   || prefixed ||
     170|| `hits`  || `http://clarin.eu/fcs/dataview/hits`                  || CLARIN-FCS Generic Hits Data View || prefixed ||
     171|| `adv`   || `http://clarin.eu/fcs/dataview/advanced`              || CLARIN-FCS Advanced Data View     || prefixed ||
     172|| `sru`   || `http://docs.oasis-open.org/ns/search-ws/sruResponse` || SRU                               || prefixed ||
     173|| `diag`  || `http://docs.oasis-open.org/ns/search-ws/diagnostic`  || SRU Diagnostics                   || prefixed ||
     174|| `zr`    || `http://explain.z3950.org/dtd/2.0/`                   || SRU/ZeeRex Explain                || prefixed ||
     175{{{
     176#!div style="border: 1px solid #000000; font-size: 75%"
     177What to do about SRU 1.2 backwards compatibility; they used to have XML namespaces from LOC.
    178178}}}
    179179
     
    394394
    395395=== Versioning and Extensions
    396 ==== Backwards Compatibility
     396==== Backwards Compatibility #backwardsCompatibility
    397397{{{
    398398#!div style="border: 1px solid #000000; font-size: 75%"
     
    402402
    403403Clients `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.
     404
     405When using SRU 1.2 Endpoints `SHOULD` use the following legacy XML namespace names (namespace URIs) for serializing responses:
     406 * `http://www.loc.gov/zing/srw/` for SRU response documents, and
     407 * `http://www.loc.gov/zing/srw/diagnostic/` for diagnostics within SRU response documents.
     408Clients `MUST` be able to process the legacy XML namespaces as well as the OASIS XML namespaces. CLARIN-FCS deviates from the OASIS specification [#REF_SRU_Overview OASIS-SRU-Overview] and [#REF_SRU_12 OASIS-SRU-12] to ensure backwards comparability with SRU 1.2 services as they were defined by the [#REF_LOC_SRU_12 LOC-SRU12].
    404409
    405410Pseudo algorithm for version detection heuristic:
     
    435440Endpoints `SHOULD` implement APD Binding for SRU 1.2, as defined in [#REF_SRU_12 OASIS-SRU-12]. \\
    436441Endpoints and Clients `MAY` also implement APD binding for version 1.1.
    437 
    438 {{{
    439 #!div style="border: 1px solid #000000; font-size: 75%"
    440 TODO: think about XML namespaces
    441 }}}
    442 Endpoints and Clients `MUST` use the following XML namespace names (namespace URIs) for serializing responses:
    443  * `http://www.loc.gov/zing/srw/` for SRU response documents, and
    444  * `http://www.loc.gov/zing/srw/diagnostic/` for diagnostics within SRU response documents.
    445 CLARIN-FCS deviates from the OASIS specification [#REF_SRU_Overview OASIS-SRU-Overview] and [#REF_SRU_12 OASIS-SRU-12] to ensure backwards comparability with SRU 1.2 services as they were defined by the [#REF_LOC_SRU_12 LOC-SRU12].
     442'''NOTE:''': when implementing SRU 1.2 Endpoints and Clients `MUST` behave like described in the section [#backwardsCompatibility Backwards Compatibility].
    446443
    447444Endpoints or Clients `MUST` support CQL conformance ''Level 2'' (as defined in [#REF_OASIS_CQL OASIS-CQL, section 6]), i.e. be able to ''parse'' (Endpoints) or ''serialize'' (Clients) all of CQL and respond with appropriate error messages to the search/retrieve protocol interface.