I think this example comes from tei-simple.odd compiled by Brian afair,
where <model> for <choice> element was explicitly 'pulling' its children
into alternate and to prevent the children being processed further this
rule was invented. So this <model> would go into elementSpec for sic, corr,
reg et consortes. If it explains anything.
On 5 February 2016 at 19:01, Lou Burnard
OK, so this means "if I am inside a <choice>, and I have more than one sibling, then destroy me"?
What elementSpec would this typically be attached to?
On 05/02/16 18:46, James Cummings wrote:
Siblings not parents. ..it goes up a level and sees if there is more than one child.
J
-- Dr James Cummings, Academic IT, University of Oxford
-----Original Message----- From: Lou Burnard [lou.burnard@retired.ox.ac.uk] Received: Friday, 05 Feb 2016, 18:41 To: tei-council@lists.tei-c.org [tei-council@lists.tei-c.org] Subject: [tei-council] weird example
The spec for <model> currently has a whole slew of examples, some of which need to go elsewhere I think. And one or two of them are entirely mysterious. This one for example:
<exemplum xml:lang="en"> <egXML xmlns="http://www.tei-c.org/ns/Examples"> <model predicate="parent::choice and count(parent::*/*) gt 1" behaviour="omit"/> </egXML> </exemplum>
Can someone please explain to me what this is meant to achieve? It seems to be saying "if my parent is <choice> and any of my parents has more than one child node, then suppress me".
In the immortal words of Manuel, che?
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived