[mapserver-commits] r8151 - trunk/docs/development/rfc
svn at osgeo.org
svn at osgeo.org
Mon Dec 1 00:33:33 EST 2008
Author: hobu
Date: 2008-12-01 00:33:33 -0500 (Mon, 01 Dec 2008)
New Revision: 8151
Modified:
trunk/docs/development/rfc/ms-rfc-1.txt
trunk/docs/development/rfc/ms-rfc-10.txt
trunk/docs/development/rfc/ms-rfc-11.txt
trunk/docs/development/rfc/ms-rfc-12.txt
trunk/docs/development/rfc/ms-rfc-13.txt
trunk/docs/development/rfc/ms-rfc-14.txt
trunk/docs/development/rfc/ms-rfc-15.txt
trunk/docs/development/rfc/ms-rfc-16.txt
trunk/docs/development/rfc/ms-rfc-17.txt
trunk/docs/development/rfc/ms-rfc-18.txt
trunk/docs/development/rfc/ms-rfc-19.txt
trunk/docs/development/rfc/ms-rfc-2.txt
trunk/docs/development/rfc/ms-rfc-21.txt
trunk/docs/development/rfc/ms-rfc-22a.txt
trunk/docs/development/rfc/ms-rfc-23.txt
trunk/docs/development/rfc/ms-rfc-24.txt
trunk/docs/development/rfc/ms-rfc-25.txt
trunk/docs/development/rfc/ms-rfc-26.txt
trunk/docs/development/rfc/ms-rfc-27.txt
trunk/docs/development/rfc/ms-rfc-28.txt
trunk/docs/development/rfc/ms-rfc-29.txt
trunk/docs/development/rfc/ms-rfc-3.txt
trunk/docs/development/rfc/ms-rfc-30.txt
trunk/docs/development/rfc/ms-rfc-31.txt
trunk/docs/development/rfc/ms-rfc-32.txt
trunk/docs/development/rfc/ms-rfc-33.txt
trunk/docs/development/rfc/ms-rfc-34.txt
trunk/docs/development/rfc/ms-rfc-35.txt
trunk/docs/development/rfc/ms-rfc-36.txt
trunk/docs/development/rfc/ms-rfc-37.txt
trunk/docs/development/rfc/ms-rfc-38.txt
trunk/docs/development/rfc/ms-rfc-39.txt
trunk/docs/development/rfc/ms-rfc-4.txt
trunk/docs/development/rfc/ms-rfc-40.txt
trunk/docs/development/rfc/ms-rfc-41.txt
trunk/docs/development/rfc/ms-rfc-42.txt
trunk/docs/development/rfc/ms-rfc-43.txt
trunk/docs/development/rfc/ms-rfc-44.txt
trunk/docs/development/rfc/ms-rfc-45.txt
trunk/docs/development/rfc/ms-rfc-46.txt
trunk/docs/development/rfc/ms-rfc-47.txt
trunk/docs/development/rfc/ms-rfc-48.txt
trunk/docs/development/rfc/ms-rfc-5.txt
trunk/docs/development/rfc/ms-rfc-6.txt
trunk/docs/development/rfc/ms-rfc-7.1.txt
trunk/docs/development/rfc/ms-rfc-7.txt
trunk/docs/development/rfc/ms-rfc-8.txt
trunk/docs/development/rfc/ms-rfc-9.txt
Log:
add Ids to RFCs
Modified: trunk/docs/development/rfc/ms-rfc-1.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-1.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-1.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -8,7 +8,8 @@
:Author: Frank Warmerdam, Independent
:Contact: warmerdam at pobox.com
:Last Edited: $Date$
-:Status: Superseded by RFC 23
+:Status: Superseded by :ref:`rfc23`
+:Id: $Id$
Summary
Modified: trunk/docs/development/rfc/ms-rfc-10.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-10.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-10.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -12,6 +12,7 @@
:Author: Steve Lime
:Contact: sdlime at comcast.net
:Status: passed
+:Id: $Id$
Abstract
--------
Modified: trunk/docs/development/rfc/ms-rfc-11.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-11.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-11.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Author: Stephen Lime
:Contact: sdlime at comcast.net
:Status: passed
+:Id: $Id$
Overview
--------
Modified: trunk/docs/development/rfc/ms-rfc-12.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-12.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-12.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -7,6 +7,8 @@
:Date: 2006/02/28
:Author: Umberto Nicoletti
:Contact: umberto.nicoletti at gmail.com
+:Status: Draft
+:Id: $Id$
Overview
--------
Modified: trunk/docs/development/rfc/ms-rfc-13.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-13.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-13.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -8,9 +8,9 @@
:Author: Yewondwossen Assefa
:Contact: yassefa at dmsolutions.ca
:Status: passed
+:Id: $Id$
-
Overview
--------
Modified: trunk/docs/development/rfc/ms-rfc-14.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-14.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-14.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -9,6 +9,7 @@
:Contact: steve.lime at DNR.STATE.MN.US
:Status: Complete
:Version: MapServer 4.10
+:Id: $Id$
Description: Current it is possible to have features with pixel coordinates
and to draw them by setting TRANSFORM FALSE in a layer definition. However
Modified: trunk/docs/development/rfc/ms-rfc-15.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-15.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-15.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Last Edited: $Date$
:Status: Draft
:Version: Not assigned yet
+:Id: $Id$
1. Overview
-----------
Modified: trunk/docs/development/rfc/ms-rfc-16.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-16.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-16.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Last Edited: May 22, 2006
:Status: adopted and implemented
:Version: MapServer 4.10
+:Id: $Id$
Purpose
--------
Modified: trunk/docs/development/rfc/ms-rfc-17.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-17.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-17.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Last Edited: 2007/07/18
:Status: Adopted (2007/07/18) - Implementation completed (2007/07/23)
:Version: MapServer 5.0
+:Id: $Id$
Purpose
--------
Modified: trunk/docs/development/rfc/ms-rfc-18.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-18.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-18.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -24,10 +24,10 @@
MapServer will be extended to allow the use of encrypted passwords as part
of the CONNECTION string for the following layer types:
-* Oracle Spatial
-* PostGIS
-* ESRI SDE
-* OGR
+* :ref:`Oracle Spatial <oci>`
+* :ref:`PostGIS <input_postgis>`
+* :ref:`ESRI SDE <arcsde>`
+* :ref:`OGR <ogr>`
The Tiny Encryption Algorithm (TEA) at
http://www.simonshepherd.supanet.com/tea.htm will be used for the
Modified: trunk/docs/development/rfc/ms-rfc-19.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-19.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-19.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -9,6 +9,7 @@
:Contact: steve.lime at DNR.STATE.MN.US
:Status: Passed (in process)
:Version: MapServer 5.0
+:Id: $Id$
Description: Presently MapServer supports binding of label and style
properties for a few select attributes (e.g. angle). However, it is
Modified: trunk/docs/development/rfc/ms-rfc-2.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-2.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-2.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Last Edited: $Date$
:Status: Completed
:Version: MapServer 4.8
+:Id: $Id$
Description: Developing inline features or shapes within MapScript can be a
bit cumbersome. One alternative would be to allow users to define feature
Modified: trunk/docs/development/rfc/ms-rfc-21.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-21.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-21.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -9,6 +9,7 @@
:Contact: warmerdam at pobox.com
:Status: adopted
:Version: MapServer 5.0
+:Id: $Id$
Overview
--------
Modified: trunk/docs/development/rfc/ms-rfc-22a.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-22a.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-22a.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,28 +10,45 @@
:Last Edited: 2007/06/24
:Status: Discussion Draft
:Version: Mapserver 5.0
+:Id: $Id$
1. Overview
-----------
-Currently the various query operations involve multiple accesses to the data providers which may cause a significant performance impact depending on the providers. In the first phase all of the features in the given search area are retrieved and the index of the relevant shapes are stored in the result cache. In the second phase the features in the result cache are retrieved form the provider one by one. Retaining the shapes in the memory we could eliminate the need of the subsequent accesses to the providers and increase the overall performance of the query.
-Implementing the cache requires a transformation of the data between the data provider and the client. From this aspect it is desirable to provide a framework to implement this transformation in a higher level of abstraction.
+Currently the various query operations involve multiple accesses to the data
+providers which may cause a significant performance impact depending on the
+providers. In the first phase all of the features in the given search area are
+retrieved and the index of the relevant shapes are stored in the result cache.
+In the second phase the features in the result cache are retrieved form the
+provider one by one. Retaining the shapes in the memory we could eliminate the
+need of the subsequent accesses to the providers and increase the overall
+performance of the query. Implementing the cache requires a transformation of
+the data between the data provider and the client. From this aspect it is
+desirable to provide a framework to implement this transformation in a higher
+level of abstraction.
2. Purpose
----------
-The main purpose of this RFC is to implement a feature cache and retain the shapes in the memory for the further retrievals during a query operation.
-However I would also want to create a mechanism so that a layer could use another layer as a data source. This outer layer could apply transformations on the shapes coming from the base layer or even retain the shapes in the memory for the subsequent fetches.
-Here are some other examples where this framework would provide a solution:
+The main purpose of this RFC is to implement a feature cache and retain the
+shapes in the memory for the further retrievals during a query operation.
+However I would also want to create a mechanism so that a layer could use
+another layer as a data source. This outer layer could apply transformations
+on the shapes coming from the base layer or even retain the shapes in the
+memory for the subsequent fetches. Here are some other examples where this
+framework would provide a solution:
a. Constructing geometries based on feature attributes
b. Modifying the geometries or the feature attribute values
c. Geometry transformations (like GEOS operations)
d. Feature cache
- e. Providing default layer style based on external style information, or attribute based styling
+ e. Providing default layer style based on external style information, or
+ attribute based styling
f. Providing custom data filters
-Setting up a proper layer hierarchy one can solve pretty complex issues without the need of creating additional (eg. mapscript) code. Later on - as a live example - I'll show up the solution of the following scenario:
+Setting up a proper layer hierarchy one can solve pretty complex issues
+without the need of creating additional (eg. mapscript) code. Later on - as a
+live example - I'll show up the solution of the following scenario:
a. The user will select one or more shapes in one layer (by attibute selection in this case).
b. Cascaded transformations will be applied on the selected shapes (I'll use the GEOS convexhull and buffer operations)
Modified: trunk/docs/development/rfc/ms-rfc-23.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-23.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-23.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -9,6 +9,7 @@
:Contact: warmerdam at pobox.com, sdlime at dnr.state.mn.us
:Last Edited: 2008/01/25
:Status: Adopted
+:Id: $Id$
Summary
-----------
@@ -18,6 +19,7 @@
MapServer project - both technical and non-technical.
Examples of PSC management responsibilities:
+
* setting the overall development road map
* developing technical standards and policies (e.g. coding standards,
file naming conventions, etc...)
@@ -124,26 +126,34 @@
-----------------------------
Guiding Development
- Members should take an active role guiding the development of new features
- they feel passionate about. Once a change request has been accepted
- and given a green light to proceed does not mean the members are free of
- their obligation. PSC members voting "+1" for a change request are
- expected to stay engaged and ensure the change is implemented and
- documented in a way that is most beneficial to users. Note that this
- applies not only to change requests that affect code, but also those
- that affect the web site, technical infrastructure, policies and standards.
+...............................
+
+Members should take an active role guiding the development of new features
+they feel passionate about. Once a change request has been accepted
+and given a green light to proceed does not mean the members are free of
+their obligation. PSC members voting "+1" for a change request are
+expected to stay engaged and ensure the change is implemented and
+documented in a way that is most beneficial to users. Note that this
+applies not only to change requests that affect code, but also those
+that affect the web site, technical infrastructure, policies and standards.
+
IRC Meeting Attendance
- PSC members are expected to participate in pre-scheduled IRC development
- meetings. If known in advance that a member cannot attend a meeting,
- the member should let the meeting organizer know via e-mail.
+...............................
+
+PSC members are expected to participate in pre-scheduled IRC development
+meetings. If known in advance that a member cannot attend a meeting,
+the member should let the meeting organizer know via e-mail.
+
Mailing List Participation
- PSC members are expected to be active on both the mapserver-users
- and mapserver-dev mailing lists, subject to open source mailing list
- etiquette. Non-developer members of the PSC are not expected to respond
- to coding level questions on the developer mailing list, however they
- are expected to provide their thoughts and opinions on user level
- requirements and compatibility issues when RFC discussions take place.
+...............................
+PSC members are expected to be active on both the mapserver-users
+and mapserver-dev mailing lists, subject to open source mailing list
+etiquette. Non-developer members of the PSC are not expected to respond
+to coding level questions on the developer mailing list, however they
+are expected to provide their thoughts and opinions on user level
+requirements and compatibility issues when RFC discussions take place.
+
Bootstrapping
-----------------
Modified: trunk/docs/development/rfc/ms-rfc-24.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-24.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-24.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -12,8 +12,8 @@
:Version: Mapserver 5.0
:Tracker: http://trac.osgeo.org/mapserver/ticket/2032
:Tracker 3.2: http://trac.osgeo.org/mapserver/ticket/2442
+:Id: $Id$
-
.. sectnum::
.. contents:: Table of Contents
Modified: trunk/docs/development/rfc/ms-rfc-25.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-25.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-25.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -9,6 +9,7 @@
:Contact: steve.lime at DNR.STATE.MN.US
:Status: Draft
:Version:
+:Id: $Id$
Overview
========
Modified: trunk/docs/development/rfc/ms-rfc-26.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-26.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-26.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Last Edited: $Date$
:Status: Implemented
:Version: MapServer 5.0
+:Id: $Id$
Mapserver terminology is mostly good and consistent, with a few exceptions.
The two that generate the most confusion and TRANSPARENCY (layerObj) and
Modified: trunk/docs/development/rfc/ms-rfc-27.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-27.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-27.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Last Edited: 2007/06/29
:Status: Adopted (2007/05/25) - Implementation completed (2007/07/05)
:Version: MapServer 5.0
+:Id: $Id$
Overview
--------
Modified: trunk/docs/development/rfc/ms-rfc-28.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-28.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-28.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Last Edited: 2007/08/24
:Status: Adopted (2007-06-29) - Implementation completed (2007/07/06)
:Version: MapServer 5.0
+:Id: $Id$
Overview
--------
Modified: trunk/docs/development/rfc/ms-rfc-29.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-29.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-29.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Last Edited: 2007/07/31
:Status: Adopted (2007/07/05) - Completed (2007/07/09)
:Version: MapServer 5.0
+:Id: $Id$
Overview
--------
Modified: trunk/docs/development/rfc/ms-rfc-3.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-3.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-3.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,10 +10,8 @@
:Last Edited: $Date$
:Status: Adopted
:Version: MapServer 4.8
+:Id: $Id$
-
-
-
Abstract Solution
-----------------
Modified: trunk/docs/development/rfc/ms-rfc-30.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-30.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-30.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Last Edited: 2007/09/05
:Status: Draft
:Version: MapServer 5.2
+:Id: $Id$
Overview
--------
Modified: trunk/docs/development/rfc/ms-rfc-31.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-31.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-31.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -8,7 +8,8 @@
:Author: Steve Lime
:Contact: Steve.Lime at DNR.State.MN.US
:Version: 5.0
-:Status: Accepted (2007/06/22)
+:Status: Accepted (2007/06/22) Implemented
+:Id: $Id$
Description: This RFC addresses the ability of the MapServer tokenizer
(in maplexer.l and mapfile.c) to work from strings as well as files. A
@@ -100,9 +101,9 @@
default behavior but should be enabled explicitly. Enabling this feature
would happen by way of a new parameter within the webObj- URLCONFIG [pattern],
with a default of NULL. The pattern would be a regular expression that would
- be applied against any map_* variables. So, one could limit changes to just
- the scalebar object with URLCONFIG 'scalebar' or allow more with
- URLCONFIG '.'. The default would not to be allow any URL configuration.
+be applied against any map_* variables. So, one could limit changes to just
+the scalebar object with URLCONFIG 'scalebar' or allow more with
+URLCONFIG '.'. The default would not to be allow any URL configuration.
Backwards Compatibility
~~~~~~~~~~~~~~~~~~~~~~~
@@ -191,7 +192,7 @@
Bug IDs
~~~~~~~
-2143
+http://trac.osgeo.org/mapserver/ticket/2143
Voting history
~~~~~~~~~~~~~~
Modified: trunk/docs/development/rfc/ms-rfc-32.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-32.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-32.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -8,6 +8,7 @@
:Author: Steve Lime, John Novak
:Contact: Steve.Lime at DNR.State.MN.US
:Status: Pending
+:Id: $Id$
Overview
~~~~~~~~
@@ -34,6 +35,9 @@
is really just a gdImagePtr we can use current code that renders to a GD image
along side any AGG routines.
+.. note::
+
+ See :ref:`agg` for more information.
Technical Solution
~~~~~~~~~~~~~~~~~~
@@ -60,14 +64,14 @@
core. The following files are to be modified to add AGG specific processing
blocks that are basically straight copies of GD support:
-mapdraw.c
-mapdrawgdal.c
-maperror.c
-maplegend.c
-mapoutput.c
-mapraster.c
-mapresample.c
-maputil.c
+- mapdraw.c
+- mapdrawgdal.c
+- maperror.c
+- maplegend.c
+- mapoutput.c
+- mapraster.c
+- mapresample.c
+- maputil.c
No new functionality is added to these files, rather just else-if blocks.
Modified: trunk/docs/development/rfc/ms-rfc-33.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-33.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-33.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Last Edited: 2007/07/09
:Status: draft
:Version: MapServer 5.0
+:Id: $Id$
Overview
~~~~~~~~
Modified: trunk/docs/development/rfc/ms-rfc-34.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-34.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-34.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -9,6 +9,7 @@
:Contact: dmorissette at mapgears.com
:Last Edited: 2007/07/19
:Status: Adopted (2007/07/19)
+:Id: $Id$
Overview
--------
Modified: trunk/docs/development/rfc/ms-rfc-35.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-35.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-35.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -9,6 +9,7 @@
:Contact: warmerdam at pobox.com, dmorissette at mapgears.com
:Last Edited: 2007/12/07
:Status: Withdrawn (2007/12/07)
+:Id: $Id$
Overview
--------
Modified: trunk/docs/development/rfc/ms-rfc-36.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-36.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-36.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -9,6 +9,7 @@
:Contact: steve.lime at dnr.state.mn.us
:Last Edited: 2007/10/23
:Status: Development
+:Id: $Id$
Overview
--------
Modified: trunk/docs/development/rfc/ms-rfc-37.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-37.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-37.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -9,12 +9,8 @@
:Revision: $Revision$
:Date: $Date$
:Status: Draft
+:Id: $Id$
-.. contents::
- :depth: 3
- :backlinks: top
-
-
==============================================================================
Purpose
==============================================================================
Modified: trunk/docs/development/rfc/ms-rfc-38.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-38.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-38.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -5,20 +5,13 @@
******************************************************************************
:Author: Howard Butler
- Hobu, Inc
- 1528 Ranier Dr.
- Iowa City, IA 52246
-:Contact: hobu.inc at gmail.com
+:Contact: hobu.inc at gmail.com
:Revision: $Revision$
:Date: $Date$
:Status: Implemented
:Version: 5.2
+:Id: $Id$
-.. contents::
- :depth: 3
- :backlinks: top
-
-
==============================================================================
Purpose
==============================================================================
Modified: trunk/docs/development/rfc/ms-rfc-39.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-39.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-39.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -9,8 +9,8 @@
:Contact: assefa at dmsolutions.ca
:Status: Adopted
:Version: MapServer 5.2
+:Id: $Id$
-
Overview
--------
Modified: trunk/docs/development/rfc/ms-rfc-4.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-4.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-4.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Last Edited: $Date$
:Status: adopted
:Version: MapServer 4.8
+:Id: $Id$
Overview
--------
Modified: trunk/docs/development/rfc/ms-rfc-40.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-40.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-40.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Last Edited: 2007/12/03
:Status: Implemented
:Version: MapServer 5.4
+:Id: $Id$
Overview
--------
Modified: trunk/docs/development/rfc/ms-rfc-41.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-41.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-41.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -9,6 +9,7 @@
:Contact: warmerdam at pobox.com
:Status: Adopted
:Version: 5.2
+:Id: $Id$
Overview
--------
Modified: trunk/docs/development/rfc/ms-rfc-42.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-42.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-42.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Last Edited: 2008/04/01
:Status: Adopted 2008/04/01 - Implementation completed
:version: MapServer 5.2
+:Id: $Id$
==============================================================================
Overview
Modified: trunk/docs/development/rfc/ms-rfc-43.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-43.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-43.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Last Edited: 2008/05/02
:Status: Adopted on 2008/04/29 - Completed
:Version: MapServer 5.2
+:Id: $Id$
Overview
--------
Modified: trunk/docs/development/rfc/ms-rfc-44.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-44.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-44.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,8 +10,8 @@
:Last Edited: 2008/08/19
:Status: Draft
:Version:
+:Id: $Id$
-
:ref:`rfc31` introduced a new syntax for modifying :ref:`mapfiles <mapfile>`
via URL. Object parameters could specified together in mapfile snippets making
it easier to make changes with far fewer characters. At the same time access
Modified: trunk/docs/development/rfc/ms-rfc-45.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-45.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-45.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -9,6 +9,7 @@
:Contact: Steve.Lime at DNR.State.MN.US
:Status: Draft
:Version: MapServer 5.4
+:Id: $Id$
(*partiallly derived in part from a document prepared by Håvard and
discussions with other developers working on cartographic output*)
Modified: trunk/docs/development/rfc/ms-rfc-46.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-46.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-46.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -9,13 +9,8 @@
:Contact: hobu.inc at gmail.com
:Last Edited: $Date$
:Status: Proposed
+:Id: $Id$
-
-.. contents::
- :depth: 3
- :backlinks: top
-
-
==============================================================================
Purpose
==============================================================================
Modified: trunk/docs/development/rfc/ms-rfc-47.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-47.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-47.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Last Edited: 2008/10/15
:Status: Adopted on 2008-10-15 - Completed
:Version: MapServer 5.4
+:Id: $Id$
Overview
--------
Modified: trunk/docs/development/rfc/ms-rfc-48.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-48.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-48.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -9,8 +9,8 @@
:Contact: Steve.Lime at DNR.State.MN.US, thomas.bonfort at camptocamp.com
:Status: Draft
:Version: MapServer 5.4
+:Id: $Id$
-
Summary
------------------------------------------------------------------------------
Modified: trunk/docs/development/rfc/ms-rfc-5.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-5.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-5.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Last Edited: $Date$
:Status: Adopted
:Version: MapServer 4.8
+:Id: $Id$
Purpose
-------
Modified: trunk/docs/development/rfc/ms-rfc-6.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-6.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-6.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -9,6 +9,7 @@
:Contact: bill at binko.net
:Last Edited: $Date$
:Status: Proposed
+:Id: $Id$
Description: This proposal addresses the need to be able to easily
map continuous feature values to a continuous range of colors. This RFC is
Modified: trunk/docs/development/rfc/ms-rfc-7.1.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-7.1.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-7.1.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -9,6 +9,7 @@
:Contact: warmerdam at pobox.com and tomkralidis at hotmail.com
:Last Edited: $Date$
:Status: Adopted
+:Id: $Id$
.. note::
Modified: trunk/docs/development/rfc/ms-rfc-7.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-7.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-7.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -7,9 +7,12 @@
:Contact: warmerdam at pobox.com
:Last Edited: $Date$
:Status: Adopted
+:Id: $Id$
-(Note: this RFC is superseded by :ref:`RFC 7.1 <rfc7.1>`)
+.. note::
+ This RFC is superseded by :ref:`RFC 7.1 <rfc7.1>`
+
Purpose
-------
Modified: trunk/docs/development/rfc/ms-rfc-8.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-8.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-8.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -10,6 +10,7 @@
:Last Edited: $Date$
:Status: adopted
:Version: MapServer 4.8
+:Id: $Id$
Purpose
--------
Modified: trunk/docs/development/rfc/ms-rfc-9.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-9.txt 2008-12-01 02:45:06 UTC (rev 8150)
+++ trunk/docs/development/rfc/ms-rfc-9.txt 2008-12-01 05:33:33 UTC (rev 8151)
@@ -9,6 +9,7 @@
:Contact: steve.lime at DNR.STATE.MN.US
:Status: Implemented
:Version: MapServer 4.10
+:Id: $Id$
Description: A the moment processing of attributes exposed via query templates
is limited to a couple forms of escaping. This is too limiting. It would be
More information about the mapserver-commits
mailing list