Opened 22 years ago

Closed 19 years ago

#158 closed defect (duplicate)

[WMS] Broken ref. to digitalearth DTD

Reported by: dmorissette Owned by: dmorissette
Priority: high Milestone:
Component: WMS Server Version: 4.1
Severity: normal Keywords:
Cc: trem@…, nsavard@…

Description

Subject:  [mapserver-users] digitalearth DTD
   Date:  Mon, 8 Apr 2002 12:55:36 +1000
   From:  "Trem Stamp" <trem@socialchange.net.au>
     To:  "Mapserv Users List" <mapserver-users@lists.gis.umn.edu>

Hi all,
 
I noticed today that my application breaks when getting the mapserv WMS 
capabilities document in mapserv3.5.  There appears
to be a reference to:
 
http://www.digitalearth.gov/wmt/xml/exception_1_0_0.dtd
 
This no longer appears to be a valid url.  I realise that 
http://www.digitalearth.gov/wmt/xml/exception_1_0_1.dtd is valid, but this
isn't being requested.
 
 
Using this url:
http://maps-dev.socialchange.net.au/cgi-bin/mapserv?
map=mapfiles/geoscience10m.map&WMTVER=1.0.1&request=capabilities&LAYERS=
 
I get...................
 
<!DOCTYPE WMT_MS_Capabilities SYSTEM 
"http://www.digitalearth.gov/wmt/xml/capabilities_1_0_0.dtd"
 [
 <!ELEMENT VendorSpecificCapabilities EMPTY>
 ]>  <!-- end of DOCTYPE declaration -->
 
Is this dtd going to be reliable or is it now not being used?
 
Cheers,
 
Trem

Change History (7)

comment:1 by dmorissette, 21 years ago

Cc: assefa@… added
Version: 4.04.1
This is quite likely still an issue in 4.0. 
I or Assefa should check this in 4.1.  

Maybe we can add this DTD to our http://ogc.dmsolutions.ca/ repository, or ask 
OGC to add this to their http://schemas.opengis.net/ repository.  Let's talk 
about this when we get there.

comment:2 by nsavard@…, 20 years ago

Cc: nsavard@… added

comment:3 by nsavard@…, 20 years ago

*** Bug 381 has been marked as a duplicate of this bug. ***

comment:4 by nsavard@…, 20 years ago

Resolution: fixed
Status: newclosed
Fixed.  Now the DTD used is
"http://schemas.opengis.net/wms/1.1.1/WMS_exception_1_1_1.dtd".

comment:5 by nsavard@…, 20 years ago

Verified on 4.3 version.

comment:6 by dmorissette, 20 years ago

Resolution: fixed
Status: closedreopened
The problem was with WMS 1.0.0. I believe the problem would still be present
with that version.

comment:7 by dmorissette, 19 years ago

Resolution: duplicate
Status: reopenedclosed
This will be addressed by bug 657. Marking as duplicate.

*** This bug has been marked as a duplicate of 657 ***
Note: See TracTickets for help on using tickets.