Changes between Version 14 and Version 15 of QueryLanguage

Timestamp:

01/04/11 13:42:42 (13 years ago)

Author:

vronk

Comment:

update MD query

QueryLanguage

@@ -88 +88 @@
   * we could extend this and first try to interpret the term as a `cmdIndex` and only if such index does not exist, continue treat it as a term. 
   * But still we would have to decide if the term should be searched in (all) metadata indices or rather in the content.
+  * Currently MDService treats simple term queries as a simple full-text search in all (fields of all) MDRecords.
 
 == Metadata Query ==
-[wiki:CmdiMetadataServices#InterfaceDefinition MDService] will provide three main methods/operations:
-
- `getCollections()`::
-   provides information the hierarchical structure the md-records are grouped in.
- `queryModel()`::
-   provides information about the metadata (meta-model?), ie which components/elements/values are used in the repository. As query-parameter it only needs to accept/understand `cmdIndex`.
- `searchRetrieve()` ::
-   is the core operation to retrieve the actual MDRecords. In the `query`-parameter it has to accept any query on metadata. It probably shouldn't ignore even the content-part (`ccs.`) of the query, where it should check for the availability of indices used in the query in given collections.
+There was a longer development of the interface specification for MDRepository/MDService. See for more details under [wiki:CmdiMetadataServices#InterfaceDefinition MDService#Interface definition]. 
+
+And although at the moment MDService can’t claim conformance with SRU/CQL standard, the core parts conform to the specification: MDService accepts the query in CQL-format (even parsing it, ensuring the syntactic validity) and returns a `<searchRetrieveResponse>` result as defined by the protocol. 
+
+Following describes the specific usage of CQL for formulating MD-queries:
 
 === Types of `cmdIndex` ===