[mapserver-dev] RFC 70: TinyOWS Integration

[Lime, Steve D (DNR)]

I'd like to propose getting Olivier commit rights for the documentation tree to maintain the RFC. Any objections?

Steve

-----Original Message-----
From: mapserver-dev-bounces at lists.osgeo.org [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of Olivier Courtin
Sent: Monday, May 02, 2011 2:13 AM
To: MapServer Dev List
Subject: Re: [mapserver-dev] RFC 70: TinyOWS Integration


On Apr 28, 2011, at 4:31 PM, Lime, Steve D (DNR) wrote:

> Hi all: Olivier floated a draft a few weeks ago and it's now sitting  
> alongside all other
> RFCs which should make it a little easier to review:
>
>   http://mapserver.org/development/rfc/ms-rfc-70.html
>
> Please take a look and let's move this forward.



Few changes in RFC, as 1.0.0rc1 is just coming out


--- Downloads/ms-rfc-70.txt	2011-05-02 08:58:52.000000000 +0200
+++ Desktop/ms-rfc-70.txt	2011-05-02 09:08:56.000000000 +0200
@@ -158,23 +158,29 @@
  (No Xlink nor Lock profile implemented)

  TinyOWS trunk on OGC CITE unit test:
- - WFS-T 1.1.0 (r4) : 519 'Passed' / 34 'Failed'
+ - WFS-T 1.1.0 (r4) : 559 'Passed' / 0 'Failed'
+ - WFS-T 1.0.0 (r3) : 398 'Passed' / 0 'Failed'

  4.5 External Dependancies
  -------------------------
   - LibXML2 >= 2.6.20
   - PostgreSQL >= 8.1.0
   - PostGIS >= 1.5.0
- - Flex
   - FastCGI is optional (but recommended)

  4.6 MapFile notions not yet addressed
  -------------------------------------
  Some Mapfile concepts are not yet present in TinyOWS:
- - Supporting other database than PostGIS
- - Ability to associate each layer to a different database connection
- - Some specifics configuration stuff not required by OGC compliancy,
-   but who still could be useful.
+ - Only PostGIS CONNECTIONTYPE are handled
+ - TinyOWS don't pretend to support right now all the WFS parameters  
available in MapFile
+ - But on the other hand you should be able to configure every part  
of TinyOWS from MapFile
+ - Each CONNECTION string value in layers must be the same.
+ - MapFile PROJECTION content is not parsed, so use explicit wfs_srs
+ - MapFile LAYER/FILTER is not parsed.
+ - Defaults values are TinyOWS ones, even for common properties  
shared by both apps.
+ - TinyOWS don't use DATA element from MapFile, so you have to use  
tinyows_table (and tinyows_schema if needed) in each layer.
+ - If DUMP is not set to TRUE on a layer both Read and Write access  
are shutdown for these layer
+

  4.7 Build system
  ----------------
@@ -191,6 +197,7 @@
  - More exhaustive unit tests policy (not only OGC ones)
  - More consistent behaviour and configuration directives for both  
TinyOWS and MS.
  - Oracle Spatial support
+- Application Schema support

  5. Voting history
  -----------------

--
Olivier _______________________________________________
mapserver-dev mailing list
mapserver-dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-dev