Merge branch 'master' of ssh://git.indexdata.com:222/home/git/pub/pazpar2

[pazpar2-moved-to-github.git] / doc / book.xml

diff --git a/doc/book.xml b/doc/book.xml
index ff1b58b..7c9c9d4 100644 (file)
--- a/doc/book.xml
+++ b/doc/book.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0" standalone="no"?>
 <?xml version="1.0" standalone="no"?>

-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1//EN"
-    "http://www.oasis-open.org/docbook/xml/4.1/docbookx.dtd" 
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+    "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" 

 [
      <!ENTITY % local SYSTEM "local.ent">
      %local;
 [
      <!ENTITY % local SYSTEM "local.ent">
      %local;

@@ -27,6 +27,9 @@
   <author>
    <firstname>Mike</firstname><surname>Taylor</surname>
   </author>
   <author>
    <firstname>Mike</firstname><surname>Taylor</surname>
   </author>

+  <author>
+   <firstname>Dennis</firstname><surname>Schafroth</surname>
+  </author>

   <releaseinfo>&version;</releaseinfo>
   <copyright>
    <year>&copyright-year;</year>
   <releaseinfo>&version;</releaseinfo>
   <copyright>
    <year>&copyright-year;</year>

@@ -76,8 +79,8 @@
    -- <ulink url="&url.xslt;">XSLT</ulink> is used to normalize and extract
    data from retrieval records for display and analysis. It can be used
    against any server which supports the 
    -- <ulink url="&url.xslt;">XSLT</ulink> is used to normalize and extract
    data from retrieval records for display and analysis. It can be used
    against any server which supports the 

-   <ulink url="&url.z39.50;">Z39.50</ulink> or <ulink url="&url.sru;">SRU/SRW</ulink>
-   protocol. Proprietary
+   <ulink url="&url.z39.50;">Z39.50</ulink>, <ulink url="&url.sru;">SRU/SRW</ulink> 
+   or <ulink url="&url.solr;">SOLR</ulink> protocol. Proprietary

    backend modules can function as connectors between these standard
    protocols and any non-standard API, including web-site scraping, to
    support a large number of other protocols.
    backend modules can function as connectors between these standard
    protocols and any non-standard API, including web-site scraping, to
    support a large number of other protocols.

@@ -159,7 +162,7 @@
    proprietary framework for building connectors that enable Pazpar2
    to access
    thousands of online databases, in addition to the vast number of catalogs
    proprietary framework for building connectors that enable Pazpar2
    to access
    thousands of online databases, in addition to the vast number of catalogs

-   and online services that support the Z39.50/SRU/SRW protocols.
+   and online services that support the Z39.50/SRU/SRW/SOLR protocols.

   </para>
   </section>
 
   </para>
   </section>
 

@@ -347,7 +350,7 @@
 
    <para>
     The test UIs are located in <literal>www</literal>. Ensure that this
 
    <para>
     The test UIs are located in <literal>www</literal>. Ensure that this

-    directory is available to the web server by copying 
+    directory is available to the web server by copying

     <literal>www</literal> to the document root, 
     using Apache's <literal>Alias</literal> directive, or
     creating a symbolic link: for example, on a Debian or Ubuntu
     <literal>www</literal> to the document root, 
     using Apache's <literal>Alias</literal> directive, or
     creating a symbolic link: for example, on a Debian or Ubuntu

@@ -644,8 +647,8 @@
    <title>Connecting to non-standard resources</title>
    <para>
     Pazpar2 uses Z39.50 as its switchboard language -- i.e. as far as it
    <title>Connecting to non-standard resources</title>
    <para>
     Pazpar2 uses Z39.50 as its switchboard language -- i.e. as far as it

-    is concerned, all resources speak Z39.50, or its webservices derivatives,
-    SRU/SRW. It is, however, equipped
+    is concerned, all resources speak Z39.50, its webservices derivatives,
+    SRU/SRW and SOLR servers exposing Lucene indexes. It is, however, equipped

     to handle a broad range of different server behavior, through
     configurable query mapping and record normalization. If you develop
     configuration, stylesheets, etc., for a new type of resources, we
     to handle a broad range of different server behavior, through
     configurable query mapping and record normalization. If you develop
     configuration, stylesheets, etc., for a new type of resources, we