Changes between Version 3 and Version 4 of FCS-Specification-Notes

Timestamp:

06/17/15 13:02:02 (9 years ago)

Author:

Leif-Jöran

Comment:

Added agreement on treatment of unquoted MWEs as implicitly quoted.

FCS-Specification-Notes

@@ -8 +8 @@
    * Should the behavior be controlled by the client, e.g. by sending a auxiliary parameter like {{{fcs-spans}}}?
    * Jörg: We should do as other search engines do: Use different highlighting colours for the the variables (in the example above: kind, taal) and highlight them (this gives discontinues hit markers)
- * CQL clarification for FCS: quoted strings shall be handles literally; unquoted strings are invalid
+ * CQL clarification for FCS: quoted strings shall be handles literally; unquoted strings are invalid. Note relation to MWE below.
 == Implementation ==
  * (brought up by Olha) XML-Schema design: always add Schema types, e.g. for EndpointDescription element. This allows easier use of toolks like JAX-B.
+ * Agreement on how to treat MWEs. After a poll with the technical contacts of the endpoints, there is an agreement that unquoted MWEs should be treated like being implicitly quoted. Thus the aggregator will be changed in one of the comming releases to not send unquoted MWEs to the endpoints as a first measure. This will be enforced in client libs for FCS version 2.
 
-== Discusion ==
+== Discussion ==
 
 None yet.