Closed antoniolocandro closed 3 years ago
The file is valid when verifying it with Oxygen XML, configured to use both xerces and Saxon EE as validating parsers. Saxon also raises some warnings about the GML schema self inclusion, etc. This is beyond our control.
XMLSpy and Notepad++ seem to be unable to deal with the schema declaration complexity. The errors that they raise are not related to the AIXM file itself, they are related to the schema declarations or the schema files. I do not know what XML parser these two are using.
My recommendation is to use xerces for validation - https://xerces.apache.org/
Hi I think the problem is not linked to the tools, but linked to the event schema referencing in the new version of the file.
The event schema references the http://www.aixm.aero/schema/5.1/event/Event_Features.xsd, instead of a 5.1.1 version, and I guess it induces the errors in XMLSpy (2017 for me), due to a double gml declaration coming from AIXM 5.1 and AIXM 5.1.1...
Eddy, and if I'm not wrong, I suggest the following:
Normally, a tool like XMLSpy (2017+) should be able to validate AIXM 5 messages.
Antonio, in the meanwhile, when downloading the file, just remove the event part of the xsi:schemaLocation, and XMLSpy will validate.
You are probably right! The Event schema declaration is not even necessary in the baseline Donlon sample. I think that it is simpler to just remove it.
Agreed, it would be better to have genuine AIXM 5 messages for the AIXM 5 samples.
It's corrected. XMLSpy 2014 is happy now.
File in its current form does not pass validations for the XSD as it has invalid elements
Tried in Altova XML Spy
Tried in Notepad++