X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Fserver.xml;h=af98f12d7eb5b4ccb2a8b5d7ec61be6c0cec4e67;hb=4478d785b7769691261005c98063b98a5a5971b3;hp=411319684a579d02e2d8751785347da4eea7eca7;hpb=a4d2f62568bcf788630502fc1cbcad1163d3f87a;p=idzebra-moved-to-github.git diff --git a/doc/server.xml b/doc/server.xml index 4113196..af98f12 100644 --- a/doc/server.xml +++ b/doc/server.xml @@ -1,5 +1,5 @@ - + The Z39.50 Server @@ -309,17 +309,7 @@ The records in the explain database are of type - grs.sgml and can be retrieved as - SUTRS, XML, - GRS-1 and ASN.1 Explain. - - - Classic Explain only defines retrieaval of Explain information - via ASN.1. Pratically no Z39.50 clients supports this. Fortunately - they don't have to - since Zebra allows retrieval of this information - in the other formats. - - + grs.sgml. The root element for the Explain grs.sgml records is explain, thus explain.abs is used for indexing. @@ -512,16 +502,16 @@ Scan - Zebra does not support SRU's + Zebra supports SRU's scan operation, as described at - + . + Scanning using CQL syntax is the default, where the + standard scanClause parameter is used. - This is a rather embarrassing surprise as the pieces are all - there: Z39.50 scan is supported, and SRU scan requests are - recognised and diagnosed. To add further to the embarrassment, a - mutant form of SRU scan is supported, using + In addition, a + mutant form of SRU scan is supported, using the non-standard x-pScanClause parameter in place of the standard scanClause to scan on a PQF query clause.