Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] Correct way to test for no match

From: Wendell Piez <wapiez@------------.--->
To: xsl-list@-----.------------.---
Date: 10/5/2009 4:56:00 PM
Dan,

At 01:48 PM 10/4/2009, you wrote:
>I've used this approach myself to help determine when a new element 
>has been added or someone starts using an element I've not seen used.
>
>In this case I was in a when clause and I was trying to capture 
>various combinations of markup errors.
>
><xsl:when 
>test="ancestor::ipb/figure/subfig/graphic[@boardno=$sht_num]/@boardno">
>
>So I was trying to understand what value this particular test would 
>return so I could trap it.
>
>In this case it was originally used like this and the function was 
>indicating an empty or null value was being returned, so I was 
>trying to match on that empty value.
>
>unparsed-entity-uri(ancestor::ipb/figure/subfig/graphic[@boardno=$sht_num]/@boardno)
>
>In this case I probably should have rearranged the when and 
>otherwise tests and matched the good value and let the otherwise 
>handled everything else. ultimately I also realized there was no 
>value in doing this elaborate matching as the result is the same as 
>the $sht_num.

Yes, exactly.

If $value is known to be 'x', then /path/to/node[@with=$value]/@with 
is always either

* 'x' (a @with node exists, and it has value 'x' by virtue of the 
'@with=$value' predicate on its parent in the path), or

* Nothing (no such node exists, has no value, coerced to '' when cast 
as a string)

That's effectively what you have with 
"ancestor::ipb/figure/subfig/graphic[@boardno=$sht_num]/@boardno".

(I leave aside the possibility that there may be multiple such nodes.)

I think you have two questions:

1. What is unparsed-entity-uri($sht_num)?
2. Is $sht_num referred to elsewhere in the document?

... and the code you are refactoring has conflated these.

This might sometimes be useful, if for example you are only 
interested in (1) if (2) is true. That is,

unparsed-entity-uri(ancestor::ipb/figure/subfig/graphic[@boardno=$sht_num]/@boardno)

will return a URI if (and only if) $sht_num appears as a @boardno on 
an ancestor::ipb/figure/subfig/graphic, and is also declared as an 
unparsed entity (with a URI not ''); otherwise it will be ''.

But you still need to keep the two questions clear in your head.

BTW, to refer to this as a "match" is somewhat confusing, since it's 
not a template match.

Cheers,
Wendell



======================================================================
Wendell Piez                            mailto:wapiez@m...
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
   Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================


--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe@l...>
--~--



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent