Well, well. Turns out the constraints I was suggesting are already there. :-) Although I think my 2nd suggestion in my e-mail is somewhat better, and will deal with that via a ticket soon. Not only can not think of why an empty <constraint> is helpful, it seems silly and possibly puts a bit of a burdon on processing. And you're absolutly right about my erroneous value of ident=, of course.
Our concern was to fix a bug that was impeding our implementation of the JTEI schema, and actually made our own examples invalid. If you'd like to extend the ticket to add the new constraints, please go ahead. As far as <oneOrMore> vs <zeroOrMore> is concerned, as you say, I don't think it makes any difference; as long as we can put multiple things in the Schematron namespace in there, I'm happy. Perhaps someone can think of a reason why an empty <constraint> would be useful?
In your code below, shouldn't this:
be this: