I tested XSD output on the same file (using teitoxsd with the sydb-occurs2 stylesheets), and the result seems correct -- there were 2 errors: 1) The content of <xenoData> is flagged as ambiguous. This is a problem with anyXML, the Stylesheets, or xenoData itself; it has nothing to do with the changes in sydb-occurs2, as the exact same problem occurs with the dev branch of the stylesheets. 2) The customized content model for <bibl> is flagged as ambiguous; which, it turns out, it is. When I run the same ODD through teitoxsd with the dev stylesheets, the errors are quite a bit worse: spurious maxOccurs="unbounded" are inserted in some places, breaking the XSD.
I think you should also check what DTD and XSD outputs look like. As I said on the original ticket, we ought not to generate dtd or xsd which is actually illegal, even if it matches what the ODD says it should less well than the RNG output.
True enough. IIRC, current DTD and XSD generation produces schemas which are valid, but match incorrect # of things?