<?xml version="1.0"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:dc="http://purl.org/dc/elements/1.1/"
         xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
         xmlns="http://purl.org/rss/1.0/">




    



<channel rdf:about="http://mapserver.gis.umn.edu/development/rfc/RSS">
  <title>RFCs</title>
  <link>http://mapserver.gis.umn.edu</link>
  
  <description>
    
       A MapServer RFC describes a major change in the technological underpinnings of MapServer, major additions to functionality, or changes in the direction of the project.
       
  </description>
  
  
  
            <syn:updatePeriod>weekly</syn:updatePeriod>
            <syn:updateFrequency>1</syn:updateFrequency>
            <syn:updateBase>2005-11-19T22:08:21Z</syn:updateBase>
        
  
  <image rdf:resource="http://mapserver.gis.umn.edu/logo.jpg"/>

  <items>
    <rdf:Seq>
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-1"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-2"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-3"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-4"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-5"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-6"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-7"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-7.1"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-8"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-9"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-10"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-12"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-11"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-13"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-14"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-15"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-16"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-17"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-18"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-19"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-21"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-22a"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-23"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-24-FIRSTDRAFT"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-24"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-25"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-26"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-27"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-28"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-29"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-30"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-31"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-32"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-33"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-34"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-35"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-36"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-37"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-38"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-39"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-40"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-41"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-42"/>
        
        
            <rdf:li rdf:resource="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-43"/>
        
    </rdf:Seq>
  </items>

</channel>

    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-1">        <title>MS RFC 1: Technical Steering Committee Guidelines</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-1</link>        <description>This document describes how the MapServer Technical Steering Committee determines membership, and makes decisions on MapServer technical issues.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>FrankW</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-09-13T14:59:08Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-2">        <title>MS RFC 2: Creating line features and/or shapes using WKT</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-2</link>        <description>Developing inline features or shapes within MapScript can be a 
bit cumbersome.  One alternative would be to allow users to define feature 
using the Well-Known Text format.  The proposed solution would allow users 
to use this format:</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>sdlime</dc:creator>        <dc:rights></dc:rights>                <dc:date>2006-01-05T22:17:44Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-3">        <title>MS RFC 3: Layer Plug-in Architecture</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-3</link>        <description>Change current layer infrastructure from switch based
static solution to the virtual table based dynamic solution.  The main
objectives for this proposal are cleaning and simplifying code and
provide a robust architecture to implement dynamic plug-in API for
external layer providers.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>jaa</dc:creator>        <dc:rights></dc:rights>                <dc:date>2005-12-14T22:33:52Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-4">        <title>MS RFC 4: MapServer Raster Resampling</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-4</link>        <description>Additional resampling kernels will be implemented in the MapServer GDAL
raster resampler code including "averaging", "bilinear" and "cubic". </description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>FrankW</dc:creator>        <dc:rights></dc:rights>                <dc:date>2005-12-17T17:06:45Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-5">        <title>MS RFC 5: MapServer Horizon Reprojection Improvements</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-5</link>        <description>To provide a practical solution to MapServer Bug 411 - Clipping Issue
with Ortho Projection:</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>FrankW</dc:creator>        <dc:rights></dc:rights>                <dc:date>2006-11-30T14:41:43Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-6">        <title>MS RFC 6: Color Range Mapping of Continuous Feature Values</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-6</link>        <description>This proposal addresses the need to be able to easily
map continuous feature values to a continuous range of colors.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>bbinko</dc:creator>        <dc:rights></dc:rights>                <dc:date>2005-12-14T19:36:36Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-7">        <title>MS RFC 7: MapServer CVS Commit Management</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-7</link>        <description>Procedures for selecting CVS committers, and rules for committers. </description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>FrankW</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-07-02T13:37:18Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-7.1">        <title>MS RFC 7.1: MapServer SVN Commit Management</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-7.1</link>        <description>To formalize SVN commit access, and specify some guidelines for SVN committers.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>tomkralidis</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-07-02T13:32:18Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-8">        <title>MS RFC 8: Pluggable External Feature Layer Providers</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-8</link>        <description>Provide a way to user actually plug-in
external third party feature layer providers to the mapserver at run time.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>jaa</dc:creator>        <dc:rights></dc:rights>                <dc:date>2005-12-14T22:33:25Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-9">        <title>MS RFC 9: Item tag for query templates</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-9</link>        <description>A the moment processing of attributes exposed via query templates is limited to a couple forms of escaping. This RFC describes a simple scheme to allow for extended processing of attributes before sending to the a users.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>sdlime</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-03-13T18:28:47Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-10">        <title>MS RFC 10: Joining the Open Source Geospatial Foundation</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-10</link>        <description>The Open Source Geospatial Foundation (OSGeo) presents a unique opportunity 
for MapServer in that it can provide an umbrella organization that can 
provide benefits and possibilities that a project by itself simply cannot 
provide.  This RFC will outline what those benefits can be to the project, 
define MapServer's role in participating, and describe the unique process of 
how we propose to decide to join. </description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>hobu</dc:creator>        <dc:rights></dc:rights>                <dc:date>2006-02-21T16:04:26Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-12">        <title>MS RFC 12: C code Unit tests</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-12</link>        <description>Implement unit testing for the c portion of mapserver code.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>unicoletti</dc:creator>        <dc:rights></dc:rights>                <dc:date>2006-03-03T10:55:16Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-11">        <title>MS RFC 11: Support for Curved Labels</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-11</link>        <description>This RFC addresses one of the most frequently requested features for MapServer- labels that follow curved linear features.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>sdlime</dc:creator>        <dc:rights></dc:rights>                <dc:date>2006-02-21T16:54:57Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-13">        <title>MS RFC 13: SOS support </title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-13</link>        <description>Support of Sensor Observation Service in Mapserver.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>yassefa</dc:creator>        <dc:rights></dc:rights>                <dc:date>2006-06-04T16:39:25Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-14">        <title>MS RFC 14: Relative Coordinates for INLINE features</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-14</link>        <description>Current it is possible to have features with pixel coordinates and to draw them by setting TRANSFORM FALSE in a layer definition. However the coordinates are relative to the upper lefthand corner of the image (0,0) which makes it impossible to anchor things like copyright statements to the other corners of the images if the image size can change (e.g. via WMS).</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>sdlime</dc:creator>        <dc:rights></dc:rights>                <dc:date>2006-05-18T20:44:51Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-15">        <title>MS RFC 15: Support for thread neutral operation of mapserver/mapscript</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-15</link>        <description>The purpose of this change is to get a significant performance boost by removing "big locks" from the code. It would add a significal improvement of the applications having high number of multiple threads executed simultaneously. This activity could bring in a more feasible support for some application models not really aimed at now like Microsoft ASP.NET. May result in higher clarity of the code by determining the code segments affected by multiple threads.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>szekerest</dc:creator>        <dc:rights></dc:rights>                <dc:date>2006-08-07T22:38:32Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-16">        <title>MS RFC 16: MapScript WxS Services</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-16</link>        <description>Provide MapScript access to WMS/WFS/WCS services for customization.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>FrankW</dc:creator>        <dc:rights></dc:rights>                <dc:date>2006-07-15T02:12:40Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-17">        <title>MS RFC 17: Dynamic Allocation of layers, styles, classes and symbols</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-17</link>        <description>Modify the MapServer core libraries so that lists of layers, classes
and styles are dynamic, not fixed to compile limits MS_MAXCLASSES, 
MS_MAXSTYLES, MS_MAXLAYERS and MS_MAXSYMBOLS.
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>FrankW</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-09-05T20:04:11Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-18">        <title>MS RFC 18: Encryption of passwords in mapfiles</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-18</link>        <description>This proposal provides a mechanism to protect database connection passwords used inside mapfiles by encrypting them instead of including them in plain text.
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>dmorissette</dc:creator>        <dc:rights></dc:rights>                <dc:date>2006-08-11T17:35:01Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-19">        <title>MS RFC 19: Style &amp; Label attribute binding</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-19</link>        <description>Presently MapServer supports binding of label and style properties for a few select attributes (e.g. angle). However, it is cumbersome to add new bindings which leads to unecessarily complex structures and code that is difficult to maintain. This RFC presents ideas to bring a bit of order to that chaos and make expansion of this capability easier to achive.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>sdlime</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-07-17T15:45:29Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-21">        <title>MS RFC 21: MapServer Raster Color Correction</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-21</link>        <description>To add support to MapServer to apply color correction curves (aka lookup tables) to raster images on the fly. </description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>FrankW</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-07-13T17:10:16Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-22a">        <title>MS RFC 22a: Feature cache for long running processes and query processing</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-22a</link>        <description>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.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>szekerest</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-06-26T15:05:13Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-23">        <title>MS RFC 23: Project Steering Committee Guidelines</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-23</link>        <description>This document describes how the MapServer Project Steering Committee (formerly the Technical Steering Committee) determines membership, and makes decisions on MapServer technical and project managment issues.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>sdlime</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-01-25T17:06:24Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-24-FIRSTDRAFT">        <title>[first draft] MS RFC 24: Mapscript memory management</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-24-FIRSTDRAFT</link>        <description>Describe an implementation of a unified memory management solution for mapscript that addresses current issues with garbage collection in the hosting languages (c#, java, perl, python,ruby,tcl).</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>unicoletti</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-04-24T09:02:50Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-24">        <title>MS RFC 24: Mapscript memory management</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-24</link>        <description>Describe an implementation of a unified memory management solution for mapscript that addresses current issues with garbage collection in the hosting languages (c#, java, perl, python,ruby,tcl).
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>unicoletti</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-01-10T15:00:29Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-25">        <title>MS RFC 25: Align MapServer pixel and extent models with OGC models (DRAFT)</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-25</link>        <description>At present MapServer uses different pixel and extent model than defined by OGC services such as WCS and WMS. Although it has been dealt with successfully over the years the differences have led to various subtle bugs.  In addition, it is not clear that users completely understand the differences which again can lead to subtle problems. This RFC proposes to update the MapServer models to match those presented in OGC service specifications.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>sdlime</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-10-24T04:39:17Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-26">        <title>MS RFC 26: Ver. 5 Terminology Cleanup</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-26</link>        <description>Mapserver terminology is mostly good and consistent, with a few exceptions. The two that generate the most confusion and TRANSPARENCY (layerObj) and various scale referencing parameters (e.g. MINSCALE).</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>sdlime</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-07-16T17:16:45Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-27">        <title>MS RFC 27: Label Priority</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-27</link>        <description>This RFC introduces a new PRIORITY parameter on the LABEL object to control the order in which labels are rendered.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>dmorissette</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-09-05T19:58:40Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-28">        <title>MS RFC 28: Redesign of LOG/DEBUG output mechanisms</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-28</link>        <description>MapServer 4.10 and older used to have multiple LOG/DEBUG output mechanisms that did not play well together. In order to improve the usability of the software this RFC proposes a new LOG/DEBUG output mechanism with more control on the output location (logfile or stderr) and that works under all supported web servers.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>dmorissette</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-09-05T20:00:12Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-29">        <title>MS RFC 29: Dynamic Charting Capability</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-29</link>        <description>This RFC proposes the addition of simple dynamic charting capability in MapServer 5.0 based on the patch proposed by Thomas Bonfort in ticket #1800.
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>dmorissette</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-09-06T10:14:22Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-30">        <title>MS RFC 30:  Support for WMS 1.3.0</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-30</link>        <description>This RFC documents the changes required in order to upgrade MapServer's OGC
WMS support to version 1.3.0 of the specification.
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>dmorissette</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-09-05T20:02:43Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-31">        <title>MS RFC 31: Loading MapServer Objects from Strings</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-31</link>        <description>This RFC addresses the ability of the MapServer tokenizer to work from strings as well as files. It covers mapscript and url-based string sources.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>sdlime</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-09-20T21:01:10Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-32">        <title>MS RFC 32: Support for Anti-Grain Geometry (AGG) Rendering Engine</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-32</link>        <description>This RFC details the addition of AGG, a high-performance 2-D rendering engine, to MapServer as an output option.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>sdlime</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-07-24T20:24:17Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-33">        <title>MS RFC 33: Removing msLayerWhichItems() function from maplayer.c</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-33</link>        <description>This RFC details removal of the function msLayerWhichItems in maplayer.c and the resulting changes to the rest of the code base. This change is necessary in support of feature caching for long running processes and to facilitate one-pass queries. </description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>sdlime</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-07-24T20:24:18Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-34">        <title>MS RFC 34: MapServer Release Manager and Release Process</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-34</link>        <description>This RFC documents the MapServer Release Manager role and the phases of
MapServer's Release Process.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>dmorissette</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-07-19T21:19:01Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-35">        <title>MS RFC 35: Standards Compliance Enforcement</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-35</link>        <description>This RFC introduces a mechanism to tell mapserver to enforce OGC standards compliance, or alternatively to be permissive.  It also details short term adjustments to handling of the STYLE= required parameter in MapServer 5.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>FrankW</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-12-07T20:04:22Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-36">        <title>MS RFC 36: Simplified template support for query output</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-36</link>        <description></description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>sdlime</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-11-20T05:52:55Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-37">        <title>MS RFC 37: MapServer Spatial Reference Improvements and Additions</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-37</link>        <description>This RFC details optional improvements to MapServer's Spatial Reference description, acquisition, and definition for LAYERs.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>hobu</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-11-01T22:11:30Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-38">        <title>MS RFC 38: Native Microsoft SQL Server 2008 Driver for MapServer</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-38</link>        <description>To provide a read-only, native MapServer driver that connects to Microsoft
SQL Server 2008 (henceforth called SQL Server) on Windows as a PLUGIN 
datasource driver.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>hobu</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-11-14T03:06:08Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-39">        <title>MS RFC39: Support of WMS/SLD named styles in MapServer</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-39</link>        <description>Add Support of WMS/SLD named styles in MapServer</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>assefa</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-06-25T16:24:12Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-40">        <title>MS RFC 40: Support label text transformations</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-40</link>        <description>This RFC proposes the addition of simple label text transformations, such as text centering or conditional line wrapping based on line lengths</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>tbonfort</dc:creator>        <dc:rights></dc:rights>                <dc:date>2007-12-03T13:27:10Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-41">        <title>MS RFC 41: Support of WCS 1.1.x Protocol</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-41</link>        <description>It is proposed to extend MapServer to support the WCS 1.1 protocol.  MapServer already supports the WCS 1.0 protocol, but WCS 1.1 is significantly different. 
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>FrankW</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-04-16T05:09:15Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-42">        <title>MS RFC 42: Support of Cookies Forwarding</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-42</link>        <description>This RFC propose to extend MapServer to forward HTTP Cookies when doing OWS requests. </description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>juliensam</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-04-30T14:47:00Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-43">        <title>MS RFC 43: Direct tile generation for Google Maps API</title>        <link>http://mapserver.gis.umn.edu/development/rfc/ms-rfc-43</link>        <description></description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>dmorissette</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-05-02T13:55:04Z</dc:date>        <dc:type>Page</dc:type>    </item>




</rdf:RDF>
