Re: [tei-council] anyElement XSD pain

* First thought on solving the problem Hugh posted is to just drop support for DTDs and XSDs. :-) * I'm yet to be convinced that <rngContent> is a good idea, let alone a requirement to move forward, but have not thought about it very much yet -- am willing to be convinced. * Why would we want to drop support for RNG in content models? Lou wasn't suggesting that initially, and my instinct is that's a bad idea. (Adding XSD is not an idea I'm fond of, but it's better than dropping RNG.) * Remember, the solution to the dreaded dreaded double-declaration- of-id problem is to turn DTD compatibility mode OFF. (We don't want the limitations of DTDs imposed on our RELAX NG.)