Subject: RE: [xsl] How do you get the non-transformed character entity out of MSXML3.0 From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx> Date: Wed, 19 Sep 2001 13:20:26 -0400 |
As an aside, what is the reasoning behind attributes not having a single text node child?
As stated in section 5.7 of the XPath 1.0 spec, "Characters inside comments, processing instructions and attribute values do not produce text nodes."
It seems to me that XPath is lacking in this case. Of those three, comments are the only ones that end up only having text within them. Attributes have an expanded name and text, and processing instructions have a 'string value' as defined by the spec, but also have what appear to be attributes (though they aren't defined as such).
I'm sure this wasn't just done randomly, but I fail to see the logic in this. Why is XPath limited by its data model, etc. to not be able to select just the text portion of these nodes? Can someone please clue me in?
Cheers, Wendell
====================================================================== Wendell Piez mailto:wapiez@xxxxxxxxxxxxxxxx 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 ======================================================================
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] [Announce] Sablotron 0.70, Petr Cimprich | Thread | [xsl] Absolute paths in document() , Adam Van Den Hoven |
Re: [xsl] Relative URLs, Wendell Piez | Date | RE: [xsl] variable as select for te, Michael Kay |
Month |