[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Re: Feature Request: a fail condition for
Re: Feature Request: a fail condition for
Subject: Re: Feature Request: a fail condition for <xsl:if> From: James Clark <jjc@xxxxxxxxxx> Date: Wed, 13 Jan 1999 12:00:11 +0700 |
Tyler Baker wrote: > You would not have to wrap everything in a > choose element if you did something like: > > <xsl:if test=""> > </xsl:if> > <xsl:else-if test=""> > </xsl:else-if> > <xsl:else> > </xsl:else> > > Not sure how to represent this in a DTD, You can't do it well. In the DTD you would have to allow xsl:if, xsl:else-if and xsl:else anywhere. DTDs don't work very well for expressing the structure of XSL stylesheets. What's needed is a cross between an element content model and a mixed content model, where you have the full power of an element content model, but #PCDATA is allowed, and whitespace is handled by applying a default white space handling rule of ignoring whitespace-only #PCDATA chunks. > but I think it would be more natural > to most programmers. Probably true. James XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: Feature Request: a fail conditi, Tyler Baker | Thread | Feature Request - Node Set Processi, G. Ken Holman |
Re: Comments and entities was:, James Clark | Date | Re: GOTCHA!, Oren Ben-Kiki |
Month |
Keywords