TMTOWTDI
I would prefer to think of the schematron as extending and/or restricting the data model: your example works well enough when you’re using schema to define your data model (and I’m sure you could do something equally well with RELAX), but if you’re still
saddled with DTDs the 'conflicting' approach is your only option.
There is also an argument to be made for loose data model definitions and tight QA requirements if the ramifications of frequent changes to your DTD or Schema outweigh those of your QA system – such is the case we have with our suppliers.
Tom
The
XML Schema and the Schematron schema are making conflicting
assertions. Surely
that is a sign of poor design.
This message is confidential. You should not copy it or disclose its contents
to anyone. You may use and apply the information for the intended purpose only.
OUP does not accept legal responsibility for the contents of this message. Any
views or opinions presented are those of the author only and not of OUP. If this
email has come to you in error, please delete it, along with any attachments.
Please note that OUP may intercept incoming and outgoing email
communications.
