Opened 18 years ago

Closed 17 years ago

Last modified 17 years ago

#1693 closed defect (fixed)

[Context] context 1.0 write code uses WMS instead of OGC:WMS

Reported by: bartvde@… Owned by: jlacroix
Priority: high Milestone:
Component: MapScript-PHP Version: 4.8
Severity: normal Keywords:
Cc:

Description

When outputting a WMC, Mapserver uses WMS for the value of the service
attribute of Server, whereas the OGC example (on schemas.opengis.net) as
well as Ionic use OGC:WMS

<Server service="OGC:WMS"

See also the example in the OGC WMC 1.0 spec:
http://www.opengeospatial.org/docs/03-036r2.pdf

Change History (9)

comment:1 by jlacroix, 18 years ago

Note this is fixed in WMC 1.1 support.
Before that, the WMC only specified "string" as the type for the Server's
service parameter. If I remember well, we write only "WMS" because at the time
the context support was developped "OGC:WMS" was not used anywhere (version
0.1.4 at the time). So I'm not sure from which version we should change it to
"OGC:WMS".

Also since in 1.0.0 specify only the string type it's legal to use "WMS"...

What do you think?

comment:2 by bartvde@…, 18 years ago

Hi Julien,

what Mapserver does is valid according to the schema, that's true. But I think
it would be more wise to follow the examples from the specification document
though, only ofcourse if it won't break backward compatibility which I don't
think it does (since the Ionic OGC:WMS in the WMC 1.0 document was parsed
correctly to CONNECTIONTYPE WMS).

Bart

comment:3 by dmorissette, 18 years ago

Cc: dmorissette@… added
Owner: changed from mapserverbugs to jlacroix
Reassigned to Julien.

comment:4 by tomkralidis, 17 years ago

It looks like this has been done (see mapcontext.c, line 1940). Julien: can you verify?

in reply to:  4 comment:5 by bartvde, 17 years ago

Replying to tomkralidis:

It looks like this has been done (see mapcontext.c, line 1940). Julien: can you verify?

Hi Tom, it has not been done yet (see http://cvs.gis.umn.edu/cgi-bin/viewcvs/mapserver/mapcontext.c?rev=1.81&content-type=text/vnd.viewcvs-markup). For WMC 1.1 it outputs OGC:WMS, but for WMC 1.0 it outputs WMS instead of OGC:WMS. I think we should use OGC:WMS also for WMC 1.0, but Julien and I did not agree on that part if I remember correctly.

comment:6 by tomkralidis, 17 years ago

Ah, ok. I misunderstood this one. :)

OK, if we set Server/@service"OGC:WMS" for 1.0.0 and 1.1.0, I think that's fine. I don't know that alot of clients actually use the value when binding as opposed to an identifier. Infact, I think this attribute may have originally been a placeholder for future versions of WMC which may support other OGC types.

Julien: is this okay with you?

comment:7 by jlacroix, 17 years ago

Resolution: fixed
Status: newclosed

Thanks for the precision. I updated the code to write "OGC:WMS" for the 1.0.0 version. I left previous versions use "WMS" because the examples in those documents used "WMS".

Marking as FIXED

comment:8 by jlacroix, 17 years ago

BTW, I updated only the SVN head version. Should it be back ported to 4.10?

comment:9 by bartvde, 17 years ago

I think svn head is fine.

Note: See TracTickets for help on using tickets.