[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [relax-ng] A mechanism for handling inclusion/exclusion
My apologies for not responding to this message sooner. Thank you for the reminder, Makoto. / "MURATA Makoto (FAMILY Given)" <EB2M-MRT@asahi-net.or.jp> was heard to say: | On 13 Oct 2003 10:34:28 +0700 | James Clark <jjc@jclark.com> wrote: | |> I think it's a little confusing to have context be handled as a new kind |> of pattern. Would it be possible instead to handle it in the |> name-class? Your example might be written instead as: |> |> a = element a - a//a { mixed { (em|span)* } } |> span = element span - span//span { mixed { (a|em)* } } |> em = element em - em//em { mixed { (span|a)* } } | | I think that this approach is simpler and probably good enough | although my original is more powerful. | | Norm, how do you feel? This is your area. I think simple exclusion of elements (X|Y|Z) from appearing anywhere in the descendants of X is the 80% case. As such, I think the name-class approach looks like it would cover 80% case and it seems a lot less complicated than adding context as a new kind of pattern. That said, I don't know if I still think this is something we need to do or not. Because I wanted[1] some way of implementing exclusions, I turned to generating Schematron rules (from RELAX NG annotation markup) to do it. This lead quickly to the realization that I could generate a lot of other interesting context-rules. So now I find myself in the situation where I could remove a few rules if I had exclusions in RELAX NG, but I'd still have others that I want to keep. I guess my current position is that if we decided to do a RELAX NG 2.0 at some point in the future, we should discuss implementing exclusions. But I wouldn't argue for doing a 2.0 for that feature any more. Be seeing you, norm [1] http://norman.walsh.name/2004/01/01/absinthe -- Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc. NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]