Changes between Version 84 and Version 85 of Taskforces/FCS/FCS-Specification-Draft

Timestamp:

05/24/22 12:46:26 (2 years ago)

Author:

Erik Körner

Comment:

Fix heading and internal links

Taskforces/FCS/FCS-Specification-Draft

@@ -710 +710 @@
 A Client `MUST` ignore any custom extensions it does not understand and skip over these XML fragments when parsing the Endpoint's response.
 
-The non-normative appendix contains an [#extensionExample example], how an extension could be implemented.
+The non-normative appendix contains an [#Endpointcustomextensions example], how an extension could be implemented.
 
 # CLARIN-FCS to SRU/CQL binding #
@@ -1143 +1143 @@
 For SRU 2.0 the request parameter `queryType` `MUST` be used unless the query language is CQL which is the default. For using FCS-QL the value `MUST` be ''fcs''.
  
-## List of diagnostics
+## List of diagnostics ##
 {{{#!comment
 For FCS 2.0 we keep the column Impact, i.e. if diagnostic is fatal or non-fatal.
@@ -1158 +1158 @@
 || `http://clarin.eu/fcs/diagnostic/14` || General processing hint. || E.g. "No matches, because layer 'XY' is not available in your selection of resources" || non-fatal || Endpoints `MUST` use this diagnostic only if the Client performed an Advanced Search request. ||
 
-## CLARIN FCS-QL Grammar Specification ## #fcsQLEBNF
+## CLARIN FCS-QL Grammar Specification ##
 The version of the CLARIN FCS-QL is tied to the FCS Core version starting with version 2.0.
 
@@ -1322 +1322 @@
 }}}
 
-## Endpoint custom extensions #extensionExample
+## Endpoint custom extensions ##
 The CLARIN-FCS protocol specification allows Endpoints to add custom data to their responses, e.g. to provide hints to an (XSLT/XQuery) application that works directly on CLARIN-FCS. It could use the custom data to generate back and forward links for a GUI to navigate in a result set.