Are all your examples @valid="feasible" ? If so, I claim that that at least explains why they don't show up in the validation. My understanding of macroXML is that the requirement for a single element corresponds with the requirement that the content of <egXML> be well formed, i.e. have a single root element. Cases where there is no single root element, but where adding one would make the example well-formed, are marked as @valid="feasible", and not checked during validation. On 24/09/15 12:34, Syd Bauman wrote:
Um, if this were truly a bug surely it would have shown up during validation of P5 in the makefile? One would have thought so.
Can you cite one or two of the 140 cases you've identified? <egXML xmlns="http://www.tei-c.org/ns/Examples" xml:lang="en" valid="feasible"> <castItem type="role"> <role xml:id="Barnardo">Bernardo</role> </castItem> <castItem type="role"> <role xml:id="Francisco">Francisco</role> <roleDesc>a soldier</roleDesc> </castItem> <!-- ... --> <sp who="#Barnardo"> <speaker>Bernardo</speaker> <l n="1">Who's there?</l> </sp> <sp who="#Francisco"> <speaker>Francisco</speaker> <l n="2">Nay, answer me: stand, and unfold yourself.</l> </sp> </egXML>
It's true that macro.anyXML is a problem area in the purification process. But it does allow multiple children, as long as they are properly nested within a single root. Not the way I read it, or my oXygen validates w/ it. I see
macro.anyXML = element * - (tei:* | teix:egXML) { attribute * { text }*, ( text | macro.anyXML )* }
which is very clear that 'macro.anyXML' gets replaced by one and only one element.
I assume you're not confusing egXML with exemplum? Not at all.