Tokens.xml fails to validate

[SlightlyCircuitous]

When running xmllint --schema ./cards.xsd ./tokens.xml using the current v4 cards.xsd, I receive the following error:

./tokens.xml:7: element cockatrice_carddatabase: Schemas validity error : Element 'cockatrice_carddatabase', attribute '{https://www.w3.org/2001/XMLSchema-instance}noNamespaceSchemaLocation': The attribute '{https://www.w3.org/2001/XMLSchema-instance}noNamespaceSchemaLocation' is not allowed.

Am i doing something wrong or is this an issue of expectations mismatch between cards.xsd and tokens.xml?

I have been simply ignoring this message because I know the xml works fine with that attribute, but it would be nice if the validation tool would tell me everything is OK when I run it with a valid file.

[tooomm]

Try changing https to http in the w3.org URL.

Please also see #65 and especially #93, maybe there are also other linked issues.
Also Cockatrice/Cockatrice#3710.

Psithief had concerns there as it looks like the XSD at Cockatrice is not perfect and would need an update to XSD v1.1.
Maybe you've some more insights there? Or the situation changed?

[SlightlyCircuitous]

That does actually fix the problem, thank you!

Now that I look at it, both cards.xml and cards.xsd use http and only tokens.xml uses https so I guess it's just the odd one out for some reason. Should we change that in tokens.xml or is it like that for a reason? Alternatively, I guess the xsd could be altered to also accept https as valid.

[ebbit1q]

looking at the history this was introduced in #71

[ebbit1q]

looking at the latest spec it is required to be http, and xmllint is correct in refusing the https url https://www.w3.org/TR/xmlschema11-1/#sec-nss-special

[tooomm]

The URL is fixed since 2 years in #93 (c73fcaf), that's why I knew http fixes it. :)

[ebbit1q]

when will #93 be ready for review though?

[tooomm]

I stopped working on it a long time ago, and just updated it from time to time as I like to see such a check at one point. Once #208 is merged, I would update it again.
Even as is, it allowed me to spot and fix many issues in the files already and helps to provide a good quality.

Though, the blocker for merging was, that Psithief had concerns and it looked like the XSD at Cockatrice is not perfect and would need an update to XSD v1.1 in order to make the check really be useful?
Please feel free to double check, I've no experience with XSD files and XML validation really. Maybe the situation changed or the concerns are not valid (any longer)! --> #93 (comment)