Motion to adopt MS-RFC-35 - Standards compliance enforcement

[Daniel Morissette]

Kralidis,Tom [Burlington] wrote:
>>>> On 11/8/2007 at 9:31 AM, in message <47332BE4.3000105 at mapgears.com>, Daniel
> Morissette <dmorissette at MAPGEARS.COM> wrote:
>> Since there have been no proposed changes to MS-RFC-35, I hereby motion 
>> that we adopt "MS-RFC-35 - Standards Compliance Enforcement"
>>
>> http://mapserver.gis.umn.edu/development/rfc/ms-rfc-35/ 
>>
>> ...and I start with my +1.
>>
>> Once the RFC is adopted we can implement the fixes and release 5.0.1.
>>
>> Daniel
> 
> If the vote is still on, and fwiw, I put forth -1 with the rationale(s) I have provided in earlier communications.


Well, the vote is still on, and your "fwiw" is worth a lot: it's a veto, 
it means that we're in a dead-end and need to revisit the RFC to proceed.

Is there a way we can adapt the proposal to address your concerns? As 
Tamas wrote: Do you have any other idea to solve the original problem 
besides of waiting for everyone to implement the standards entirely?

Do you realize that the current situation with the STYLES requirement 
being enforced just makes MapServer appear as broken in the eyes of 
users and doesn't help interoperability at all? How many other WMS 
servers out there do require STYLES? Google Earth comes with a list of 
about 40 preloaded WMS service URLs which I presume have all been tested 
with Google Earth (I didn't test them myself) and presumably all work 
without requiring the STYLES parameter. From a quick browse of the list 
that includes some MapServer, cubeserv, ArcIMS, intergraph, Demis and a 
bunch of others I can't recognize from the URL.

Hopefully you also took note that it was recognized on the WMS-dev list 
that STYLES being required is a mistake from the early WMT 0.1 days and 
that a change proposal has been sent to the WMS.RWG to fix it? See 
http://lists.eogeo.org/pipermail/wms-dev/2007-October/000916.html

Daniel
-- 
Daniel Morissette
http://www.mapgears.com/