default XML namespaces should be consistent

Tom,

I agree with you and personally like this idea to make xmlns values consistent.

Set milestone to 1.5.0 (or later) as GPX is 1.5.0 (we won't change GML NS for 1.4.5, will we ?)

I voluntarily used xmlns:ogr="http://osgeo.org/gdal" in GPX to me more "up-to-date". http://ogr.maptools.org is a bit outdated, since it's a redirection to http://www.gdal.org. I think this doesn't matter very much as these URLs are not used by any software logic. This is more a "political" decision, than a technical one. So I will not fight very long. We must decide for one NS, and that'll do ;-)

Why not just http://www.gdal.org ?

I'm afraid I don't understand the ramifications of changing this for existing drivers. It seems to me the worst thing you can do with names spaces is to go changing them arbitrarily. Where they actually point is irrelavent.

Without a good explanation, I'm not willing to change the GML driver. So it is up to Even whether he wants the GPX driver to be consistent or not. If he is going to make any change I imagine before 1.5 release would be better than after.

Lets either resolve this or close it as WONTFIX.

Even, Mateusz, please review last note.

Replying to statement Where they actually point is irrelavent.. If there is no plan to enable XSD hosting in future, then indeed it's irrelevant and I don't have any recommendation other than leave it as is.

Replying to warmerdam:

I'm afraid I don't understand the ramifications of changing this for existing drivers. It seems to me the worst thing you can do with names spaces is to go changing them arbitrarily. Where they actually point is irrelavent.

Correct. Many XML parsers register namespaces when processing a document, so changing them would mean ramifications w.r.t. backwards compatibility.

Without a good explanation, I'm not willing to change the GML driver. So it is up to Even whether he wants the GPX driver to be consistent or not. If he is going to make any change I imagine before 1.5 release would be better than after. Lets either resolve this or close it as WONTFIX.

This ticket was put forth because the new GPX driver had a different namespace. Why don't we, then, stay consistent with http://ogr.maptools.org/ as the namespace?

Even if we wanted to do it, We couldn't host any XSD anyway. The name space is for "ogr:" prefixed tags, which are tags used for any non-GPX attributes that go in the <extensions> tag. So it's not possible to write an XSD. It depends on the attribute schema. It's different for the default namespace, which relates to the GPX XML schema hosted at http://www.topografix.com/GPX/1/1 I don't really understand why it should be consistent with GML, but as I said, I don't care at all if someone wants to change it. I'm closing as wontfix.

Replying to rouault:

Even if we wanted to do it, We couldn't host any XSD anyway. The name space is for "ogr:" prefixed tags, which are tags used for any non-GPX attributes that go in the <extensions> tag. So it's not possible to write an XSD. It depends on the attribute schema. It's different for the default namespace, which relates to the GPX XML schema hosted at http://www.topografix.com/GPX/1/1 I don't really understand why it should be consistent with GML, but as I said, I don't care at all if someone wants to change it. I'm closing as wontfix.

The main point of this ticket was to be consistent with the OGR namespace. GML defines ogr with xmlns:ogr="http://ogr.maptools.org/". Just thought we'd do the same with other XML flavours which define ogr.