Opened 18 years ago

Closed 18 years ago

Last modified 18 years ago

#1576 closed defect (fixed)

OGC test suite problem with get capabilities DTD

Reported by: assefa Owned by: mapserverbugs
Priority: high Milestone:
Component: WMS Server Version: unspecified
Severity: normal Keywords:
Cc: nsavard@…

Description

Problem reproted by Normand Savard 

We ran the OGC Cite WMS tests suite against our new MapServer version.  
The "wms/wmsops/getcapabilities/response/2 
<http://cite.occamlab.com/tsOGC/interface/ViewTestSource?
testid=wms/wmsops/getcapabilities/response/2&ts=0021&sesstype=OGC>" test did 
not pass.  The result log said that the DTD we used does not match the DTD 
specified in the specification (see the message below).

The DTD pointed out by the specification is located at 
http://www.digitalearth.gov/wmt/xml/capabilities_1_1_1.dtd.  The DTD we used 
is located at 
http://schemas.opengeospatial.net/wms/1.1.1/capabilities_1_1_1.dtd.  I verify 
with the "diff" command on Linux that both DTDs are the same.

Did someone come across this same issue with this test?  Do someone know what 
does the message mean?


---------------------------------------

Apparanetly the valid dtd to use for 1.1.1 is 
http://schemas.opengeospatial.net/wms/1.1.1/WMS_MS_Capabilities.dtd for the 
test to pass.

Change History (6)

comment:1 by assefa, 18 years ago

Cc: nsavard@… added
Resolution: fixed
Status: newclosed
Fixed in cvs head : the current fix is to use the specified 
WMS_MS_Capabilities.dtd if the schemalocation defined is 
http://schemas.opengeospatial.net or there is no schema location (which goes 
by default to http://schemas.opengeospatial.net).

Norm please confirm and close bug.  I also deleted the e-mail sent yesterday 
in response to your quetion. Please add it to this bug report. Thanks

comment:2 by nsavard@…, 18 years ago

This is the answer to the email I sent to the OGC Cite list.

----------------------

Normand,

Try using
http://schemas.opengeospatial.net/wms/1.1.1/WMS_MS_Capabilities.dtd,
which is the DTD that is actually published in the specification.
http://www.digitalearth.gov/wmt/xml/capabilities_1_1_1.dtd and
http://schemas.opengeospatial.net/wms/1.1.1/capabilities_1_1_1.dtd are
modified bug-fix versions.  I don't understand why this update was
published as capabilities_1_1_1 instead of renaming it to something like
capabilities_1_1_1_revA, but that is the situation.

Chuck Morris

comment:3 by nsavard@…, 18 years ago

I ran the OGC Cite tests suite on MS 4.8 RC2 and all 88 tests passed.

comment:4 by nsavard@…, 18 years ago

Resolution: fixed
Status: closedreopened
This OGC Cite test failed again because the OWS_DEFAULT_SCHEMAS_LOCATION
constant does not point to "http://schemas.opengeospatial.net/" in mapows.h.  It
actually points out to "http://schemas.opengis.net".


Tested with R4.10 beta 3.

comment:5 by dmorissette, 18 years ago

Resolution: fixed
Status: reopenedclosed
See bug 1873 about the change to ows_schemas_location that was required because
OGC decided to shutdown schemas.opengeospatial.net (and a few days later they
brought it back up because of all the trouble that had caused, but I heard that
they still plan to take it down everntually.)

Is the problem really caused simply by the change of the default schema
location? I would be surprised if that was the case since both repositories
should point t the same files. Anyway, if the URL of the schema location is
really the source of this failure then please contact the OGC CITE list and ask
them to fix their test to be in line with OGC's own choice to use
schemas.opengis.net as the primary schema repository.

Finally, this bug had been fixed and released in v4.8. Please do not reopen
released bugs, instead please create new bugs with a reference to old bugs if
necessary.

Closing again as FIXED.

comment:6 by dmorissette, 18 years ago

Actually, I see that you had already commented about this issue in bug 1878...
Note: See TracTickets for help on using tickets.