& XSLT On Saturday 21 July 2007 01:04, Richard E. Rathmann wrote:
>  > Vaclav Barta schrieb:
>  >> On Friday 20 July 2007 20:27, Birgit Kellner wrote:
>  >>> children of the element <span> that can be contained within <seg>.
>  >> seg/span/text()
>  > Yes, but that wouldn't get me the proper sequence, no?
>  > Consider:
>  > <seg>This is <span>a cold breeze</span><note>Oh, and here's some text
>  > which deals with a completely different subject-matter, say, bunny
>  > rabbits on a balcony.</note> on an unbearably hot summer evening.</seg>
>  Assuming that $seg contains a reference to the "seg" node in the example
>  above:
> 
>  my $seg_text = '';
>  for my $node ($seg->findnodes('text() | span'))
>  {
>      $seg_text .= $node->findvalue('string(.)');
>  }
> 
>  will produce "This is a cold breeze on an unbearably hot summer
>  evening."   Is this what you are trying to achieve (or at least steer
>  you in the right direction)?
> 
>  FYI, the 'text() | span' XPath expression above selects just the raw
>  text node and "span" element children of the "seg" element, skipping the
>  "note" element children (or any other child nodes, for that matter).  By
>  combining the two separate relative XPaths "text()" and "span" with an
>  or operator, findnodes() will return all the nodes in the proper
>  sequence.
I'm not saying it won't, but is it supported usage? I've looked it up 
yesterday and have been quite surprised to find in http://www.w3.org/TR/xpath 
that a nodeset is "an unordered collection of nodes without duplicates", as 
well as quite a few XML geeks pointing out that the rest of the spec pretty 
much assumes nodes in nodesets are kept in document order. Does XML::LibXML 
(that is, libxml2) guarantee order?

	Bye
		Vasek
_______________________________________________
Perl-XML mailing list
Perl-XML@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs