bryan wrote:
node-sets can be passed to XSLT as external objects.
Do you mean that a node-set can be passed and accessed without using a
node-set function?
To access an external object, it must be passed as argument to another
extension function.
Do you mean that the exslt node-set() is not
supported but sablotron does have a way for working with node-sets? Or
do you mean that if a node-set is passed as an external object to the
xslt then the xslt can access said node-set without an extension
function, otherwise the xslt cannot access the node-set; I know this
sounds sort of weird but it's how things work in .Net when dealing with
external node-sets being passed in, when they're passed in you can't
access them with node-set() but just access them without an extension
function, and when you build up a node-set internal to your document you
need to use node-set() - so anyway that's the reason I ask what
otherwise seems like a weird question.
For XSLT, external objects are opaque things. They can only be passed
from one custom function to another. External objects aren't a way to
replace node-set() - just a possible workaround in some cases. The
node-set() function is still in the to-do list.
Or is the "node-sets can be passed to XSLT as external objects" in
reference to "virtual xml documents" as per the xml.com article on the
same subject in Sablotron?
No, that's another storry :)
--
Petr Cimprich
Ginger Alliance
www.gingerall.com
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list