added a lot of info about attribute sets, PQF query structure, and string use attributes

[idzebra-moved-to-github.git] / doc / zebrasrv-virtual.xml

diff --git a/doc/zebrasrv-virtual.xml b/doc/zebrasrv-virtual.xml
index 2ed8c92..248ab14 100644 (file)
--- a/doc/zebrasrv-virtual.xml
+++ b/doc/zebrasrv-virtual.xml
@@ -1,5 +1,5 @@
 <!-- 
 <!-- 

-   $Id: zebrasrv-virtual.xml,v 1.6 2006-04-25 12:26:27 marc Exp $
+   $Id: zebrasrv-virtual.xml,v 1.7 2006-06-13 13:45:08 marc Exp $

    Description of the virtual host mechanism in YAZ GFS
    Included in both manual and man page for yaz-ztest
 -->
    Description of the virtual host mechanism in YAZ GFS
    Included in both manual and man page for yaz-ztest
 -->

@@ -11,9 +11,9 @@
 </para>
 <para>
  A backend can be configured to execute in a particular working
 </para>
 <para>
  A backend can be configured to execute in a particular working

- directory. Or the YAZ frontend may perform <ulink url="http://www.loc.gov/standards/sru/cql/">CQL</ulink> to RPN conversion, thus
- allowing traditional Z39.50 backends to be offered as a  <ulink url="http://www.loc.gov/standards/sru/srw/">SRW</ulink>/ <ulink url="http://www.loc.gov/standards/sru/">SRU</ulink>
- service.  <ulink url="http://www.loc.gov/standards/sru/srw/">SRW</ulink>/ <ulink url="http://www.loc.gov/standards/sru/">SRU</ulink> Explain information for a particular backend may also
+ directory. Or the YAZ frontend may perform <ulink url="&url.cql;">CQL</ulink> to RPN conversion, thus
+ allowing traditional Z39.50 backends to be offered as a  <ulink url="http://www.loc.gov/standards/sru/srw/">SRW</ulink>/ <ulink url="&url.sru;">SRU</ulink>
+ service.  <ulink url="http://www.loc.gov/standards/sru/srw/">SRW</ulink>/ <ulink url="&url.sru;">SRU</ulink> Explain information for a particular backend may also

  be specified.
 </para>
 <para>
  be specified.
 </para>
 <para>

@@ -128,8 +128,8 @@
   <varlistentry><term>element <literal>cql2rpn</literal> (optional)</term>
    <listitem>
     <para>
   <varlistentry><term>element <literal>cql2rpn</literal> (optional)</term>
    <listitem>
     <para>

-     Specifies a filename that includes <ulink url="http://www.loc.gov/standards/sru/cql/">CQL</ulink> to RPN conversion for this
-     backend server. See <ulink url="http://www.loc.gov/standards/sru/cql/">CQL</ulink> section in YAZ manual.
+     Specifies a filename that includes <ulink url="&url.cql;">CQL</ulink> to RPN conversion for this
+     backend server. See <ulink url="&url.cql;">CQL</ulink> section in YAZ manual.

      If given, the backend server will only "see" a Type-1/RPN query. 
     </para>
    </listitem>
      If given, the backend server will only "see" a Type-1/RPN query. 
     </para>
    </listitem>

@@ -138,7 +138,7 @@
   <varlistentry><term>element <literal>explain</literal> (optional)</term>
    <listitem>
     <para>
   <varlistentry><term>element <literal>explain</literal> (optional)</term>
    <listitem>
     <para>

-     Specifies  <ulink url="http://www.loc.gov/standards/sru/srw/">SRW</ulink>/ <ulink url="http://www.loc.gov/standards/sru/">SRU</ulink> ZeeRex content for this server. Copied verbatim
+     Specifies  <ulink url="http://www.loc.gov/standards/sru/srw/">SRW</ulink>/ <ulink url="&url.sru;">SRU</ulink> ZeeRex content for this server. Copied verbatim

      to the client. As things are now, some of the Explain content
      seems redundant because host information, etc. is also stored
      elsewhere.
      to the client. As things are now, some of the Explain content
      seems redundant because host information, etc. is also stored
      elsewhere.

@@ -199,7 +199,8 @@
  elements.
 </para>
 <para>
  elements.
 </para>
 <para>

- For <literal>"server2"</literal> elements for <ulink url="http://www.loc.gov/standards/sru/cql/">CQL</ulink> to RPN conversion
+ For <literal>"server2"</literal> elements for 
+<ulink url="&url.cql;">CQL</ulink> to RPN conversion

  is supported and explain information has been added (a short one here
  to keep the example small).
 </para>
  is supported and explain information has been added (a short one here
  to keep the example small).
 </para>