[mapserver-commits] r12633 - trunk/docs/en/ogc

[svn at osgeo.org]

Author: dmorissette
Date: 2011-10-06 19:55:31 -0700 (Thu, 06 Oct 2011)
New Revision: 12633

Modified:
   trunk/docs/en/ogc/wms_server.txt
Log:
Small corrections to new cascaded GetLegendGraphics section (#3923)

Modified: trunk/docs/en/ogc/wms_server.txt
===================================================================
--- trunk/docs/en/ogc/wms_server.txt	2011-10-06 18:35:40 UTC (rev 12632)
+++ trunk/docs/en/ogc/wms_server.txt	2011-10-07 02:55:31 UTC (rev 12633)
@@ -9,7 +9,7 @@
 
 :Author: Jeff McKenna
 :Contact: jmckenna at gatewaygeomatics.com
-:Last Updated: 2010-10-01
+:Last Updated: 2011-10-06
 
 .. contents:: Table of Contents
     :depth: 2
@@ -1478,7 +1478,7 @@
 Cascading WMS Requests
 ----------------------
 
-Currently, there are 3 requests that support wms cascading:
+Currently, there are 3 requests that support WMS cascading:
 
 - GetMap
 
@@ -1490,15 +1490,14 @@
   legend was returned using the layer classes. To preserve that behavior, a
   GetLegendGraphic request will be cascaded only **if**:
 
-  1. The request is enabled via the *_enable_request metadatas.  
+  1. The GetLegendGraphic request is enabled via the *_enable_request metadata.
 
-  2. The layer does not contain any class with the name property. ie:
+  2. The layer does not contain any class with the name property set. ie:
 
   .. code-block:: mapfile
 
      CLASS
-       NAME "near white"
-       EXPRESSION ([red] > 200 AND [green] > 200 AND [blue] > 200)
+       NAME "Parks"
        STYLE
          COLOR 0 255 0
        END
@@ -1508,8 +1507,8 @@
 
 .. note::
 
-   If you know that the external WMS server *do not* support a wms request,
-   you should disable it manually for your layer using the
+   If you know that the remote WMS server *does not* support a given WMS 
+   request, you should disable this request explicitly for your layer using the
    (ows/wms)_enable_request metadata. Otherwise, you will simply get the
    XML exception from the cascaded server.