Implement `NeTEx` schema

[Bergmann89]

Follow up for #151

[HelloJowet]

I encountered this issue today and would love to see it resolved since this package is super helpful for my work. Thanks for the great repo!

[Bergmann89]

Hey @HelloJowet,

I currently have some other stuff in the pipeline that I would like to finish fist, before I continue on this one. If you are willing to contribute something to the project, you can also try to write a simple example for the NeTEx schema yourself. If you face any issue I can support you here.

[HelloJowet]

Hey @Bergmann89,

Thanks for the response! I went ahead and created a minimal reproduction for the TypeAlreadyDefined bug based on the NeTEx schema issue we discussed. You can find the repo here: xsd_parser__type_already_defined_bug__minimal_reproduction.

The README explains how the collision happens when complexTypes differ only by a trailing underscore and both reference the same group. You can switch between the minimal schema and the real NeTEx XSDs using an environment variable.

Let me know if you have any questions or need more details!

[Bergmann89]

Thanks, that help. I created a sub-issue for this bug.