[obspy-users] QuakeML catalog import: XML namespaces that qualify for .extra mechanism

Tobias Megies megies at geophysik.uni-muenchen.de
Thu Sep 26 16:06:25 CEST 2019

Hi Fabian,

I see the problem, I'd class it a bug. Writing works fine but during
reading they seem to get left out. I've opened a ticket on github to
track this.


Any reason to not just read any namespaces, even the native ones of the
document back into extra? I don't see how the schema wouldn't allow
having e.g. http://quakeml.org/xmlns/quakeml/1.2 elements as custom
ones, even though that really might not be intended usage of the standard.


On 26/09/2019 13:17, Fabian Euchner wrote:
> Hi all,
> currently, only XML extension elements with namsepaces that do *not* start 
> with http://quakeml.org/xmlns/ are included into the .extra mechanism. I find 
> that a bit too restrictive because
> i) Nothing prevents users to assign such namespaces to their extension 
> elements (which is fine for development and testing, or documents that are not 
> public). Then there is a big surprise that these elements are missing in 
> .extra. One has to dig deep into the source code to find out why.
> ii) In particular, extension elements that are taken from the semi-official 
> QuakeML 2.0 draft (and thus live "legally" in http://quakeml.org/xmlns/) are 
> neglected.
> I suggest that all namespaces are allowed (with the exception, of course, of 
> the document's namespaces, http://quakeml.org/xmlns/quakeml/1.2 and http://
> quakeml.org/xmlns/bed/1.2).
> Best regards,
> Fabian

More information about the obspy-users mailing list