Index: /branches/PublicaMundi_David-devel/docs/_themes/sphinx_rtd_theme/breadcrumbs.html
===================================================================
--- /branches/PublicaMundi_David-devel/docs/_themes/sphinx_rtd_theme/breadcrumbs.html	(revision 695)
+++ /branches/PublicaMundi_David-devel/docs/_themes/sphinx_rtd_theme/breadcrumbs.html	(revision 696)
@@ -8,5 +8,5 @@
     <li>{{ title }}</li>
       <li class="wy-breadcrumbs-aside">
-       $date$
+       $Date$
       </li>
   </ul>
Index: /branches/PublicaMundi_David-devel/docs/_themes/sphinx_rtd_theme/layout.html
===================================================================
--- /branches/PublicaMundi_David-devel/docs/_themes/sphinx_rtd_theme/layout.html	(revision 695)
+++ /branches/PublicaMundi_David-devel/docs/_themes/sphinx_rtd_theme/layout.html	(revision 696)
@@ -107,5 +107,5 @@
       <div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="main navigation">
         {% block menu %}
-          {% set toctree = toctree(maxdepth=2, collapse=False, includehidden=True) %}
+          {% set toctree = toctree(maxdepth=2, collapse=False, includehidden=False) %}
           {% if toctree %}
               {{ toctree }}
Index: /branches/PublicaMundi_David-devel/docs/client/howto.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/client/howto.rst	(revision 695)
+++ /branches/PublicaMundi_David-devel/docs/client/howto.rst	(revision 696)
@@ -39,8 +39,11 @@
 
 Compiling ZOO-Client templates
----------------------------
+---------------------------===
 
-In order to work with ZOO-Client, you will first need to compile the provided `Mustache <http://mustache.github.io/>`_
-templates using `Node.js <http://nodejs.org/>`__. The ZOO-Client templates are located in the ``/zoo-project/zoo-client/lib/tpl`` directory downloaded from svn.
+In order to work with ZOO-Client, you will first need to compile the
+provided `Mustache <http://mustache.github.io/>`_ templates using
+`Node.js <http://nodejs.org/>`__. The ZOO-Client templates are located
+in the ``/zoo-project/zoo-client/lib/tpl`` directory downloaded from
+svn.
 
 * Install Node.js (see related `documentation <https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager>`__.)
@@ -64,5 +67,5 @@
 
 Building ZOO-Client documentation
---------------------------
+---------------------------------
 
 You may also build the ZOO-Client API documentation using `jsDoc
Index: anches/PublicaMundi_David-devel/docs/contents.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/contents.rst	(revision 695)
+++ 	(revision )
@@ -1,27 +1,0 @@
-.. _contents:
-
-ZOO-Project documentation 
-=============================
-
-This is the `ZOO-Project <http://zoo-project.org>`__ Open WPS Platform official documentation.
-
-.. toctree::
-   :maxdepth: 2
-
-   intro
-   install/index
-   kernel/index
-   services/index
-   api/index
-   client/index
-   contribute/index
-
-This document is released under the Creative Commons
-Attribution-ShareAlike 4.0 International Public License (`CC-BY-SA
-<https://creativecommons.org/licenses/by-sa/4.0/legalcode>`__).
-
-.. image:: _static/by-sa.png
-   :height: 141px
-   :width: 403px
-   :scale: 50 %
-   :alt: CC-BY-SA license
Index: /branches/PublicaMundi_David-devel/docs/contribute/code.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/contribute/code.rst	(revision 695)
+++ /branches/PublicaMundi_David-devel/docs/contribute/code.rst	(revision 696)
@@ -13,16 +13,18 @@
 
 Submit new code
---------------------------
+---------------
 
 For new comers
-*************************
+**************
 
 New source code or existing source code corrections (patches) should
-be submitted using the ZOO-Project bug tracking system (`ZOO-Trac <http://zoo-project.org/trac>`__ ).
+be submitted using the ZOO-Project bug tracking system (`ZOO-Trac
+<http://zoo-project.org/trac>`__ ).
 
-Create a new ticket in order to describe your code or patch and attach
-it to the ticket (attach all the needed files needed to use your code
-or patch). It will then be checked and discussed with the developers,
-and can potentially be integrated and merged with the trunk.
+Create a `new ticket <http://zoo-project.org/trac/newticket>`__ in
+order to describe your code or patch and attach it to the ticket
+(attach all the files required to use your code or patch). It will
+then be checked and discussed with the developers, and can potentially
+be integrated and merged with the trunk.
 
 For registered developers
Index: /branches/PublicaMundi_David-devel/docs/contribute/dev.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/contribute/dev.rst	(revision 695)
+++ /branches/PublicaMundi_David-devel/docs/contribute/dev.rst	(revision 696)
@@ -9,5 +9,5 @@
 -----------------------------
 
-Permission for SVN commit access shall be provided to new developers only if accepted by the ZOO-Project Project Steering Committee. A proposal should be written to the PSC for new committers and voted. 
+Permission for SVN commit access shall be provided to new developers only if accepted by the ZOO-Project Project Steering Committee. A proposal should be written to the PSC for new committers and voted.
 
 Removal of SVN commit access should be handled by the same process.
@@ -24,9 +24,10 @@
 ------------------
 
-A list of all project committers will be kept in the main zoo-project directory (called COMMITTERS) listing for each SVN committer:
+A list of all project committers will be kept in the main zoo-project directory (called `COMMITTERS <http://zoo-project.org/trac/browser/trunk/zoo-project/COMMITTERS>`__) listing for each SVN committer:
 
     * Userid: the id that will appear in the SVN logs for this person.
     * Full name: the users actual name.
     * Email address: A current email address at which the committer can be reached. It may be altered in normal ways to make it harder to auto-harvest.
+
 
 SVN Administrator
Index: /branches/PublicaMundi_David-devel/docs/contribute/doc.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/contribute/doc.rst	(revision 695)
+++ /branches/PublicaMundi_David-devel/docs/contribute/doc.rst	(revision 696)
@@ -28,6 +28,11 @@
 ........................................
 
-The current structure of the ZOO Project documentation process is for developers with :ref:`SVN <svn>` commit access to maintain their documents in reStructuredText format, and therefore all documents live in the /docs directory in SVN.  The `Sphinx <http://sphinx.pocoo.org/>`__ documentation generator is used to convert the reStructuredText files to html, and the live
-website is then updated on an hourly basis.
+The current structure of the ZOO Project documentation process is for
+developers with :ref:`SVN <svn>` commit access to maintain their
+documents in reStructuredText format, and therefore all documents live
+in the /docs directory in SVN.  The `Sphinx
+<http://sphinx.pocoo.org/>`__ documentation generator is used to
+convert the reStructuredText files to html, and the live website is
+then updated on an hourly basis.
 
 
@@ -49,9 +54,9 @@
    ::
 
-       sudo easy_install Sphinx
+       sudo easy_install Sphinx==1.3.1
        
    .. note::
     
-      Make sure you install Sphinx 1.0 or more recent.  See note above.  
+      Make sure you install Sphinx 1.3.1 or more recent. 
       
 * Checkout the /docs directory from SVN, such as:
@@ -88,9 +93,9 @@
    ::
 
-       sudo easy_install Sphinx
+       sudo easy_install-2.7 Sphinx==1.3.1
        
    .. note::
    
-      Make sure you install Sphinx 1.0 or more recent.  See note above.        
+      Make sure you install Sphinx 1.3.1 or more recent. 
 
 * Install `MacTex <http://www.tug.org/mactex/2009/>`__ if you want to build pdfs
@@ -127,5 +132,5 @@
    ::
 
-       easy_install Sphinx
+       easy_install Sphinx==1.3.1
 
    ...you should see message: "Finished processing dependencies for Sphinx"
@@ -133,5 +138,5 @@
    .. note::
    
-      Make sure you install Sphinx 1.0 or more recent.  See note above.
+      Make sure you install Sphinx 1.3.1 or more recent.  See note above.
       
 * Install `MiKTeX <http://miktex.org>`__ if you want to build pdfs
Index: /branches/PublicaMundi_David-devel/docs/contribute/howto.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/contribute/howto.rst	(revision 695)
+++ /branches/PublicaMundi_David-devel/docs/contribute/howto.rst	(revision 696)
@@ -1,4 +1,4 @@
 How to contribute ?
-==================
+===================
 
 Please consider the following simple rules if you would like to contribute to  the `ZOO-Project <http://zoo-project.org>`__  open source software.
@@ -37,7 +37,7 @@
 ..   csv-table::
      
-  Name,Description,Address
-    zoo-discuss,General mailing list for ZOO-Project users and developers,zoo-discuss@lists.osgeo.org
-    zoo-psc,Project Steering Committe mailing list,zoo-psc@lists.osgeo.org
+  Name,Description
+    `zoo-discuss <http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss>`__,General mailing list for ZOO-Project users and developers
+    `zoo-psc <http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-psc>`__,Project Steering Committe mailing list
     
 
Index: /branches/PublicaMundi_David-devel/docs/contribute/translate.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/contribute/translate.rst	(revision 695)
+++ /branches/PublicaMundi_David-devel/docs/contribute/translate.rst	(revision 696)
@@ -23,5 +23,5 @@
           for i in Title Abstract; 
            do
-            grep $i $j | sed "s:$i = :_(\":g;s:$:\"):g" ;
+            grep $i $j | sed "s:$i = :_ss(\":g;s:$:\"):g" ;
            done;
        done > locale/.cache/my_service_string_to_translate.c
@@ -33,5 +33,5 @@
   
       #!/bin/bash
-      xgettext service.c locale/.cache/my_service_string_to_translate.c -o message.po -p locale/po/ -k_
+      xgettext service.c locale/.cache/my_service_string_to_translate.c -o message.po -p locale/po/ -k_ss
 
 Once 'messages.po' is created, use the following command to create the po file for the targeted language for translation. We will use the French language here as an example :
@@ -45,7 +45,7 @@
 Edit the zoo_fr_FR.po file with your favorite text editor or using one of the following tools :
 
- * [http://www.poedit.net/ poedit]
- * [http://translate.sourceforge.net/wiki/virtaal/index virtaal]
- * [https://www.transifex.net/projects/p/grass6/c/grass64/ transifex]
+ * `poedit <http://www.poedit.net/>`__
+ * `virtaal <http://translate.sourceforge.net/wiki/virtaal/index>`__
+ * `transifex <https://www.transifex.net/>`__
  
 Once the zoo_fr_FR.po file is completed, you can generate and install the corresponding *mo* file using the following command : 
@@ -61,9 +61,9 @@
 example, such a request:
 
-[http://youserver/cgi-bin/zoo_loader.cgi?request=GetCapabilities&service=WPS]
+http://youserver/cgi-bin/zoo_loader.cgi?request=GetCapabilities&service=WPS
 
 would become the following:
 
-[http://youserver/cgi-bin/zoo_loader.cgi?request=GetCapabilities&service=WPS&language=fr-FR]
+http://youserver/cgi-bin/zoo_loader.cgi?request=GetCapabilities&service=WPS&language=fr-FR
 
 The following command may also be useful in order to pull all the translations already available for a specific language.
Index: /branches/PublicaMundi_David-devel/docs/index.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/index.rst	(revision 696)
+++ /branches/PublicaMundi_David-devel/docs/index.rst	(revision 696)
@@ -0,0 +1,26 @@
+.. _contents:
+
+ZOO-Project documentation 
+=============================
+
+This is the `ZOO-Project <http://zoo-project.org>`__ Open WPS Platform official documentation.
+
+.. toctree::
+   :maxdepth: 2
+
+   intro
+   install/index
+   kernel/index
+   services/index
+   api/index
+   client/index
+   contribute/index
+
+This document is released under the Creative Commons
+Attribution-ShareAlike 4.0 International Public License (`CC-BY-SA
+<https://creativecommons.org/licenses/by-sa/4.0/legalcode>`__).
+
+.. image:: _static/by-sa.png
+   :width: 103px
+   :scale: 50 %
+   :alt: CC-BY-SA license
Index: /branches/PublicaMundi_David-devel/docs/install/centos.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/install/centos.rst	(revision 696)
+++ /branches/PublicaMundi_David-devel/docs/install/centos.rst	(revision 696)
@@ -0,0 +1,110 @@
+.. _install-centos:
+
+Installation on CentOS
+======================
+
+Use the following instructions to install `ZOO-Project <http://zoo-project.org>`__ on CentOS distributions. 
+
+Prerequisites
+----------------------
+
+.. code-block:: guess
+
+  yum install apache2
+  yum install build-essentials
+  yum install gcc-c++
+  yum install zlib-devel
+  yum install libxml2-devel
+  yum install bison
+  yum install openssl 
+  yum install python-devel
+  yum install subversion
+
+
+Installation
+----------------------
+
+Compile then install FastCGI library from source
+
+::
+
+  wget http://www.fastcgi.com/dist/fcgi.tar.gz
+  tar xzf fcgi-2.4.0.tar.gz 
+  ./configure
+  make
+  make install
+  echo /usr/local/lib >> /etc/ld.so.conf.d/local.conf
+  ldconfig
+
+Compile then install the autoconf tools :
+
+::
+
+  wget http://ftp.gnu.org/gnu/autoconf/autoconf-latest.tar.gz
+  tar xzf autoconf-latest.tar.gz
+  ./configure --prefix=/usr
+  make 
+  make install
+
+Compile then install the flex tool :
+
+::
+
+  wget http://downloads.sourceforge.net/project/flex/flex/flex-2.5.35/flex-2.5.35.tar.gz?r=http%3A%2F%2Fflex.sourceforge.net%2F&ts=1292529005&use_mirror=switch
+  tar xzf flex-2.5.35.tar.gz
+  cd flex-2.5.35
+  ./configure --prefix=/usr
+  make
+  make install
+
+Using the curl provided in the CentOS distribution will produce a ZOO-Kernel unable to run any 
+Service. Indeed, some segmentation faults occur when trying to run ``Execute`` requests on the ZOO-Kernel, 
+compiling the ZOO-Kernel setting ``USE_GDB`` flag in the ``CFLAGS`` of your ``Makefile`` will let you run 
+ZOO-Kernel from gdb and be able to get more information on what is going wrong with your ZOO-Kernel. 
+Doing this we can figure out that code on `line 173 <http://zoo-project.org/trac/browser/trunk/zoo-kernel/ulinet.c#L173>`__ 
+and `line 175 <http://zoo-project.org/trac/browser/trunk/zoo-kernel/ulinet.c#L175>`__ have to be commented in the 
+``ulinet.c`` file to get a ZOO-Kernel working using the curl available in CentOS (curl version 7.15.5). 
+If you don't apply the modification, you will get an error from a gdb session pointing 
+segfault in ``Curl_cookie_clearall``.
+
+You can optionally compile then install curl from source :
+
+::
+
+  wget http://curl.haxx.se/download/curl-7.21.3.tar.bz2
+  tar xjf curl-7.21.3.tar.bz2
+  cd curl-7.21.3
+  ./configure --prefix=/usr
+  make
+  make install
+
+Compile then install Python :
+
+::
+ 
+  wget http://www.python.org/ftp/python/2.6.6/Python-2.6.6.tar.bz2
+  tar xjf Python-2.6.6.tar.bz2
+  cd Python-2.6.6
+  ./configure
+  make
+  make install
+
+Compile then install your own GDAL library :
+
+::
+
+  wget http://download.osgeo.org/gdal/gdal-1.7.3.tar.gz
+  tar xzf gdal-1.7.3.tar.gz
+  cd gdal-1.7.3
+  ./configure  # add your options here
+  make
+  make install
+
+Install the Sun JAVA SDK into ``/usr/share`` then use the following command to ensure that the ``libjvm.so`` 
+will be found at runtime from any context.
+
+::
+
+  echo /usr/share/java-1.6.0-openjdk-1.6.0.0/jre/lib/i386/client/ >> /etc/ld.so.conf.d/jvm.conf
+  ldconfig
+  
Index: /branches/PublicaMundi_David-devel/docs/install/debian.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/install/debian.rst	(revision 696)
+++ /branches/PublicaMundi_David-devel/docs/install/debian.rst	(revision 696)
@@ -0,0 +1,130 @@
+.. _install-debian:
+
+Installation on Debian / Ubuntu
+===============================
+
+Use the following instructions to install `ZOO-Project <http://zoo-project.org>`__ on Debian or Ubuntu distributions. 
+
+Prerequisites
+-------------
+
+Using Debian
+......................
+
+The following command should install all the required dependancies on Debian. See the :ref:`install-prereq` section for additional information.
+
+.. code-block:: guess
+
+   apt-get install flex bison libfcgi-dev libxml2 libxml2-dev curl openssl autoconf apache2 python-software-properties subversion python-dev libgdal1-dev build-essential libmozjs185-dev
+
+Using Ubuntu
+......................
+
+On Ubuntu, use the following command first to install the required dependancies :
+
+.. code-block:: guess
+
+   sudo apt-get install flex bison libfcgi-dev libxml2 libxml2-dev curl openssl autoconf apache2 python-software-properties subversion libmozjs185-dev python-dev build-essential
+
+Then add the *UbuntuGIS* repository in order to get the latest versions of libraries
+
+.. code-block:: guess
+
+   sudo add-apt-repository ppa:ubuntugis/ppa
+   sudo apt-get update
+
+Install the geographic library as follow:
+
+.. code-block:: guess
+
+   sudo apt-get install libgdal1-dev
+
+
+Installation
+------------
+
+:ref:`install-download` ZOO-Project latest version from svn using the following command:
+
+.. code-block:: guess
+
+  svn checkout http://svn.zoo-project.org/svn/trunk zoo-project
+
+Install the *cgic* library from packages using the following command:
+
+.. code-block:: guess
+
+  cd zoo-project/thirds/cgic206/
+  make
+
+Head to the :ref:`kernel_index` directory
+
+.. code-block:: guess
+
+  cd ../../zoo-project/zoo-kernel/
+
+Create a configure file as follow:
+
+.. code-block:: guess
+
+  autoconf
+
+Run configure with the desired options, for example with the following command:
+
+.. code-block:: guess
+
+  ./configure --with-js --with-python
+
+.. note::
+   Refer to the :ref:`installation` section for the full list of available options
+
+Compile ZOO-Kernel as follow:
+
+.. code-block:: guess
+
+  make
+
+Copy the necessary files to the `cgi-bin` directory (as administrator user)
+
+.. code-block:: guess
+
+  cp main.cfg /usr/lib/cgi-bin
+  cp zoo_loader.cgi /usr/lib/cgi-bin
+
+Install ZOO ServiceProviders, for example the basic Python service (as administrator user)
+
+.. code-block:: guess
+
+  cp ../zoo-services/hello-py/cgi-env/*.zcfg /usr/lib/cgi-bin
+  cp ../zoo-services/hello-py/*.py /usr/lib/cgi-bin/
+
+Edit the *main.cfg* file as follow (example configuration):
+
+.. code-block:: guess
+
+  nano /usr/lib/cgi-bin/main.cfg
+  - serverAddress = http://127.0.0.1
+
+
+Test the ZOO-Kernel installation with the following requests:
+
+.. code-block:: guess
+
+   http://127.0.0.1/cgi-bin/zoo_loader.cgi?ServiceProvider=&metapath=&Service=WPS&Request=GetCapabilities&Version=1.0.0
+
+.. code-block:: guess
+
+   http://127.0.0.1/cgi-bin/zoo_loader.cgi?ServiceProvider=&metapath=&Service=WPS&Request=DescribeProcess&Version=1.0.0&Identifier=HelloPy
+
+.. code-block:: guess
+
+   http://127.0.0.1/cgi-bin/zoo_loader.cgi?ServiceProvider=&metapath=&Service=WPS&Request=Execute&Version=1.0.0&Identifier=HelloPy&DataInputs=a=myname
+
+
+.. note:: 
+
+   Such request should return well formed XML documents (OWS documents responses).
+
+.. warning:: 
+
+   If ZOO-Kernel returns an error please check the :ref:`kernel_config` and beware of the :ref:`install-prereq`.
+
Index: /branches/PublicaMundi_David-devel/docs/install/download.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/install/download.rst	(revision 696)
+++ /branches/PublicaMundi_David-devel/docs/install/download.rst	(revision 696)
@@ -0,0 +1,45 @@
+.. _install-download:
+
+Download
+=============
+
+Several ways to download the `ZOO-Project <http://zoo-project.org>`_ source code are available and explained in this section.
+
+.. warning::
+    The ZOO-Project svn is the place where developement happens. Checking out svn is the best way to be always up to date.
+
+
+ZOO-Project SVN
+-------------------------------
+
+.. _svn:
+
+Download the `latest <http://zoo-project.org/trac/browser/trunk>`_ `ZOO-Project <http://zoo-project.org>`_  source code using the following *svn* command:
+
+::
+
+  svn checkout http://svn.zoo-project.org/svn/trunk zoo-src
+
+Registered ZOO-Project developers would prefer the following:
+
+::
+
+  sed "s:\[tunnels\]:\[tunnels\]\nzoosvn = /usr/bin/ssh -p 1046:g" -i ~/.subversion/config
+  svn co svn+zoosvn://svn.zoo-project.org/var/svn/repos/trunk zoo-src
+  
+.. note::
+    The ZOO-Project svn server listens on the 1046 (1024+22) portvb(instead of 22 by default), so please use a specific tunnel to access the svn server, as shown in the command above.
+
+
+ZOO-Project releases archives
+-------------------------------
+
+Each new `ZOO-Project <http://zoo-project.org>`_ major release is also made available on the project official website as .zip and .tar.bz2 archives. Head to the `Download <http://zoo-project.org/Code/Download>`_ section to get the latest or older ZOO-Project releases. 
+
+.. warning::
+    Don't use older versions of ZOO-Project if you want to use new features and avoid older code issues. Prefer svn or github instead.
+
+ZOO-Project Github
+-------------------------------
+
+The ZOO-Project svn is mirrored in this Github `repository <https://github.com/kalxas/zoo-project/>`_ in case you would like to fork it.
Index: /branches/PublicaMundi_David-devel/docs/install/index.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/install/index.rst	(revision 695)
+++ /branches/PublicaMundi_David-devel/docs/install/index.rst	(revision 696)
@@ -10,9 +10,11 @@
    :maxdepth: 2
    
-   install-prerequisites
-   install-download
-   install-confoptions
-   install-installation
-   install-onwindows
+   prerequisites
+   download
+   installation
+   debian
+   opensuse
+   centos
+   windows
 
 
Index: anches/PublicaMundi_David-devel/docs/install/install-confoptions.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/install/install-confoptions.rst	(revision 695)
+++ 	(revision )
@@ -1,199 +1,0 @@
-.. _install-configure:
-
-Configure options
-==============
-
-This section provides information on :ref:`kernel_index` configure options. It is recommanded to also read the :ref:`kernel_config` section for configuration technical details.
-
-Configure options
------------------
-
-Here is the list of available options as returned by *./configure --help* command:
-
-::
-
-  --with-PACKAGE[=ARG]    Use PACKAGE [ARG=yes]
-  --without-PACKAGE       Do not use PACKAGE (same as --with-PACKAGE=no)
-  --with-gdal-config=FILE Specifies an alternative gdal-config file
-  --with-xml2config=FILE  Specifies an alternative xml2-config file
-  --with-python=PATH      Enables python support or specifies an alternative directory for python installation (disabled by default)
-  --with-pyvers=NUM       Uses a specific python version
-  --with-php=PATH         Enables php support or specify an alternative directory for php installation, disabled by default
-  --with-perl=PATH        Enables perl support or specifies an alternative directory for perl installation, disabled by default
-  --with-java=PATH        Enables java support or specifies a JDK_HOME, disabled by default
-  --with-js=PATH          Enables javascript support, disabled by default
-  --with-mapserver=PATH   Specifies the path for MapServer compiled source tree
-  --with-itk=PATH          Specifies an alternative location for the ITK library
-  --with-itk-version=VERSION          Specifies an alternative version for the ITK library     
-  --with-otb=PATH         Enables optional OrfeoToolbox support
-  --with-saga=PATH        Enables optional SAGA GIS support 
-
-All the options are described in more details in the following sections.
-
-GDAL Support (Required) 
-........................................
-
-If gdal-config program is not found in PATH, a *--with-gdal-config* option can be used to specify its location. For instance, if gdal-config lies in ``/usr/local/bin`` which is not in PATH, you may use the following command:
-
-::
-
-  $ ./configure --with-gdal-config=/usr/local/bin/gdal-config
-
-XML2 Support (Required) 
-........................................
-
-
-If xml2-config program is not found in PATH, a *--with-xml2config* option can be used  to specify its location. For instance, if xml2-config is installed in ``/usr/local/bin`` which is not in PATH, you may use the following command:
-
-::
-
-  $ ./configure --with-xml2config=/usr/local/bin/xml2-config
-
-
-Python Support (Optional) 
-..............................................
-
-The *--with-python* option is required to activate the :ref:`kernel_index` Python support, using the following command:
-
-::
-
-  $ ./configure --with-python
-
-This assumes that python-config is found in PATH. If not, then you can specify the Python 
-installation directory using the following command (with ``/usr/local`` as example python directory):
-
-::
-
-  $ ./configure --with-python=/usr/local
-
-
-Python Version (Optional) 
-..............................................
-
-A specific version of Python can be used, with the *--with-pyvers* option as shown bellow:
-::
-
-  $ ./configure --with-pyvers=2.6
-
-
-PHP Support (Optional) 
-..............................................
-
-The *--with-php* option is required to activate the :ref:`kernel_index` PHP support, using the following command:
-
-::
-
-  $ ./configure --with-php
-
-This assumes that php-config is found in PATH. If not, then you can specify the PHP installation  directory, using the following command (with ``/usr/local`` as example PHP directory)
-
-::
-
-  $ ./configure --with-php=/usr/local
-
-.. warning::
-    ZOO-Kernel optional PHP support requires a local PHP Embedded installation. Read more `here <http://zoo-project.org/trac/wiki/ZooKernel/Embed/PHP>`__.
-
-
-Perl Support (Optional) 
-..............................................
-
-The *--with-perl* option can be used for activating the ZOO-Kernel Perl support, as follow:
-
-::
-
-  $ ./configure --with-perl
-
-This assumes that perl is found in PATH. For instance, if Perl is installed in /usr/local and /usr/local/bin which is not found in PATH,
-then the following command can be used (this assumes that /usr/local/bin/perl exists):
-
-::
-
-  $ ./configure --with-perl=/usr/local
-
-
-Java Support (Optional) 
-..............................................
-
-In order to activate the Java support for ZOO-Kernel, the
-*--with-java* configure option must be specified and sets the installation path of your Java SDK. For instance, 
-if Java SDK is installed in the ``/usr/lib/jvm/java-6-sun-1.6.0.22/`` directory,  then the following command can be used:
-
-::
-
-  $ ./configure --with-java=/usr/lib/jvm/java-6-sun-1.6.0.22/
-
-This assumes that the ``include/linux`` and ``jre/lib/i386/client/`` subdirectories exist in ``/usr/lib/jvm/java-6-sun-1.6.0.22/``, that the ``include/linux`` directory contains the jni.h headers file and that the ``jre/lib/i386/client/`` directory contains the libjvm.so file.
-
-.. note:: 
-   With Mac OS X you only have to set *macos* as the value for the *--with-java* option 
-   to activate Java support. For example:
-
-   ::
-
-     $ ./configure --with-java=macos
-
-.. _js-support:
-
-JavaScript Support (Optional) 
-..............................................
-
-In order to activate the JavaScript support for ZOO-Kernel,
-the *--with-js* configure option must be specified. If you are using a "Debian-like" GNU/Linux distribution then 
-dpkg will be used to detect if the required packages are installed and you don't have to 
-specify anything here. The following command is only needed (assuming that js_api.h and libmozjs.so are found in default directories):
-
-::
-
-  $ ./configure --with-js 
-
-If youwant to use a custom installation of `SpiderMonkey <https://developer.mozilla.org/en/SpiderMonkey>`__ ,or if you are not using a Debian packaging 
-system, then you'll have to specify the directory where it is installed. For  instance, if SpiderMonkey is in /usr, then the following command must be used:
-
-::
-
-  $ ./configure --with-js=/usr
-
-
-MapServer Support (Optional) 
-..............................................
-
-
-In order to activate the WMS, WFS and WCS output support using
-MapServer, the *--with-mapserver* option must be used. The path to
-``mapserver-config`` which is located in the source code of MapServer
-must also be set, using the following command:
-
-::
-
-  $ ./configure --with-mapserver=/path/to/your/mapserver_config/
-
-
-Read more about the :ref:`kernel-mapserver`.
-
-
-Orfeo Toolbox Support (Optional) 
-.....................................................
-
-In order to activate the optional Orfeo Toolbox support, the *--with-otb* option must be used, using the following command:
-
-::
-
-  $ ./configure --with-otb=/path/to/your/otb/
-
-
-Read more about the :ref:`kernel-orfeotoolbox`.
-
-
-SAGA GIS Support (Optional) 
-.....................................................
-
-
-In order to activate the optional SAGA GIS support, the *--with-saga* option must be used, using the following command:
-
-::
-
-  $ ./configure --with-saga=/path/to/your/saga/
-
-
-Read more about the :ref:`kernel-sagagis`.
Index: anches/PublicaMundi_David-devel/docs/install/install-download.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/install/install-download.rst	(revision 695)
+++ 	(revision )
@@ -1,45 +1,0 @@
-.. _install-download:
-
-Download
-=============
-
-Several ways to download the `ZOO-Project <http://zoo-project.org>`_ source code are available and explained in this section.
-
-.. warning::
-    The ZOO-Project svn is the place where developement happens. Checking out svn is the best way to be always up to date.
-
-
-ZOO-Project SVN
--------------------------------
-
-.. _svn:
-
-Download the `latest <http://zoo-project.org/trac/browser/trunk>`_ `ZOO-Project <http://zoo-project.org>`_  source code using the following *svn* command:
-
-::
-
-  svn checkout http://svn.zoo-project.org/svn/trunk zoo-project
-
-Registered ZOO-Project developers would prefer the following:
-
-::
-
-  sed "s:\[tunnels\]:\[tunnels\]\nzoosvn = /usr/bin/ssh -p 1046:g" -i ~/.subversion/config
-  svn co svn+zoosvn://svn.zoo-project.org/var/svn/repos/trunk zoo-project
-  
-.. note::
-    The ZOO-Project svn server listens on the 1046 (1024+22) portvb(instead of 22 by default), so please use a specific tunnel to access the svn server, as shown in the command above.
-
-
-ZOO-Project releases archives
--------------------------------
-
-Each new `ZOO-Project <http://zoo-project.org>`_ major release is also made available on the project official website as .zip and .tar.bz2 archives. Head to the `Download <http://zoo-project.org/Code/Download>`_ section to get the latest or older ZOO-Project releases. 
-
-.. warning::
-    Don't use older versions of ZOO-Project if you want to use new features and avoid older code issues. Prefer svn or github instead.
-
-ZOO-Project Github
--------------------------------
-
-The ZOO-Project svn is mirrored in this Github `repository <https://github.com/kalxas/zoo-project/>`_ in case you would like to fork it.
Index: anches/PublicaMundi_David-devel/docs/install/install-installation.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/install/install-installation.rst	(revision 695)
+++ 	(revision )
@@ -1,309 +1,0 @@
-.. _install-installation:
-
-Installation on Unix/Linux
-=================
-
-For the impatient
---------------
-
-Run the following commands from the directory where you :ref:`install-download` and extracted the ZOO Kernel source code in order to build the ``zoo_loader.cgi`` CGI program with default options.
-
-::
-
-   cd zoo-kernel
-   autoconf  
-   ./configure
-   make
-
-This should produce executables for the *zoo_loader.cgi* CGI program in the ``zoo-kernel`` directory. Copy the *zoo_loader.cgi* and *main.cfg* files to the HTTP server ``cgi`` directory and start using it.
-
-.. warning:: 
-
-   Edit ZOO-Kernel installation settings in the *main.cfg* file (set ``tmpPath`` and ``tmpUrl`` to fit your web server configuration).
-
-Debian / Ubuntu
-----------------------
-
-Use the following instructions to install `ZOO-Project <http://zoo-project.org>`__ on Debian or Ubuntu distributions. 
-
-Prerequisites
-......................
-
-Using Debian
-**********************
-
-The following command should install all the required dependancies on Debian. See the :ref:`install-prereq` section for additional information.
-
-.. code-block:: guess
-
-   apt-get install flex bison libfcgi-dev libxml2 libxml2-dev curl openssl autoconf apache2 python-software-properties subversion python-dev libgdal1-dev build-essential libmozjs185-dev
-
-Using Ubuntu
-**********************
-
-On Ubuntu, use the following command first to install the required dependancies :
-
-.. code-block:: guess
-
-   sudo apt-get install flex bison libfcgi-dev libxml2 libxml2-dev curl openssl autoconf apache2 python-software-properties subversion libmozjs185-dev python-dev build-essential
-
-Then add the *UbuntuGIS* repository in order to get the latest versions of libraries
-
-.. code-block:: guess
-
-   sudo add-apt-repository ppa:ubuntugis/ppa
-   sudo apt-get update
-
-Install the geographic library as follow:
-
-.. code-block:: guess
-
-   sudo apt-get install libgdal1-dev
-
-
-Installation
-......................
-
-:ref:`install-download` ZOO-Project latest version from svn using the following command:
-
-.. code-block:: guess
-
-  svn checkout http://svn.zoo-project.org/svn/trunk zoo-project
-
-Install the *cgic* library from packages using the following command:
-
-.. code-block:: guess
-
-  cd zoo-project/thirds/cgic206/
-  make
-
-Head to the :ref:`kernel_index` directory
-
-.. code-block:: guess
-
-  cd ../../zoo-project/zoo-kernel/
-
-Create a configure file as follow:
-
-.. code-block:: guess
-
-  autoconf
-
-Run configure with the desired options, for example with the following command:
-
-.. code-block:: guess
-
-  ./configure --with-js --with-python
-
-.. note::
-   Refer to the :ref:`install-configure` section for the full list of available options
-
-Compile ZOO-Kernel as follow:
-
-.. code-block:: guess
-
-  make
-
-Copy the necessary files to the `cgi-bin` directory (as administrator user)
-
-.. code-block:: guess
-
-  cp main.cfg /usr/lib/cgi-bin
-  cp zoo_loader.cgi /usr/lib/cgi-bin
-
-Install ZOO ServiceProviders, for example the basic Python service (as administrator user)
-
-.. code-block:: guess
-
-  cp ../zoo-services/hello-py/cgi-env/*.zcfg /usr/lib/cgi-bin
-  cp ../zoo-services/hello-py/*.py /usr/lib/cgi-bin/
-
-Edit the *main.cfg* file as follow (example configuration):
-
-.. code-block:: guess
-
-  nano /usr/lib/cgi-bin/main.cfg
-  - serverAddress = http://127.0.0.1
-
-
-Test the ZOO-Kernel installation with the following requests:
-
-.. code-block:: guess
-
-   http://127.0.0.1/cgi-bin/zoo_loader.cgi?ServiceProvider=&metapath=&Service=WPS&Request=GetCapabilities&Version=1.0.0
-
-.. code-block:: guess
-
-   http://127.0.0.1/cgi-bin/zoo_loader.cgi?ServiceProvider=&metapath=&Service=WPS&Request=DescribeProcess&Version=1.0.0&Identifier=HelloPy
-
-.. code-block:: guess
-
-   http://127.0.0.1/cgi-bin/zoo_loader.cgi?ServiceProvider=&metapath=&Service=WPS&Request=Execute&Version=1.0.0&Identifier=HelloPy&DataInputs=a=myname
-
-
-.. note:: 
-
-   Such request should return well formed XML documents (OWS documents responses).
-
-.. warning:: 
-
-   If ZOO-Kernel returns an error please check the :ref:`kernel_config` and beware of the :ref:`install-prereq`.
-
-
-OpenSUSE
-----------------------
-
-:ref:`kernel_index` is maintained as a package in `OpenSUSE Build Service (OBS) <https://build.opensuse.org/package/show?package=zoo-kernel&project=Application%3AGeo>`__. RPM are thus provided for all versions of OpenSUSE Linux (11.2, 11.3, 11.4, Factory).
-
-Stable release
-......................
-
-Use the following instructions to install ZOO-Project latetst release on OpenSUSE distribution.
-
-One-click installer
-*******************
-
-A one-click installer is available `here <http://software.opensuse.org/search?q=zoo-kernel&baseproject=openSUSE%3A11.4&lang=en&exclude_debug=true>`__. 
-For openSUSE 11.4, follow this direct `link <http://software.opensuse.org/ymp/Application:Geo/openSUSE_11.4/zoo-kernel.ymp?base=openSUSE%3A11.4&query=zoo-kernel>`__.
-
-Yast software manager
-*********************
-
-Add the `Application:Geo <http://download.opensuse.org/repositories/Application:/Geo/>`__ repository to the software repositories and then ZOO-Kernel can then be found in Software Management using the provided search tool.
-
-Command line (as root for openSUSE 11.4)
-****************************************
-
-Install ZOO-Kernel package by yourself using the following command:
-
-.. code-block:: guess
-
-  zypper ar http://download.opensuse.org/repositories/Application:/Geo/openSUSE_11.4/
-  zypper refresh
-  zypper install zoo-kernel
-
-Developement version
-......................
-
-The latest development version of ZOO-Kernel can be found in OBS under the project `home:tzotsos <https://build.opensuse.org/project/show?project=home%3Atzotsos>`__. ZOO-Kernel packages are maintained and tested there before being released to the Application:Geo repository. Installation methods are identical as for the stable version. Make sure to use `this <http://download.opensuse.org/repositories/home:/tzotsos/>`__ repository instead.
-
-Command line (as root for openSUSE 11.4)
-********************************************
-
-Install latest ZOO-Kernel trunk version with the following command:
-
-.. code-block:: guess
-
-  zypper ar http://download.opensuse.org/repositories/home:/tzotsos/openSUSE_11.4/
-  zypper refresh
-  zypper install zoo-kernel
-  zypper install zoo-kernel-grass-bridge
-
-Note that there is the option of adding the zoo-wps-grass-bridge package. This option will automatically install grass7 (svn trunk).
-
-
-CentOS
-----------------------
-
-Use the following instructions to install `ZOO-Project <http://zoo-project.org>`__ on CentOS distributions. 
-
-Prerequisites
-......................
-
-.. code-block:: guess
-
-  yum install apache2
-  yum install build-essentials
-  yum install gcc-c++
-  yum install zlib-devel
-  yum install libxml2-devel
-  yum install bison
-  yum install openssl 
-  yum install python-devel
-  yum install subversion
-
-
-Compile then install FastCGI library from source
-
-::
-
-  wget http://www.fastcgi.com/dist/fcgi.tar.gz
-  tar xzf fcgi-2.4.0.tar.gz 
-  ./configure
-  make
-  make install
-  echo /usr/local/lib >> /etc/ld.so.conf.d/local.conf
-  ldconfig
-
-Compile then install the autoconf tools :
-
-::
-
-  wget http://ftp.gnu.org/gnu/autoconf/autoconf-latest.tar.gz
-  tar xzf autoconf-latest.tar.gz
-  ./configure --prefix=/usr
-  make 
-  make install
-
-Compile then install the flex tool :
-
-::
-
-  wget http://downloads.sourceforge.net/project/flex/flex/flex-2.5.35/flex-2.5.35.tar.gz?r=http%3A%2F%2Fflex.sourceforge.net%2F&ts=1292529005&use_mirror=switch
-  tar xzf flex-2.5.35.tar.gz
-  cd flex-2.5.35
-  ./configure --prefix=/usr
-  make
-  make install
-
-Using the curl provided in the CentOS distribution will produce a ZOO-Kernel unable to run any 
-Service. Indeed, some segmentation faults occur when trying to run ``Execute`` requests on the ZOO-Kernel, 
-compiling the ZOO-Kernel setting ``USE_GDB`` flag in the ``CFLAGS`` of your ``Makefile`` will let you run 
-ZOO-Kernel from gdb and be able to get more information on what is going wrong with your ZOO-Kernel. 
-Doing this we can figure out that code on `line 173 <http://zoo-project.org/trac/browser/trunk/zoo-kernel/ulinet.c#L173>`__ 
-and `line 175 <http://zoo-project.org/trac/browser/trunk/zoo-kernel/ulinet.c#L175>`__ have to be commented in the 
-``ulinet.c`` file to get a ZOO-Kernel working using the curl available in CentOS (curl version 7.15.5). 
-If you don't apply the modification, you will get an error from a gdb session pointing 
-segfault in ``Curl_cookie_clearall``.
-
-You can optionally compile then install curl from source :
-
-::
-
-  wget http://curl.haxx.se/download/curl-7.21.3.tar.bz2
-  tar xjf curl-7.21.3.tar.bz2
-  cd curl-7.21.3
-  ./configure --prefix=/usr
-  make
-  make install
-
-Compile then install Python :
-
-::
- 
-  wget http://www.python.org/ftp/python/2.6.6/Python-2.6.6.tar.bz2
-  tar xjf Python-2.6.6.tar.bz2
-  cd Python-2.6.6
-  ./configure
-  make
-  make install
-
-Compile then install your own GDAL library :
-
-::
-
-  wget http://download.osgeo.org/gdal/gdal-1.7.3.tar.gz
-  tar xzf gdal-1.7.3.tar.gz
-  cd gdal-1.7.3
-  ./configure  # add your options here
-  make
-  make install
-
-Install the Sun JAVA SDK into ``/usr/share`` then use the following command to ensure that the ``libjvm.so`` 
-will be found at runtime from any context.
-
-::
-
-  echo /usr/share/java-1.6.0-openjdk-1.6.0.0/jre/lib/i386/client/ >> /etc/ld.so.conf.d/jvm.conf
-  ldconfig
-  
Index: anches/PublicaMundi_David-devel/docs/install/install-onwindows.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/install/install-onwindows.rst	(revision 695)
+++ 	(revision )
@@ -1,159 +1,0 @@
-.. include:: <xhtml1-lat1.txt>
-.. include:: <xhtml1-symbol.txt>
-
-.. _install-onwindows:
-
-	     
-Installation on Windows |trade|
-====================
-
-Using OSGeo4W
---------------
-
-Install OSGeo4W
-..........................................
-
-First download the OSGeo4W installer from  http://trac.osgeo.org/osgeo4w/, and install it with all the dependencies needed by your 
-WPS services such as GDAL for example.
-
-.. warning::
-    FastCGI, libxml, Python and cURL are mandatory
-
-Install ZOO4W
-..........................................
-
-Once OSGeo4W installed on your platform, you will need more GNU tools and libraries. `This package <http://www.zoo-project.org/dl/tool-win32.zip>`__  contains full dependencies required to compile on a WIN32 platform and this one contains `full runtime dependencies <http://www.zoo-project.org/dl/zoo-runtime.zip>`__ . Place it to your ``C:\OSGeo4W\bin``.
-
-Download the `binary version <http://www.zoo-project.org/dl/zoo_loader.cgi>`__  of ZOO Kernel for WIN32, then place it in the ``C:\OSGeo4W\bin`` directory. Don't forget to place the *main.cfg* file in the same directory, you can use a modified copy of  `this file <http://www.zoo-project.org/trac/browser/trunk/zoo-kernel/main.cfg>`__.
-
-Additionaly, the binary version of the OGR Services Provider available from `here <http://www.zoo-project.org/dl/zoo-services-win32.zip>`__ can be used directly. Place the two libraries with their respective .zcfg files in your local ``C:\OSGeo4W\bin`` directory to do so.
-
-Compile ZOO from source
----------------------
-
-.. warning::
-   Ensure to first perform the :ref:`prerequisite steps <kernel-installation-prereq>` before compiling the ZOO Kernel.
-
-The following steps are for use with the Microsoft Visual Studio compiler (and tested with MSVC 2008).
-
-1. Make sure the gnuwin32 tools *bison.exe*  and *flex.exe* are found in your path.  You can download the GNUwin32 tools `here <http://www.zoo-project.org/dl/tool-win32.zip>`__.
-
-2. Modify the *nmake.opt* file to point to your local libraries.  You can find a modified nmake.opt that points to local libs `here <http://www.zoo-project.org/trac/attachment/ticket/27/nmake.opt>`__. 
-   You can also find a modified ``zoo-project\zoo-kernel\makefile.vc`` file `here <http://www.zoo-project.org/trac/attachment/ticket/27/makefile.vc>`__.
-   
-3. Execute:
-
-   ::
-   
-     nmake /f makefile.vc
-     
-4. A file *zoo_loader.cgi* should be created.  Note that if another file named *zoo_loader.cgi.manifest* is also created, you
-   will have to run another command:
-   
-   ::
-   
-     nmake /f makefile.vc embed-manifest
-     
-5. Copy the files *zoo_loader.cgi*  and *main.cfg* into your cgi-bin directory.
-
-6. Using the command prompt, test the zoo-kernel by executing the following command:
-
-   ::
-   
-     D:\ms4w\Apache\cgi-bin> zoo_loader.cgi
-     
-   which should display a message such as:
-   
-   ::
-   
-     Content-Type: text/xml; charset=utf-8
-     Status: 200 OK
-     
-     <?xml version="1.0" encoding="utf-8"?>
-     <ows:ExceptionReport xmlns:ows="http://www.opengis.net/ows/1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xsi:schemaLocation="http://www.opengis.net/ows/1.1 http://schemas.opengis.net/ows/1.1.0/owsExceptionReport.xsd" xml:lang="en-US" version="1.1.0">
-       <ows:Exception exceptionCode="MissingParameterValue">
-         <ows:ExceptionText>Parameter &lt;request&gt; was not specified</ows:ExceptionText>
-       </ows:Exception>
-     </ows:ExceptionReport>
-     
-7. Edit the *main.cfg* file so that it contains values describing your WPS service.  An example of such 
-   a file running on Windows is:
-   
-   ::
-   
-     [main]
-     encoding = utf-8
-     version = 1.0.0
-     serverAddress = http://localhost/
-     lang = en-CA
-     tmpPath=/ms4w/tmp/ms_tmp/
-     tmpUrl = /ms_tmp/
-     
-     [identification]
-     title = The Zoo WPS Development Server
-     abstract = Development version of ZooWPS. See http://www.zoo-project.org
-     fees = None
-     accessConstraints = none
-     keywords = WPS,GIS,buffer
-     
-     [provider]
-     providerName=Gateway Geomatics
-     providerSite=http://www.gatewaygeomatics.com
-     individualName=Jeff McKenna
-     positionName=Director
-     role=Dev
-     adressDeliveryPoint=1101 Blue Rocks Road
-     addressCity=Lunenburg
-     addressAdministrativeArea=False
-     addressPostalCode=B0J 2C0
-     addressCountry=ca
-     addressElectronicMailAddress=info@gatewaygeomatics.com
-     phoneVoice=False
-     phoneFacsimile=False
-     
-8. Open a web browser window, and execute a GetCapababilites request on your WPS service: http://localhost/cgi-bin/zoo_loader.cgi?request=GetCapabilities&service=WPS
-
-   The response should be displayed in your browser, such as:
-   
-   ::
-   
-     <wps:Capabilities xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 http://schemas.opengis.net/wps/1.0.0/wpsGetCapabilities_response.xsd" service="WPS" xml:lang="en-US" version="1.0.0">
-     <ows:ServiceIdentification>
-       <ows:Title>The Zoo WPS Development Server</ows:Title>
-       <ows:Abstract>
-         Development version of ZooWPS. See http://www.zoo-project.org
-       </ows:Abstract>
-       <ows:Keywords>
-         <ows:Keyword>WPS</ows:Keyword>
-         <ows:Keyword>GIS</ows:Keyword>
-         <ows:Keyword>buffer</ows:Keyword>
-       </ows:Keywords>
-       <ows:ServiceType>WPS</ows:ServiceType>
-       <ows:ServiceTypeVersion>1.0.0</ows:ServiceTypeVersion>
-       ...
-       
-Optionally Compile Individual Services
-.............................................................
-
-An example could be the *OGR base-vect-ops* provider located in the ``zoo-project\zoo-services\ogr\base-vect-ops`` directory.  
-
-1. First edit the *makefile.vc* located in that directory, and execute:
-
-   ::
-   
-     nmake /f makefile.vc
-     
-   Inside that same directory, the *ogr_service.zo* file should be created.
-   
-2. Copy all the files inside ``zoo-services\ogr\base-vect-ops\cgi-env`` into your ``cgi-bin`` directory
-
-3. Test this service provider through the following URL:
-
-http://localhost/cgi-bin/zoo_loader.cgi?request=Execute&service=WPS&version=1.0.0&Identifier=Buffer&DataInputs=BufferDistance=1@datatype=interger;InputPolygon=Reference@xlink:href=http%3A%2F%2Fwww.zoo-project.org%3A8082%2Fgeoserver%2Fows%3FSERVICE%3DWFS%26REQUEST%3DGetFeature%26VERSION%3D1.0.0%26typename%3Dtopp%3Astates%26SRS%3DEPSG%3A4326%26FeatureID%3Dstates.15
-   
-   The response displayed in your browser should contain:
-   
-   ::
-   
-     <wps:ProcessSucceeded>Service "Buffer" run successfully.</wps:ProcessSucceeded>
-
Index: anches/PublicaMundi_David-devel/docs/install/install-prerequisites.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/install/install-prerequisites.rst	(revision 695)
+++ 	(revision )
@@ -1,37 +1,0 @@
-.. _install-prereq:
-
-Prerequisites
-=============
-
-Mandatory
------------------
-
-The following libraries are required to install :ref:`kernel_index`. Please make sure they are available on your system before anything else.
-
-- autoconf (`http://www.gnu.org/software/autoconf/ <http://www.gnu.org/software/autoconf/>`_)
-- cgic (`http://www.boutell.com/cgic <http://www.boutell.com/cgic>`_)
-- cURL (`http://curl.haxx.se <http://curl.haxx.se>`_ )
-- FastCGI (`http://www.fastcgi.com <http://www.fastcgi.com>`_ )
-- Flex & Bison (`http://flex.sourceforge.net/ <http://flex.sourceforge.net/>`_ | `http://www.gnu.org/software/bison/ <http://www.gnu.org/software/bison/>`_ )
-- libxml2 (  http://xmlsoft.org )
-- OpenSSL (  http://www.openssl.org )
-- Python (  http://www.python.org )
-- GDAL (for using the available GDAL based ZOO-Services) (http://gdal.org/) 
-
- .. warning::
-    It is mandatory to install every library listed above before compiling and installing ZOO-Kernel
-
-Optional
------------------
-
-You may also consider the following optional libraries:
-
-- MapServer (for ZOO-Kernel optional WMS, WFS and WCS support) (http://mapserver.org)
-- PHP Embedded (for ZOO-Kernel optional PHP support) (http://www.php.net)
-- Java SDK (for ZOO-Kernel optional Java support) (http://java.sun.com)
-- SpiderMonkey (for ZOO-Kernel optional Javascript support) (http://www.mozilla.org/js/spidermonkey/)
-- SAGA GIS (for ZOO-Kernel optional SAGA support)(http://www.saga-gis.org/en/index.html/)
-- OrfeoToolbox (for ZOO-Kernel optional OTB support) (https://www.orfeo-toolbox.org/)
-- Insight Segmentation and Registration Toolkit  (http://itk.org/ITK/resources/software.html/>)
-- GRASS GIS (for using it through WPSGrassBridge) (http://grass.osgeo.org)
-
Index: /branches/PublicaMundi_David-devel/docs/install/installation.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/install/installation.rst	(revision 696)
+++ /branches/PublicaMundi_David-devel/docs/install/installation.rst	(revision 696)
@@ -0,0 +1,456 @@
+.. _install-installation:
+
+Installation on Unix/Linux
+==========================
+
+To build and install ZOO-Project on your Web Server you will need 4
+steps :
+
+ * build the cgic library,
+ * install the ZOO-Kernel,
+ * install the ZOO-Services,
+ * testing your installation.
+
+Build cgic
+----------
+
+Run the following commands from the ``thirds/cgic`` directory to build
+the cgic library.
+
+::
+
+   cd thirds/cgic
+   make
+
+The cgic library originaly come from `http://www.boutell.com/cgic
+<http://www.boutell.com/cgic>`_.
+
+.. warning:: 
+
+   You may need to edit the ``Makefile`` in case you are using a 64 bits
+   platform for building and your fcgi library is not located in ``/usr/lib64``.
+
+Install the ZOO-Kernel
+----------------------
+
+
+For the impatient
+.................
+
+Run the following commands from the directory where you :ref:`install-download` and extracted the ZOO Kernel source code in order to build the ``zoo_loader.cgi`` CGI program with default options.
+
+::
+
+   cd zoo-project/zoo-kernel
+   autoconf  
+   ./configure
+   make
+   make install
+
+This should produce executables for the *zoo_loader.cgi* CGI program
+(located per default in ``/usr/lib/cgi-bin/``) and a shared library
+``libzoo_service``  (located per default in ``/usr/local/lib``).
+
+.. warning:: 
+
+   Edit ZOO-Kernel installation settings in the ``main.cfg`` file (set
+   ``tmpPath`` and ``tmpUrl`` to fit your web server configuration).
+
+
+Configure options
+.................
+
+This section provides information on :ref:`kernel_index` configure options. It is recommanded to also read the :ref:`kernel_config` section for configuration technical details.
+
+Here is the list of available options as returned by ``./configure --help`` command:
+
+.. list-table:: Configure Options
+   :header-rows: 1
+
+   * - Option
+     - Description
+   * - ``--with-cgi-dir=PATH``
+     - Specifies an alternative cgi directory path (default:
+       /usr/lib/cgi-bin)
+   * - ``--with-db-backend``
+     - Relies on a database for storing status messages and response
+       files
+   * - ``--with-yaml=PATH``
+     - Specifies an alternative location for the yaml library
+   * - ``--with-fastcgi=PATH``
+     - Specifies an alternative location for the fastcgi library
+   * - ``--with-gdal-config=FILE``
+     - Specifies an alternative gdal-config file
+   * - ``--with-xml2config=FILE``
+     - Specifies an alternative xml2-config file
+   * - ``--with-python=PATH``
+     - Enables python support or specifies an alternative directory
+       for python installation (disabled by default)
+   * - ``--with-pyvers=NUM``
+     - Uses a specific python version
+   * - ``--with-js=PATH`` 
+     - Enables javascript support, disabled by default
+   * - ``--with-php=PATH`` 
+     - Enables php support or specify an alternative directory for php
+       installation, disabled by default
+   * - ``--with-java=PATH``
+     - Enables java support or specifies a JDK_HOME, disabled by
+       default
+   * - ``--with-ruby=PATH``
+     - To enable ruby support or specify an alternative directory for
+       ruby installation, disabled by default
+   * - ``--with-rvers=NUM``
+     - To use a specific ruby version
+   * - ``--with-perl=PATH``
+     - Enables perl support or specifies an alternative directory for
+       perl installation, disabled by default
+   * - ``--with-mapserver=PATH``
+     - Specifies the path for MapServer compiled source tree
+   * - ``--with-itk=PATH`` 
+     - Specifies an alternative location for the ITK library
+   * - ``--with-itk-version=VERSION``
+     - Specifies an alternative version for the ITK library 
+   * - ``--with-otb=PATH``
+     - Enables optional OrfeoToolbox support
+   * - ``--with-wx-config=PATH``
+     - Specifies an alternative path for the wx-config tool
+   * - ``--with-saga=PATH``
+     - Enables optional SAGA GIS support 
+
+
+.. code ::
+
+  --with-cgi-dir=PATH     Specifies an alternative cgi directory path (
+                          default: /usr/lib/cgi-bin)
+  --with-db-backend       Relies on a database for storing status messages and
+                          response files
+  --with-yaml=PATH        Specifies an alternative location for the yaml
+                          library
+  --with-fastcgi=PATH     Specifies an alternative location for the fastcgi
+                          library
+  --with-xml2config=FILE  Specifies an alternative xml2-config file
+  --with-xsltconfig=FILE  Specifies an alternative xslt-config file
+  --with-gdal-config=FILE Specifies an alternative gdal-config file
+  --with-proj=PATH        Specifies an alternative location for PROJ4 setup
+  --with-geosconfig=FILE  Specifies an alternative geos-config file
+  --with-cgal=PATH        Specifies an alternative location for CGAL setup
+  --with-mapserver=PATH   Specifies the path for MapServer compiled source
+                          tree
+  --with-python=PATH      To enable python support or Specifies an alternative
+                          directory for python installation, disabled by
+                          default
+  --with-pyvers=NUM       To use a specific python version
+  --with-js=PATH          Specifies --with-js=path-to-js to enable js support,
+                          specify --with-js on linux debian like, js support
+                          is disabled by default
+  --with-php=PATH         To enable php support or specify an alternative
+                          directory for php installation, disabled by default
+  --with-java=PATH        To enable java support, specify a JDK_HOME, disabled
+                          by default
+  --with-ruby=PATH        To enable ruby support or specify an alternative
+                          directory for ruby installation, disabled by default
+  --with-rvers=NUM        To use a specific ruby version
+  --with-perl=PATH        To enable perl support or specify an alternative
+                          directory for perl installation, disabled by default
+  --with-itk=PATH         Specifies an alternative location for the itk
+                          library
+  --with-itk-version=VERSION
+                          Specifies an alternative version for the itk library
+  --with-otb=PATH         Specifies an alternative location for the otb
+                          library
+  --with-wx-config=PATH   Specifies an alternative path for the wx-config tool
+  --with-saga=PATH        Specifies an alternative location for the SAGA-GIS
+                          library
+
+
+
+
+::
+
+  --with-cgi-dir=PATH     Specifies an alternative cgi directory path (default: /usr/lib/cgi-bin)
+  --with-db-backend       Relies on a database for storing status messages and response files
+  --with-yaml=PATH        Specifies an alternative location for the yaml library
+  --with-fastcgi=PATH     Specifies an alternative location for the fastcgi library
+  --with-gdal-config=FILE Specifies an alternative gdal-config file
+  --with-xml2config=FILE  Specifies an alternative xml2-config file
+  --with-python=PATH      Enables python support or specifies an alternative directory for python installation (disabled by default)
+  --with-pyvers=NUM       Uses a specific python version
+  --with-js=PATH          Enables javascript support, disabled by default
+  --with-php=PATH         Enables php support or specify an alternative directory for php installation, disabled by default
+  --with-java=PATH        Enables java support or specifies a JDK_HOME, disabled by default
+  --with-ruby=PATH        To enable ruby support or specify an alternative directory for ruby installation, disabled by default
+  --with-rvers=NUM        To use a specific ruby version
+  --with-perl=PATH        Enables perl support or specifies an alternative directory for perl installation, disabled by default
+  --with-mapserver=PATH   Specifies the path for MapServer compiled source tree
+  --with-itk=PATH          Specifies an alternative location for the ITK library
+  --with-itk-version=VERSION          Specifies an alternative version for the ITK library     
+  --with-otb=PATH         Enables optional OrfeoToolbox support
+  --with-wx-config=PATH   Specifies an alternative path for the wx-config tool
+  --with-saga=PATH        Enables optional SAGA GIS support 
+
+All the options are described in more details in the following sections.
+
+GDAL Support (Required) 
+........................
+
+If gdal-config program is not found in your ``PATH``, a
+``--with-gdal-config`` option can be used to specify its location. For
+instance, if ``gdal-config`` lies in ``/usr/local/bin`` which is not in
+your PATH, you may use the following command:
+
+::
+
+  $ ./configure --with-gdal-config=/usr/local/bin/gdal-config
+
+XML2 Support (Required) 
+........................
+
+If xml2-config program is not found in PATH, a *--with-xml2config* option can be used  to specify its location. For instance, if xml2-config is installed in ``/usr/local/bin`` which is not in PATH, you may use the following command:
+
+::
+
+  $ ./configure --with-xml2config=/usr/local/bin/xml2-config
+
+
+Python Support (Optional) 
+..............................................
+
+The ``--with-python=yes`` option is required to activate the :ref:`kernel_index` Python support, using the following command:
+
+::
+
+  $ ./configure --with-python=yes
+
+This assumes that python-config is found in your ``PATH``. If not,
+then you can specify the Python installation directory using the
+following command (with Python installed in the ``/usr/local``
+directory):
+
+::
+
+  $ ./configure --with-python=/usr/local
+
+
+Python Version
+**************
+
+If multiple Python versions are available and you want to use a
+specific one, then you can use the ``--with-pyvers`` option as shown
+bellow:
+
+::
+
+  $ ./configure --with-pyvers=2.7
+
+
+PHP Support (Optional) 
+..............................................
+
+The ``--with-php=yes`` option is required to activate the
+:ref:`kernel_index` PHP support`, using the following command:
+
+::
+
+  $ ./configure --with-php=yes
+
+This assumes that ``php-config`` can be found in the ``<PATH>/bin``
+directory . So, supposing the your ``php-config`` can be found in
+``/usr/local/bin``, then use the following command:
+
+::
+
+  $ ./configure --with-php=/usr/local
+
+.. warning::
+    ZOO-Kernel optional PHP support requires a local PHP Embedded installation. Read more `here <http://zoo-project.org/trac/wiki/ZooKernel/Embed/PHP>`__.
+
+
+Perl Support (Optional) 
+..............................................
+
+The ``--with-perl=yes`` option can be used for activating the
+ZOO-Kernel Perl support, as follow:
+
+::
+
+  $ ./configure --with-perl=yes
+
+This assumes that perl is found in your PATH. For instance, if Perl is
+installed in ``/usr/local`` and ``/usr/local/bin`` is not found in
+your ``PATH``, then the following command can be used (this assumes
+that ``/usr/local/bin/perl`` exists):
+
+::
+
+  $ ./configure --with-perl=/usr/local
+
+
+Java Support (Optional) 
+..............................................
+
+In order to activate the Java support for ZOO-Kernel, the
+`--with-java` configure option must be specified and sets the
+installation path of your Java SDK. For instance,  if Java SDK is
+installed in the ``/usr/lib/jvm/java-6-sun-1.6.0.22/`` directory,
+then the following command can be used:
+
+::
+
+  $ ./configure --with-java=/usr/lib/jvm/java-6-sun-1.6.0.22/
+
+This assumes that the ``include/linux`` and ``jre/lib/i386/client/``
+subdirectories exist in ``/usr/lib/jvm/java-6-sun-1.6.0.22/``, and
+that the ``include/linux`` directory contains the ``jni.h`` headers file
+and that the ``jre/lib/i386/client/`` directory contains the ``libjvm.so``
+file.
+
+
+.. note:: 
+   With Mac OS X you only have to set *macos* as the value for the
+   ``--with-java`` option to activate Java support. For example:
+
+   ::
+
+     $ ./configure --with-java=macos
+
+.. _js-support:
+
+JavaScript Support (Optional) 
+..............................................
+
+In order to activate the JavaScript support for ZOO-Kernel,
+the ``--with-js=yes`` configure option must be specified. If you are using
+a "Debian-like" GNU/Linux distribution then  dpkg will be used to
+detect if the required packages are installed and you don't have to
+specify anything here. The following command is only needed (assuming
+that js_api.h and libmozjs.so are found in default directories):
+
+
+::
+
+  $ ./configure --with-js=yes
+
+If you want to use a custom installation of `SpiderMonkey
+<https://developer.mozilla.org/en/SpiderMonkey>`__ , or if you are not
+using a Debian packaging  system, then you'll have to specify the
+directory where it is installed. For  instance, if SpiderMonkey is in
+``/usr/local/``, then the following command must be used:
+
+::
+
+  $ ./configure --with-js=/usr/local
+
+
+MapServer Support (Optional) 
+..............................................
+
+
+In order to activate the WMS, WFS and WCS output support using
+MapServer, the ``--with-mapserver`` option must be used. The path to
+``mapserver-config`` which is located in the source code of MapServer
+must also be set, using the following command:
+
+::
+
+  $ ./configure --with-mapserver=/path/to/your/mapserver_config/
+
+
+Read more about the :ref:`kernel-mapserver`.
+
+
+Orfeo Toolbox Support (Optional) 
+.....................................................
+
+In order to activate the optional Orfeo Toolbox support, the
+``--with-otb`` option must be used, using the following command:
+
+::
+
+  $ ./configure --with-otb=/path/to/your/otb/
+
+
+Read more about the :ref:`kernel-orfeotoolbox`.
+
+.. warning::
+    To build the Orfeo Toolbox support you will require ITK, the
+    default version of ITK is 4.5, in case you use another version,
+    please make sure to use the ``--with-itk-version`` to specificy
+    what is the version available on your system.
+
+SAGA GIS Support (Optional) 
+.....................................................
+
+
+In order to activate the optional SAGA GIS support, the *--with-saga* option must be used, using the following command:
+
+::
+
+  $ ./configure --with-saga=/path/to/your/saga/
+
+
+Read more about the :ref:`kernel-sagagis`.
+
+.. warning::
+    In case wx-config is not in your ``PATH`` please, make sure to use
+    the ``--with-wx-config``  to specify its location.
+
+Install ZOO-Services
+--------------------
+
+.. warning::
+    We present here a global installation procedure for basics
+    ZOO-Services, for details about automatic installation of services
+    provided by :ref:`kernel-orfeotoolbox` or :ref:`kernel-sagagis`,
+    please refer to there specific documentations.
+
+Depending on the programming language used to implement the
+ZOO-Services you want to install, you will need to build a
+Services Provider. In the case of *C* and *Fotran*, you would create a
+shared library exporting the functions corresponding to all the
+ZOO-Services provided by this Services Provider. In case of *Java*,
+you will need to build a Java Class. In any other programming
+language, you should simply have to install the ServiceProvider and
+the zcfg files.
+
+If building a Shared library or a Java class is required, then you
+should find a ``Makefile`` in the service directory which is
+responsible to help you build this Services Provider. So you should
+simply run the `make` command from the Service directory to generate
+the required file.
+
+Then you simply need to copy the content of the ``cgi-env`` directory
+in ``cgi-bin``.
+
+To install the ``ogr/base-vect-ops`` Services Provider, supposing that
+your ``cgi-bin`` directory is ``/usr/local/lib`` use the following
+commands:
+
+.. code::
+
+    cd zoo-project/zoo-services/ogr/base-vect-ops
+    make
+    cp cgi-env/*.* /usr/lib/cgi-bin
+
+.. note::
+    You may also run ``make install`` directly after ``make``.
+
+
+To install the hello-py Services Provider, use the following commands:
+
+.. code::
+
+    cd zoo-project/zoo-services/hello-py/
+    cp cgi-env/* /usr/lib/cgi-bin
+
+
+Testing your installation
+-------------------------
+
+To test your installation yous should first be able to run the
+following command from the ``cgi-bin`` directory:
+
+.. code::
+
+    ./zoo_loader.cgi "request=GetCapabilities&service=WPS"
+
+
Index: /branches/PublicaMundi_David-devel/docs/install/opensuse.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/install/opensuse.rst	(revision 696)
+++ /branches/PublicaMundi_David-devel/docs/install/opensuse.rst	(revision 696)
@@ -0,0 +1,53 @@
+.. _install-opensuse:
+
+Install on OpenSUSE
+===================
+
+:ref:`kernel_index` is maintained as a package in `OpenSUSE Build Service (OBS) <https://build.opensuse.org/package/show?package=zoo-kernel&project=Application%3AGeo>`__. RPM are thus provided for all versions of OpenSUSE Linux (11.2, 11.3, 11.4, Factory).
+
+Stable release
+----------------------
+
+Use the following instructions to install ZOO-Project latetst release on OpenSUSE distribution.
+
+One-click installer
+...................
+
+A one-click installer is available `here <http://software.opensuse.org/search?q=zoo-kernel&baseproject=openSUSE%3A11.4&lang=en&exclude_debug=true>`__. 
+For openSUSE 11.4, follow this direct `link <http://software.opensuse.org/ymp/Application:Geo/openSUSE_11.4/zoo-kernel.ymp?base=openSUSE%3A11.4&query=zoo-kernel>`__.
+
+Yast software manager
+.....................
+
+Add the `Application:Geo <http://download.opensuse.org/repositories/Application:/Geo/>`__ repository to the software repositories and then ZOO-Kernel can then be found in Software Management using the provided search tool.
+
+Command line (as root for openSUSE 11.4)
+........................................
+
+Install ZOO-Kernel package by yourself using the following command:
+
+.. code-block:: guess
+
+  zypper ar http://download.opensuse.org/repositories/Application:/Geo/openSUSE_11.4/
+  zypper refresh
+  zypper install zoo-kernel
+
+Developement version
+********************
+
+The latest development version of ZOO-Kernel can be found in OBS under the project `home:tzotsos <https://build.opensuse.org/project/show?project=home%3Atzotsos>`__. ZOO-Kernel packages are maintained and tested there before being released to the Application:Geo repository. Installation methods are identical as for the stable version. Make sure to use `this <http://download.opensuse.org/repositories/home:/tzotsos/>`__ repository instead.
+
+Command line (as root for openSUSE 11.4)
+********************************************
+
+Install latest ZOO-Kernel trunk version with the following command:
+
+.. code-block:: guess
+
+  zypper ar http://download.opensuse.org/repositories/home:/tzotsos/openSUSE_11.4/
+  zypper refresh
+  zypper install zoo-kernel
+  zypper install zoo-kernel-grass-bridge
+
+Note that there is the option of adding the zoo-wps-grass-bridge package. This option will automatically install grass7 (svn trunk).
+
Index: /branches/PublicaMundi_David-devel/docs/install/prerequisites.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/install/prerequisites.rst	(revision 696)
+++ /branches/PublicaMundi_David-devel/docs/install/prerequisites.rst	(revision 696)
@@ -0,0 +1,37 @@
+.. _install-prereq:
+
+Prerequisites
+=============
+
+Mandatory
+-----------------
+
+The following libraries are required to install :ref:`kernel_index`. Please make sure they are available on your system before anything else.
+
+- autoconf (`http://www.gnu.org/software/autoconf/ <http://www.gnu.org/software/autoconf/>`_)
+- gettext (`https://www.gnu.org/software/gettext/ <https://www.gnu.org/software/gettext/>`_ )
+- cURL (`http://curl.haxx.se <http://curl.haxx.se>`_ )
+- FastCGI (`http://www.fastcgi.com <http://www.fastcgi.com>`_ )
+- Flex & Bison (`http://flex.sourceforge.net/ <http://flex.sourceforge.net/>`_ | `http://www.gnu.org/software/bison/ <http://www.gnu.org/software/bison/>`_ )
+- libxml2 (  http://xmlsoft.org )
+- OpenSSL (  http://www.openssl.org )
+- GDAL (http://gdal.org/) 
+
+ .. warning::
+    It is mandatory to install every library listed above before compiling and installing ZOO-Kernel
+
+Optional
+-----------------
+
+You may also consider the following optional libraries:
+
+- MapServer (for ZOO-Kernel optional WMS, WFS and WCS support) (http://mapserver.org)
+- Python (  http://www.python.org )
+- PHP Embedded (for ZOO-Kernel optional PHP support) (http://www.php.net)
+- Java SDK (for ZOO-Kernel optional Java support) (http://java.sun.com)
+- SpiderMonkey (for ZOO-Kernel optional Javascript support) (http://www.mozilla.org/js/spidermonkey/)
+- SAGA GIS (for ZOO-Kernel optional SAGA support)(http://www.saga-gis.org/en/index.html/)
+- OrfeoToolbox (for ZOO-Kernel optional OTB support) (https://www.orfeo-toolbox.org/)
+- Insight Segmentation and Registration Toolkit  (http://itk.org/ITK/resources/software.html/>)
+- GRASS GIS (for using it through WPSGrassBridge) (http://grass.osgeo.org)
+
Index: /branches/PublicaMundi_David-devel/docs/install/windows.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/install/windows.rst	(revision 696)
+++ /branches/PublicaMundi_David-devel/docs/install/windows.rst	(revision 696)
@@ -0,0 +1,159 @@
+.. include:: <xhtml1-lat1.txt>
+.. include:: <xhtml1-symbol.txt>
+
+.. _install-onwindows:
+
+	     
+Installation on Windows |trade|
+====================
+
+Using OSGeo4W
+--------------
+
+Install OSGeo4W
+..........................................
+
+First download the OSGeo4W installer from  http://trac.osgeo.org/osgeo4w/, and install it with all the dependencies needed by your 
+WPS services such as GDAL for example.
+
+.. warning::
+    FastCGI, libxml, Python and cURL are mandatory
+
+Install ZOO4W
+..........................................
+
+Once OSGeo4W installed on your platform, you will need more GNU tools and libraries. `This package <http://www.zoo-project.org/dl/tool-win32.zip>`__  contains full dependencies required to compile on a WIN32 platform and this one contains `full runtime dependencies <http://www.zoo-project.org/dl/zoo-runtime.zip>`__ . Place it to your ``C:\OSGeo4W\bin``.
+
+Download the `binary version <http://www.zoo-project.org/dl/zoo_loader.cgi>`__  of ZOO Kernel for WIN32, then place it in the ``C:\OSGeo4W\bin`` directory. Don't forget to place the *main.cfg* file in the same directory, you can use a modified copy of  `this file <http://www.zoo-project.org/trac/browser/trunk/zoo-kernel/main.cfg>`__.
+
+Additionaly, the binary version of the OGR Services Provider available from `here <http://www.zoo-project.org/dl/zoo-services-win32.zip>`__ can be used directly. Place the two libraries with their respective .zcfg files in your local ``C:\OSGeo4W\bin`` directory to do so.
+
+Compile ZOO from source
+---------------------
+
+.. warning::
+   Ensure to first perform the :ref:`prerequisite steps <kernel-installation-prereq>` before compiling the ZOO Kernel.
+
+The following steps are for use with the Microsoft Visual Studio compiler (and tested with MSVC 2008).
+
+1. Make sure the gnuwin32 tools *bison.exe*  and *flex.exe* are found in your path.  You can download the GNUwin32 tools `here <http://www.zoo-project.org/dl/tool-win32.zip>`__.
+
+2. Modify the *nmake.opt* file to point to your local libraries.  You can find a modified nmake.opt that points to local libs `here <http://www.zoo-project.org/trac/attachment/ticket/27/nmake.opt>`__. 
+   You can also find a modified ``zoo-project\zoo-kernel\makefile.vc`` file `here <http://www.zoo-project.org/trac/attachment/ticket/27/makefile.vc>`__.
+   
+3. Execute:
+
+   ::
+   
+     nmake /f makefile.vc
+     
+4. A file *zoo_loader.cgi* should be created.  Note that if another file named *zoo_loader.cgi.manifest* is also created, you
+   will have to run another command:
+   
+   ::
+   
+     nmake /f makefile.vc embed-manifest
+     
+5. Copy the files *zoo_loader.cgi*  and *main.cfg* into your cgi-bin directory.
+
+6. Using the command prompt, test the zoo-kernel by executing the following command:
+
+   ::
+   
+     D:\ms4w\Apache\cgi-bin> zoo_loader.cgi
+     
+   which should display a message such as:
+   
+   ::
+   
+     Content-Type: text/xml; charset=utf-8
+     Status: 200 OK
+     
+     <?xml version="1.0" encoding="utf-8"?>
+     <ows:ExceptionReport xmlns:ows="http://www.opengis.net/ows/1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xsi:schemaLocation="http://www.opengis.net/ows/1.1 http://schemas.opengis.net/ows/1.1.0/owsExceptionReport.xsd" xml:lang="en-US" version="1.1.0">
+       <ows:Exception exceptionCode="MissingParameterValue">
+         <ows:ExceptionText>Parameter &lt;request&gt; was not specified</ows:ExceptionText>
+       </ows:Exception>
+     </ows:ExceptionReport>
+     
+7. Edit the *main.cfg* file so that it contains values describing your WPS service.  An example of such 
+   a file running on Windows is:
+   
+   ::
+   
+     [main]
+     encoding = utf-8
+     version = 1.0.0
+     serverAddress = http://localhost/
+     lang = en-CA
+     tmpPath=/ms4w/tmp/ms_tmp/
+     tmpUrl = /ms_tmp/
+     
+     [identification]
+     title = The Zoo WPS Development Server
+     abstract = Development version of ZooWPS. See http://www.zoo-project.org
+     fees = None
+     accessConstraints = none
+     keywords = WPS,GIS,buffer
+     
+     [provider]
+     providerName=Gateway Geomatics
+     providerSite=http://www.gatewaygeomatics.com
+     individualName=Jeff McKenna
+     positionName=Director
+     role=Dev
+     adressDeliveryPoint=1101 Blue Rocks Road
+     addressCity=Lunenburg
+     addressAdministrativeArea=False
+     addressPostalCode=B0J 2C0
+     addressCountry=ca
+     addressElectronicMailAddress=info@gatewaygeomatics.com
+     phoneVoice=False
+     phoneFacsimile=False
+     
+8. Open a web browser window, and execute a GetCapababilites request on your WPS service: http://localhost/cgi-bin/zoo_loader.cgi?request=GetCapabilities&service=WPS
+
+   The response should be displayed in your browser, such as:
+   
+   ::
+   
+     <wps:Capabilities xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 http://schemas.opengis.net/wps/1.0.0/wpsGetCapabilities_response.xsd" service="WPS" xml:lang="en-US" version="1.0.0">
+     <ows:ServiceIdentification>
+       <ows:Title>The Zoo WPS Development Server</ows:Title>
+       <ows:Abstract>
+         Development version of ZooWPS. See http://www.zoo-project.org
+       </ows:Abstract>
+       <ows:Keywords>
+         <ows:Keyword>WPS</ows:Keyword>
+         <ows:Keyword>GIS</ows:Keyword>
+         <ows:Keyword>buffer</ows:Keyword>
+       </ows:Keywords>
+       <ows:ServiceType>WPS</ows:ServiceType>
+       <ows:ServiceTypeVersion>1.0.0</ows:ServiceTypeVersion>
+       ...
+       
+Optionally Compile Individual Services
+.............................................................
+
+An example could be the *OGR base-vect-ops* provider located in the ``zoo-project\zoo-services\ogr\base-vect-ops`` directory.  
+
+1. First edit the *makefile.vc* located in that directory, and execute:
+
+   ::
+   
+     nmake /f makefile.vc
+     
+   Inside that same directory, the *ogr_service.zo* file should be created.
+   
+2. Copy all the files inside ``zoo-services\ogr\base-vect-ops\cgi-env`` into your ``cgi-bin`` directory
+
+3. Test this service provider through the following URL:
+
+http://localhost/cgi-bin/zoo_loader.cgi?request=Execute&service=WPS&version=1.0.0&Identifier=Buffer&DataInputs=BufferDistance=1@datatype=interger;InputPolygon=Reference@xlink:href=http%3A%2F%2Fwww.zoo-project.org%3A8082%2Fgeoserver%2Fows%3FSERVICE%3DWFS%26REQUEST%3DGetFeature%26VERSION%3D1.0.0%26typename%3Dtopp%3Astates%26SRS%3DEPSG%3A4326%26FeatureID%3Dstates.15
+   
+   The response displayed in your browser should contain:
+   
+   ::
+   
+     <wps:ProcessSucceeded>Service "Buffer" run successfully.</wps:ProcessSucceeded>
+
Index: /branches/PublicaMundi_David-devel/docs/services/process-profiles.rst
===================================================================
--- /branches/PublicaMundi_David-devel/docs/services/process-profiles.rst	(revision 695)
+++ /branches/PublicaMundi_David-devel/docs/services/process-profiles.rst	(revision 696)
@@ -2,5 +2,5 @@
     
 Process profiles registry
-================
+=========================
 
 WPS Services belonging to the same Services provider often share the
@@ -9,5 +9,11 @@
 this may be a waste of time to write them all.
 
-:ref:`ZOO-Kernel <kernel_index>` is able to handle metadata inheritance from `rev. 607 <http://www.zoo-project.org/trac/changeset/607>`__, and this solves the issue of writing many ZCFG with same input and output. A registry can be loaded (before any other ZCFG files) and contain a set of Process Profiles organized in hierarchic levels according to the following rules:
+:ref:`ZOO-Kernel <kernel_index>` is able to handle metadata
+inheritance from `rev. 607
+<http://www.zoo-project.org/trac/changeset/607>`__, and this solves
+the issue of writing many ZCFG with same input and output. A registry
+can be loaded (before any other ZCFG files) and contain a set of
+Process Profiles organized in hierarchic levels according to the
+following rules:
 
   * *Concept*: The higher level in the hierarchy. *Concepts* are basic text files containing an abstract description of a WPS Service.
@@ -171,2 +177,3 @@
         </Supported>
     </DataOutputs>
+
