This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: expression value not a node set on content match
- To: xsl-list at mulberrytech dot com
- Subject: Re: expression value not a node set on content match
- From: David Carlisle <davidc at nag dot co dot uk>
- Date: Thu, 4 May 2000 18:25:54 +0100 (BST)
- References: <Pine.GSO.4.05.10005041230450.4190-100000@jet.cc.emory.edu>
- Reply-To: xsl-list at mulberrytech dot com
oops I just posted an anaysis of the expression
@code='g'
contains(text(),'21 ')
and *[ @code='x'
and contains(text(),'0141-6400')
but I notice that you in fact have
select="record[ @tag='773'/*[@code='g' ....
which certainly isn't correct but which I can't correct as I
don't know what it is supposed to mean.
@tag='773' is a boolean: it's true if the current node has an
attrbute called tag with value 773
you can't use the / operator after a boolean valued expression
only after a node set.
I _think_ you want (looking at the original post)
record[
data-field[@tag='773']
[subfield[@code='x']='0000-1234'
and
contains(subfield[@code='g']='21 ')
]
]
David
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list