Re: XML Schemas: Best Practices

[Rick Jelliffe <ricko@allette.com.au>]

That is an interesting paper.

I am surprised there is no treatment yet of the Extension framework that
Extensiblity developed. Also, Schematron does allow you to specify the
values of A and B, but in a separate section "diagnostics" which would
presumably appear in the appinfo for the top-level schema; a message like
"error!" in the schema itself is sort of wrong, because we want to assert
what is the positive case (e.g. so that the assertion can be used in
interfaces to tell the user what is or should be going on): it is not a
"error" to have a missing element during the editing of a document,
and it should not be reported as such. (At validation time, it can be
reported as an error, of course, but we don't want to build in use-semantics
into text assertions, as a matter of schematron best practise:-)

Cheers, and thanks for the good work
Rick Jelliffe