[mapserver-commits] r10595 - trunk/docs/en/development/rfc

[svn at osgeo.org]

Author: warmerdam
Date: 2010-10-12 08:42:20 -0700 (Tue, 12 Oct 2010)
New Revision: 10595

Modified:
   trunk/docs/en/development/rfc/ms-rfc-62.txt
Log:
Added note on GetCapabilities changes, and clarify wfs_formats a bit.


Modified: trunk/docs/en/development/rfc/ms-rfc-62.txt
===================================================================
--- trunk/docs/en/development/rfc/ms-rfc-62.txt	2010-10-12 15:04:34 UTC (rev 10594)
+++ trunk/docs/en/development/rfc/ms-rfc-62.txt	2010-10-12 15:42:20 UTC (rev 10595)
@@ -27,7 +27,8 @@
 
 2) If the wfs_formats metadata exists on the layer, it should be a comma
 delimited list of output formats permitted for this layer.  Any other will not
-be selectable with the OUTPUTFORMAT parameter to GetFeature.
+be selectable with the OUTPUTFORMAT parameter to GetFeature.  The value in
+this parameter will be the "NAME" from the OUTPUTFORMAT declaration.
 
 3) The existing GML2/GML3 generation support will be retained in essentially
 it's current form within mapwfs.c, but it's preamble and postfix generation
@@ -38,7 +39,19 @@
 generated by a call to msReturnTemplateQuery() which already supports output
 via the new template engine (RFC 36) as well as call outs for other renderers.
 
+WFS GetCapabilities Changes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
+In WFS 1.1.0 mode the GetCapabilities document lists the set of formats
+allowed for the OUTPUTFORMAT parameter.  As part of this development it
+will be extended to show all the legal output formats for all of the
+layers (based on wfs_formats metadata).  
+
+Note that in WFS 1.0.0 there is no mechanism to discover supported formats
+automatically, and even in WFS 1.1.0 there is no mechanism to discover
+which formats are available for which layers.  
+
+
 outputFormatObj
 ~~~~~~~~~~~~~~~