Mapping XSD - Website Version vs Repo Version

[internalsystemerror]

The XSD hosted on the website at https://www.doctrine-project.org/schemas/orm/doctrine-mapping.xsd is currently being generated from https://github.com/doctrine/doctrine-website/blob/master/source/schemas/orm/doctrine-mapping.xsd. However this differs in some key ways from https://github.com/doctrine/orm/blob/2.9.x/doctrine-mapping.xsd.

Which XSD should be used for validating the XML mappings? As an example, the XSD in this repository requires that elements be ordered (such as <cascade> before <join-columns>) whereas the one hosted on the website does not. (Note: I am using xmllint from libxml2-utils for validation)

Some possibly related issues I found:
doctrine/orm#6968
doctrine/orm#6728

[greg0ire]

Which XSD should be used for validating the XML mappings?

The best is ./vendor/doctrine/orm/doctrine-mapping.xsd IMO: it's up to date and it's local.

[internalsystemerror]

Thanks, that's the one I'm currently using. Should the hosted one be versioned and based on the one in here?

[greg0ire]

From #92 (comment)

It needs to be located here

@jwage hi! What makes you say that? Shouldn't we recommend ./vendor/doctrine/orm/doctrine-mapping.xsd for all intents and purposes? Or are there cases where it would be desirable to use an online versions (situations where Composer is not available but curl is).

I think this is a maintenance burden. Anyway, transferring the issue to the website since it can be generalized to other XSD files.

[SenseException]

@greg0ire It would make more sense than having one xsd-file for every doc-version of ORM. Having a link to the file per version would be a nice-to-have though.