[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

[xsl] RE: Implementing Conditional Text

Subject: [xsl] RE: Implementing Conditional Text
From: Michele R Combs <mrrothen@xxxxxxx>
Date: Tue, 12 Jun 2012 21:00:36 +0000

Cluttering up the XML with tons of PIs seems at least as inconvenient as
cluttering up a DTD with conditional elements.  Is there no existing
element/attribute combination, such as <span>, in the DTD that could serve
this purpose?  Alternatively, if you have control over the DTD, you could add
an element/attribute with the allowable values normal/special.

So for example:
<p>Mary had a little <span class="normal">lamb</span><span
<p>Mary had a little <text cond="normal">lamb</text><text

Then you'd just suppress either the normal or the special text, whichever you
wanted to output, when you process.  This would only require one pass, yes?
Or am I over-simplifying?


-----Original Message-----
From: Craig Sampson [mailto:Craig.Sampson@xxxxxxx]
Sent: Tuesday, June 12, 2012 4:39 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: [xsl] Implementing Conditional Text


We, our publications XML support group, are being asked to support conditional
text in our source documents.

We've come up with an idea but before going any further I thought I'd run it
by this group to see if anyone had done this before or if anyone had a better

We plan to use processing-instructions (PIs) entered by the authors that would
indicate which conditions were on or off. These PIs would be inserted near the
top of the documents. There would be additional PIs identifying the beginning
and end of conditional text strings. We would use a XSL transform to
preprocess these documents and convert the PIs into pseudo elements that could
then be processed in a second XSLT preprocessor would keep or discard the
strings based on the conditions set in the PIs at the top of the document. The
resulting document would not have any of the PIs or pseudo elements just the
content that was kept.

We want to use PIs so we don't have to dirty up our DTD with conditional
elements that would be allowed everywhere. I can't think of any way to
eliminate the conversion to pseudo elements which solves the problem of
identifying and controlling the conditional text.

We are not allowing the conditional text to break existing element boundaries
or to be nested within other conditions so the following example should
represent what we're trying to do:

<p>Mary had a little <?condStart normal:true?>lamb<?condStop
normal:true?><?condStart special:true?>pony<?condStop special:true?>...</p>

In the example if the PIs at the top of the document set "normal" to "true"
and  "special" to "false" then Mary had a little lamb. If both conditions are
set to true then Mary will have both the lamb and the pony.

Can anyone poke holes in this solution or suggest a better way to accomplish

Craig R. Sampson    SAS Institute Inc.  email: craig.sampson@xxxxxxx
  XML Technologies  SAS Campus Drive    phone: (919) 531-7417
                    Cary, NC.  27513    FAX:   (919) 677-4444
     Please consider the environment before printing this email

Current Thread