Subject: Re: [xsl] Processing IDREFS attributes From: David Carlisle <davidc@xxxxxxxxx> Date: Tue, 1 Nov 2005 22:05:41 GMT |
> that was where I was going, but I'm surprised that a function was provided > to track down IDs but not one to pull apart IDREFS, or build that tokenize > functionality into the id() function itself. It does. The attribute doesn't need to be declared IDREF: any space separated string is split up automatically: Xpath 1 says The id function selects elements by their unique ID (see [5.2.1 Unique IDs]). When the argument to id is of type node-set, then the result is the union of the result of applying id to the string-value of each of the nodes in the argument node-set. When the argument to id is of any other type, the argument is converted to a string as if by a call to the string function; the string is split into a whitespace-separated list of tokens (whitespace is any sequence of characters matching the production S); the result is a node-set containing the elements in the same document as the context node that have a unique ID equal to any of the tokens in the list. David ________________________________________________________________________ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Processing IDREFS attribu, Dan Vint | Thread | Re: [xsl] Processing IDREFS attribu, Dan Vint |
[xsl] Recursive substitution, Agnisys | Date | Re: [xsl] Processing IDREFS attribu, David Carlisle |
Month |