upvote
> can tell in an instant whether or not the document is correct

Speaking of "correctness"... It seems to me people almost never mention that while schema verification can detect a lot of issues, in the end it cannot replace actual content validation. There are often arbitrarily complicated constraints on data that requires custom code to validate.

This is analogous to the ridiculous claim that type checking compilers can tell you whether the program is correct or not.

reply
If your type checking was in the Martin-Löf school, and you started with a putative proof that what you wanted to execute was possible, then maybe! B^>
reply
I'm happy to use XSD for certain situations, but it has some frustrating inabilities and complexities.

The impression I've got from the last 20 years is that a chunk of the XML community gave up on XSD and went to RELAX-NG instead, but only got halfway there.

reply
what jobs require XSD verification?
reply
Anything that wants to be sure that the data passed to it is structurally valid.
reply
E.g.:

> All consumers are required to meet schema validation. Schema validation is the verification that the operations inside the SOAP Body match the contract created by Jack Henry in the XSD documents. It should be noted, that the VER_x tags are required in the requests to meet schema.

https://jackhenry.dev/jxchange-soap/getting-started/developm...

reply
Ideally all of them.
reply