Can't tell you if oXygen can help you find the non-deterministic content model, but some thoughts: * Use RELAX NG * Non-determinism occurs when a parser would not be able to tell which "branch" of the content model it is matching. E.g. <!ELEMENT duck ( a+, b*, a+ )> If a <duck> has only an <a>, a parser would not know whether it should match the first 'a+' or the second one. * Use RELAX NG * Even if you can't use XMetal, quite a few simple free tools will do this for you. I am quite fond of `xmllint` for this purpose. * Use RELAX NG * If you post your DTD, I'm sure any number of us would be happy to point out where the non-determinism is. (This is your best bet for a one-time problem, but doesn't scale well, of course :-) * Use RELAX NG
First time poster. I hope this question hasn’t been up for discussion before – I was not able to find anything helpful in the archives. I have a DTD that I need to debug. The ”problem" is that Oxygen validates the DTD just fine, whereas some XML editors (e.g. XMetal) complain about a ”non-deteministic” content model. So, my question is, does Oxygen (15.2) has some kind of ”strict mode” DTD validation? Because I do not have access to some XMetal-debug-fo, I must use Oxygen to debug my DTD.
Any help is greatly appreciated!