Was reviewing a policy, looked at it and said, that won't work. But ran
it through Simulator and it did.

Split a string into two or more nodes. But instead of storing the
result as a nodeset, store it as a string.

I would have thought you would get the concatenated values of the
nodeset's text.

So if you had split bob,john,jane then as a nodeset you get a nodeset of:

and as a string, you would get bobjohnjane and to get a particular value
you would need an XPATH of $VarName[1] or the like.

Why do you get just the first value back, when storing the split result
as a string?

PS: I was thinking an article detailing as many places that I know of,
where treating a token as a string vs a nodeset produces different
results would be interesting.