The schematron rule for this is rather lengthy and could be rewritten into a shorter form ... or into two separate rules.
The intention seems to be that if there's an msItem in the file, that msItem must have a textLang child or an ancestor msItem or ancestor msContents must have a textLang child AND that every msItem must have textLang. AND that every msItem inside an msItem must have a texLang.
The constraint requiring mainLang to have content will apply to every textLang element. If that is the intent, the logic of this rule could be specified better by `````. The regex that stipulates what this content could be specified inside attDef as well.
The schematron rule for this is rather lengthy and could be rewritten into a shorter form ... or into two separate rules.
The intention seems to be that if there's an msItem in the file, that msItem must have a textLang child or an ancestor msItem or ancestor msContents must have a textLang child AND that every msItem must have textLang. AND that every msItem inside an msItem must have a texLang.
The constraint requiring mainLang to have content will apply to every textLang element. If that is the intent, the logic of this rule could be specified better by `` ```. The regex that stipulates what this content could be specified inside attDef as well.