I accept the responsibility for this bug, and have fixed it.

However, I respectfully point out that specifying a specific element order in the schema like that does not make for a very user friendly content model.

>a specific element order in the schema like that does not make for a very user friendly content model.

It's often claimed that a fixed order makes things harder for writers but easier for readers, and that document design should be optimized for readers.

I suppose that depends who your reader is. If the reader is XQuery or my SAX based XQTS test runner, an undefined order makes little difference. If the reader is human, then I'd argue that a narrative order is best - which is very different to a fixed order.

Thanks.