> The second problem is the unquantifiable nature of the 'text' pattern > combined with the restriction on mixing data and elements. I can't > figure out any way to express a *non-empty* requirement in Relax NG: > > # Some elements are defined to have as a content model significant > # inline content. This means that at least one descendant of the > # element must be significant text or embedded content. > # > # Significant text, for the purposes of determining the presence > # of significant inline content, consists of any character other > # than those falling in the Unicode categories Zs, Zl, Zp, Cc, > # and Cf. [UNICODE] > > Even without the Unicode-level restrictions, I don't see any way of > requiring an element to have *some* inline content. Perhaps a > 'requiredText' pattern that didn't have 'text's implicit 'zeroOrMore' > would help here. (It would have to count white space as insufficient > text.) > ISO/IEC 26300
At present, I am afarid that there are no mechanisms for addressing the requirement. One way to solve this is to extend the <text> pattern so that it can have additional attributes for constraining text contents. DSDL Part 7 (Character Repertoire Description Language) may be used as a basis for such additional attributes in the future. But we have to finish CRDL (which is still a CD) and extend RELAX NG as well. Cheers, -- MURATA Makoto (FAMILY Given) <[EMAIL PROTECTED]>
