Separate (brief) section on connectors.

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

diff --git a/doc/book.xml b/doc/book.xml
index 9d98b7b..55fb83c 100644 (file)
--- a/doc/book.xml
+++ b/doc/book.xml
@@ -24,6 +24,9 @@
   <author>
    <firstname>Jakub</firstname><surname>Skoczen</surname>
   </author>
+  <author>
+   <firstname>Mike</firstname><surname>Taylor</surname>
+  </author>
   <releaseinfo>&version;</releaseinfo>
   <copyright>
    <year>&copyright-year;</year>
@@ -56,6 +59,9 @@
  
  <chapter id="introduction">
   <title>Introduction</title>
+
+  <section id="what.pazpar2.is">
+  <title>What Pazpar2 is</title>
   <para>
    Pazpar2 is a stand-alone metasearch engine with a web-service API, designed
    to be used either from a browser-based client (JavaScript, Flash,
@@ -81,7 +87,7 @@
    user management and attractive displays are expected to be implemented by
    applications that use Pazpar2. Pazpar2 itself is user-interface independent.
    Its functionality is exposed through a simple XML-based web-service API,
-   designed to be easy to use from an AJAX-enabled browser, Flash
+   designed to be easy to use from an Ajax-enabled browser, Flash
    animation, Java applet, etc., or from a higher-level server-side language
    like PHP, Perl or Java. Because session information can be shared between
    browser-based logic and server-side scripting, there is tremendous
@@ -121,15 +127,6 @@
    usability and let Pazpar2 do what it does best -- metasearch.
   </para>
   <para>
-   If you wish to connect to commercial or other databases which do not
-   support open standards, please contact Index Data on
-   <email>info@indexdata.com</email>. We have a
-   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.
-  </para>
-  <para>
    Pazpar2 is our attempt to re-think the traditional paradigms for
    implementing and deploying metasearch logic, with an uncompromising
    approach to performance, and attempting to make maximum use of the
@@ -151,6 +148,20 @@
    Pazpar2 is covered by the GNU General Public License (GPL) version 2.
    See <xref linkend="license"/> for further information.
   </para>
+  </section>
+
+  <section id="connectors">
+  <title>Connectors to non-standard databases</title>
+  <para>
+   If you wish to connect to commercial or other databases which do not
+   support open standards, please contact Index Data on
+   <email>info@indexdata.com</email>. We have a
+   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.
+  </para>
+  </section>
 
   <section id="name">
    <title>A note on the name Pazpar2</title>
@@ -444,11 +455,11 @@
     possible to combine Pazpar2 either with your server-side dynamic
     website scripting, with scripting or code running in the browser, or
     with any combination of the two. Pazpar2 is an excellent tool for
-    building advanced, AJAX-based user interfaces for metasearch
+    building advanced, Ajax-based user interfaces for metasearch
     functionality, but it isn't a requirement -- you can choose to use
     Pazpar2 entirely as a backend to your regular server-side scripting.
     When you do use Pazpar2 in conjunction
-    with browser scripting (JavaScript/AJAX, Flash, applets,
+    with browser scripting (JavaScript/Ajax, Flash, applets,
     etc.), there are   special considerations.
    </para>
 
@@ -573,7 +584,7 @@
    <para>
     You can use Pazpar2 from any environment that allows you to use
     webservices. The initial goal of the software was to support
-    AJAX-based applications, but there literally are no limits to what
+    Ajax-based applications, but there literally are no limits to what
     you can do. You can use Pazpar2 from Javascript, Flash, Java, etc.,
     on the browser side, and from any development environment on the
     server side, and you can pass session tokens and record IDs freely