Invalid URL in WMS services

[cruiz]

XML schemas must point to a valid URL. There are applications that can't consume WMS services because of this.

This can be fixed changing the ​http://mapserver.gis.umn.edu/mapserver for ​http://www.mapserver.org/mapserver instead.

The same happens with the new schema to validate XML map files:

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ms="http://mapserver.gis.umn.edu/mapserver" targetNamespace="http://mapserver.gis.umn.edu/mapserver" elementFormDefault="qualified" attributeFormDefault="unqualified" version="5.6.0">

[tomkralidis]

Please clarify. Can you post a testcase so I can reproduce?

[dmorissette]

Tom, this is because the default namespace URI for most OGC XML docs we produce uses mapserver.gis.umn.edu (default value hardcoded in source).

cruiz: FYI you can use the ows_namespace_uri metadata in your mapfile to override the default value.

I will change the default to ​http://www.mapserver.org/mapserver for 5.6.0-beta2.

[tomkralidis]

Replying to dmorissette:

Tom, this is because the default namespace URI for most OGC XML docs we produce uses mapserver.gis.umn.edu (default value hardcoded in source).

cruiz: FYI you can use the ows_namespace_uri metadata in your mapfile to override the default value.

I will change the default to ​http://www.mapserver.org/mapserver for 5.6.0-beta2.

Careful. Note that the namespace URI doesn't have to necessarily resolve to a real, physical URL. As well, many XML parsers bind to the namespace to traverse elements. I think this will cause backward compatibility issues.

[dmorissette]

Really? That sounds scary. I won't change anything in the OGC services for now, but it would be great to have a plan for resolution before beta3 next week.

FYI I have changed the namespace in the xmlmapfile/mapfile.xsd in r9361

cruiz: can you please be more specific on which applications fail with MapServer because of this, and how?

[tomkralidis]

Replying to dmorissette:

Really? That sounds scary. I won't change anything in the OGC services for now, but it would be great to have a plan for resolution before beta3 next week.

I would suggest ​http://www.mapserver.org/mapserver as the default namespace URI as a way forward, but we should discuss migration and be aware of the issues. Maybe a discussion on mapserver-dev.

FYI I have changed the namespace in the xmlmapfile/mapfile.xsd in r9361

Ah, ok. I made ​http://mapserver.gis.umn.edu/mapserver in the XML Schema to be consistent with the rest of the default namespace URI definition in the codebase.

cruiz: can you please be more specific on which applications fail with MapServer because of this, and how?

[dmorissette]

ok. I have changed the mapfile.xsd again, to use ​http://www.mapserver.org/mapserver this time (will be in 5.6.0-beta1)

Let's continue this discussion on the -dev list and come back here when we have consensus. (I hate it when tickets turn into long discussions)

[dmorissette]

I have noticed that the WMS 1.3.0 implementation does not support the *_namespace_uri and *_namespace_prefix metadata which are available with other specs to override the default namespace URI and prefix. I have created ticket #3143 about this.

[cruiz]

I've tested WMS with many applications like Autodesk Map, Quantum GIS, gvSIG. But using Kosmo ​http://www.opengis.es/index.php?option=com_docman&task=doc_download&gid=49&Itemid=42 wich is developed in Java, based in JUMP, throws an error about the invalid URL.

I'll make some tests with the 'ows_namespace_uri' tag in metadata section to see if this override works.

[tomkralidis]

There's no reason why a namespace URI should be causing any XML parser (let along a WMS client) to throw an error.

[cruiz]

For the record, this is what the Kosmo GIS application throws:

Error parsing response - Error creating feature instance from element 'highways': No schema information for namespace "​http://mapserver.gis.umn.edu/mapserver" provided.

Now i'm testing the 5.6.0-beta2 version to see what happens.

[cruiz]

Daniel: The WMS tests with Kosmo GIS application and Mapserver 5.6.0-beta2 was succesful. But now testing with WFS throws the same error. Did you change the hardcoded URL for the WFS too ?

[dmorissette]

I didn't change anything (neither in WMS nor WFS), so the error must be related to something else than the namespace, it just happens to refer to the namespace as the identifier of the schema that is missing.

[tomkralidis]

FYI I had some help testing this today (thanks wildint) I downloaded Kosmo GIS 1.2.1 and tried this. WMS works as expected.

I can't seem to find the WFS support. Which version of Kosmo GIS are you testing with?

[cruiz]

Thanks Tom.

I'm using Kosmo 2.0, since the Mapserver version 5.6 beta 2 WMS works fine, but not a WFS service.

Certainly Daniel didn't change nothing hardcoded, because the URL ​http://mapserver.gis.umn.edu/mapserver stills there.

[tomkralidis]

Replying to cruiz:

Thanks Tom.

I'm using Kosmo 2.0, since the Mapserver version 5.6 beta 2 WMS works fine, but not a WFS service.

Certainly Daniel didn't change nothing hardcoded, because the URL ​http://mapserver.gis.umn.edu/mapserver stills there.

Can you point me to where I can download Kosmo 2.0? Thanks.

[cruiz]

Tom,

Kosmo 2.0 can't be downloaded right now. We have this version unofficially. The creators are working fine with this version and Deegree. But I have this kind of troubles working with Mapserver.

[tomkralidis]

Replying to cruiz:

Tom,

Kosmo 2.0 can't be downloaded right now. We have this version unofficially. The creators are working fine with this version and Deegree. But I have this kind of troubles working with Mapserver.

Thanks for the info. I am closing this ticket as I am unable to reproduce this issue. Once Kosmo GIS 2.0 becomes publically available, feel free to open this ticket again and we can look into the issue at that point in time.